Work · Switchless • Concept 2024 to 2025

One app that runs all your smart home sensors

Problem

In most smart homes, each sensor has its own app and its own rules. Even "run the fan when it's humid" is hard to set up.

My call

Home rules read like a sentence. Most apps show every part of a rule in one form. I split it into "when something happens" and "this is what happens."

Result

It never launched, and the company has closed. The whole app was designed and handed off in Figma.

Role

The product designer on a team of four, for nine months. I designed the rule builder.

  • Two phones on a dark app: one room's five sensor readings with a light control, and the New Automation builder with Triggers, When something happens, and Actions, This is what happens.
    One room's five sensor readings, and one rule builder.
  • Two versions of the New Automation screen: the frosted glass style over a bright gradient that we dropped, and the solid dark builder with tips under Triggers and Actions.
    Left, the glass look we dropped. Right, the empty builder with tips.
  • Three phones in the solid dark style: the automation builder, a list of sensor cards for temperature, noise, air quality, humidity and occupancy, and a room screen.
    The solid cards we kept, handed off to engineering.
Role
Product Designer
Timeline
October 2024 to June 2025
Team
Kayley Vu, Warren Wu, Nicho Naugle
Tools
Figma
Client
Switchless (early-stage startup)
Status
Concept

Problem

Five sensors meant five apps and five ways of thinking.

In a normal smart home, temperature lives in one app and humidity in another. Each has its own screens and rules.

The goal: one picture of your home, not five. The hard part was rules. Take "when it's humid and the room is empty, run the fan." It's easy to say and easy to design badly.

Five apps' worth of sensors, in one home screen and one rule builder.

Process

I mapped how the sensors talk to the phone before any screens.

With the team, I mapped what the hub senses and what it sends. Then, how fast the app must show it.

Why first? If the app says a light is on when it's off, people stop trusting it. The screen is only as honest as the data under it.

Process

I turned home rules into something that reads like a sentence.

Most automation apps show every part of a rule at once, in one form.

I split each rule in two: "when something happens" and "this is what happens." Read top to bottom, it's a sentence. Those plain names helped more than any layout change. People could check a rule in their own words.

Two New Automation screens: one with a finished rule, Trigger 1 above three actions for the living room light, porch light and bedroom fan; one empty, with a tip under Triggers and under Actions.
Left, the glass style we dropped. Right, the empty builder with tips.

Process

We threw out our first look after the founders' weekly reviews.

Our first look used frosted glass over bright colors. It was trendy, but the numbers were hard to read.

We switched to solid dark cards with the same reading order on each. A weekly review only helps if you let it kill something you liked.

The glass look we dropped, wiped into the solid cards we kept.

Final Design

One design system for every sensor card, though the product never launched.

One typeface and one color per kind of sensor. Red always means security or temperature, and blue always means humidity.

Switchless was meant to replace five apps, so the one app had to work the same way everywhere.

Switchless design system foundations: the Montserrat type scale, base and state colors, a color per device type, device button components, and the home screen built from them.
One type scale, one color per device, one home screen.

Reflection

I couldn't say who opens the app and when. Now I ask first.

After the company closed, a mentor asked me something. Who opens this app, when, and why? I had no answer. We designed for "people who want a smart home." That's a market, not a moment.

Next time, I'd write that sentence before the first sketch.