Apple's Kitchen HomeView Slammed as a CarPlay Appendage

Apple is brewing a smart home screen device designed for the kitchen, but a recent episode of The Verge's podcast Vergecast revealed a controversial developer policy: any CarPlay app will be forced to support this new screen (HomeView), with virtually no option for developers to opt out.

The "Strong-Arm" Logic of the Developer Terms

According to the discussion on the show, Apple explicitly states in its developer terms that if you build a CarPlay app, it must be able to run on HomeView — no room for negotiation. In the host's own words, "you have almost no ability to turn it off" — once an app enters the CarPlay ecosystem, it automatically shows up on this kitchen screen.

This binding strategy left both hosts baffled. Their core question: why is Apple's answer to an entirely new hardware category simply to port over CarPlay apps, rather than encouraging developers to rethink interaction for this new context?

CarPlay is Apple's in-car system solution introduced in 2014, allowing an iPhone to project specific apps (such as navigation, music, and calls) onto a car's head unit screen. Its app ecosystem is built on MFi (Made for iPhone) certification and a dedicated CarPlay app category. Historically, Apple has used similar licensing terms to rapidly expand CarPlay's coverage, but forcing an app category to be reused across devices is not its usual practice. HomeView's mandatory binding is mechanically closer to treating the CarPlay app category as a "universal screen-mirroring app" rather than an independent category reviewed separately for new hardware.

New Hardware Category, Old Logic

From a product positioning standpoint, a shared kitchen screen should be an entirely new interaction scenario — used by multiple people, placed in a common area of the home, with usage contexts completely different from a phone. The hosts pointed out that this was a prime opportunity for Apple to rally developers to build "genuinely cool, interesting, multi-user" apps — and that it should be "the number one priority on the list."

But the reality is that developers are already overwhelmed by Apple's numerous new requirements: iPhone Duo needs adaptation to new screen sizes, rumors of a touchscreen Mac are circulating, and now there's HomeView on top of it all. Asking developers to also innovate for the kitchen scenario at this point is inherently unconvincing — especially when Apple's actual approach is to give them no choice and simply mandate CarPlay app inheritance.

A Market Ceiling Locked by the iPhone Ecosystem

The hosts raised a second, more fundamental concern: binding HomeView to CarPlay apps means the device's app supply and user base are locked into a subset of iPhone users. Apple has indeed sold a massive number of iPhones, and any company would love to reach a "significant portion" of that enormous base — but the problem is that this product is destined from the start to only appeal to people already in the iPhone world.

In the show's words: "I can't imagine someone outside the iPhone ecosystem seriously considering this product." This creates a self-reinforcing loop: the app ecosystem depends on iPhone users, the product's appeal depends on iPhone users, and the new user groups that might have been won over by a kitchen smart screen are shut out.

The so-called "iPhone user subset" in this discussion actually refers to users who simultaneously meet the following conditions: owning a relatively new model, having subscribed to or used CarPlay-related apps, and being willing to buy yet another screen for the home. Apple's global active iPhone user base numbers in the billions, but the proportion actually using CarPlay apps is far lower than the total — so the "significant portion" remains a group narrowed by multiple conditions. This determines that HomeView's addressable market has a structural ceiling from day one.

Editorial View: Convenient Inheritance Is Not Scenario Innovation

From an engineering efficiency perspective, letting CarPlay apps automatically adapt to HomeView does lower the barrier to entry for developers and guarantees a roster of apps at launch. But the cost is sacrificing the imagination of this new category — a shared screen in the kitchen should derive its value from experiences tailored for family collaboration and multi-user interaction, not from another resizing of phone apps onto a smaller display.

More subtly, there's the developer relationship. When Apple is simultaneously pushing multiple new hardware directions, using mandatory terms to bundle CarPlay and HomeView may be convenient in the short term, but in the long term it could erode developers' enthusiasm for new platforms. After all, developers are willing to invest in a promising new category only if they can see a matching product logic — not be told by a clause that "your app is already compatible."

While this discussion didn't include an official Apple response, the questions it raises are worth attention: when a new hardware's app strategy is merely an extension of the old ecosystem, is the category actually innovating — or just adding to the existing ecosystem?

From a platform economics perspective, mandatory inheritance can be seen as a "cold start" strategy: new hardware fears nothing more than a lack of apps at launch, and letting the existing app catalog auto-populate solves the "is there anything to use" problem in the shortest time possible. But this strategy typically only applies to accessory products, not to independent categories that carry high expectations. If Apple wants HomeView to become a home hub, it needs to offer differentiated incentives beyond inheritance — such as exclusive APIs, revenue-share perks, or dedicated recommendation slots — otherwise developers will lack the motivation to invest in new interaction paradigms.

One-line Summary

Apple forces CarPlay apps to support HomeView, criticized for stifling kitchen screen innovation.

Paragraph Summary

The Verge's Vergecast podcast discussion points out that Apple requires all CarPlay apps to support its upcoming kitchen smart screen HomeView, with virtually no opt-out for developers. Critics argue that a shared kitchen screen should be a new category encouraging multi-user, multi-interaction innovation, yet Apple chose to directly port CarPlay apps rather than guide developers to redesign. Meanwhile, developers already face mounting pressure from iPhone Duo screen adaptation, touchscreen Mac rumors, and more, with HomeView adding further burden. More fundamentally, the strategy locks app supply and user scale into a subset of iPhone users, creating a self-reinforcing loop that struggles to attract new users outside the ecosystem. Mandatory inheritance lowers integration costs but may drain developer enthusiasm for the new platform.