Apple HomeView Explained: A $299 Hub That Leans on the iPhone

Apple announced Apple HomeView on October 13, 2026, a $299 central home hub with a 7-inch screen and Siri AI. The announcement came two days before an October 16 episode of The Vergecast devoted to the device.
What Apple announced
Apple describes HomeView as bringing entertainment, connection, and smart home management together in one place, powered by Apple Intelligence with Siri AI Apple Newsroom. Apple Intelligence is the company's name for its built-in AI features.
The hardware has an iPad-like shape with a 7-inch display Reuters. It stays plugged into power at all times. It can control doorbells.
How it knows who is in the room
Identity is central to the design. HomeView includes face recognition and can recognize up to six voices and faces. It supports personalized content for up to six people. It also uses data from the iPhone, a detail noted in Reuters coverage of the launch.
Power stays on. Identity is worked out in the room itself. Processing is shared with the phone. That combination lets one shared screen serve several household members without asking each person to log in for each use.
Where the apps come from
Early recaps listed apps and widgets on HomeView MacRumors. A later account from David and Nilay on The Vergecast revises that picture. They report that HomeView relies almost entirely on CarPlay, Apple's system for showing iPhone apps on another screen, rather than running as its own app platform The Verge. Their episode focuses on that app situation and why Apple chose not to make the hub into its own app platform.
What launched with it
HomeView did not arrive alone. Apple announced Apple Home Collection, a new lineup of smart home accessories built with LG Electronics and Schneider. It announced HomePod mini 2 with Siri AI, new colors, and improved audio. It unveiled a new Apple TV 4K with Siri AI that works as a home hub for controlling smart home accessories.
The wider picture
The broader context here is the choice between starting a new app system and reusing one that already exists. A dedicated home app store would need new SDKs, the toolkits developers use to build apps, plus review queues, permission rules, and incentives to get developers to join. Showing apps through CarPlay reuses an existing distribution path, an existing sandbox, or isolated space where apps run, and existing tools for media, messaging, and navigation already tested for shared use in cars.
In my view, that tradeoff fits this kind of product. A screen that stays on the wall and is shared by several people does not need the full flexibility of a tablet. It needs fast switching between people, easy handoff from personal phones, and steady behavior for shared jobs like answering the doorbell and controlling music.
For builders, the focus shifts from making separate home apps to handling identity and continuity. If personalization follows voice and face, and the actual work happens on the phone, then reliability depends on sensing who is nearby, linking accounts, and working sensibly when the linked phone is not there. Those are systems problems more than screen-design problems.
Looking ahead, the hopeful possibility is simple. Shared screens have long stayed basic because personalization was hard. A hub that knows who is in front of it, stays powered, and borrows ability from phones already in pockets could make shared computing workable without asking developers to support another separate platform.


