Second app surface

A world-class PWA layer without touching the Flutter client.

BioPay now ships as two aligned products: the existing Flutter mobile app and an installable web companion built for offline quick pay, Add to Home Screen, background sync, share targets, and crawlable public pages.

Open Quick Pay iOS install guide

Install becomes available after user engagement.

PWA outcomes

What the BioPay PWA adds

Install path Chrome prompt plus Safari share-sheet guidance

Offline mode Cached routes, IndexedDB shortcuts, queued sync work

Distribution Manifest, shortcuts, screenshots, badges, share target

Security posture Headers, CSP, Permissions-Policy, no token storage in localStorage

Quick-pay routing

Compose a reusable USSD flow, generate a QR instantly, and deep-link clean URLs into the installed app shell.

Offline shortcut pack

Save payees in IndexedDB, browse them offline, and keep field agents moving even when bandwidth drops.

Contextual engagement

Install and notification prompts appear only after the app has already delivered value, never on first load.

Performance and SEO

Public pages remain crawlable while the app shell stays installable.

The landing page, privacy policy, and terms route are static HTML documents with route-level metadata, canonical URLs, and social tags. The interactive PWA lives under /app/ where deep links, service workers, and share targets matter most.

Platform strategy

The Flutter app remains the native runtime.

No Flutter UI contract changes are required. The PWA complements it with lightweight install flows, public discoverability, and browser-native resilience patterns that the report expects.