Wander Sign In / Up Flow Challenge
When initially approaching the sign in and sign up flows I thought it would be similar to sign up flows I’ve approached before. However, there was a key element to their pre-beta sign-up that made a unique solution necessary.
For the past few months, you could sign up to be notified when Wander launches, but also reserve your Wander name. In this process only a username and email were captured, but no password. This is great for lowering the conversion barrier and having a friendly way to capture user emails, but produces another use case to account for when launching.
The effect of this key anomaly is that at the time Wander Weeks is released (and any time thereafter) we could have 3 types of users:
We needed a way for all 3 user types (when I say “user types” here I am only referring where they are in authentication and not personas) to enter Wander, and handle the odd case of the user who has entered their email, but not yet provided a password. The one variable that all users need to or have already entered is their email. So, the solution is to first have the user enter their email. This essentially acts as a key to tell us which door to open next. Once we determine if the email is known or unknown to us, we then know how much information we already have from the user, and therefore know which fields to populate next. (enter password you have already defined, or enter a new password for the first time). Another benefit to this flow is that we do not have to bring the user out of the experience and to their email to confirm, resulting in a lower drop-off rate. For the few to none cases where users attempt to enter another user’s email before they have defined a password (see 50% user type), we allow the user to reset their password and confirm any changed passwords via email or contact us directly to monitor what happened.
Stay tuned for the full Wander release. It’s an exceptional team and I’ve had a lot of fun working with them.