Safari on HomeView is a short, square screen, and your sticky header will notice
Iris Calderón
Your header is position: sticky. Your cookie bar is position: fixed at the bottom. Your newsletter modal is tall, and its close button sits at the top. On a laptop, fine. On a viewport shorter than 600px, the header and the bar eat most of the screen and the modal runs off the bottom with no way out.
That screen is now a Safari target. In a post on the WebKit blog, Jen Simmons announces that Safari runs on Apple HomeView, alongside Safari on macOS, iOS, iPadOS and visionOS. HomeView has a square, 7-inch display. People talk to it from across the room, or tap it up close.
Her headline advice to developers is reassuring. Most likely, you don't need to do anything. I agree, with one condition. That only holds if you never baked a device shape into your CSS.
The assumptions that break
The post names them directly. Some sites assume a screen is landscape or portrait, never square. Some assume the viewport is always taller than 600px. On HomeView it's shorter.
That second one is the trap. Most of us never wrote it down. It piled up: a sticky header here, a fixed bottom bar there, a dialog sized against the design file.
The post lists two ways it fails. Sticky or fixed-position headers and footers can leave almost no room for the main content on a short screen. And modals taller than the viewport, newsletter signups being the classic case, can leave users with no way to dismiss them.
Two declarations for the worst one
Here's the quick fix the post gives for those modals:
.modal {
max-height: 90svh;
overflow-y: auto;
}
Read it mechanically. svh is the small viewport height unit, measured as if the browser's toolbars are showing, so it's the conservative height. max-height caps the box at 90% of it. overflow-y: auto turns the modal into its own scroll container once the content is taller than the box. The box never pushes past the bottom edge, and the close button stays on screen.
My take: this belongs in your base modal styles today, HomeView or not. A phone in landscape has the same short height. Which is exactly how the post suggests you test.
The sticky header gets no snippet in the post, and I'm not going to make one up. It's a judgment call anyway. Decide what earns permanent space on a short screen. Usually less than you think.
Voice users call controls by name
This part isn't about layout, and it's the part I'd take most seriously. Voice is a main way people use HomeView. Simmons puts it simply: someone speaking to a page isn't pointing at a button, they're calling its name. That works with semantic HTML. Real buttons, links and form fields, and a clear label on every control.
The div with a click handler and an unlabelled icon inside was already a problem for keyboard users. Now it's also a control nobody can ask for out loud.
Media gets the same treatment. HomeView plays audio and video, and the post asks for captions as WebVTT files inside track elements:
<video controls>
<source src="theshow.mp4" type="video/mp4">
<source src="theshow.webm" type="video/webm">
<track default
kind="captions"
srclang="en"
label="English"
src="captions.vtt">
</video>
Run a recipe site? Safari's cooking experience builds a step-by-step view from schema.org Recipe data in JSON-LD. If your recipes don't carry that markup yet, now there's a concrete reason to add it.
Stop reading the user agent
Safari on HomeView reports an iOS user agent. Any script that maps an iOS user agent to an iPhone is now wrong about a screen on a kitchen counter. WebKit's advice is to drop UA sniffing and use feature detection, testing directly for the API you need. For the custom banner nudging people to install your app, the post points to Smart App Banners instead, so Safari decides whether a banner makes sense on the device at all.
Same lesson every new form factor teaches. The device you sniffed for is never the only one sending that string.
Test on what you already own
No HomeView on your desk? The post gives two options. Turn a phone to landscape and fix whatever breaks because of the short height. Or open Responsive Design Mode in Safari and set the viewport to 448×364.
My verdict: this launch is less about one device than about one number. If 600px of height is holding something up in your stylesheet, find it. Start with the modal. Two declarations. Then scroll your site at 364px tall and count how much of the screen your header and footer keep for themselves.
Source: WebKit Blog (webkit.org)