Distribution
Store and App Installation
In Moss today, Store owns discovery and install entry, and the wallet turns that into an actual usable app.
3 sectionsstore-installation
01
What the Store Does
Store is more than a frontend catalog. It works with the wallet runtime as the installation entry point.
In the current model, `LogicRegistry` handles app publication and install entitlement, `installApp(wallet, logic)` records that an account installed an app, and wallet-side `enableApp(app)` makes the installed app actually available inside the wallet.
- Apps are registered into the Store path first.
- Users install from Store instead of manually trusting arbitrary addresses.
- Installation and wallet-local enablement are separate states.
- There is no separate NFT-license contract in the current model.
02
Why Installation Goes Through Store
- Ordinary users should not need to reason about raw contract addresses before installing an app.
- Store defines the normal product path and reduces arbitrary-address installation risk.
- Install state becomes verifiable on-chain instead of a frontend-only memory of 'installed'.
- The wallet still needs to enable the app before it becomes visible inside the Runtime.
How to read installation now
Publication, installation, and enablement are different things in Moss. Store handles installation, the wallet handles enablement, and actual usage happens inside the Runtime.
03
What the User Actually Feels
- Open an app detail page in Store.
- Install it for the current wallet.
- Let the wallet enable it as a Runtime-available app.
- Return to the Runtime and keep using it there.