Skip to content

Latest commit

 

History

History
154 lines (97 loc) · 7.73 KB

Product Description.md

File metadata and controls

154 lines (97 loc) · 7.73 KB

Immuni's Product Description

Table of contents

Context

This document describes the features and user flows made available by the Immuni app. It assumes that you have already read the High-Level Description.

Each section covers a specific part of the app. Features are described from the user’s point of view, using sentences in the first-person voice. When required, more details on how the app delivers that particular feature are provided as sub-points. Note that this document does not attempt to define the specific details of the user experience or of the user interface. However, both are designed following the requirements laid out below.

In most of the cases, screenshots demonstrate how features are displayed on screen, based on the latest design of the app’s user interface.

Initialisation

Language detection

I use the app in my preferred system language. If the app does not offer that language, it defaults to British English.

  • The app is available in Italian, German, and British English.
  • If the app detects a match between the user’s language preferences and one of the available languages, the app uses that language.
  • If no such match is found, British English is used as the default.

Required update

I am notified if my version of iOS or Google Play Services does not support the Apple and Google Exposure Notifications framework. I am given the most straightforward way to update it, if necessary.

  • Immediately upon being opened, if the app detects that an iOS or Google Play Services update is needed, a non-dismissible screen appears, inviting the user to perform the update.
  • As soon as the user returns to the app after the update is complete, the screen disappears.

I am notified if I need to update the app. If that is the case, I am given the most straightforward way to do so.

  • The app fetches the indication of the minimum version the server supports on a regular basis.
  • If the version of the app is prior to the minimum version supported, when opening the app a non-dismissible screen informs the user that they need to download the latest version.
  • As soon as the user returns to the app after the update, that screen is no longer shown.

Required Update

Onboarding

Welcome

I receive a brief explanation of why the app is useful and how it works.

  • The app explains its benefits for both the individual user and the wider community.
  • The app explains how it works, with a simplified description of the exchange of rolling proximity identifiers via Bluetooth and match detection.
  • The app explains how privacy is preserved for all parties involved: Immuni does not know the identity of the user or of the people with whom the user comes into contact.

Welcome
How It Works

Privacy

I am informed of what data the app processes and, more generally, how my privacy is protected.

  • The app lists data that it does not collect or process at all (e.g., geolocation, user identity, and contact information).
  • The app describes some of the ways it protects the user’s privacy (e.g., by encrypting data and server connections).
  • The app lists data that it collects and shares, and for what purposes it does so.

I read the app’s Privacy Notice and accept the Terms of Service, and I confirm that I am at least 14 years old.

  • The app provides links to access both its Privacy Notice and Terms of Service.
  • Confirmation of being 14 or older and accepting both Privacy Notice and Terms of Service is required to continue.

Province selection

I state the province in which I live, with full awareness of for what purpose this information is used.

  • The app shows a screen that allows the user to select from a list the region in which they live.
  • Based on the region the user chooses, the app shows a screen that allows the user to select the province in which they live.
  • The screen explains that the province is used to provide location-specific guidance, where required.

Province Selection

Permissions

I provide all the permissions and I activate the device services required for the app to work correctly.

  • The app asks for the user’s permission to use the Apple and Google Exposure Notifications framework.
  • If Bluetooth is inactive, the app notifies the user that it cannot work and provides simple instructions on how to reactivate it.
  • The app asks for the user’s permission to send them push notifications.

Permissions

Home

App status

I check if the app works as intended and, if that is not the case, I easily take action to restore its correct behaviour.

  • In the Home screen, a card informs the user if everything works correctly.
  • If the user withdrew any permission or disabled services that are necessary for the app to operate, the app displays a card informing them that the app is not working correctly. The card also provides guidance for the user to fix every issue detected, in a fashion similar to that which takes place during the onboarding process.

App Status

Exposure notification and suggestions

I can receive generic advice on what to do to protect myself from the spread of COVID-19.

I am notified if I am at risk due to recent contact with a SARS-CoV-2 positive user, and I receive advice on what to do.

  • The advice varies depending on the nature of the exposure and the province in which the user lives.
  • If required, the app advises the user to get in touch with the National Healthcare Service (Servizio Sanitario Nazionale) and provides them with methods of doing so.

Exposure Notification and Suggestions

Settings

I can access the app’s Privacy Notice and Terms of Service.

I can contact Customer Support to solve issues I am experiencing with the app or to clarify any doubts I have about it.

  • The app shows the app’s version number to help with troubleshooting.

I can change the province where I live, if necessary.

Settings

Data upload

I can upload my data when the outcome of a SARS-CoV-2 test is available and positive, with the guidance of a health operator.

  • The health operator asks the user to tap ‘Data upload’ in the ‘Settings’ tab.
  • The app shows a random, temporary 10-character alphanumeric code to the user.
  • The user dictates the 10-character code to the health operator, who inserts it into a web interface.
  • Upon the health operator’s request, the user taps ‘Verify’ to verify the code and proceed to the next step.
  • The app shows an explanation of what data is about to be uploaded and why.
  • When the user taps ‘Upload data’, the app uploads all the previously described data.
  • Finally, the app shows a confirmation message saying that the upload was successful.

Data Upload

FAQ

I can receive comprehensive answers to common questions that I may have about the app.

  • Upon tapping ‘Frequently asked questions’, the user is provided with a list of questions.
  • Questions are prioritised so that the app can ensure the most pressing and common ones are presented first.
  • If the user taps any of them, a separate screen will open to reveal the answer to that question.