Adding a Live App to the Discover section
A Live App is a third-party application that runs inside Ledger Wallet and reaches the user’s Ledger signer through the Wallet API. The Discover section is where users find and launch them.
This page explains the two technical paths Ledger supports for building a Live App, when to choose each, and how the business and development tracks fit together.
Business track: getting an invitation
Discover listings are invitation-only. To open the conversation, fill in the partner intake form and email discover@ledger.fr. Until Ledger confirms a slot, you can still develop and test against your own manifest in Developer mode.
Two integration paths
Live Apps integrate with Ledger Wallet through one of two mechanisms. They are not interchangeable: each is suited to a different kind of application.
dApp Browser (EVM-only)
The dApp Browser hosts your existing web dApp inside a Ledger Wallet WebView and injects an EIP-1193 provider that signs through the Ledger device. You keep your current frontend and add a manifest that tells Ledger Wallet how to load it.
Wallet API (any chain)
The Wallet API gives a Live App typed access to accounts, currencies, messages, transactions, and storage on any supported chain: Bitcoin, Ethereum, Solana, Cosmos and many more (the full list of families covers 30+ chains). Live Apps embed the @ledgerhq/wallet-api-client and call methods such as client.account.list() directly, instead of going through a generic EVM provider.
Choosing between them
| Question | Choose dApp Browser | Choose Wallet API |
|---|---|---|
| Is your dApp EVM-only? | yes | no |
| Do you already have a working web dApp using EIP-1193? | yes | optional |
| Do you need fine-grained API surface (specific signing flows, custom transactions, storage)? | no | yes |
| Are you targeting non-EVM chains (Bitcoin, Solana, Cosmos…) ? | no | yes |
| Required language/skills | JS/TS | React + JS/TS |
If the answer is “yes” in both columns (EVM dApp wanting Wallet API granularity), pick the Wallet API.
Development track
Whichever path you pick, the development sequence is the same:
- Make sure your app can talk to a Ledger device. This is generally already the case for an existing dApp, but if it is not, use the Device Management Kit.
- Build the integration. Either customize your dApp for the Browser and write a manifest, or pull in the Wallet API client (or the React bindings) and call the modules you need.
- Add Clear Signing. For EVM contracts, prefer ERC-7730 metadata; fall back to a plugin only if your contract data does not fit. For non-EVM chains, talk to the Ledger team during your invitation conversation.
- Test locally with Developer mode. Enable Developer mode in Ledger Wallet and load your manifest as a local app. For Wallet API apps, the Wallet API simulator lets you run the app in a browser without Ledger Wallet at all.
Required skills
| Step | Skills |
|---|---|
| Wallet API integration | React + JavaScript/TypeScript |
| dApp Browser integration | JavaScript/TypeScript |
| ERC-7730 Clear Signing | JSON authoring (no on-device code) |
| Plugin (only when ERC-7730 isn’t enough) | C, Ledger OS, and the Ethereum Plugin SDK |