Lack of WebKit webview support in Apple's tvOS poses problems for porting many apps that use webviews to display web widgets and pages
Since Apple announced the new Apple TV … Tweets: Andrew Savory / @savs : No Webviews on the new AppleTV: http://medium.com/... We've regressed a long way since 2007: http://www.apple.com/... Logan Turley / @lstreetjournal : Apple TV Without Webviews: Companies can no longer leverage a universal HTML5/CS/JS-based UI for multiple platforms http://medium.com/... Steven Sinofsky / @stevesi : Apple TV and no Webview http://medium.com/... Makes sense: no way to reliably interact with webview UI. Been tried & failed *many* times. Steve T-S / @stroughtonsmith : @dlpasco the fun part: WebKit, UIWebView, etc, are all there, just they removed the headers from the SDK. Now count as private API @greatdanehugs : @stshank this isn't that controversial. Web devs also shut out from Apple Watch...watchkit is native only. Android WearSdk also native only Daniel Pasco / @dlpasco : We looked at moving NetNewsWire to Apple TV, but the lack of webviews was a show stopper. Will impact others as well http://bit.ly/1Kg6SBn
Context & Ripple Effects
The new Apple TV's SDK shipped without WebKit webviews, closing off the trick many iOS developers relied on: one universal HTML5/CSS/JS interface shared across iPhone, iPad, and now the living room. As Steven Sinofsky noted in the reaction, there is no reliable way to interact with webview UI from a remote control — an approach that has been tried and failed repeatedly — but that still leaves developers with substantial rewrites rather than ports.
This was an early data point in a longer Apple posture toward web runtimes on its platforms: years later the company would refuse 16 new Web APIs in Safari over fingerprinting concerns [[a:955200]], restrict PWAs ahead of the EU DMA's browser-engine mandate [[a:849219]], and keep pushing its own curated TV app with Channels as the front door to television content [[a:941664]] rather than web-rendered widgets inside third-party apps.
First-order effects
- Developers whose apps display web pages or web widgets cannot port them to the new Apple TV at all — they face full native rewrites on tvOS or skipping the platform, and NetNewsWire-style readers and any HTML5-widget app are directly blocked.
- Cross-platform teams lose the ability to leverage a single HTML5/JS codebase for Apple TV, raising their per-platform engineering costs immediately.
Second-order effects
- Competing TV platforms that do support webviews become relatively more attractive targets for the same apps, pressuring Apple to justify the omission purely on interaction-quality grounds.
- Content and media partners get pushed toward Apple's own distribution surface — the TV app and its Channels service — instead of embedding web-based experiences in their own apps, reinforcing Apple's gatekeeping position it had already strained with cable providers and networks.
Third-order effects
- If the pattern holds — no webviews on tvOS, Safari refusing contentious APIs, PWA limits ahead of DMA — web runtimes on Apple platforms shrink to what Apple alone permits, converting rendering-engine access into a regulatory question rather than a technical one.
- The structural outcome is a stricter SDK governance gap: every Apple platform defines its own allowed UI substrate, and developers budget for native implementations everywhere rather than assuming web technology travels.
The trend: Apple is progressively walling off web runtimes across its platforms — from tvOS webviews to Safari API refusals and PWA limits — forcing native development and steadily drawing regulator attention.