Packages

Use this hub when you need to decide which Legato package to adopt first.

For the canonical package support view, use the Compatibility and Support Matrix.

Package chooser

If your first risk is…	Start with	Why
Shared playback semantics across layers (events, snapshots, invariants)	@ddgutierrezc/legato-contract	You stabilize app vocabulary and behavior assumptions before runtime wiring.
Native playback runtime integration in a Capacitor app (commands, media session, listeners)	@ddgutierrezc/legato-capacitor + @ddgutierrezc/legato-contract	You get runtime APIs while keeping the same shared contract model across app layers.
Native playback runtime integration in an Expo React Native app	@ddgutierrezc/legato-react-native + @ddgutierrezc/legato-contract	You get Expo Modules runtime bindings plus explicit host and parity evidence boundaries.

Package guides

Contract package

Contract-only surface for tracks, snapshots, events, errors, capabilities, and invariants.

Capacitor package

Capacitor runtime integration for audioPlayer, mediaSession, listeners, and sync helpers.

React Native package

Expo Modules runtime binding with parity-scoped API, host boundaries, and evidence-guided validation.

Before you install

1. Pick the package from your integration risk, not from future guesses.
2. If you choose Capacitor, keep @ddgutierrezc/legato-contract aligned to the same supported line.
3. Review Releases before upgrades so you can validate version matrix and user impact in your CI.
4. Confirm final compatibility assumptions in the Compatibility and Support Matrix.

If you want an opinionated onboarding sequence, continue with Golden Paths.