top of page
multiple screens copy.png

So.We Smart House

So.We is a mobile application that offers the users control and management of smart devices and the creation of automated routines for their houses.

​

My role: As a UX/UI Designer, I was responsible for the creation of mid- and high-fidelity prototypes, and the research, design, and validation of a new feature: automated routines. The product already had an MVP version running which I was responsible for improving.

​

The context: The discovery process for this project was conducted in cooperation with the design team.

​

The team found that the target audience for the app. is young people that are proficient with technology and are deeply concerned about sustainability. Therefore, energy-saving and optimization of tasks are key factors for the product.

 

The persona below is a representation of this audience.

Persona.png

The process

The conception, creation, and validation of the "routine" functionality was conducted using the iterative process.

 

In other words, we constantly tested the changes with real users to validate design decisions in order to improve the overall user experience. 

Iteration.png

Roadmap

The roadmap below illustrates the steps we took for the conception to the final design of the feature "Routines":

roadmap.png
1.png

We conducted a competitors analysis to understand exactly what we are doing right (or wrong) to create an effortless user experience and a product that people enjoy using.

​

We focused the analysis on automated routines only to better prospect usability issues.

​

What are the advantages of competitors analysis?

comp.png

What have we found?

Group 7117.png
Group 7118.png

Following the competitor analysis, we conducted a brainstorming section.

The session`s objective was to improve what already worked well on our competitor`s product while exploring their weaknesses to create a product that would stand out.

The following points were prioritized to be worked on:

Group 7136.png
2.png

"Routine" flow and architecture

Firstly, we created a sitemap of how the "routines" feature would be structured, which served as a base to design mid-fidelity prototypes.

Fluxo Completo.jpg

Mid-fidelity prototyping

Basic screens with the necessary information for users to create and configure automated routines were designed using the MVP`s components.

 

It allowed us to go from the conceptual stage to the implementation stage fast.

Advantages of using mid-fidelity prototypes

Group 7137.png

Mid-fidelity prototype schematics

mid fid.jpg

Usability testing

We tested our design and the proposed solutions with users that matched the persona.

​

Five users were subjected to conduct five tasks to verify if the app was easy to navigate and if the tasks could be completed with ease.

ezgif.com-gif-maker.gif

What have we found?

The usability sessions provided us with many interesting insights into how to improve our product regarding usability and easiness.

SOPRANO - Teste de Usabilidade [ROTINA].jpg

Due to the amount of information gathered during the tests, we created an affinity map to help us access the recurrent and more important issues to be worked on.

affinity.jpg

Further, a 2x2 Matrix (Effort X Impact) was created to help us prioritize which issues we should take action on more urgently than others:

2x2 matrix.jpg

What should we work on?

​

Most of the solutions proposed after the competitive analysis brainstorm worked well, however, new issues arose

​

We conducted another brainstorming session where we applied the "How Might We" technique to come up with validatable solutions for the problems we encountered.

​

Below are the main issues found and what we came up with as how to address them:

problem solution 1.png
problem solution 2.png
Group 7161.png
3.png

Since words and icons weren`t intuitive enough to the users, we decided to run a survey to access the mind map of our users:

SURVEY obj 1.png
SURVEY obj 2.png
SURVEY obj 3.png

Among the questions, we presented descriptions of the routine functionality and asked what term better represents it. Additionally, we offered several icons and enquired which one best fits the functionality.

What have we found?

We clarified some demographics and user expertise with smart devices and general tech, however, the most important insights were the following:

Quet 3.png
Question 1.png
Group 7169.png
Group 7168.png
Group 7167.png
2.png

The solutions we came upon in previous steps were prototyped in high-fidelity: 

Home.png

New Home screen

template.gif

Routine feature tutorial

A new set of usability tests validated most of our solutions, increasing the completion rate of the tasks given to users drastically:

Usability testing.png
5.png

After some final tweaks, design version 1 was considered closed for development.

​

The next steps are the introduction of new features and monitorization of data and reviews that users leave on Google Play and Apple Store.

What have I learned?

​

The most valuable lesson I`ve got from working on this project was the importance of constant validation, especially through usability testing.

​

This dynamic helps elucidate how users will interact with your product and brings light to potential usability issues.

 

I consider the conduction of usability tests one of the most important UX practices when either before launching a new feature or to evaluate issues of features already in use.

glying iphones.png

Click below to navigate the interactive prototypes:

Download So.We Smart Home on Google Play and Apple Store:

get-it-on-play-store-button-and-apple-app-store-icon-vector 1.png
get-it-on-play-store-button-and-apple-app-store-icon-vector 5.png
bottom of page