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
Where the portal grows
Reference
- docs/publishing-design.md
- evm/src/Publisher.sol
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
publish(label)step, run over content that is already uploaded.nextAvailableAt), no personhood, and not the owner.Where the portal grows
Reference