Boards work on iPads in airplanes. What is your mobile and offline story — native apps or another responsive website?

The full executive answer

Our choice is a progressive web app — PWA — rather than native apps, and it is a considered one. A PWA is a web application that installs to the home screen, launches full-screen like an app, and keeps working offline via a service worker — a background component, standardised by the W3C, that caches the application and its data on the device. For the board-member-on-a-plane scenario, that means previously loaded briefings and dashboards remain readable with no connectivity, and the platform's document exports — the board pack as PDF or PowerPoint — are by nature offline artefacts once generated.

Why not native: two more codebases, two app-store review cycles gating every release — which would break the merge-to-production delivery model I have described — and no access advantage for what is fundamentally a reading-and-deciding product rather than a camera-and-sensors product. One codebase serving desktop, tablet and phone keeps every user on the same version on the same day.

Also in the experience layer: realtime collaboration — multiple executives in the same assessment see one another's activity live rather than overwriting each other. Roadmap honesty: offline today is read-and-review resilience, not full offline authoring with conflict resolution — that is a deliberate scope line, and deepening offline capture is demand-driven roadmap.