The W3C Technical Architecture Group argues that installing websites is now a core browser capability and must be made easy and obvious to users and authors. Installable sites provide a persistent presence and native-like launch behavior while remaining inside the web’s security and permission model. Variability across browsers has confused users and driven authors toward native apps, so the expectation is that general-purpose browsers offer clear, discoverable install affordances and that installation support be broadly available across engines and OSes. The finding focuses on same-origin installs (cross-origin installs are not widely supported) and excludes specialized user agents like kiosks or embedded web views.
Concrete expectations require user agents to present an obvious, labeled install option reachable without deep menu navigation, and to inform users what installation does. Operating systems must give third-party browsers equal access to mechanisms for adding sites to home screens, docks, or launchers, and must launch installed sites with the browser that performed the install so session state (e.g., logins) is preserved. Programmatic same-origin install APIs are encouraged only if they invoke the browser’s own install flow; user agents must retain control over timing, eligibility, and abuse mitigation. The recommendation reflects past experience (manifests, beforeinstallprompt) and rejects spontaneous prompts while urging vendor exploration of manifest-first APIs.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.