- Client
- HomeHub (our own system)
- Role
- Product Design, iOS / watchOS, Hub Services & TV App
- Timeline
- 2026 · in daily use in one home
- Year
- 2026
- Category
- Smart Home
Overview
HomeHub is our own smart-home system. It runs one house every day: the lights, the back-door lock, the blinds, two thermostats, the speakers, the camera and the TVs, from a phone, a watch, the TV and a web dashboard.
It is not a product for sale and it has no public address. We built it to see what it takes to make many devices from many brands feel like one calm system. The iPhone app ships to the household through internal TestFlight builds.
Why
HomeHub is where we make many devices from many brands feel like one product, every day, in a real house: our own design language, our own hub and our own apps on top of the hardware people already own.
The challenge
A modern house ends up with one app per brand: lights in one, the lock in another, thermostats, speakers, cameras and the TV in four more. None of them knows what the others are doing, and the house cannot react to anything as a whole. We wanted one place to see and run the home, and a house that responds on its own.
What made it hard
- Every brand brings its own app, account and idea of a “room”, and none of them talk to each other.
- Commands have to work on the home Wi-Fi and from anywhere, without opening the house to the internet.
- A lock and cameras raise the bar: unlocking and viewing have to be protected, and cameras should only record when nobody is home.
- The interface has to stay calm with dozens of devices: what is on, what is locked and what needs attention, at a glance.
Approach
One hub, many small bridges. A Raspberry Pi on the home network runs a separate service for each device family, so a flaky integration never takes down the rest, and Firebase carries commands from outside the house.
One design language everywhere. “Arc” is deep navy with a sky-to-cobalt gradient; gold appears only when a lamp is actually on, green means locked and safe, and rose means something needs you. Numbers use fixed-width digits so live temperatures never jitter.
Process
- The hub: Bridges for Hue, Sonos, Nest, SwitchBot (lock, blinds and plugs), the camera, the TVs, a humidifier and the PC, behind one API, with remote access over a private network.
- The app: An Expo iPhone app: Home, Devices, the assistant and an activity feed, with Face ID before unlocking or viewing cameras, two-factor sign-in and household invites.
- Watch and widgets: A native Apple Watch app for the lock, lights, scenes and climate, and home-screen widgets for the lock and favourite rooms.
- Automations: A rules engine with an in-app editor: a Goodnight routine shuts the house down, door events trigger rules and alerts, and the camera records only while everyone is away.
- The TV: A replacement home screen for the living-room Fire TV with the time, weather, house status and the assistant, and a screensaver that glides into place.
What we built
- One app for the house: Lights with brightness and colour, thermostats with a dial, blinds, plugs, the lock and the TVs, grouped by what they do.
- A house assistant: Type or say “dim the office to 40 and make it blue”, then “and lock the back door”. It runs the commands and answers in plain words.
- Goodnight and away: Goodnight locks up, closes the blinds and turns off the lights, TVs and PC. Rules react to the door and to who is home.
- Cameras that respect home: Viewing asks for Face ID, and recording runs only while everyone is away.
- A watch and widgets: Lock, lights, scenes and climate from the wrist or the home screen.
- A TV that knows the house: A custom living-room home screen with the house status and the assistant’s latest note.
How it was built
A Raspberry Pi on the home network runs TypeScript bridge services on Fastify, one each for Hue, Sonos, the camera, the TVs, a humidifier, Alexa and the PC, plus a rules engine; Nest and SwitchBot run through Firebase Cloud Functions. Remote access runs over a private network instead of open ports.
The iPhone app is Expo and React Native, with a native Apple Watch app and widgets. The web dashboard is React and Vite, and the living-room TV runs our own Android home screen. The house assistant uses OpenAI for chat and speech-to-text and ElevenLabs for its voice, with a local model as a fallback. 1,035 automated tests across 140 files cover the hub, the apps and the rules.
Stack
- Expo + React Native: The iPhone app, with SwiftUI for the watch and widgets
- Raspberry Pi hub: TypeScript bridge services on Fastify, one per device family
- Firebase: Cloud Functions, Firestore, Storage and Hosting for the web dashboard
- Android (Java): The Fire TV home screen
- OpenAI + ElevenLabs: The assistant’s chat and speech-to-text, and its spoken voice
Outcomes
- Daily: Runs one home every day
- 5: Surfaces: iPhone, Watch, widgets, web, TV
- 10: Device families behind one app
- 1,035: Automated tests
Wins
- One calm app for lights, climate, blinds, plugs, the lock, cameras and TVs.
- A rules engine the household edits in the app, from Goodnight to door alerts.
- A native Apple Watch app, widgets and a TV home screen that share one look.
- A house assistant that runs several devices from one sentence.
Hard parts
- Many brands, one model: Each brand has its own idea of a light, a room and a scene. Small bridges translate each one into a single shape, so the apps never care which brand is behind a switch.
- Security in a home: Unlocking and camera viewing ask for Face ID, sign-in uses two-factor codes, and the house is reached over a private network rather than open ports.
- Calm with dozens of devices: Colour means something: gold only for a lamp that is on, green for locked, rose for attention. Everything else stays quiet navy.
Services
- Product Design: the “Arc” design language
- Expo / React Native iPhone App
- Apple Watch App & Home-Screen Widgets
- Raspberry Pi Hub with Device Bridges
- Rules Engine & Door Alerts
- Custom Fire TV Home Screen