Publish

Put your app in the Duo App Store

Build it with the SDK, open a pull request, and once it is merged it installs on every Duo. Six steps, and the tools below fill in most of the paperwork.

30 community apps from 4 developers are live already.
  1. Set up

    You need bun and a fork of the repository. The SDK, UI kit and CLI are not on npm yet, so you build against local archives. This creates a new app, wired up and ready to run:

    Shell
    bun install
    bun scripts/package-platform.ts      # SDK, kit and CLI archives, once
    bun packages/cli/index.mjs create my-app --packages .cache/platform-packages/artifacts.json
    cd my-app && bun install && bun run dev

    First time? Get started walks through the same commands with the simulator open beside them.

  2. Name it

    Type your app’s name and your GitHub login. You get the folder, the permanent app id, the manifest, and the two entries for community-apps/registry.json: your developer profile, shown on your tab on /apps, and the app, mapped to the accounts allowed to maintain it.

    Folder
    community-apps/pocket-garden
    App id
    com.yourlogin.duo.pocketgarden
    Developer
    your-login
    community-apps/pocket-garden/manifest.json
    1{
    2 "id": "com.yourlogin.duo.pocketgarden",
    3 "name": "Pocket Garden",
    4 "version": "1.0.0",
    5 "lane": "community",
    6 "entry": "./main.tsx",
    7 "icon": "./icon.png",
    8 "author": "your-login",
    9 "repo": "https://github.com/doan-labs/duo/tree/main/community-apps/pocket-garden",
    10 "license": "MIT",
    11 "permissions": []
    12}

    The id is the app’s identity forever: the catalog, installs and saved data all key on it. Pick the name you mean to keep.

  3. Fill the folder

    Put the app in community-apps/<app-slug>/ in your fork. Click a file to see what it is for and who checks it. fold-compass is a complete example to copy the shape from.

    community-apps/<app-slug>/

    manifest.json

    Required

    Who the app is: the reverse-DNS id, name, version, author, the "community" lane, empty permissions and every network origin it talks to.

    Checked by

    The gate validates every field, refuses reserved namespaces and makes sure the version goes up.

  4. Check it

    Run the same gate CI runs. It builds the release exactly as the catalog will:

    Shell
    bun scripts/check-submissions.ts community-apps/<app-slug>

    The script cannot judge everything. Go through what reviewers will look at:

    Before you push0 of 8

    Tick what you have covered. Nothing here is saved or sent; CI runs the real checks.

  5. Open the pull request

    Push your branch to your fork, then press Submit with GitHub. It opens a pull request against main with the app-submission template filled in: id, version, folder, dependencies, network origins, and the checklist you just went through.

    Attach both screenshots, the inner display and the cover. A submission without them cannot be reviewed.

  6. Go live

    Four stops between the pull request and the Store. Click through them:

    CI

    The submission gate validates the folder, runs duo check and builds the release, with no secrets and read-only access. Green means eligible for review, nothing more.

    To ship an update, bump version, add a changelog entry and open a new pull request. To pull an app, open an issue: delisting stops new installs, but it never uninstalls the app or deletes anyone’s data.

Prefer to ship it yourself?