Q4 Mobile: D2 Retention and Polish

[daniellekirkwood]

Quick Links

• Onboarding target state prototype (TBA)
• Project board
• All Papercut D2 issues
• Mobile Office Hours document

Overview

• We want to reduce the confusion and increase the value we provide in the first 2 days of using the iOS and Android apps.
• We want to reduce the number of WTFs uttered when first using our products.
• We will prioritse issues and measure the impact of our changes using D2 retention metrics.

Problem

Our first time user experience (FTUE) does not set users up for success, or show the value of our products. We want our FTUE to be familiar, while also introducting Element effectively in order to deepen understanding of who we are and what we do.

Understand where in the journey users feel pain today. From first impression through first tasks.

• First impressions: From the App or Play store through end of first session
• First tasks: The first time a user completes an Element Mobile Tasks

Goals

• Close commited Z-Papercut issues (link TBA)
• Review FTUE paths & compare against landscape for friction and competition
• Define Target State onboarding for mobile
  • Unite the experiences across apps. Today the Android and iOS experiences are vatly different
• Deliver significant improvements to signup and onboarding flows
  • [App Board Epic] Build a new onboarding experience element-ios#5151
  • [App Board Epic] Build a new onboarding experience  element-android#4586

Onboarding Design Principles

• Add moments of education along the way to introduce ourselves effectively
• Make a good first impression with personality to introduce meaningful delight
• Use progressive disclosure to build confidence with slow-ball questions (familiarity & feedback)

What are Papercut issues

Papercut issues are small bugs or inconsistencies that users encounter that erode trust and confidence in our products. These are expecially impactful during a user's first few days with us.

• Link to all D2 mobile papercut issues

"Target State papercut issues" are tasks that can be completed within a few days and lead us closer to the target state of FTUE.

• Link to D2 mobile papercut issues tagged as FTUE (link TBA)

Assumptions

• Users who complete tasks are stickier

Other Requirements

• Ask for permission to track events for analytics
• Ask for access to contacts
• Ask for notifications permissions
• https://github.com/vector-im/internal-planning/issues/148

Tasks & Timeline

Sprint 1 - October 19 - November 1

Release date: October 25

• Eng: DevX Sprint & Other tech focussed issues
• Replace Matomo by PostHog element-ios#5035
• Sort SSO providers by relevance element-android#4277
• Design: User research brief: Round 1
• UserTesting sessions for FTUE. element-android#4321
• UserTesting notes
• Design: UserTesting Synthesis & shareout with team
• Design: PostHog

Other:

• Android Community Testing (link TBA)

Sprint 2 - November 2 - November 15

RC date: November 3 | Release date: Nobvember 8

• Design: Prepare screens for Target State Papercut issues (date)
• Design: Develop prototype for internal use & ciculate for feedback (date)
• Eng: Android PostHog
• ...

Papercut issues:

• Target State:
• Other:

Sprint 2 - November 16 - November 29

RC date: November 17 | Release date: Nobvember 22

• ...
• ...
• ...

Papercut issues:

• Target State:
• Other:

Sprint 2 - November 30 - December 13

RC date: | Release date:

• ...
• ...
• ...

Papercut issues:

• Target State:
• Other:

Sprint 2 - December 14 - December 27

RC date: | Release date:

• ...
• ...
• ...

Papercut issues:

• Target State:
• Other:

Sprint 2 - December 28 - January 10

RC date: | Release date:

• ...
• ...
• ...

Papercut issues:

• Target State:
• Other:

[daniellekirkwood]

Feedback from Android Community Testing on October 20, 2021

• After clicking on get started, it might not be obvious for newbies what they should do: the request for selecting a server is very prominent while the log in is very 'opaque' and people could be unsure how they should act given they have an account
• On the initial screen, it assumes I don't have an account and first login option is my MXID only. Need to go through the register flow to get to other signin options
• Try to send a DM, click contact book, select contact, select create, can't send message due to identity server not being configured
• There is no way to use the phone number associated to the account to sign in
• When starting a DM; After finding a user, the view is confusing
• Add people to the room as part of the create room flow?
• I should not have to type @ to log in
• When trying to log in, the google logo looks bad
• Add Leave button to overflow menu in a Room/DM

[daniellekirkwood]

This issue is out of date and no longer representative of the work ongoing. I will close this issue and create a new one for accuracy (&ease)