Web Application Manifest
Generated by GPT-5-miniExpansion Funnel Raw 59 → Dedup 0 → NER 0 → Enqueued 0
| Web Application Manifest | |
|---|---|
| Name | Web Application Manifest |
| Developer | Google LLC; originally spec proposed by Alex Russell and contributors from W3C community groups |
| Released | 2014 |
| Latest release | Living Standard |
| Platform | World Wide Web |
| License | Open web standards |
Web Application Manifest The Web Application Manifest is a W3C-aligned JSON-based metadata file that enables Mozilla, Microsoft, Apple Inc., Google, Samsung and other vendors to present Progressive Web Apps with native-like installability across Android (operating system), Windows 10, iOS and desktop environments. It complements standards from WHATWG, HTML5, Service Workers and Open Web Platform specifications to give webpages discoverable metadata for Chrome, Firefox, Safari, Edge and other user agents.
Overview
The manifest defines machine-readable information such as name, icons, start URL and display mode referenced by user agents like Chrome and Firefox during installation and presentation, integrating with ecosystems such as Google Play (progressive distribution), Microsoft Store, Apple App Store workflows for hybrid packaging, and enterprise deployment scenarios used by IBM and Microsoft Corporation. Origins and installability checks intersect with work from W3C Web App Manifest Community Group, WHATWG, and specifications tied to web capabilities demonstrated at events like Google I/O and WWDC.
Specification and Format
The JSON schema follows conventions influenced by RFC 8259 and employs fields standardized through collaboration among browser vendors, contributors from Mozilla Foundation, Microsoft Corporation, and platform stakeholders including Samsung, Opera Software, and Intel Corporation. The manifest file is linked via an HTML element within HTML5 documents served from origins subject to HTTPS rules defined in specifications shaped by IETF. The living standard is maintained alongside related specs for Service Workers, Web App Install Banner heuristics, and Payment Request API interop.
Key Properties and Usage
Common properties include "name" and "short_name" for display text used by Android launchers and Windows tiles; "icons" arrays referencing PNG or SVG assets used by Chrome and Edge; "start_url" that determines navigation state for session restoration on Firefox; "display" values ("standalone", "fullscreen", "minimal-ui", "browser") that map to UX models seen in iOS and Android shells; and "scope" that constrains navigation and origin semantics relevant to Same-origin policy discussions handled by W3C and IETF. Developers employ "theme_color" and "background_color" to harmonize with platform chrome on Android, Windows, and macOS, often coordinated with design systems from Material Design and guidance from Human Interface Guidelines at Apple Inc..
Installation and App-like Behavior
User agents compute installability using manifest presence alongside Service Worker registration and secure contexts (HTTPS), mirroring practices championed at conferences such as Google I/O and Microsoft Build. On Android, Chrome may present an install prompt derived from manifest metadata and engagement heuristics; on Windows 10, Edge and Chromium can generate PWAs that appear in the Start menu and be packaged for the Microsoft Store. On iOS, Safari uses a subset of manifest features supplemented by legacy meta tags from Apple Inc. documentation. Packaging initiatives like Trusted Web Activity and tools from Microsoft and Google enable distribution through native stores while preserving manifest-driven startup behavior.
Security and Privacy Considerations
Manifest-driven behaviors interact with origin-bound security models overseen by standards bodies such as IETF and W3C; requirements for HTTPS, integrity of referenced icon assets, and same-origin constraints mitigate spoofing and clickjacking risks documented in advisories from CERT and research groups at USENIX and ACM. Privacy implications arise when manifests enable heuristics for engagement or allow deep-linking into authenticated flows, issues debated at venues like DEF CON and in publications by Electronic Frontier Foundation. Platforms may treat manifest metadata as user-visible branding, so supply-chain controls and code-signing practices from vendors like Google LLC and Microsoft Corporation are relevant to trust and provenance.
Browser and Platform Support
Support varies: Google Chrome and other Chromium-based browsers implement a broad manifest subset and install flows; Mozilla Firefox supports core properties with differing UX; Apple Safari on iOS implements limited manifest semantics and relies on Apple Inc.-specific meta tags for parity; enterprise browsers and custom shells from Samsung and Opera Software exhibit vendor-specific behaviors. The cross-vendor evolution is tracked by W3C Web App Manifest Community Group, bug trackers at Chromium and Mozilla, and interoperability reports produced by WebPlatform-adjacent projects and standards evangelists from Google and Microsoft.