Product SDK
createApp call gives you wallet, storage, and Bulletin in a single object. Leaf packages handle chain clients, transactions, keys, and crypto.Install
pnpm add @parity/product-sdkWho this is for
You’re building a Polkadot app that runs inside a host. That could be Polkadot Desktop, Polkadot Mobile, a web host like dot.li , or a custom host you’re embedding the test SDK into. You want wallet, storage, and Bulletin access without hand-wiring PAPI clients, CID computation, and signer bridges for every project.
createApp gives you that common surface in one call. The leaf packages cover everything else: PAPI chain clients, transaction submission and batching, key derivation, crypto primitives, ink! contract interactions, statement store pub/sub. Each leaf package works on its own, so you can install just the ones you need.
For tooling or scripts that run outside a host (plain Node, a browser tab with no host around it), skip createApp and import leaf packages directly. createApp requires a host and will throw on boot without one.
What you get
Unified entry
createApp wires wallet, storage, and bulletin APIs behind a single object.
Host-integrated
Runs inside Polkadot Desktop, Polkadot Mobile, or a web host like dot.li. Accounts, storage, and permissions come from the host, so there's no wallet extension to wire up.
Typed chains
PAPI-generated descriptors for Polkadot and Kusama Asset Hub, Paseo Asset Hub, Bulletin, and Individuality. Bring your own.
Tx lifecycle
Submit, watch finalization, batch, retry. Structured errors, no opaque failures.
Multi-provider signing
Host provider in production, Dev provider for local tests. One SignerManager across both.
Content-addressed storage
Upload, pin, and retrieve via the Polkadot Bulletin Chain with CID computation.
Where to go next
- Installation: umbrella package, leaf packages, and environment requirements
- Quickstart: connect the wallet and read storage in under 20 lines
- API Reference: every exported class, function, and type across all packages