IA

Nebulo – Mobile App Case Study

Mediums: Mobile App – Android & iOS
Roles: Product, Strategy, UX and Research
Problem Statement

A Smart Home with multiple, connected and Independent devices has its own behavior and set of requests to behave as the command says, which aren’t purchased from a single brand. When it comes to handling devices from a user end he/she has to switch between multiple apps to control a single room or a device. On top of this learnability is an issue at most of the time and they prefer a human guidance rather approaching an FAQ of Jargons.

hypothesis statement

Market Segment

Primary consumer segments emerging from the connected-home market, each with their own needs, behaviors, and attitudes. Target market would be of people 25-50, young working professionals, Tech enthusiasts, entrepreneurs, executives, and innovators.

Connected-Home Market Percentageby Consumer
24% Traditionalist | 22% Urban Dweller | 19% Affluent Nester | 21% Family First
User Research
 - Jessy, Age 25, Ph.D. student. Staying in an apartment “On an unusually hot day, love being able to adjust the AC using the app, When I’m on my way to home. So it’s nice and cool when I get inside the house.”
- Apoorva, Age 33, Part-time Assistant, New Mom
“Child’s safety and whereabouts is my utmost concern. Which is why multiple Dropcams are set up throughout the spacious house. My son constantly demands full attention, so I need everything (i.e., cameras, lights, thermostat, garage, etc.) conveniently controlled by the press of a button — easily accessible in phone with one app.”
- Rahul, Age 41, Senior-level Marketing Executive, Owns a house 
“Looking for an interconnected system, where each of the devices talks to each other. It is hard to use multiple apps to control a single room.”
- Siddarth, Age 46, Construction Manager, Father of Two, & Homeowner
I love technology — at a cost-effective solution. I’m very cost-conscious and every home purchase is evaluated based on its ROI.

 

Customer Benefits

After identifying the pitfalls in using multiple apps to do a single interaction for switching on the devices. I found a new space with multiple opportunities. Listed all the benefits that include usage, reporting, monitoring and scheduling multiple brand’s devices in one app. After listing down all the possible benefits that fit the user needs. Again I pushed for a customer feedback. This time it did an impact and created a positive impact. Few benefits scored well and few aren’t. But considering the number of problems out there I put out everything and few had garnered an impact on the customers.

Job stories

Considering user motivations and casualty of the time constraint. I decided to work on the job stories to even expand into their daily lives. I decided not to use persona’s since it gives a high level of user needs with fixed attributes. But the case here is to address real users. What do they actually want to do?. hence the decision with Job stories.

With the data collected from field studies, contextual inquiries, and surveys. Analyzed and turned needs into motivations and outcomes with the help of Job stories. To write Jobs of the users, Empathy map and Customer journey map helped here to pin the minute details of the user problems in their daily life.

Breaking the stories into features is quite a consideration after many rounds of brainstorming. Before I head to the concept design I just want to make sure we are building the right solution. As suggested by the Lean product building, Importance vs Satisfaction framework helped in many places to eliminate the features that aren’t worth going after. After few rounds of user interviews, a distilled no.of features came to limelight.

But again we want to map between the highly important feature vs the low satisfaction with the competitive or existing experiences. The helped to focus on attacking the features and build a roadmap for a seamless release. Post feature priority, feature matrix helped us to identify which feature to tackle that delivers customer.

Information Architecture

IA

User Flowuser flow

Capturing user flow was an interesting part of the whole workflow. I was determined enough from the beginning of the Project on Make the app usable not in terms of the only style, but also in the interaction and ease of use throughout the app. I just want to end another design document. So I tested with users. After multiple iterations and numerous feedback arrived at a confident stage to pursue with UI.

Impact WIth design

Leave a Reply

Your email address will not be published. Required fields are marked *