Oops!

SmartHQ Sign Up Redesign

Helped audit and redesign elements of the sign up flow for SmartHQ, the smart home appliance app for GE Appliances.

For this project I worked with the UX Team to analyze the existing user sign up flow and propose changes to the flow to help users find more clarity in the information presented and to have a better understanding of reasons to input personal information

My Role : Flow Auditing & Redesign

Collaborators : Developers and UX Team

Entrypoint Excellence

Redesigned the sign up experience on the SmartHQ mobile application for GE Appliances. SmartHQ is the consumer facing mobile app with which users can control various home appliances.

For this project, the focus of the redesign was mainly around the sign up process and looking into steps to help streamline and better present certain information to the users in their sign up journey.

Initial Audit Flow

The request was to look into the sign in flow for the SmartHQ App and to identify key issues that users would face. This request was put forth as a measure to improve the experience of using the app and to improve user ratings on the App Store.

The first step in identifying the issues was to conduct an audit of the existing process. The existing sign up flow was mapped into key blocks and these were investigated. From the audit, the basic flow was mapped out, the user would be presented with a sign up call to action (CTA) and once they click on it they will be asked to input their email and country as the basc information. This information was required to create an account. The next step was to setup a password, then input the users personal data. The users then had to verify their email after which the process would be complete and they would be directed to the home screen.

Certain steps in the sign up flow were performed out of order due to the backend data structure being in place and was unable to be modified. Selection of country was one such example as different regions would be presented with certain backend issues that would be considered out of scope.

THE PROBLEM

Issues Uncovered

The initial audit of the signup flow revealing three key issues that were the focus of this project. The two major issues which were of the highest priority were in the password creation section and the personal data input section. The final issue was a much more overall issue perataining to the design and certain graphical elements.

THE PROBLEM

1

Unclear password requirements
A
The password requirements would only show up if the password strength "i" icon was tapped


The wording on the password requirements does not reflect the mandatory requirements.
The password could be a “Strong” password yet fail the requirements
B
The user has to create a password with a minimum character limit and has to meet atleast three conditions for a successful password creation.

The requirements are hidden from the user and any action taken does not provide adequate feedback. The password strength bar updates but does not show the requirements that have been met.

2

Hesitancy to provide personal data
A
Users aren’t eased into a data collection screen.


Large passage of text instantly asks for users address on a page with no address related fields. This would lead to users not providing information as evidenced by the reviews on the App Store

3

Lack of graphical elements
A
Lots of real estate on the screen to add graphical elements. Graphical elements could include an indicator of screen state or related to the CTA of the screen. Lack of any progress/action indicator.
B
Text fields do not have any placeholder text and room for animation present.

Potential Fixes

The initial audit of the signup flow revealing three key issues of varying degress of priority. Isuues 1 and 2 were the high priority items and issue 3 was a low priority item.

IDEATION

1

Clearer password requirements
1
Have the password requirements pop-up after a certain number of characters have been typed.

E.g  After 6 characters there is pop up with the required password information. If the password meets all the criteria then doesn’t show up
2
Have the password requirements be tied to the password strength option as a drop down menu.
3
The password has a check mark to indicate whether requirements have been met, populates automatically, not when you only hit the submit button.Text fields do not have any placeholder text and room for animation present.
4
If a certain requirement hasn't been met, then an error indicator pops up next to unmet requirement indicating that it needs to be accounted for.

2

Clearer Intent with Onboarding
1
Lots of real estate on the screen to add graphical elements. Graphical elements could include an indicator of screen state or related to the CTA of the screen. Lack of any progress/action indicator.
2
Text fields do not have any placeholder text and there is room for animation present

3

New graphical elements
1
Added graphical elements to give context to the what screen the user is on.
Placeholders line up with the text entry field and animate upwards when tapped to make room for content. This adds a sense of dynamism to the app
2
Using animations to give the user feedback on certain actions performed. Animations that require waiting or loading are the ones emphasized as they are visible on screen for a relatively longer time.
DESIGN DECISIONS

Development Prototypes

Once there was a direction established, prototypes were made to send to the developers. For these prototypes, the key choices that were made and screens designed are shown below.

1

Clearer password requirements

2

Clearer Intent with Onboarding

3

New graphical elements

Figma Prototype

A prototype for the sign up flow was built in Figma. This protoype was meant to convey the flow of the sign up screens and show how the password and data input screens would change.

This is an interactive prototype and can be navigated from the start of the sign up flow till its end.

THE PAYOFF

Personal Takeaways

This was a great project to work due to the nature of its structure. Things had to move quick and the timeline was around a month for the deliverables of the design. I felt that the project helped me work with tighter schedules andquicker iterations within my team and the rest of stakeholders involved. I felt that analyzing and redesigning certain aspects was a good lesson in restraint and control to see what could be changed realistically rather than work at it with recklesss abandon. Overall a very quick and fun project to work on!

MY THOUGHTS