Come home to intelligence.

Fragmentation is the obvious problem. Too many apps, too many brands, nothing talking to anything. It is real, and every competitor already claims to solve it, so it cannot carry the case on its own.

Research surfaced two problems underneath it.

Smart homes have one user and many inhabitants.In the multi-person households we studied, one person, the one who installed everything, had all of the control. Control lived in that person's phone, scattered across a dozen logins, and everyone else negotiated with the home through them. The fragmentation problem wasn't just "too many apps." It was that the interface to a fundamentally shared space was private. A phone-first product, however well designed, inherits that flaw by default.

Updates aren't neglected out of laziness.The cost of updating is paid per device, the benefit is invisible, and the timing is always wrong, mid-movie, mid-dinner, mid-use. People weren't careless; the system made care expensive. Insecure homes are a UX outcome, not a user failure. This finding is what made the broadcast tuner matter: it collapses the per-device cost to zero. The remaining problem, making invisible security feel like visible care, was a design problem. It became section 10.

The technology fixed where the tuner lives. It did not fix where the interface should. The industry default, a companion mobile app, was still the safe move, so before committing the home's interface to the television I pressure-tested it against the alternatives.

Why the TV won

Three arguments carried it. It's the only screen in the home that's communal by default, which is what the shared-home finding demanded. The differentiator literally lives inside it, putting the experience anywhere else separates the product from its edge. And the daily job of a smart home is monitoring, not fiddling: homes are checked constantly and configured rarely, and a glanceable 10-foot dashboard fits the frequent job better than a 6-inch screen you have to unlock.

What the decision cost

Committing to the TV wasn't free, and the honest accounting shaped the rest of the product.

A TV is not a phone stretched wide. People sit metres away, drive it with a remote, and want information they can absorb in a glance. These six principles aren't aesthetic preferences, each is a direct consequence of the surface we chose.

It took three rounds to reach a working 10-foot system. The first two versions carried habits from desktop and mobile design, and each round removed a layer of them. The mistakes are shown next to the screens that contain them, and each correction led to a decision in the final design.

v3 wasn't styled into shape, it was audited against the two platform rulebooks for the living room: Apple's tvOS Human Interface Guidelines and Google's Android TV design guidance. Each card pairs the platform's rule with where v3 answers it, and with the round that broke it first.

Round one split the home across tabs: Rooms, Scenes, Devices, each a silo (evidence in section 05). It matched how manufacturers organize, not how households speak. Nobody says "the Philips Hue A19", they say "the bedroom light", and no single tab could answer them. v3 collapsed the silos into one model.

The model had to carry both mental models as equal citizens: what a thing is (Devices), and where it lives(Spaces). Playbooks sit on top as the verb layer, if devices and spaces are the home's nouns, playbooks are its verbs.

The rename tells the story: rounds one and two called automations "Scenes", language borrowed from AV presets, something you switch on. v3 renamed them Playbooks, because a scene sets a mood once, while a playbook orchestrates devices, spaces, and conditions over time. The noun changed because the model changed.

The home surface answers the four questions a household actually asks from the couch: how much energy are we using, what is the home doing right now, is everything safe, and what needs my attention.

On a remote, every extra card adds key-presses, so the layout keeps any primary answer within a few directional moves, with alerts first in the focus order.

Round one's dashboards literally were mission control, twenty-plus targets, dials, camera walls, thin labels on heavy chrome (section 05). They demoed well on a monitor and glanced terribly from a couch. The v3 surface is calm at rest and dense on demand, eight cards answering the four questions, each opening into detail only when asked.

Playbook authoring was the hardest interaction problem in the product: building trigger-condition-action logic with a D-pad. Rounds one and two dodged it with phone furniture, rows of scene cards behind toggle switches (section 05), which made automations things you flip, not things you author.

The redesign restructured authoring as sentence assembly from constrained pickers, and made templates the starting point rather than a blank canvas: editing Morning Meditation into your own routine beats composing one from nothing.

The loop closes with voice in both directions: assistants as trigger, and the home reporting back, "Siri turned the bedroom lights off", so an automated home never feels like it's acting behind your back.

Broadcast updates were iZak's technical edge and its biggest UX risk: the differentiator is, by definition, invisible. One signal, every home, every device current, and if it works perfectly, nobody ever notices. Invisible security doesn't build trust. Visible care does.

So the update system was designed as a trust surface, not a background process:

Meter data is only useful if it changes a decision. The weekly report leads with predicted cost, the number that actually changes behaviour, before consumption, splits usage by space and appliance so heavy rooms are obvious, and sets carbon against solar generation for the households where green is the motivator. Built for Mike: insight without a dashboard-tinkering hobby.

The storefront closes the loop: recommendations generated from gaps in the home's existing device graph, pre-bundled combos with one total price, and onboarding into the same unified surface. One guardrail held throughout, recommendations serve the home's completeness, not engagement targets.

TVs idle far more than they play, and the platforms fill that idle time with wallpapers and ambience screens. iZak uses that idle time: when the TV is on but not in use, the app shifts to an ambient state, a live spatial representation of the home. Events appear where they happen: a door unlocking, lights switching on.

Committing to the TV made mobile load-bearing, not optional. The phone carries the jobs the couch can't: configuration, device-level depth, away-from-home moments, and space setup. Configure and act in the moment, from the pocket.

The phone shares the TV's dark system, so nothing has to be relearned crossing between them, the same components and the same language, sized for the hand instead of the room.

The consumer experience is the demand side of a two-sided platform. Before screens, I mapped the exchange that makes the model viable, manufacturers automating deployment and monitoring device health across their installed base, broadcasters pushing updates and content over spectrum, homeowners getting automation, control, and real-time insight, and defined the minimum viable platform: the smallest core interaction that makes all three sides show up.

iZak is concept-stage work, and I'd rather be precise about what that means than imply outcomes that don't exist. The concept carries four risky assumptions, here's how I'd pressure-test each:

The work delivered a product vision and strategy for an AIoT smart-home platform: a TV-first home dashboard and 10-foot design language, a Devices–Spaces–Playbooks model that maps to how people live, an energy surface that turns meter data into decisions, and a broadcast-update concept designed as a trust system rather than a background process, all grounded in persona, use-case, and competitor research.

The through-line was treating the television not as a screen for watching, but as the one place a household could see, understand, and command everything at home, with the hardest technical problem, keeping every device current, solved quietly in the background.

Come home to intelligence: the home, made legible from the couch.