Mobile FTUE (Epic)

[daniellekirkwood]

Project Board

As part of the WTF initiative to improve our app and increase it's quality, we are focussing on the D1 metric. We believe that by improving user onboarding we will drastically improve the D1 metric, quality, and usability of Element.

Go to the parent issue and WTF epic

Outputs are in 2 categories: First Impressions & First Tasks.

UserTesting on the mobile apps revealed that the current Onboarding flow gives users very little personality, education, or value from the app. It also lands users on the homepage with minimal investment and maximum confusion: “What do I do now?”

First impressions

An improved onboarding experience \(FTUE\) will provide the missing components to new users. We believe by better guiding users through the sign up and sign in flow we accurately set expectations, increase value, and encourage commitment.

First tasks

Using WTFs and Papercuts to improve the onboarding experience after sign up. Taking users from the first visit to the homepage right through creating their own Room, DM, etc. There are a number of first tasks that require improvements, cross referencing WTFs & Papercuts with D1 & R30 metrics will enable us to prioritise those with highest impact

First Impressions:

Figma

• Build Splash screens
• Build Use case screens
• Mobile FTUE: Choose a server (Meta) #126
• Mobile FTUE: Connect to a server #127
• Mobile FTUE: Create an Account (meta) #128
• Mobile FTUE: Email collect & Verify (meta) #129
• Mobile FTUE: Privacy policy and Captcha (meta) #130
• Mobile FTUE: Celebration screens (meta) #131
• Mobile FTUE: Profile Personalisation screens (meta) #132
• Mobile FTUE: Popups and permissions (meta) #133
• Mobile FTUE: Sign in flow (Meta) #134
• Mobile FTUE: Password recovery (meta) #135
• Mobile FTUE: Measuring success and Analytics #136

First Impressions Issue Tracking

Issue	Android	iOS
The Epic Build a new onboarding experience #146	element-hq/element-android#4586	element-hq/element-ios#5151
Build FTUE Splash screens	element-hq/element-android#4584	element-hq/element-ios#5159
Build FTUE Use Case screen	element-hq/element-android#4585	element-hq/element-ios#5160
Build FTUE: Choose Server screen #126	element-hq/element-android#2396	element-hq/element-ios#5161
Build FTUE: Create Account screen #128	element-hq/element-android#5277	element-hq/element-ios#5648
Build FTUE: Email collect & verify screens #129	element-hq/element-android#5278	element-hq/element-ios#5649
Build FTUE: Privacy policy & Captcha screens #130	element-hq/element-android#5279	element-hq/element-ios#5650
Build FTUE: Celebration screens \(x2\) #131	element-hq/element-android#5280	element-hq/element-ios#5651
Build FTUE: Profile personalisation screens #132	https://github.com/vector-im/element-android/issues/5281	element-hq/element-ios#5652
Build FTUE: Permissions & Pop ups #133	element-hq/element-android#5282	element-hq/element-ios#5653
Error states: TBD	Case-by-case	Case-by-case
Sign in flow #134	element-hq/element-android#5283	element-hq/element-ios#5654
Password recovery #135	element-hq/element-android#5284	element-hq/element-ios#5655
Add Analytics tracking for Notifications on/off #136	N/A. Android does not need to ask for Notification permission.	element-hq/element-ios#5164
Measuring success and analytics #136	element-hq/element-android#5285	element-hq/element-ios#5656
Automated testing...	Ask Engineering	Ask Engineering
First tasks: Definition #171	--	--

 

First Tasks:

• FTUE: First Tasks #171
• New Direct Messages screen is inconsistent between the different platforms #83

[daniellekirkwood]

How this issue works...

• There's a parent WTF issue (link)
• Each task in this Epic has a Meta issue where discussions are captured and decisions are made.
• Each Meta task has a Platform specific issue in order to track the work on our project board and know the stage of each platform at any given time. iOS is here and Android is here
• Each App board has an Epic to represent the work Sprint to Sprint: iOS Android

[daniellekirkwood]

How delivery will work

• There are 3 phases: 2 Bookends (Start & End), and The Middle.

Bookend:Start	Bookend: End	The Middle
Build Splash screens Build Use case screens	#126 #127 #128 #129 #130 #133 #134 #135	#131 #132

We will not ship Bookend: End without also shipping The Middle

At every stage:

• Mobile FTUE: Measuring success and Analytics #136

[daniellekirkwood]

First tasks was removed from the DoD for this project, therefore I'm closing this issue as done.