Initial page displayed after application is started.

(TBD - splash state of welcome, where generic loading will be performed - SDK initialization, icon assets download, etc)

UML flows

Scenarios

  1. app is started and checks if user session is present and whether customerId is persisted on device

  2. If found, customer data are loaded from CM and we navigate user to:

    1. Dashboard (for customer that is onboarded)

    2. Onboarding (for customer that has not finished onboarding)

    3. Passcode input page (when customerId present, but needs to be authentiated) FE - passcode input page

    4. TBD - other states (offboarded, rejected, etc)

  3. If not found user remains on welcome page

  4. User can change localization of application using dropdown in appbar (options are fixed in app code)

  5. User can interact with action buttons:

    1. Get started - triggers onboarding flow (starts with privacy policy) FE: privacy policy page

    2. Sign in - triggers login flow (starts with phone input) - FE - phone input page

Back action - exits application without any confirmation prompt

Elements

Tag

Description

Data

1

App logo

SafiAppBar with logo (color override)

2

Localization dropdown

TBD

3

Promo images

Image paths
1 - app/images/onboarding_secure.png

2 - app/images/onboarding_3.png

3 - app/images/onboarding_8.png

4 - app/images/onboarding_1.png

5 - app/images/onboarding_9.png

4

Promo titles

Localization keys
1 - login.welcome.text.page1

2 - login.welcome.text.page2

3 - login.welcome.text.page3

4 - login.welcome.text.page4

5 - login.welcome.text.page5

5

Onboarding action button

Localization key - login.welcome.text.onboardingStart

Action - starts onboarding flow (navigates to privacy policy page)

6

Sign in (login) action button

Localization keys - login.welcome.text.loginStart.prefix , login.welcome.text.loginStart.action

Action - starts login flow (navigates to phone input page)

Attachments: