App Development Reference¶

Introduction¶

This is the technical-depth companion to the App Development how-to guides. Where the guides walk you through tasks step by step, this section explains what each component is, how it works, and where its limits are — the level of detail you need when integrating against the surface.

A Polkadot Product is a sandboxed application you build that runs inside one of the Polkadot Apps. The Host it runs in mediates everything sensitive, including signing, chain access, storage, and outbound requests, through a protocol called TrUAPI, and the Product talks to Polkadot's on-chain infrastructure through the SDK and the Host. This reference is organized along those axes: Hosts, the TrUAPI protocol between Host and Product, and the infrastructure components Products consume.

Architecture¶

Your Product sits at the top of a layered stack. You write the Product itself; everything below — the Product SDK that exposes typed methods, the Polkadot Apps that load and sandbox your Product, and the underlying chains, decentralized storage, and name service — is provided by the platform. The Host (whichever Polkadot App is loading your Product) mediates every interaction through TrUAPI and prompts the user for anything sensitive.

Hosts¶

Hosts are the runtime containers that load and run Polkadot Products:

• Polkadot App: The mobile Host. Holds the user's signing key, runs Proof of Personhood, and is the canonical signer for every transaction a Product submits anywhere in the Triangle.
• Polkadot Desktop: The desktop Host. Loads Products by .dot name, mediates signing requests to the paired mobile App, and exposes the Host API surface to the Product running inside it.
• Polkadot Web: The web Host (dot.li). Loads Products in a browser sandbox and documents the visiting flow, shield states, and on-chain polkadot.com integration.

Protocol¶

The TrUAPI reference documents the protocol between Hosts and Products: the conceptual sandbox model, the 11 method groups (TrUAPI Calls, Permissions, Local Storage, Account Management, Signing, Chat, Statement Store, Preimage, Chain Interaction, Payment, Entropy), the versioning model, and the package reference table.

Infrastructure¶

Per-component reference for the on-chain infrastructure Products consume:

• Bulletin Chain: Content-addressed storage with explicit authorization, chunked uploads, time-bound retention, and renewal.
• Statement Store: Gossip-distributed, signed statements on the People Chain for real-time signaling between users.
• dotNS: The .dot name system, including PopRules pricing, the contract architecture, and the registration flow.
• Proof of Personhood: The Ring-VRF mechanism and the per-pallet surface (people, game, score, identity, universal basic capacity, coinage).
• HOP: The cross-chain hop protocol.

Skills¶

The product-sdk skills reference documents what skills exist, what each one does, and how to use them inside your Product workflow.

Where to Go Next¶