Reach
Shipped. Installable spaces, offline viewing, location-aware delivery and nearby notifications are built and live; only server-sent Web Push (v2) is still arriving in phases. What follows is how it works, not where it’s headed.
Everything else in this documentation is about how content is stored, compiled and served. Reach is about the last step: how that content actually arrives in front of a visitor — and increasingly, that visitor is holding a phone.
Reach is organised in three layers, and the layering matters for understanding both how things work and where their limits come from.
The PWA app. Installable & offline covers delivery: every URL is installable, content stays available offline, and the same machinery serves a space site and the cross-space account app. This layer is about getting content onto the device.
The capabilities. Geolocation and Notifications are device capabilities: things the browser can do for a site, but only with the visitor’s explicit consent. Each page explains how its consent works, what the capability provides, and — importantly — where the operating system draws lines that no website can cross. More capabilities will join this family over time (camera, microphone, audio) following the same pattern: one consent model, one page each. The shared consent model that all of them obey is centralised in Device consents.
The behaviours. Proximity is the first of a third kind: not a capability itself, but a composition of capabilities into something meaningful — location plus notifications becomes “tell me when I’m near a place.” Behaviours are where the platform’s content model and the device’s capabilities meet. More will follow (reminders for upcoming events is a natural next one), each built from the same capability building blocks.
Reach also has an audience that never installs anything: crawlers. Search & indexing covers how a space announces itself — a self-maintaining sitemap, edge-generated robots, and watch pages that make media findable.
The mechanics of all three layers lean directly on choices made far upstream, in the compiled graph and the file-based core.
How consent works
Every device capability follows one model — granted to the device and browser (never an account), requested only on your own gesture through the browser’s native prompt, per-capability and revocable, degrading quietly when withheld. That shared model, and the set of consents available, is the subject of Device consents.