Product design, strategy, & leadership
Wellframe-Sign-Up-Cover.png

Wellframe: Mobile app sign-up

Increasing member conversion rates within an aggressive set of constraints.
Product Design (iOS, Android)

Project details

sign-up-feature-graphic.png

Discovery

Comparative analysis

I looked at apps with similarly complex signup flows that require lots of highly specific information for identity verifaction.

The Robinhood investing app, one of the north stars I examined at length. I liked their focus on low cognitive load, by only having the user fill out one field at a time.

The Robinhood investing app, one of the north stars I examined at length. I liked their focus on low cognitive load, by only having the user fill out one field at a time.

Wealthsimple, another financial app that I looked at for inspiration. I liked the progress bar and the “Let’s get you set up” screen (bottom left) to give context for all the information that they would be asking for next.

Wealthsimple, another financial app that I looked at for inspiration. I liked the progress bar and the “Let’s get you set up” screen (bottom left) to give context for all the information that they would be asking for next.

Technical discovery

User flow diagram of the all the possible sign-up variations

User flow diagram of the all the possible sign-up variations

Whiteboarding the sign-up flow and where it hits the API endpoints

Whiteboarding the sign-up flow and where it hits the API endpoints

 

Wireframing & early prototyping

Early-stage sketches

Early-stage sketches

First-pass wireframes

First-pass wireframes

 

Design + engineering workshop

There was a disconnect between what I had learned in my discovery and what the mobile development team knew about the code for the signup flows: how it worked currently and what I proposed changing. To get the entire team on the same page (including our newly hired PM), I facilitated creating an artifact to share my knowledge, in a collaborative way: I led a series of design workshops to construct a “blueprint” of the onboarding paths. Our first session was very simple—we merely plotted out the screens from my prototype and indicated where each API call was made. Over time as we considered each idea and made decisions about what to change, we added those details to our blueprint. 

Our entire blueprint for the sign-up experience, including flags for screen taxonomy, event logging naming conventions, API calls, components, expected behaviors, error states, field validation, image assets, navigational model notes, and more.

Our entire blueprint for the sign-up experience, including flags for screen taxonomy, event logging naming conventions, API calls, components, expected behaviors, error states, field validation, image assets, navigational model notes, and more.

sign-up-blueprint-zoom.jpg

Color-coordinated post-it notes overlay several types of information—everything from the form fields on each screen (including what entries should trigger errors, and what validation each should have), to naming conventions for the screens to be used in tagging for event-logging data.

 

Visual design

Illustration mood board and the resultant illustration components

Illustration mood board and the resultant illustration components

sign-up-progress-bar-animation.gif
Top: Defining animations for screen transitions;  Bottom: defining micro-interactions for text fields

Top: Defining animations for screen transitions;
Bottom: defining micro-interactions for text fields

New visual design language and component based design framework that resulted from the flow redesign

New visual design language and component based design framework that resulted from the flow redesign

sign-up-visual-design.png

Selection of screens in final design style

 

Content design

Defining content strategy throughout one variation of the user experience

Defining content strategy throughout one variation of the user experience

Writing error states and dialogs

Writing error states and dialogs

Documenting content for development, so we could more easily update rather than relying on mockups to have the exact final copy

Documenting content for development, so we could more easily update rather than relying on mockups to have the exact final copy

 

Solution

The final solution for this project is a bold statement about the direction that Wellframe’s mobile app design is moving. With a new, crisp visual design language, a refined content strategy and tone of voice, and lower cognitive load per screen in this complicated flow, Wellframe is poised to make a great first impression on new users. The new sign-up flow provides a smooth user experience that introduces Wellframe’s brand and conveys their value prop in a simple, accessible, and friendly format.

Recording of live product

Start screen

Error message

Access code screen

Inline error

Loading/checking screen

Step completion confirmation