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


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

Alert Mobile app

Roles: User Research, Ideation, Concepts, Experience design

A platform to measure design

Designers and stakeholders get into a loop of subjective opinions without thinking about Time, user and the value. What makes a design good?. Numbers. When it is measured with a purpose. This is the story of how we Solved a problem with a product to deliver purpose of deciding the right design for the product and users.

The challenge
When the client approached me with a unique concept. The timeline and the layer of the problem are challenging. I myself stepped out of the designer shoe to understand more about the design and designer problems.

“The absolute challenge we faced is aligning every radical designer’s problem and needs.”

We approached users(Designers) form every possible industry, medium, location, studies etc.. Though it was an interesting study, the challenging part was finding who does what role. Because designers do every possible role in their respective field.

Needs First Approach

After we segregated the group of users who serve their knowledge in different industries. The needs-based approach helped to identify the between primary and secondary. Every designer has their own set of problems. But when it comes to product, we gave yourself a responsibility to approach from the complex, that is the root of the needs. Hence the approach.

“We were sure. We don’t want to build another analytics tool, which is complex to understand.”

The Game: Design vision

I got to know that the Game is a complex one and the home run is the only option. To handle every problem out there, I needed to build a strategy. Said that I wanted to create an armor which anyone who comes into the project to wear and get to know the battlefield. A seamless setup that doesn’t require a meeting to explain.

South Pole: Discovery

After discovering our ideal user and the target market. We interviewed multiple faces of designers with different roles and responsibilities. Everyone we faced had some similar patterns, but different motivations.

After all the discussion one emerged problem from all of them is the number they require to prove that the design actually works and eliminate the bias towards the decision. Most of them worried about the users who are going to use the design which initially finds a place in the dark because of a biased decision. For a designer, this has been the age-old problem and for decision making people it is not a choice, but have to make the decision.

But how do we educate everyone to deliver the right designs within a limited Time?

Contextual Inquiry

Mapping all the needs helped to look at each stage of the user what he feels, thinks, does etc. Out of all critical decisions to be made. I myself borrowed sometime to understand more about customers. So I started with their day to day life, process, how they design on what basis, how the decision for the final design is made etc..

This lens provided us a valuable insight. Not only they are not able to identify the correct number in analytics, but they need more fast, precise and simple number to make the decision.

“I don’t want a two page report of analytics which finally ends up in archive folder. Just the numbers to inform everyone that the deisgn is valuable.”

“I have read a lot of artilcles on measuring deisgn. But, somehow deep down I feel there should be a simple information to convince a particular design is valid.”

Jobs, Motivations, Mapping of problems

Applying job stories to extract the motivations, situation, and casualty of the user. To know more what jobs they want to get done. From the stage one, I avoided using persona’s not by the subjective fact. But I want to address the real situations and motivations of the user, Rather looking up the imaginary attributes. Everyone was excited to work on this process to know what it yields out. As you can see this simple way lead us to multiple needs and motivations.

After finding out the motivations and scenarios. I started mapping problems and roots. Categorized each problem into their own bucket and the level of problems. Starting from the project to closing the project, mapped all the stages of the user. This helps in which stage does the problem comes and how a user faces the situation.

The Experience