In 2012, I worked on a project for a Seattle based network security company to design their mobiles apps that make the registration experience easier and faster for their users especially enterprise admins.

Illustration - WatchGuard registration app

Who is WatchGuard?
"For over 20 years, WatchGuard has pioneered cutting-edge cyber-security technology and delivered it as easy-to-deploy and easy-to-manage solutions. With industry-leading network security, secure Wi-Fi, and network intelligence products and services, WatchGuard enables more than 80,000 small and midsize enterprises from around the globe to protect their most important assets..."

The problem
The previous registration experience is frustrating because user have to manually input the 10+ digits on the company website in order to activate the device, which is tedious and definitely not a easy solution for the customer with tons of devices to manage. We hope to use camera and image processing technology to solve this problem. 
discover user value
How to solve
1. This solution should be easy to get on major mobile platforms. 
2. There should be a solution that simplifies the registration process.
3. We need a reliable solution to replace the manually input step.
4. We need to provide immediate feedback of success, failure, and error statuses.
5. It should possibly have a history of registered devices for the user to check.
Design iterations
The first draft I created was an action driven experience, which means the main activity is streamlined by the button, Sign in -> Registration-> Done or Register new. The main screen shows the registration history of the user. 

User flow - First draft

discussion and iteration
There were some debates. One is about "Scalability". The current design is very simple and based on one task. If the client wants to add new feature to the app, they need to redesign the patterns. So we need to come up with a solution that enables future content from the framework level.
Second is about "Cover everything or focus on one". In the real world, the user should have several ways to register the device. 1). input numbers; 2). scan using camera; 3). scan from a previous image. Ideally, we can put the three ways under one register tab. However, at that moment, we were only asked to develop one feature, that is to scan from the camera FAST, and right after the user is logged in. So we had to compromise on the interaction consistency of the tab functionality. However, this didn't bring too much user confusion when we did user test.

Shall we cover all the scenarios?

User flow - Revised based on client feedback


You may also like

Back to Top