FTUE - Update sign up steps ordering

[ouchadam]

The ideal ordering is

• Create account
• Enter and verify email
• Privacy policy / T&Cs
• Captcha

[bmarty]

Sorry, I am late in the party, but I think that the client should follow the order provided by the server.

So what is required to fix this issue is a server configuration change IMO

[ouchadam]

cc @daniellekirkwood

For extra context, with this issue merged, the app will respect the server order for the legacy middle section flow and override the order for our new flow (based on the combined register feature flag)

[bmarty]

And as a user, I think the most expected order will be

• Create account
• Captcha (to filter out bot first, and not annoy the user with this boring step just before the end)
• Privacy policy / T&Cs (because if the user does not agree, there is no need to ask for their email first. Also the T&C can explain what we will do with their email, so they have to be accepted first)
• Enter and verify email

[daniellekirkwood]

@bmarty - we put a lot of thought into the ordering of the screens and how the 'story' plays out for the user during signup. Happy to discuss further.

For extra context, with this issue merged, the app will respect the server order for the legacy middle section flow and override the order for our new flow (based on the combined register feature flag)

Thanks, @ouchadam. Let me play this back to make sure I'm following -
If the user's server choice enforces an alternative ordering of these screens then the new flow will honour that? What is the ordering of matrix.org?

[bmarty]

(OK, just cannot resist to add my 2 cents: I keep thinking that asking for Captcha at the end, user will see a WTF like: "wait, I have already provided my email and clicked on the link it contains, so of course I am not a robot!")

Current order on matrix.org is:

    "flows": [
        {
            "stages": [
                "m.login.recaptcha",
                "m.login.terms",
                "m.login.email.identity"
            ]
        }
    ],

And the app is following this order at the moment.

[ouchadam]

Thanks, @ouchadam. Let me play this back to make sure I'm following - If the user's server choice enforces an alternative ordering of these screens then the new flow will honour that? What is the ordering of matrix.org?

I'm afraid it's the opposite, the legacy flow respects the server order whereas the new FTUE flow manually overrides it. It's worth noting that iOS has been manually overriding the server flow in their current (non FTUE) implementation as they show the email verification first

[daniellekirkwood]

Thanks both for your input!

@bmarty you raise a great point - there are also other screens that different servers may require, right?

• captcha
• Ts&Cs (and other documents)
• email verification
• phone verification

Is anything missing from this list?

I'll assign this to Amsha and we will discuss with her when she's back :)

[daniellekirkwood]

Decision made

We will force Matrix.org into the order that we have confidence is the best for our users (putting the potentially blocking info up front)

The flow will respect the order that other servers request.

👀 @amshakal @ouchadam @bmarty