WebKit Says Safari on Apple HomeView Most Likely Needs No Site Changes, but Points to Recipe JSON-LD, an iOS User Agent and a Short Viewport
WebKit's November 13 post says developers most likely need do nothing for Safari on Apple HomeView, then flags recipe JSON-LD for its cooking view, an iOS user agent and a viewport shorter than 600px.
Overview
WebKit published Safari on Apple HomeView on November 13, 2026, in a post written by Jen Simmons. It says Safari “also lives on Apple HomeView, joining Safari on macOS, iOS, iPadOS, and visionOS,” and tells web developers: “Most likely, you don’t need to do anything. This is Safari, powered by WebKit.” The post then lists several things worth checking, among them recipe markup, a user agent that reports iOS, and a viewport that is shorter than some sites assume. MacRumors reported on November 13 that Apple’s HomeView smart display “launched today.”
What WebKit tells developers
Recipes. According to WebKit, Safari on HomeView has a new cooking experience: it “recognizes when users are on a webpage with a recipe, and offers a streamlined view of step-by-step instructions.” The post says Safari “creates this view from recipe data in the schema.org recipe type in JSON-LD,” and advises sites that do not yet support that type to mark up the recipe details in JSON and add it to the page. Its sample markup includes the fields name, image, prepTime, cookTime, recipeYield, recipeIngredient and recipeInstructions, the last as HowToStep entries.
Captions and input. WebKit says video captions should be included as WebVTT files inside track elements. On input, it says voice is “a key part of how people use the device,” and that semantic HTML, with “real buttons, links, and form fields, and a clear label on every control,” makes voice interaction work.
User agent. WebKit’s post says “Safari on HomeView also reports an iOS user agent,” and notes that some sites assume an iOS user agent means the device is an iPhone. It says user-agent sniffing “can result in unintended consequences as technology evolves” and recommends feature detection instead; MDN describes feature detection as a check “to see if a specific feature is available to the client instead of figuring out which browser is rendering your page.” For app-download banners, WebKit points to Smart App Banners, saying such a banner “might not make sense on HomeView, and you can rely on Safari to figure that out.”
Screen shape. WebKit describes HomeView’s display as “the square, 7-inch display,” and says some sites assume a screen is either landscape or portrait “and never square,” or that “the viewport is always taller than 600px, while on HomeView it’s shorter.” It says sticky or fixed headers and footers “might leave almost no room for the main content,” and that modals taller than the viewport “might leave users with no way to dismiss them.” Its suggested quick fix for modals is max-height: 90svh; overflow-y: auto;. Without a device, WebKit suggests testing on a phone in landscape orientation, or using Safari’s Responsive Design Mode with the viewport set to 448×364.
What Apple and the press report
Apple’s HomeView page says: “When you find a recipe in Safari, just tap the Start Cooking button to view a streamlined format that’s easy to follow.” MacRumors, in a report that relays the release notes for HomeView software version 27.2 from an Apple support document, quotes the line that Safari “lets you browse the web and includes a new Cooking experience that auto-detects supported recipes, reformatting them with step-by-step instructions and inline timers” (MacRumors). That is Apple’s wording, passed on by the outlet rather than independently tested.
9to5Mac’s Chance Miller, in a review published on November 12 after what he calls ten days with the device in his kitchen, writes that opening a recipe in Safari “gives you the option to convert it into a dedicated cooking interface,” and that a recipe found on an iPhone can be handed off by holding the phone in front of HomeView. He says he tried the feature “with recipes of varying lengths from multiple different websites without any major problems,” but also that “it does struggle if a website splits the recipe into multiple pages.” The review does not say why, and does not mention schema.org or JSON-LD; WebKit’s post does not mention multi-page recipes.
In MacRumors’ tidbits roundup, guest controls let the owner decide what guests can access, and “Safari can be turned on or off, or adult websites can be blocked.”
Two sets of numbers
Apple’s specifications page lists a “1088-by-1088-pixel resolution at 220 ppi” for the 7-inch display, a figure 9to5Mac’s review repeats. WebKit’s testing suggestion is a 448×364 viewport. These are different measures, a panel resolution and a test viewport, and none of the cited sources states how the second relates to the first, so the Herald does not reconcile them.
What we don’t know
- None of the cited sources gives the Safari or WebKit version running on HomeView. Apple’s product page and the release notes relayed by MacRumors refer to HomeView software version 27.2.
- None of the cited sources says what Safari’s cooking experience does with a recipe page that lacks the schema.org markup WebKit describes. MacRumors, quoting Apple, says it detects “supported recipes” without defining the term.
- WebKit’s post gives no example user-agent string. Neither MacRumors nor 9to5Mac, the press outlets cited here, refers to WebKit’s post in the pages cited.
WebKit also published a Safari 27.1 post for iPhone Duo on October 23, 2026, previously reported by the Herald.