Review web installation and controlled store packaging.
CustodyForge declares an installable web app configuration. Installation on the actual deployment still requires browser verification. Microsoft, Google, and Apple submissions require owner accounts, signing, screenshots, device testing, and review approval.
Company enrollment requires a verified administrator. Customer workspace access requires a paid subscription and an active company account with assigned permissions.
Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release.
Install CustodyForge
CustodyForge can run from the browser and install like an app on supported phones and computers.
Open this page in Chrome, Edge, or Android Chrome to install CustodyForge from the browser menu.
Store configuration checklist
What has to happen before the app appears in public stores.
The web app is the source of truth. Store packages should point to the production web app, keep the same authentication and billing controls, and use store listings as distribution channels.
The declared manifest and URLs are evaluated for browser-install packaging. A supported-browser install on the actual deployment still requires verification. Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release.
The declared PWA configuration is evaluated for Microsoft Store packaging. Publisher identity, listing assets, deployment checks, and Store review still require verification. Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release.
Google Play needs a Trusted Web Activity package, Play Console owner access, signing, screenshots, privacy details, and domain verification before submission. Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release.
Apple distribution needs an Apple Developer account, an iOS wrapper build, device testing, privacy answers, screenshots, support URL, and App Review approval. Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release.
An HTTPS URL is declared; current domain and deployment verification remain required.
Web app manifest is generated from the app.
Icon, theme color, standalone display, and app scope are declared.
Formal store submissions still require owner accounts and review approval.
Store-readiness statuses describe declared configuration only. They do not verify a live deployment, native app or store approval, or paid customer release. Verify browser install on the actual deployment before promoting it; confirm Microsoft Partner Center ownership before packaging a store submission.