Skip to content

Developer Portal #52

Description

@BigTava

Epic

As a developer, I want a Developer Portal inside Browse where I can publish, launch, and manage my apps, so that shipping feels like a launch instead of a command-line chore.

Why

This is the first supply-side need from the engagement design (docs/publishing-design.md). There are no apps yet, so the priority is giving developers a real place to publish. Today publishing is a command-line step (Publisher.publish(label)) with no in-app entry point and no feedback.

v1 scope: the launch moment

  • In-app publish flow for the publish(label) step, run over content that is already uploaded.
  • A success screen that confirms the app is live.
  • A shareable launch card (icon, name, one-line pitch).
  • A deeplink to the app that opens or offers install.
  • Failure states handled directly, not as raw reverts: rate limit (show the next slot time from nextAvailableAt), no personhood, and not the owner.
  • The publish entry point appears only when the signed-in user owns the label.
  • A coordinated push of real-human recommends at launch, so the opening spike is genuine and survives.

Where the portal grows

  • Manage listings: unpublish and republish an app.
  • A developer profile: the apps you shipped and your standing.
  • Earnings: tips in PGAS with no platform cut.
  • Feedback: recommends, installs, and honour for your apps in one place.

Reference

  • docs/publishing-design.md
  • evm/src/Publisher.sol

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions