Mobile FTUE: Measuring success and Analytics

[daniellekirkwood]

Measuring Success

Our primary goal is to reduce the number of WTFs in the first session, and in turn increase D1 retention.

D1 retention overtime

---

February 15, 2022 : 48.4% (iOS) & 55.7% (Android)

---

What we know...
We see users struggle with onboarding in Android and yet their D1 retention is higher than those on iOS. iOS users breeze through FTUE and their retention is 7% lower.
Our hypothesis: A little friction during sign up and first tasks encourages determination.
We see the drop off between D1 and D7 retention is slightly higher on Android than on iOS.
Our hypothesis: Too much friction leads to abandonment.

How will we know we're winning?

• D1 retention is going up
• Issues reported by those completing UserTesting sessions go down

How will we know when we're done?
The bounds of this project are defined as:

• Delivered FTUE flow as designed here
• Made meaningful impact to the identified 'first tasks'

Analytics tracking

• Use case screen: We should track the responses to the use case screen so that we can create cohorts in the data and learn how different user groups use the app in their first few days. This also means that we should track the main actions in the app

Issues

• Mobile FTUE: Add Analytics tracking for Notifications (iOS) element-ios#5164
• FTUE: Analytics tracking element-android#5285
• FTUE: Analytics tracking element-ios#5656
• Track "Signup" event on Posthog element-ios#6074

[daniellekirkwood]

element-hq/element-ios#5164 has been removed from the definition of done for this issue, so we're closing it.