Developer Portal

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

Start with docs/publishing-design.md and evm/src/Publisher.sol, especially Publisher.publish(label) and nextAvailableAt, to understand the existing publishing flow and failure cases. Then map where Browse can expose an owner-only entry point. Done means the v1 launch-moment checklist is covered, including success, shareable launch, deeplink, and handled failure states.