PRODUCT DESIGN CASE STUDY - Conceptual

Atlas - A room-first smart-home experience

Atlas - A room-first smart-home experience

Try the prototype

ROLE
Solo product designer

ROLE
Solo product designer

TIMELINE
About 3 weeks

TIMELINE
About 3 weeks

SCOPE
Mobile · 26 screens

SCOPE
Mobile · 26 screens

STATUS
Concept · not user-tested

STATUS
Concept · not user-tested

TOOLS
Figma, HTML, CSS and JavaScript

TOOLS
Figma, HTML, CSS and JavaScript

01 — The problem

Smart homes promise simplicity. The experience often delivers the opposite.

This project started with something much smaller. My room had three remotes—one for the fan, one for the air conditioner and one for the curtains. That was just one room. Every bedroom had its own set, and the living room had another. Controlling the house meant juggling remotes instead of simply interacting with my home.

The goal I set: anyone in the family, from a grandparent to a teenager, should be able to pick up the phone and control the room they’re in without learning how the system works.

My first instinct was to put every device in one place.

HOME → ALL DEVICES → LIGHTS / LOCKS / PLUGS / SPEAKERS

It ended app-switching, but people still had to scan a long list and remember what each device was called.

“One app” did not automatically mean “one understandable home.”

02 — The insight

People think in rooms,
not devices.

No one walks into a bedroom thinking about “Bulb 03.” They think about the bedroom.

BEFORE
Devices → Categories → Rooms → Controls

AFTER
Home → Rooms → Devices → Controls

01 — The problem

Smart homes promise simplicity. The experience often delivers the opposite.

This project started with something much smaller. My room had three remotes—one for the fan, one for the air conditioner and one for the curtains. That was just one room. Every bedroom had its own set, and the living room had another. Controlling the house meant juggling remotes instead of simply interacting with my home.

The goal I set: anyone in the family, from a grandparent to a teenager, should be able to pick up the phone and control the room they’re in without learning how the system works.

My first instinct was to put every device in one place.

HOME → ALL DEVICES → LIGHTS / LOCKS / PLUGS / SPEAKERS

It ended app-switching, but people still had to scan a long list and remember what each device was called.

“One app” did not automatically mean “one understandable home.”

02 — The insight

People think in rooms,
not devices.

No one walks into a bedroom thinking about “Bulb 03.” They think about the bedroom.

BEFORE
Devices → Categories → Rooms → Controls

AFTER
Home → Rooms → Devices → Controls

The product

Atlas at a glance

Six of the 26 screens.

Atlas opens in the room you’re in and shows only its devices.

If the guess is wrong, the room list is one tap away.

Devices with a range get their own screen: a large dial with − and +.

Set-up asks where a device lives, so it lands in the right room.

Every automation reads as one plain sentence before it’s saved.

Members see exactly what they can and can’t change.

03 — What exists today

Both apps start from the whole home. Atlas starts from your room.

Google Home · Apple Home

Open

Whole home

Find room

Find device

Use it

Atlas

Open

Your room

Use it

Google Home opens on pinned Favorites, with every device in a Devices tab. Apple Home shows every room in one long scroll.

04 — Secondary research

What research says about rooms, detection and families

I had no participants, so I read published research. These are other people’s findings, not mine.

Finding 01

Bedrooms belong to the people who sleep there.

In a two-week diary study, devices in private rooms were controlled mostly by the people using that room; living-room devices were open to everyone.

Kenderova & Neusesser, Nielsen Norman Group, 2025

In Atlas: everything is organised by room, the way households already divide control.

Finding 02

Right room 86–92% of the time.

A Bluetooth beacon system tested in a real house placed people in the correct room 85.9% of the time across three rooms and 92.1% across five.

Simplified indoor localization using Bluetooth beacons, Sensors, 2024

In Atlas: roughly one guess in ten could be wrong, so switching rooms is always one tap.

Finding 03

Homes follow whoever set them up.

Interviews found “pilot” users configure the smart home, and “passenger” users find it harder to fit devices into their daily lives.

Koshy, Park, Cheng & Karahalios, CHI 2021

In Atlas: members get clear, limited access, so they can act without asking the owner each time.

05 — User flow

Six flows, mapped screen by screen

Atlas guesses the room; every other flow starts from there.

06 — Principles

Four rules every decision comes back to

01

Places, not hardware

People think about their home by room, so Atlas does too.

Decisions 01, 03

02

Simple stays immediate

A light is one tap. Only devices with a range open a screen.

Decision 02

03

Usable at every age

Big targets and plain words, for grandparents and teenagers alike.

Decisions 02, 03, 04

04

Shared without surprises

Anyone can use the home; changes that affect everyone need the owner.

Decision 05

07 — Design decisions

01 — Room-first control

The application opens into a room, not an inventory.

The application opens into a room, not an inventory.

Atlas opens in the room you’re standing in, detected by Bluetooth proximity, and shows only that room’s devices. A room selector stays visible, so switching rooms is always one tap away.

Trade-off

Detection can be wrong, and Bluetooth proximity isn’t validated yet. An always-visible room selector costs a little space, but a wrong guess never traps anyone.

How I’d measure it

How often people accept the suggested room without switching, and the time from opening the app to the first device action.

02 — Right amount of control

Simple actions stay immediate. More controls appear only when needed.

Simple actions stay immediate. More controls appear only when needed.

Lights and plugs toggle straight from their card. Tapping a device opens its own screen with bigger controls: a temperature dial with − and + for the thermostat, and a brightness slider for lights.

Trade-off

Changing the temperature takes one extra tap, but the controls are big enough for anyone in the family to use comfortably.

How I’d measure it

Time and mis-taps when setting a target temperature, and whether people of different ages prefer dragging the dial or tapping − and +.

03 — GUIDED DEVICE SETUP

Adding a device becomes a guided journey through the home.

Adding a device becomes a guided journey through the home.

Atlas breaks setup into clear steps: find the device, connect it, name it, assign it to a room and test that it works.

Trade-off

Five steps take longer than a single “add device” form, but each step asks one question a non-technical person can answer.

How I’d measure it

Set-up completion rate, and the step where people drop off or go back.

04 — Readable automations

Every automation ends as a sentence the household can understand.

Every automation ends as a sentence the household can understand.

People choose when the automation runs, what happens and where it applies. Before saving, Atlas combines those choices into one plain-language rule.

Trade-off

Building rules from when, what and where limits how complex an automation can get; advanced conditions would need another level.

How I’d measure it

Whether people can predict what an automation does from its sentence alone, and how often they edit one right after saving it.

05 — Shared household access

Everyday control is shared without giving everyone administrative access.

Everyday control is shared without giving everyone administrative access.

Household members can control rooms and manage everyday automations. Sensitive actions, such as changing home settings or managing members, remain owner-controlled.

Trade-off

Household members can’t change home settings or manage members, so some requests still go through the owner.

How I’d measure it

How many everyday automations non-owners create, and how often members ask the owner for a change.

07 — Design decisions

01 — Room-first control

The application opens into a room, not an inventory.

Atlas opens in the room you’re standing in, detected by Bluetooth proximity, and shows only that room’s devices. A room selector stays visible, so switching rooms is always one tap away.

Trade-off

Detection can be wrong, and Bluetooth proximity isn’t validated yet. An always-visible room selector costs a little space, but a wrong guess never traps anyone.

How I’d measure it

How often people accept the suggested room without switching, and the time from opening the app to the first device action.

02 — Right amount of control

Simple actions stay immediate. More controls appear only when needed.

Lights and plugs toggle straight from their card. Tapping a device opens its own screen with bigger controls: a temperature dial with − and + for the thermostat, and a brightness slider for lights.

Trade-off

Changing the temperature takes one extra tap, but the controls are big enough for anyone in the family to use comfortably.

How I’d measure it

Time and mis-taps when setting a target temperature, and whether people of different ages prefer dragging the dial or tapping − and +.

03 — GUIDED DEVICE SETUP

Adding a device becomes a guided journey through the home.

Atlas breaks setup into clear steps: find the device, connect it, name it, assign it to a room and test that it works.

Trade-off

Five steps take longer than a single “add device” form, but each step asks one question a non-technical person can answer.

How I’d measure it

Set-up completion rate, and the step where people drop off or go back.

04 — Readable automations

Every automation ends as a sentence the household can understand.

People choose when the automation runs, what happens and where it applies. Before saving, Atlas combines those choices into one plain-language rule.

Trade-off

Building rules from when, what and where limits how complex an automation can get; advanced conditions would need another level.

How I’d measure it

Whether people can predict what an automation does from its sentence alone, and how often they edit one right after saving it.

05 — Shared household access

Everyday control is shared without giving everyone administrative access.

Household members can control rooms and manage everyday automations. Sensitive actions, such as changing home settings or managing members, remain owner-controlled.

Trade-off

Household members can’t change home settings or manage members, so some requests still go through the owner.

How I’d measure it

How many everyday automations non-owners create, and how often members ask the owner for a change.

08 — Foundations

A calm palette instead of a tech palette

Most smart-home apps lean on cool blues and dark screens. I wanted Atlas to feel like part of the home, so I chose soft, natural greens and kept warm amber for warnings only.

Primary green

#3F9460

Buttons, “on” states, active tab

Background

#F1F5EA

Soft, paper-like green

Ink

#1F2621

Text with a hint of green

Warm amber

#C9782A

Warnings only

From the Figma file: 17 colour tokens, an Inter type scale, 24 px icons and the components every screen is built from.

09 — Reflection

The project changed when I realised the fix wasn't a universal remote — it was reorganising the home around rooms instead of devices.

Organising Atlas around rooms changed more than the home screen. Setup, automations, family access and notifications all follow from it.

Recognising the limits: Atlas is 26 screens built over about three weeks, and it hasn’t been tested with users. Bluetooth room detection is a proposal I haven’t validated technically, which is why the room selector never leaves the Home screen.

10 — Next steps

What I’d test first

01

Room detection in a real home

How often Bluetooth picks the right room, especially near doorways and shared walls.

02

The whole family, same task

A grandparent, a parent and a teenager each set the AC temperature; compare time and errors.

03

Finding the room selector

When the guess is wrong, do people notice the selector and switch without help?

04

Dial versus − and +

Which one older users prefer for precise changes, and whether either should go.

09 — Reflection

The project changed when I realised the fix wasn't a universal remote — it was reorganising the home around rooms instead of devices.

Organising Atlas around rooms changed more than the home screen. Setup, automations, family access and notifications all follow from it.

Recognising the limits: Atlas is 26 screens built over about three weeks, and it hasn’t been tested with users. Bluetooth room detection is a proposal I haven’t validated technically, which is why the room selector never leaves the Home screen.

10 — Next steps

What I’d test first

01

Room detection in a real home

How often Bluetooth picks the right room, especially near doorways and shared walls.

02

The whole family, same task

A grandparent, a parent and a teenager each set the AC temperature; compare time and errors.

03

Finding the room selector

When the guess is wrong, do people notice the selector and switch without help?

04

Dial versus − and +

Which one older users prefer for precise changes, and whether either should go.

Create a free website with Framer, the website builder loved by startups, designers and agencies.