` and submit through `polkadot-api` directly because `@parity/product-sdk-cloud-storage` is intentionally a narrow surface.\n\n!!! warning\n Each renewal generates a new `(block, index)` pair. Track the values from the latest `Renewed` event for any subsequent renewal. Using the original values after a renewal will fail. The Bulletin Chain pallet does not emit retention events ahead of expiry; your Product needs its own scheduler (cron job, queue, or background worker) to renew before the storage expires."}
{"page_id": "apps-build-store-data-on-chain", "page_title": "Store Data on Chain", "index": 9, "depth": 2, "title": "Cross-Chain Storage from People Chain", "anchor": "cross-chain-storage-from-people-chain", "start_char": 14159, "end_char": 15539, "estimated_token_count": 278, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:c74846e1bcabfa44f738cbe124293b5a57d0df0e9aa5949841c4075afcc9dc98", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Cross-Chain Storage from People Chain\n\nPoP-gated identity lives on the People Chain. When a Product needs to attach content to that identity (for example, a PoP-Lite communication identifier or a verified-person attestation), the store has to be initiated on People Chain and dispatched to the Bulletin Chain via XCM.\n\n!!! warning \"Provisional\"\n The cross-chain path is in flight. The flow described here is the intended shape; XCM message format and authorization model may change before the path is finalized.\n\nThe flow has three phases:\n\n1. People Chain authorizes your account against its local `transactionStorage` instance (authorization on People Chain is independent of your Bulletin Chain authorization).\n2. Your account submits `transactionStorage.store(data)` on People Chain. The receipt yields a People-Chain-side `(block, index)` pair plus the computed CID.\n3. People Chain dispatches an XCM message to the Bulletin Chain that mirrors the storage record. Once XCM execution completes, the data is addressable from the Bulletin Chain's collator network with the same CID. Your Product can read it via `client.fetchBytes(cid)` exactly as if you had written directly to Bulletin.\n\nUntil the XCM dispatch is wired up, treat this section as the design contract for the path; the hand-rolled cross-chain code samples will be added once the pallet shape stabilizes."}
{"page_id": "apps-build-store-data-on-chain", "page_title": "Store Data on Chain", "index": 10, "depth": 2, "title": "Submit a Preimage", "anchor": "submit-a-preimage", "start_char": 15539, "end_char": 19012, "estimated_token_count": 733, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:c74846e1bcabfa44f738cbe124293b5a57d0df0e9aa5949841c4075afcc9dc98", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Submit a Preimage\n\nBulletin Chain has a second authorization model alongside the per-account quota you've been using. Instead of authorizing your account to store transactions and bytes, a privileged caller (Root on Bulletin, or the People Chain via the cross-chain dispatch covered in [Cross-Chain Storage from People Chain](#cross-chain-storage-from-people-chain)) can pre-authorize a specific content hash via the `authorize_preimage` extrinsic. Once that authorization is in place, anyone (including your Product) can submit the matching bytes via an unsigned transaction: no fees, no per-account quota debited.\n\nThis is the right path when:\n\n- A sponsor (an app, a parachain, or governance) pre-authorizes content for someone else to upload.\n- The People Chain → Bulletin XCM flow described in [Cross-Chain Storage from People Chain](#cross-chain-storage-from-people-chain) authorizes a hash on Bulletin, and the actual bytes get submitted by the user's Product.\n\nThe Host API exposes the submission side through `getPreimageManager` from `@parity/product-sdk-host` (already installed via the umbrella package in Set Up). Polkadot Desktop mediates the call. The Product never holds a signer for this path because the underlying transaction is unsigned.\n\n```typescript title=\"submit-preimage.ts\"\nimport { getPreimageManager } from '@parity/product-sdk-host';\n\nconst preimageManager = await getPreimageManager();\nif (!preimageManager)\n\nconst payload = new TextEncoder().encode('preimage payload bytes');\n\nconst key = await preimageManager.submit(payload);\n\nconsole.log(`Preimage submitted. Key (resource lookup): ${key}`);\n```\n\n`preimageManager.submit(payload)` resolves with the Blake2b-256 hash of the payload, which is the same hash format as a Bulletin CID. The submission is rejected if no `authorize_preimage` exists for that hash. Reading is permissionless; subscribe via `preimageManager.lookup(key, callback)`.\n\n!!! warning \"Provisional\"\n The Bulletin Chain preimage authorization flow is live on TestNet today, but the cross-chain authorization path (People Chain → Bulletin) and production environment endpoints are not yet finalized. The submission has a Host-side timeout (~120s on the current dev build) before it resolves; production timeouts may shift. The `@parity/product-sdk` API surface is pre-1.0; minor API changes are expected during the `0.x` line.\n\nThe mechanics:\n\n- Some upstream caller (Root on Bulletin, or People Chain via XCM) calls `authorize_preimage(contentHash, maxSize)`.\n- Your Product calls `preimageManager.submit(payload)`.\n- Polkadot Desktop computes the Blake2b-256 hash of the payload; the chain accepts the submission only if a matching authorization exists.\n- The bytes are stored on Bulletin Chain via an unsigned transaction with no fees and no per-account quota debited.\n- Reading is permissionless: any account can fetch the bytes by hash via `preimageManager.lookup`.\n- Retention is roughly two weeks per the standard Bulletin Chain retention window; renewal works the same way as for account-authorized stores.\n- Per-transaction byte limit is the same ~8 MiB; larger payloads are split into chunks and authorized as a DAG-PB manifest plus the chunk hashes.\n\nFor the underlying pallet surface (`authorize_preimage`, `refresh_preimage_authorization`, `remove_expired_preimage_authorization`), see [Preimage Authorization](/reference/polkadot-hub/data-storage/#preimage-authorization) in the Data Storage reference."}
{"page_id": "apps-build-store-data-on-chain", "page_title": "Store Data on Chain", "index": 11, "depth": 2, "title": "Storage Paths at a Glance", "anchor": "storage-paths-at-a-glance", "start_char": 19012, "end_char": 20598, "estimated_token_count": 418, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:c74846e1bcabfa44f738cbe124293b5a57d0df0e9aa5949841c4075afcc9dc98", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Storage Paths at a Glance\n\nThe flows in this guide target the same chain but differ in authorization, atomicity, and consumer access. Use this table to pick the right path before writing.\n\n| Path | Authorization | Atomicity | Retention | Use When |\n|:-------------------------------:|:----------------------------------------------------:|:----------------------------:|:--------------------:|:---------------------------------------------------------------:|\n| Bulletin store (small) | Bulletin authorization | Single tx | ~2 weeks (renewable) | Most Product writes |\n| Bulletin store (chunked) | Bulletin authorization | Multi-tx + DAG-PB manifest | ~2 weeks (renewable) | Files larger than 8 MiB |\n| Cross-chain via People Chain | People-Chain authorization | XCM (eventually consistent) | ~2 weeks (renewable) | PoP-attached writes |\n| Bulletin preimage submission | Pre-authorized hash (no per-account quota, no fees) | Single unsigned tx | ~2 weeks (renewable) | Sponsored uploads; receiving People Chain → Bulletin XCM dispatches |\n\nFor deeper comparison and the full pallet reference, see [Data Storage Reference](/reference/polkadot-hub/data-storage/)."}
{"page_id": "apps-build-store-data-on-chain", "page_title": "Store Data on Chain", "index": 12, "depth": 2, "title": "Where to Go Next", "anchor": "where-to-go-next", "start_char": 20598, "end_char": 21480, "estimated_token_count": 253, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:c74846e1bcabfa44f738cbe124293b5a57d0df0e9aa5949841c4075afcc9dc98", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Where to Go Next\n\n\n\n- Guide **Publish and Subscribe to Off-Chain Data**\n\n ---\n\n Your Product can store durable content; next, add real-time state between users via the Statement Store.\n\n [:octicons-arrow-right-24: Publish and Subscribe to Off-Chain Data](/apps/build/pub-sub-off-chain-data/)\n\n- Guide **Read On-Chain Data**\n\n ---\n\n Pair Bulletin writes with chain reads via the Host API's PAPI provider.\n\n [:octicons-arrow-right-24: Read On-Chain Data](/apps/build/read-chain-state/)\n\n- External **Product SDK API Reference**\n\n ---\n\n The full `product-sdk` surface beyond this recipe: every package, class, and method.\n\n [:octicons-arrow-right-24: Visit Site](https://paritytech.github.io/product-sdk/)\n\n
"}
{"page_id": "apps-deploy-your-app", "page_title": "Deploy Your App", "index": 0, "depth": 2, "title": "Introduction", "anchor": "introduction", "start_char": 19, "end_char": 270, "estimated_token_count": 52, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:208f5cdd47539472644247cca2bd9f9162df9727ef029757443e8593db355961", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Introduction\n\nThis page covers how to build and deploy a Polkadot Product using the `playground` CLI. By the end, your app bundle will be uploaded to the Bulletin Chain, registered under a `.dot` name, and discoverable in the Polkadot playground."}
{"page_id": "apps-deploy-your-app", "page_title": "Deploy Your App", "index": 1, "depth": 2, "title": "Prerequisites", "anchor": "prerequisites", "start_char": 270, "end_char": 806, "estimated_token_count": 130, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:208f5cdd47539472644247cca2bd9f9162df9727ef029757443e8593db355961", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Prerequisites\n\nBefore deploying, ensure you have:\n\n- Complete [Install Desktop and Pair](/apps/get-started/) and [Get TestNet Tokens](/apps/get-started/get-testnet-tokens/); your account needs PAS funds and a Bulletin Chain authorization. If you have not obtained a Bulletin Chain authorization yet, request one from the [Bulletin Chain authorization page](https://paritytech.github.io/polkadot-bulletin-chain/authorizations)\n- A Polkadot Product project running locally. See [Set Up Your Project](/apps/build/#set-up-your-project)"}
{"page_id": "apps-deploy-your-app", "page_title": "Deploy Your App", "index": 2, "depth": 2, "title": "Build Your App Bundle", "anchor": "build-your-app-bundle", "start_char": 806, "end_char": 1340, "estimated_token_count": 136, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:208f5cdd47539472644247cca2bd9f9162df9727ef029757443e8593db355961", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Build Your App Bundle\n\nRun `playground build` to compile your project into a deployable bundle.\n\n\n playground build\n
\n\nThe CLI auto-detects your project type and runs the appropriate build. The output is a set of static files (HTML, JS, CSS, assets) that will be uploaded in the next step.\n\n!!! tip\n If you have already built the project, you can skip this step. `playground deploy` will prompt you to reuse the existing build."}
{"page_id": "apps-deploy-your-app", "page_title": "Deploy Your App", "index": 3, "depth": 2, "title": "Deploy Your App", "anchor": "deploy-your-app", "start_char": 1340, "end_char": 6600, "estimated_token_count": 1405, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:208f5cdd47539472644247cca2bd9f9162df9727ef029757443e8593db355961", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Deploy Your App\n\nRun `playground deploy` to start the interactive deploy flow. The CLI walks you through a series of prompts, then shows a confirmation summary before uploading.\n\n\n playground deploy\n
\n\nThe CLI presents the following prompts in order:\n\n1. **Review app detail page**: A reminder that your `README.md` becomes your app's detail page on the playground. Make sure it's up to date, then press ++enter++ to continue (or ++esc++ to exit and edit it first).\n\n2. **Redeploy contracts if changed**: Smart contracts hold your app's on-chain logic and data, and deploy separately from your website. Choose **no** if you only changed the website. Choose **yes** if you changed contract code in this project. The CLI then redeploys and reinstalls the contracts and rebuilds the site to match.\n\n \n
did you change your smart contracts?\n › no · I only changed the website\n yes · I changed contract code too
\n
\n
build before deploy?\n › yes · rebuild with my latest code\n no · redeploy the existing build
\n
\n
who signs the upload?\n › dev signer · fast, no phone needed\n your phone signer · signs with your own account
\n
\n
build directory default: dist\n › .next█
\n
\n
domain\n › myproject57█
\n
\n
publish to the playground?\n › yes · list it in the public playground\n no · deploy to my .dot address only
\n
\n
playground deploy · myproject57.dot · paseo next v2 v0.34.7\n ────────────────────────────────────────────────────────────────────────
\n deploying myproject57.dot
\n signer Dev signer (no phone taps for upload)\n build skip (use existing)\n build dir .next\n contracts skip\n publish DotNS only
\n phone approvals none
\n enter to deploy · esc to cancel
\n
\n
playground deploy · myproject57.dot · paseo next v2 v0.34.7\n ────────────────────────────────────────────────────────────────────────
\n frontend
\n · build skipped\n ✓ upload + dotns
\n ✓ deploy complete
\n url https://myproject57.dot.li\n domain myproject57.dot\n app cid bafybeihvru3e6ojhopxj7xxwtafrpyvsha6kylzklryon5k67u4clr26re\n ipfs cid bafybeigr2liqwftbmily4sdxvo7mq4atgboqsrpdadypmsbpkn7c25cwja
\n
\n\n- Guide **Build Your Product**\n\n ---\n\n Set up a local project, load it in Polkadot Desktop via the `localhost` bypass, and add capabilities guide by guide.\n\n [:octicons-arrow-right-24: Set Up Your Project](/apps/build/#set-up-your-project)\n\n
"}
{"page_id": "apps-get-started", "page_title": "Install Polkadot Desktop and Pair", "index": 0, "depth": 2, "title": "Introduction", "anchor": "introduction", "start_char": 37, "end_char": 1131, "estimated_token_count": 234, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:cd064672b5d3dba60c9226afa61f22ae83a4c74746fbc83f9ab13cfac7a3c5e5", "last_updated": "2026-06-16T15:08:00+00:00", "text": "## Introduction\n\nYou should already have the Polkadot App on your phone from the [Apps overview](/apps/); it holds your key and approves signing. This page covers installing Polkadot Desktop, where your Product runs, and pairing the two with a QR scan, then forwards you to TestNet funding. About 10 minutes.\n\nTwo pieces of the Polkadot Triangle need to be talking to each other: Polkadot Desktop, where your Product runs, and the Polkadot App on your phone, where signing happens.\n\n\n\nPolkadot Desktop never holds your private key. Your identity lives on the Polkadot [People Chain](/reference/glossary/#people-chain), your private key lives in the Polkadot App, and Polkadot Desktop only ever holds a derived session public key — enough to identify you and construct per-Product accounts, but not enough to sign anything on its own."}
{"page_id": "apps-get-started", "page_title": "Install Polkadot Desktop and Pair", "index": 1, "depth": 2, "title": "Prerequisites", "anchor": "prerequisites", "start_char": 1131, "end_char": 1474, "estimated_token_count": 69, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:cd064672b5d3dba60c9226afa61f22ae83a4c74746fbc83f9ab13cfac7a3c5e5", "last_updated": "2026-06-16T15:08:00+00:00", "text": "## Prerequisites\n\nBefore getting started, ensure you have:\n\n- The [Polkadot App](/apps/) installed on your phone with an account created (your developer identity and signing device for Polkadot Products)\n- A workstation running macOS, Windows, or Linux\n- A device (iOS or Android) with a working camera\n- Network connectivity on both devices"}
{"page_id": "apps-get-started", "page_title": "Install Polkadot Desktop and Pair", "index": 2, "depth": 2, "title": "Install Polkadot Desktop", "anchor": "install-polkadot-desktop", "start_char": 1474, "end_char": 2312, "estimated_token_count": 180, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:cd064672b5d3dba60c9226afa61f22ae83a4c74746fbc83f9ab13cfac7a3c5e5", "last_updated": "2026-06-16T15:08:00+00:00", "text": "## Install Polkadot Desktop\n\n1. Download the development build of [Polkadot Desktop](https://www.polkadotcommunity.foundation/desktop).\n\n2. Install the application using your platform's standard installer.\n\n3. Launch Polkadot Desktop. On first launch, Desktop opens into the pairing flow with a QR code.\n\n \n\n !!! note \"Skip for development\"\n The login screen also exposes a **Skip (Dev only)** button. Skipping the pairing drops you straight into Desktop without a paired signer, useful for inspecting Desktop or testing a local Product that does not require signing, but most development flows assume a paired Polkadot App."}
{"page_id": "apps-get-started", "page_title": "Install Polkadot Desktop and Pair", "index": 3, "depth": 2, "title": "Pair Polkadot Desktop with the Polkadot App", "anchor": "pair-polkadot-desktop-with-the-polkadot-app", "start_char": 2312, "end_char": 4107, "estimated_token_count": 428, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:cd064672b5d3dba60c9226afa61f22ae83a4c74746fbc83f9ab13cfac7a3c5e5", "last_updated": "2026-06-16T15:08:00+00:00", "text": "## Pair Polkadot Desktop with the Polkadot App\n\nPairing is a one-time cryptographic handshake. Desktop displays the QR code, the App scans it, and the App returns a session public key that Desktop stores. From that point forward, Desktop knows who you are and can construct per-Product sub-accounts, but every signing prompt still routes back to the App for approval.\n\n1. Leave the QR code visible on the Polkadot Desktop login screen.\n\n2. In the Polkadot App, open the camera-scanning view and scan the QR code shown on Desktop. A **Link a new device?** prompt appears with the Desktop version details.\n\n \n\n3. Tap **Link** to confirm. The App briefly shows a **Connecting device...** state while the handshake completes.\n\n \n\n4. Desktop transitions from the QR code to a **Completing pairing...** state.\n\n \n\n5. Once the handshake completes, Desktop opens the main dashboard.\n\n \n\nAfter pairing, your identity on the People Chain is bound to the Polkadot App for this Desktop session. Every subsequent signing request will route to the App, and you approve or reject each one on the signing device."}
{"page_id": "apps-get-started", "page_title": "Install Polkadot Desktop and Pair", "index": 4, "depth": 2, "title": "Where to Go Next", "anchor": "where-to-go-next", "start_char": 4107, "end_char": 4413, "estimated_token_count": 86, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:cd064672b5d3dba60c9226afa61f22ae83a4c74746fbc83f9ab13cfac7a3c5e5", "last_updated": "2026-06-16T15:08:00+00:00", "text": "## Where to Go Next\n\n\n\n- Guide **Get TestNet Tokens**\n\n ---\n\n Claim TestNet tokens from the Polkadot Faucet and unlock per-service allowances.\n\n [:octicons-arrow-right-24: Continue](/apps/get-started/get-testnet-tokens/)\n\n
"}
{"page_id": "apps", "page_title": "Apps", "index": 0, "depth": 2, "title": "Get the Polkadot App", "anchor": "get-the-polkadot-app", "start_char": 28, "end_char": 397, "estimated_token_count": 101, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:96b5385e397fac2af1d038661cded23703a17ad61d1391ed952916394795e39f", "last_updated": "2026-06-18T10:12:03+00:00", "text": "## Get the Polkadot App\n\nThe Polkadot App is your wallet, identity, and signer: the center of everything you build. Install it first; every path below connects through it.\n\n\n[:material-apple: App Store — Coming soon]() [:material-google-play: Google Play](https://play.google.com/store/apps/details?id=io.pcf.polkadotapp)\n
"}
{"page_id": "apps", "page_title": "Apps", "index": 1, "depth": 2, "title": "Then Pick Your Path", "anchor": "then-pick-your-path", "start_char": 397, "end_char": 1049, "estimated_token_count": 178, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:96b5385e397fac2af1d038661cded23703a17ad61d1391ed952916394795e39f", "last_updated": "2026-06-18T10:12:03+00:00", "text": "## Then Pick Your Path\n\n\n\n- Guide **Deploy a Product in Under 15 Minutes**\n\n ---\n\n Go from nothing to a live `.dot` Product: in your browser with RevX, or from the terminal with the CLI. No local environment to set up.\n\n [:octicons-arrow-right-24: Quick Start](/apps/quick-start/)\n\n- Guide **Develop Locally (the Full Route)**\n\n ---\n\n Install Polkadot Desktop, pair it with your phone, and get TestNet tokens, then build your Product capability by capability.\n\n [:octicons-arrow-right-24: Get Started](/apps/get-started/)\n\n
"}
{"page_id": "apps", "page_title": "Apps", "index": 2, "depth": 2, "title": "What Is a Polkadot Product?", "anchor": "what-is-a-polkadot-product", "start_char": 1049, "end_char": 2605, "estimated_token_count": 364, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:96b5385e397fac2af1d038661cded23703a17ad61d1391ed952916394795e39f", "last_updated": "2026-06-18T10:12:03+00:00", "text": "## What Is a Polkadot Product?\n\n_Polkadot Products_ are what _you_ build: third-party applications that run _inside_ one of the Polkadot Apps. Products are sandboxed single-page apps (HTML / JS / CSS), addressed by `.dot` names (e.g., `awesome.dot`), registered on-chain through a decentralized name service, and they never see the user's private key. The bundle itself is published to a decentralized cloud storage provider and fetched by the Host on demand.\n\n_Polkadot Apps_ are the three applications that can host Polkadot Products, collectively known as the _Polkadot Triangle_:\n\n- **[Polkadot Desktop](/reference/apps/hosts/polkadot-desktop/)**: The workstation host. Loads Polkadot Products by their `.dot` name and runs them in a sandbox.\n- **[Polkadot App](/reference/apps/hosts/polkadot-app/)**: The mobile wallet and signer. Holds the user's private key and approves every signing request.\n- **[Polkadot Web](/reference/apps/hosts/polkadot-web/)**: The browser host at `dot.li`. Resolves `.dot` names client-side via a light client and renders the Product in a sandboxed iframe.\n\nYou build Polkadot Products. They run inside one of the Polkadot Apps. This section teaches you how.\n\n\n\nFor the architectural breakdown covering how the Product, SDK, Host, and Polkadot infrastructure relate, see the [App Development Reference](/reference/apps/)."}
{"page_id": "apps", "page_title": "Apps", "index": 3, "depth": 2, "title": "Why Build a Polkadot Product?", "anchor": "why-build-a-polkadot-product", "start_char": 2605, "end_char": 5289, "estimated_token_count": 615, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:96b5385e397fac2af1d038661cded23703a17ad61d1391ed952916394795e39f", "last_updated": "2026-06-18T10:12:03+00:00", "text": "## Why Build a Polkadot Product?\n\nPolkadot Apps is a complete environment for building Web3 decentralized applications:\n\n**Wallet built-in**: The Polkadot App on the user's phone is the wallet for every Polkadot Product they use. No wallet integration code, no \"Connect Wallet\" button to design, no signing plumbing to maintain. Your Product receives a derived per-user account and asks for signatures; approvals happen on the user's phone.\n\n**Identity built-in**: Per-Product accounts are derived from the user's `.dot` identity, so there is no signup flow. With [Proof of Personhood](/reference/apps/infrastructure/pop/), you can gate features on verified-human status without seeing who the user is, a privacy-preserving humans-only access model built into the platform. Need to recognize the same user across two of your Products? Same alias system, scoped to your Product set.\n\n**Decentralized hosting**: Your bundle lives on a decentralized cloud storage provider. Your `.dot` name lives in a decentralized name service. There is no centralized hosting provider, no DNS service, no platform in the middle. Users fetch your Product directly and verify it themselves.\n\n**Product SDK**: The Product SDK covers what you would otherwise integrate yourself:\n\n- **Chain access**: Query state and submit transactions through the Host. No RPC servers to operate; signing prompts open on the user's phone.\n- **Decentralized storage**: Upload files, get a permanent content-addressed URL.\n- **Real-time signed messaging**: Pub/sub between users of your Product via the [Statement Store](/reference/apps/infrastructure/statement-store/), every message verifiable.\n- **Privacy-preserving payments**: Request, top up, track status. Built on [Coinage](/reference/apps/infrastructure/pop/pallet-coinage/).\n- **Chat**: Rooms, bots, interactive action buttons.\n- **Identity**: Derived per-Product accounts, plus optional [Proof of Personhood](/reference/apps/infrastructure/pop/) gating.\n- **Local storage**: Per-Product key/value, persisted on the user's device.\n\nPermissions (microphone access, outbound network requests, on-chain transaction submission, and more) are declared in your Product's [manifest](/reference/apps/hosts/polkadot-desktop/permissions/) and prompted at runtime. Users see exactly what your Product can access before they grant it. The Host enforces the boundary inside its [sandbox](/reference/apps/protocol/truapi/sandbox/), not your code.\n\n**Three Hosts, one Product**: The same `.dot` bundle runs in the mobile Polkadot App, on the workstation in Polkadot Desktop, and in any browser via Polkadot Web. You do not write three apps; the Triangle abstracts the platform."}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 0, "depth": 2, "title": "Prerequisites", "anchor": "prerequisites", "start_char": 492, "end_char": 1109, "estimated_token_count": 135, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Prerequisites\n\nBefore starting, make sure you have:\n\n- The [Polkadot App](/apps/) installed on your phone with an account created; it pairs with `pg` and signs the publish step.\n- A terminal with `curl` available and permission to install CLI tools in your user shell environment.\n- A Polkadot Product project on disk with a package-manager build command.\n\n!!! note \"CLI version\"\n This route targets playground-cli `0.27.1`. The CLI is in active development and breaking changes between versions are expected. To follow along, install this version, or check this page's last update against the latest release."}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 1, "depth": 2, "title": "Install the CLI", "anchor": "install-the-cli", "start_char": 1109, "end_char": 1549, "estimated_token_count": 113, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Install the CLI\n\n1. Run the installer:\n\n ```bash\n curl -fsSL https://raw.githubusercontent.com/paritytech/playground-cli/main/install.sh | bash\n ```\n\n2. Open a new shell, or `source` your RC file, and verify the install:\n\n ```bash\n pg --version\n ```\n\n!!! note \"Command aliases\"\n The installer registers two interchangeable commands: `playground` (canonical) and `pg` (short alias). This guide uses `pg` throughout."}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 2, "depth": 2, "title": "Initialize", "anchor": "initialize", "start_char": 1549, "end_char": 2749, "estimated_token_count": 298, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Initialize\n\n`pg init` installs toolchain dependencies and pairs the CLI with your signer. It is safe to re-run; existing installs and sessions are detected and skipped.\n\n```bash\npg init\n```\n\n\n pg init\n \n ✔ logged in 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY\n ✔ username alice.dot\n ✔ product account 5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty (0x90b5ab205c6974c9ea841be688864633dc9ca8a3)\n ✔ Setup complete\n
\n!!! tip\n Toolchain install runs in parallel with the login step, so you can scan the QR code while dependencies download.\n\n!!! note \"Signer modes\"\n - **Mobile signer** (`--signer phone`, default): Pairs with the Polkadot App via QR code. Required for `pg init` and recommended for any deploy you intend to keep.\n - **Dev-only signer** (`--signer dev`): No phone needed; uses shared development keys (for example, `--suri //Alice`). The deployed `.dot` Product will be owned by the shared dev account, not by you."}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 3, "depth": 2, "title": "Build", "anchor": "build", "start_char": 2749, "end_char": 3040, "estimated_token_count": 100, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Build\n\n`pg build` auto-detects and runs your project build.\n\n```bash\npg build\n```\n\n\n pg build\n \n ✔ Build succeeded → dist/\n
"}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 4, "depth": 2, "title": "Deploy", "anchor": "deploy", "start_char": 3040, "end_char": 5208, "estimated_token_count": 566, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Deploy\n\n`pg deploy` runs the full pipeline: build the frontend, upload artifacts to the Polkadot Bulletin Chain, and register a `.dot` domain via DotNS. Before building, it always runs your package manager's install step to keep dependencies in sync.\n\n```bash\n# Interactive - pg prompts for signer, domain, and build directory\npg deploy\n\n# Dev signer - no phone needed (the deployed Product is owned by the shared dev account)\npg deploy --signer dev --domain my-app\n```\n\n\n pg deploy --signer dev --domain my-app\n \n ✔ my-app.dot is available\n ✔ Deploy complete\n URL https://dot.li/...\n Domain my-app.dot\n App CID Qm...\n
\n!!! note\n `pg deploy` includes a memory watchdog that aborts the deploy if the process exceeds 4 GB RSS. If you hit this limit, set `DOT_MEMORY_TRACE=1` alongside `DOT_DEPLOY_VERBOSE=1` to capture per-second RSS and heap samples.\n\n??? note \"More CLI commands\"\n\n - **`pg mod`**: Clones a moddable app from the Playground registry so you can customize and redeploy it as your own Product. Only apps that opted into `--moddable` at deploy time are listed. Pass a domain label, such as `my-app` or `my-app.dot`, to clone directly, or omit it to open an interactive picker showing every moddable app.\n\n ```bash\n pg mod [domain]\n ```\n\n - **`pg logout`**: Signs out of the paired account and clears session files under `~/.polkadot-apps/`. A no-op if you are not signed in.\n\n ```bash\n pg logout\n ```\n\n - **`pg update`**: Updates `pg` to the latest version from the GitHub releases page.\n\n ```bash\n pg update\n ```\n\nYou have deployed a Polkadot Product. To keep building it with your own editor and toolchain, head to the Build guides; they open with [project setup](/apps/build/#set-up-your-project) so Polkadot Desktop can load your Product from `localhost` while you iterate with live reload."}
{"page_id": "apps-quick-start-cli", "page_title": "Quick Start with the CLI", "index": 5, "depth": 2, "title": "Where to Go Next", "anchor": "where-to-go-next", "start_char": 5208, "end_char": 5567, "estimated_token_count": 100, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:205b4160a87f02aaa8c4a90265ea1d62e870c98b5bc3961b2e675f045536aa52", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Where to Go Next\n\n\n\n- Guide **Build Guides**\n\n ---\n\n Set up the local dev loop, then add capabilities to your Product: signing, on-chain reads, decentralized storage, off-chain pub/sub, and local persistence.\n\n [:octicons-arrow-right-24: Open Build Guides](/apps/build/)\n\n
"}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 0, "depth": 2, "title": "Prerequisites", "anchor": "prerequisites", "start_char": 511, "end_char": 766, "estimated_token_count": 57, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Prerequisites\n\nBefore starting, make sure you have:\n\n- The [Polkadot App](/apps/) installed on your phone with an account created; it signs the final publish step.\n- An API key for an AI provider supported by App Builder, such as OpenAI or Anthropic."}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 1, "depth": 2, "title": "Open RevX", "anchor": "open-revx", "start_char": 766, "end_char": 1033, "estimated_token_count": 75, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Open RevX\n\nOpen [RevX](https://revx.dev/) in your browser. RevX is a browser-based IDE; you will use the App Builder track to scaffold a Polkadot Product end to end.\n\n"}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 2, "depth": 2, "title": "Open App Builder", "anchor": "open-app-builder", "start_char": 1033, "end_char": 1288, "estimated_token_count": 63, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Open App Builder\n\nFrom the sidebar, select **App Builder**. App Builder is RevX's track for generating Polkadot Products using AI-assisted workflows.\n\n"}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 3, "depth": 2, "title": "Create a New App", "anchor": "create-a-new-app", "start_char": 1288, "end_char": 2313, "estimated_token_count": 217, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Create a New App\n\nClick **Create App** to start a new project. RevX automatically installs the required dependencies and initializes the project environment so you can move straight into configuration and prompting.\n\n\n\nAfter clicking **Create App**, you will see a loading screen while the IDE initializes the project environment.\n\n\n\n!!! note\n Initial setup may take a moment while dependencies install. Wait for the environment to finish initializing before configuring the builder.\n\nOnce the environment is initialized, you will see a minimal app scaffolded in the editor and running in the terminal.\n\n"}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 4, "depth": 2, "title": "Configure the Builder", "anchor": "configure-the-builder", "start_char": 2313, "end_char": 3012, "estimated_token_count": 169, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Configure the Builder\n\nFrom the App Builder view, click the **Settings** icon to open the AI configuration panel.\n\n\n\nConfigure the following:\n\n- **AI provider**: The backend service that powers code generation.\n- **API key**: The credential for your AI provider.\n- **Model**: The specific model to use from the selected provider.\n\n\n\nThese settings let the IDE generate applications using the selected AI backend. You can change them at any time if you want to switch providers or models."}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 5, "depth": 2, "title": "Generate an App", "anchor": "generate-an-app", "start_char": 3012, "end_char": 3683, "estimated_token_count": 140, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Generate an App\n\nUse the chat interface to describe the app you want to build. RevX generates the application structure and code automatically based on your prompt.\n\n!!! example \"Example prompt\"\n Build a Product that shows the balance of Alice (a standard Substrate dev account)\n\nAfter you submit the prompt, the IDE produces the project files and scaffolds the app for you to review.\n\n\n\n!!! tip\n Keep prompts concrete and scoped. Short, specific prompts tend to produce app structures that are easier to review and iterate on."}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 6, "depth": 2, "title": "Inspect the Generated Code", "anchor": "inspect-the-generated-code", "start_char": 3683, "end_char": 4088, "estimated_token_count": 83, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Inspect the Generated Code\n\nOnce generation completes, open the generated files in the editor to review what was produced. You can continue iterating on the application from within RevX: refine the prompt, edit code directly, or layer additional changes through the chat interface.\n\n"}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 7, "depth": 2, "title": "Publish to `.dot`", "anchor": "publish-to-dot", "start_char": 4088, "end_char": 4842, "estimated_token_count": 192, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Publish to `.dot`\n\nWhen your app is ready, click **Publish to .dot** to deploy the application to the Polkadot ecosystem. The publish action takes the app you generated in RevX and makes it available under a `.dot` name.\n\n\n\nAfter clicking **Start Deploy**, you will be asked to sign the transaction with your Polkadot App.\n\n\n\nAfter signing the transaction, you will see the deployment progress in the terminal. Your Product is now live under its `.dot` name. Open it in Polkadot Desktop, or on Polkadot Web at `https://.dot.li` in any browser."}
{"page_id": "apps-quick-start", "page_title": "Quick Start with RevX", "index": 8, "depth": 2, "title": "Where to Go Next", "anchor": "where-to-go-next", "start_char": 4842, "end_char": 5201, "estimated_token_count": 100, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:dc42a167c6ee8abdc8acd0dfa340dcf01c005af86a9c2cf633e2e1176a0d239c", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Where to Go Next\n\n\n\n- Guide **Build Guides**\n\n ---\n\n Set up the local dev loop, then add capabilities to your Product: signing, on-chain reads, decentralized storage, off-chain pub/sub, and local persistence.\n\n [:octicons-arrow-right-24: Open Build Guides](/apps/build/)\n\n
"}
{"page_id": "apps-tutorials-shared-todo-app", "page_title": "Build a Shared Todo App", "index": 0, "depth": 2, "title": "Introduction", "anchor": "introduction", "start_char": 27, "end_char": 2319, "estimated_token_count": 572, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:5cdbfa5345aeb58569f7a7ce8c42597c5370df2ad18835b80a96da42762e04f4", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Introduction\n\nEach [Build guide](/apps/build/) takes one `product-sdk` capability from zero to working code. This tutorial is the capstone: it combines four of them into one product, a Shared Todo Board where every participant sees changes live and the board survives durably on chain.\n\nWhat you will build, and which package carries each part:\n\n| Capability | Package | Role in the app |\n| :------------------: | :----------------------------------------: | :---------------------------------------------------------------------------------------------------------------------: |\n| Identity and signing | `signer` (via the umbrella's `wallet` API) | Connect to the Host and get the account that authors and signs everything |\n| Local persistence | `local-storage` | The board renders instantly from the device's last known state |\n| Real-time sharing | `statement-store` | Every mutation gossips to other participants as a signed statement |\n| Durable storage | `cloud-storage` | Snapshots of the board live on the [Bulletin Chain](/reference/apps/infrastructure/bulletin-chain/), addressable by CID |\n\n\n\nThe guides cover the individual calls. This tutorial focuses on how the layers compose. Statements are capped at 512 bytes and expire after 30 seconds, so they carry individual mutations, not the whole board. The Bulletin Chain holds full snapshots, and a last-write-wins channel announces the latest snapshot's CID. This is the same split Polkadot App's Chat uses: gossip for signaling, Bulletin for content.\n\nThe code in this tutorial is confirmed working with Polkadot Desktop, `@parity/product-sdk` v0.11.0, and `@parity/product-sdk-statement-store` v0.4.4."}
{"page_id": "apps-tutorials-shared-todo-app", "page_title": "Build a Shared Todo App", "index": 1, "depth": 2, "title": "Prerequisites", "anchor": "prerequisites", "start_char": 2319, "end_char": 2952, "estimated_token_count": 143, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:5cdbfa5345aeb58569f7a7ce8c42597c5370df2ad18835b80a96da42762e04f4", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Prerequisites\n\nBefore starting, ensure you have:\n\n- Node.js 20 or later.\n- Polkadot Desktop installed and paired. See [Install Desktop and Pair](/apps/get-started/).\n- A statement allowance and a Bulletin Chain storage authorization for your wallet account. See [Get TestNet Tokens](/apps/get-started/get-testnet-tokens/) and the [Bulletin Chain authorizations](https://paritytech.github.io/polkadot-bulletin-chain/authorizations) reference. Without the storage authorization, snapshot uploads are rejected.\n- The individual [Build guides](/apps/build/) are optional but helpful because they cover each capability in more depth."}
{"page_id": "apps-tutorials-shared-todo-app", "page_title": "Build a Shared Todo App", "index": 2, "depth": 2, "title": "Scaffold the Project", "anchor": "scaffold-the-project", "start_char": 2952, "end_char": 7347, "estimated_token_count": 1092, "token_estimator": "heuristic-v1", "page_version_hash": "sha256:5cdbfa5345aeb58569f7a7ce8c42597c5370df2ad18835b80a96da42762e04f4", "last_updated": "2026-06-16T14:17:44+00:00", "text": "## Scaffold the Project\n\nCreate a Next.js app and install the SDK:\n\n```bash\nnpx create-next-app@latest shared-todo-board --typescript --tailwind --eslint --app --no-src-dir\ncd shared-todo-board\nnpm install @parity/product-sdk @parity/product-sdk-statement-store @parity/product-sdk-cloud-storage @polkadot-api/json-rpc-provider\n```\n\nFour dependencies, for four reasons:\n\n- **`@parity/product-sdk`**: The umbrella package. It re-exports the wallet, local-storage, and cloud-storage capabilities this app uses, plus the React provider. See [Umbrella or Individual Packages](/apps/build/#umbrella-or-individual-packages) if you would rather install per-capability packages.\n- **`@parity/product-sdk-statement-store`**: The pub/sub client. It is not re-exported by the umbrella, so it is always its own dependency.\n- **`@parity/product-sdk-cloud-storage`**: Installed explicitly because the app imports `CloudStorageClient` directly for its authorization pre-flight; relying on the umbrella's transitive copy would depend on npm hoisting.\n- **`@polkadot-api/json-rpc-provider`**: A one-line workaround, explained below.\n\n!!! note \"Why the explicit `@polkadot-api/json-rpc-provider` dependency?\"\n Older transitive dependencies of the SDK pin `@polkadot-api/json-rpc-provider@0.0.1`, and npm hoists that version to the top of `node_modules`, which breaks the build. Declaring `^0.2.0` as a direct dependency forces the correct resolution. No `overrides` or patching is needed.\n\nWrap the app in `ProductSDKProvider` so every component can reach the SDK through `useProductSDK()`:\n\n```tsx title=\"app/providers.tsx\"\n'use client';\n\nimport { ProductSDKProvider } from '@parity/product-sdk/react';\nimport type { ReactNode } from 'react';\n\nexport function Providers({ children }: { children: ReactNode })\n >\n {children}\n \n );\n}\n```\n\nThen mount it in the root layout. The inline script is a Polkadot Desktop workaround: it sets the host webview mark synchronously, so the SDK's container detection returns true before its bundle evaluates. It forces host mode unconditionally. That is acceptable here because every capability in this app needs the Host anyway; remove the line if your Product must also run standalone in a plain browser tab:\n\n```tsx title=\"app/layout.tsx\"\nimport type { Metadata } from 'next';\nimport { Geist, Geist_Mono } from 'next/font/google';\nimport { Providers } from './providers';\nimport './globals.css';\n\nconst geistSans = Geist({\n variable: '--font-geist-sans',\n subsets: ['latin'],\n});\n\nconst geistMono = Geist_Mono({\n variable: '--font-geist-mono',\n subsets: ['latin'],\n});\n\nexport const metadata: Metadata = {\n title: 'Shared Todo Board',\n description: 'Build a Full Product tutorial companion app',\n};\n\nexport default function RootLayout({\n children,\n}: Readonly<{\n children: React.ReactNode;\n}>) ${geistMono.variable} h-full antialiased`}\n >\n \n {/* Sets the mark synchronously so isWebview() returns true before the SDK bundle evaluates */}\n \n {children}\n \n