Platform
Moss Runtime
In Moss, Runtime is not a side layer. It is the environment where apps actually run and keep being used.
What Runtime Does
Moss Runtime is the environment where apps run inside Moss Wallet. Its job is not only to show balances or an address. Its job is to host app execution, asset capabilities, and installed entry points.
Users do not start by opening one standalone app and then connecting a wallet. They enter the Runtime first, then invoke asset capabilities, installed apps, and account settings from there.
- It is the shared app runtime.
- It unifies assets, identity, apps, and settings.
- It pulls permission checks and execution context into one environment.
- It makes installed capabilities appear directly in the Runtime instead of living on external sites.
Why Runtime Matters
Without a shared Runtime, every app would have to rebuild asset handling, permissions, and interaction flow on its own. Moss flips that model: establish the Runtime first, then let apps reuse the same context.
That makes payments, tokens, NFTs, installation state, and automation persist inside one Runtime instead of being fragmented across different pages and product entries.
- Asset capabilities do not need to be reimplemented by each app.
- Permissions and install state can persist inside the Runtime.
- Installed apps become part of the Runtime.
- The user experiences one continuous environment instead of disconnected sites.
Design reading
The key move is not making a wallet look more like an app. It is providing a Runtime where apps can live and keep running over time.
What Gets Organized Inside the Runtime
A real Runtime has to place several kinds of capabilities inside one environment: wallet-native capabilities, installed app capabilities, the wallet's own asset state, and long-lived settings and security entry points.
That is why the user experience is framed as what this Runtime can do, not which site I have jumped to.
- Wallet-native capabilities: default abilities such as token and NFT management.
- Installed apps: app entry points that appear after Store installation.
- Account state: address, assets, permissions, sessions, and executable scope.
- Settings and security: network, recovery, and permission management.