Use Case 1.2 Open the app

Overview

Aspect	Description
Summary	The user opens the app manually or follows a universal link. The system checks the app version is valid, or forces the user to update. When valid, the system redirects to app introduction or app unlock.
Goal	Opening the app.
Preconditions	App is installed App version is allowed
Postconditions	None
Triggered by	User launches or resumes the app manually. User launches or resumes the app by following a universal link.
Additional Documentation	App Startup iOS App Activations Android App startup time
Possible errors	Device Insecure
Logical test cases	LTC42 Open closed app LTC43 Open app via universal link LTC54 Wallet not created when universal link is invoked

Flow

#	Description	Next
1	PRIMARY SCENARIO
1.1	System determines app startup state
1.1a	Case: App launches (iOS) or starts cold or warm (Android)¹	2
1.1b	Case: App resumes (iOS) or starts hot (Android)²	3
2	WHEN APP LAUNCHES
2.1	System displays screen ‘Splash screen’
2.1a	Event: 1 second passes	2.2
2.2	System determines whether app is rooted
2.2a	Case: Device is not rooted	3.2
2.2b	Case: Device is rooted	Error flow: Device Insecure
2.3	System executes partial flow PF1.4 Apply update policy
2.3a	Result: App version is allowed	2.3
2.4	System determines whether remote PIN is set up
2.4a	Case: User has setup a remote PIN	Go to: UC2.3 Unlock the app
2.4b	Case: User has not setup a remote PIN	Go to: UC1.1 Introduce the app
3	WHEN APP RESUMES
3.1	System determines whether remote PIN is set up
3.1a	Case: User has setup a remote PIN	3.2
3.1b	Case: User has not setup a remote PIN	Resume³
3.2	System determines whether app is locked
3.2a	Case: Wallet is unlocked	3.3
3.2b	Case: Wallet is locked	Go to: UC2.3 Unlock the app
3.3	System determines whether user has obtained PID
3.3a	Case: User has obtained PID	3.4
3.3a	Case: User has not obtained PID	Resume³
3.4	System executes partial flow PF2.7 Resolve a universal link
3.4a	Result: No (valid) universal link	Resume³

1. We use the iOS terminology 'launch' to that no process was active when opening the app. In Android, this matches the 'cold startup' or 'warm startup' processes. Even without an active process, some resources may already be loaded into memory.

2. We use the iOS terminology 'resume' to that the app process was already active when opening the app. In Android, this matches the 'hot startup' process.

3. Resume the state when the app backgrounded/suspended.