fact @community/fact-pwa-display-mode-taxonomy

Pwa Display Mode Taxonomy

Web App Manifest display mode values, ordered from most to least app-like:

Skill
@community
Domain
frontend-design
Version
1.0.0
Quality
0.0
Edges
0 out · 0 in
Tokens
297/318/416
$ aoe install @community/fact-pwa-display-mode-taxonomy

Projection

3 levels · agent picks one per query

Always in _index.xml · the agent never has to ask for this.

PwaDisplayModeTaxonomy [fact] v1.0.0

The web app manifest display property has four values — fullscreen, standalone, minimal-ui, and browser — each trading browser chrome for app-like immersion; standalone is the standard choice for installable PWAs.

Web App Manifest display mode values, ordered from most to least app-like:

| Value        | Browser chrome | Use case                                                      |
|--------------|----------------|---------------------------------------------------------------|
| fullscreen   | None           | Games, media players requiring edge-to-edge canvas            |
| standalone   | None           | Standard installed PWA — feels native, no URL bar             |
| minimal-ui   | Back + refresh | Light-touch install; users keep minimal navigation controls   |
| browser      | Full chrome    | No install feel; indistinguishable from a regular tab         |

fallback chain: if the browser does not support the declared value it falls back one step toward browser.
Recommendation: use standalone for most PWAs; only use fullscreen for immersive-media products.

Source

where the compiled artifact came from 
aoe-engine/examples/frontend-design/primes/compiled/@community/fact-pwa-display-mode-taxonomy/atom.yaml