Application UI can be improved so as to help disabled users to read easily the textual content of the app. Thus dynamic fonts must be used so as to allow the system to rescale the app, thing not possible today.

• [x] Use system fonts everywhere
• [x] Test with very small font size (with "higher font size" a11y enabled in the device)
• [x] Test with very big font size (with "higher font size" a11y enabled in the device)
• [x] Test withs several font sizes, without a11y option enabled

Add a Settings view, with a ⚙️ icon to open it next to the logo on the Home view.

This Settings screen should contain:

• Links: FAQ/VaccinTracker/...
• An additional link to open the contributors view (See #122)
• Options to contact us and/or report a bug
• UI Settings: app theme (system/light/dark) and accessibility

To be more compliant with FLOSS principles, and also thanks developers of third-party components used in this project, the list of such components can be made in the app level and the repository level.

• [x] Add a folder "licenses" listing licenses of components used in the project
• [x] Add in Settings.bundle of the app a generated lit of components in use

Description

Provide as described in issue #47 a setting screen for the application. User can tap on a gear icon to go to settings screen. This new view displays items about the official web site, contact form, Twitter profile, source code page an has also a link to make the user go to system app settings. Thus, once merge request #114 will be merged, users will be able to see all third party elements from there in one tap. Issue #37 can also be integrated at this level with its own cell (see #122).

Changes

• Gear icon from home screen
• Settings screen based on UITableView with cells
• Cell for web site
• Cell for contact form
• Cell for Twitter
• Cell for source code (GitHub)
• Cell for app settings
• VoiceOver vocalization (a11y)
• Dynamic fonts (a11y)

Related issue

Fixes #47

What I tested

For a11y, used my own device with VoiceOver enabled and large text sizes. Otherwise use the same device for navigation. See screen shots below.

Regression risks

• None

Screenshots

Checklist

• [x] I have installed SwiftLint and made sure code formatting is correct
• [x] I have performed a self-review of my own code
• [x] I tested my changes on real device
• [x] My changes generate no new warnings
• [x] I have commented my code in hard-to-understand areas
• [x] Any dependent changes have been merged into develop
• [x] I have checked there aren't other open Pull Requests for the same update/change

Here is a list of items to enrich for Voice Over:

• [x] Search field in home screen
• [x] Result of searches
• [x] Numbers
• [x] Navigation and action elements such as back button, phone and booking butons, map cell
• [x] Details of a center
• [x] Hours

Description

Implementation of 3rd shot in the app.

Changes / Definition of done

• [x] Remove any objects related to Chronodose (configuration, UI, wording)
• [x] Update business objects to manage daily slots
• [x] Update API to request for daily slots
• [x] Requests for data
• [x] Filter available slots by day (total is always displayed, or nothing)
• [x] Implement filtering to get vaccination centers with 3rd shot
• [x] Update GUI to display vaccination centers with 3rd shot
• [x] Make review of a11y (Voice Over, dynamic fonts)
• [x] Add SPDX headers in source files
• [x] Remove objects related to "appointment_schedules"? Seems not used anymore.
• [x] If no slots available, say it or don't display (cf. web front)

Related issue

Link to the Github issue #142 Link to the Github issue #150

What I tested

• Display of booster shot in UI
• Compared results with web front

Regression risks

Nothing identified

Screenshots

|Before|After| |-|-| | | |

Checklist

• [x] I have installed SwiftLint and made sure code formatting is correct
• [x] I have performed a self-review of my own code
• [x] I tested my changes on real device
• [x] My changes generate no new warnings
• [x] I have commented my code in hard-to-understand areas
• [x] Any dependent changes have been merged into develop
• [x] I have checked there aren't other open Pull Requests for the same update/change

As a user, when I change my device accessibility setting to increase or lower the font sizes, I want to have the app font size changed, so that I can easily read the content of the app.

Description

I'm adding a view to show contributors, based on the backend contributors endpoint

Related issue

Fixes #37

What I tested

The view itself

Regression risks

N/A

Screenshots

If applicable, add screenshots to help explain the fix. Otherwise please remove this section

Checklist

• [x] I have installed SwiftLint and made sure code formatting is correct
• [x] I have performed a self-review of my own code
• [x] I tested my changes on real device
• [x] My changes generate no new warnings
• [x] I have commented my code in hard-to-understand areas
• [x] Any dependent changes have been merged into develop
• [x] I have checked there aren't other open Pull Requests for the same update/change

Description

Allow to filter vaccinations centers list for "kids shot". Allow also users to filter centers by vaccine types.

Changes

• [x] Update view model / business objects to deal with new tags
• [x] Add filter buttons (do not forget a11y)
• [x] Display on filter button tap a sheet with filter options (kid shots / all / vaccines types)
• [x] Filter in segmented control list the data
• [x] What news in app (view at start)

Related issue

Link to the Github #162 issue Link to the Github #154 issue

What I tested

• Tested vocalization with VocieOver of bottom sheet
• Tested with big cities like Toulouse and Paris, and smaller ones like Caen and Blois
• Tested with departments like Ain

and compared results with in-production web app.

Tested also on simulator (iPhone SE 2nd generation with IOS 13) and real device (iPhone 12 Pro with iOS 15).

Regression risks

Not found (yet).

Screenshots

Checklist

• [x] I have installed SwiftLint and made sure code formatting is correct
• [x] I have performed a self-review of my own code
• [x] I tested my changes on real device
• [x] My changes generate no new warnings
• [x] I have commented my code in hard-to-understand areas
• [x] Any dependent changes have been merged into develop
• [x] I have checked there aren't other open Pull Requests for the same update/change

Description

Adding Valwin logo Fixed Bimedoc logo not displaying

Changes / Definition of done

• [x] Added logo in footer
• [x] Little fix on bimedoc logo
• [x] Check logo size in search section

Related issue

Link to the Github issue

What I tested

• Footer View
• Search View

Regression risks

None

Screenshots

Footer |Before|After| |-|-| | | |

Search |After| |-| | |

Checklist

• [x] I have installed SwiftLint and made sure code formatting is correct
• [x] I have performed a self-review of my own code
• [x] I tested my changes on real device
• [x] My changes generate no new warnings
• [x] I have checked there aren't other open Pull Requests for the same update/change

Why

We should list somewhere in the application the list of dependencies in use inside this iOS app. Thus depending to the component, the project will be more compliant. Moreover, listing dependencies is clear fo users and cool for developers behind these tools.

How

One tool can be used: [LicensePlist)(https://github.com/mono0926/LicensePlist). It will dive in the Xcode project magic files, and produce a global file will all direct and indirect third-party components. Then the output should be place in the Settings.bundle of the project.

First, according to the tool README, install in your local environment the tool:

brew install mono0926/license-plist/license-plist

Then run the tool:

license-plist

A folder with PLIST for each component will be generated (com.mono0926.LicensePlist), and also an index file (com.mono0926.LicensePlist.plist). These elements can be placed in the Settings.bundle folder.

A run script build phase can be added so as to update the items.

In addition, the tools we directly use in the project, i.e. referenced in our level through CocoaPods and Swift Package Manager can be listed in the repository.

Is your feature request related to a problem? Please describe. Backend had some issues today where some endpoints wouldn't load. This made us realise that if the Stats endpoint we use on the home page is down, the whole app is unusable (blocked by an error popup).

Describe the solution you'd like We should handle the Stats endpoint errors better on the home page to make sure the rest of the app can be used if it's down.

Describe alternatives you've considered N/A

Additional context N/A

Is your feature request related to a problem? Please describe.

As we can see in the in-dev web front, there is a calendar to display the available slots to get shots. The UX is better, and we should have something similar in the iOS front. The calendar will be, or is already, available on Android and web platforms.

Describe the solution you'd like

See Android et web fronts to have an idea of what could be the calendar. A big refactoring of the UI (cells, delegate, view controllers, xib) should be done, that is the reason why we should deal all previous pull requests before.

Describe alternatives you've considered

Nope

Additional context

Nope

We are going tol add a new platform on back-end, can you please add the support for it?

"plateforme": "Clikodoc"

https://www.clikodoc.com/images/home/logo_header_v1.png

A different way to handle the issue #76. Because it is preferable to stick with SFSafariWebView instead of opening Safari. Cc @NathanFallet.

UIApplication.shared.open(url, options: [.universalLinksOnly: true]) { (success) in
    if !success {
        // not a universal link or app not installed, opening in Safari Web View instead
        let safariViewController = SFSafariViewController(url: url, configuration: config) 
        safariViewController.present(vc, animated: true)
    }
}

Source: https://recoursive.com/2019/02/22/preflight_universal_links/