The dashboard

Understanding the developer dashboard

The dashboard is where a repo becomes a listing: sign in, submit your poppy, track review, publish updates, and — if you sell — connect Stripe and price your products. Listing is free.

The pieces

  1. Sign in

    Google or email + password. Creating an account means accepting the Developer Agreement — it's short, readable, and it's the contract review holds you to.

  2. Connect Stripe — only if you sell

    Stripe Connect doubles as identity verification and your payout rail. You remain the merchant of record with your own Stripe account; the platform keeps a flat 5% of platform-processed sales. Free poppies never need Stripe.

  3. Submit your poppy

    The form is the catalogue entry: id, name, tagline, description, public repo (required), version, icon (square PNG), packaged release (URL + sha256 from pack-extension) — plus your license, the age-rating questionnaire, and the data-flow declaration (see Data & privacy). Drafts save locally as you type.

  4. Track review

    Statuses are exactly three: In review Live Needs changes. A human reviews every submission — usually within days. Rejections come with a written reason; fix and resubmit.

  5. Publish updates

    Ship the new version in your repo, pack it, update the entry, resubmit. Users see an update they can review before downloading — the catalogue pins the new sha256, and if your declared permissions changed, their approval is asked again. Scope changes are never silent.

  6. Price products

    Create products (a whole-poppy unlock or named premium features), one-time or subscription. Prices live server-side and render live in the purchase button — see monetisation for the rules.

// good to know

Approval publishes instantly — no waiting for a site deploy; the catalogue serves your entry the moment it's approved.

Your name is protected once listed — first listed keeps the name; placeholders can't reserve names.