Properly dressed for each screen.

The web client is installable as a progressive web app, supports keyboard and touch, and keeps a deliberate offline shell. Account and purchase operations reconnect before changing authoritative state.

The candidate is built for current major browsers; Safari, Firefox, keyboard and assistive-technology matrix sign-off remain release checks. A text-first route remains usable when decorative motion or a service worker is unavailable.

The iOS release candidate has native navigation, secure credential storage, reduced-motion support, deep-link routing and the shared account product. It is not yet offered as a production App Store purchase.

Store products, server-side receipt verification, refund notifications, restore testing and Apple review must all pass before the App Store claim becomes live.

The Android release candidate has platform navigation, secure session storage, deep-link routing and the shared account product. It is not yet offered as a production Google Play purchase.

Play products, server-side receipt verification, real-time revocation handling, restore testing and Google review must all pass before the Play Store claim becomes live.

Web account state already has a server-backed entitlement, favourites and completion history. Native clients use the same authenticated APIs during release testing.

Cross-store entitlement reconciliation remains a launch gate, not a promise inferred from a local demo. The status on this page changes only after both store paths are verified end to end.