Ledger Live Integrations – Ledger Developer Portal

Author: Ledger Developer Portal • Format: HTML presentation

Overview

This presentation explains the primary integration paths into Ledger Live, outlines developer prerequisites and workflow, and points to official resources and examples for implementing Accounts (blockchain support), Live Apps (Discover), and Device Apps (on-device).

Why integrate with Ledger Live?

Integrating with Ledger Live lets your users access your protocol or dApp securely through Ledger’s trusted UI, leveraging hardware-backed signing and Ledger’s wide user base. Integrations can surface in Ledger Live’s Accounts, Discover (Live Apps) or as on-device Device Apps when low-level signing is required.

Integration Paths (high-level)

Accounts / Blockchain integration

What it is

Accounts integration adds native support for a blockchain and its tokens into Ledger Live’s Accounts section, allowing users to create accounts, view balances, and sign transactions with Ledger devices.

When to use

Use this path when you need protocol-level account management (balances, history, sending/receiving) and tight device signing behavior.

Live Apps (Discover)

What it is

Live Apps are web-based dApps surfaced within Ledger Live’s Discover tab. They communicate with Ledger Live via the Wallet API and Ledger Services Kits to interact with users and the connected device without shipping on-device firmware.

Device Apps

What it is

Device Apps run on Ledger hardware (BOLOS apps written in C/Rust) and are required when transactions need specialized, protocol-specific device-side logic or plugins. These require submission to Ledger’s Device App review and delivery process.

Developer Workflow & Best Practices

1. Read the submission & deliverables guidance

Before starting device-level work, consult submission requirements and documentation packaging expectations: description, installation, setup, and support details.

2. Start local dev and use the monorepo

Ledger maintains a monorepo for Ledger Live and related JS libraries; running the dev server locally and linking packages speeds iteration and testing across desktop and mobile builds.

3. Implement security and UX parity

Match Ledger’s UX patterns and ensure cryptographic flows keep user funds safe — prioritize minimal prompts on-device and clear instructions in the Host app.

4. Test across desktop & mobile

Ledger Live shares much code between desktop and mobile. Validate flows on both platforms and enable developer mode when needed for debugging.

Common Technical Components

Wallet API & WalletAPIServer

Live Apps use a JSON-RPC Wallet API to interact with Ledger Live and the connected device. There is a server pattern for bidirectional communications and local testing tools for development.

Device App Kit & SDKs

On-device development uses the Device App Kit and follows specific deliverables for review. For JavaScript ecosystems, Ledger’s JS tooling is centralized in the monorepo.

Practical Checklist (quick)

Before you begin

Testing & release

Enable Developer Mode in Ledger Live for debugging, validate signing flows on actual devices, and submit the required deliverables for review.

Official resources & references (included below)

Use the official links below for authoritative, up-to-date developer documentation, tutorials, and code examples.