Become a Publisher

Got something built and ready to share? Publishing on Brewser puts your app in front of an audience across three platforms — no gatekeepers, no app-store limbo, just your work running where people can actually find it.

From your workbench to their screens

Five steps, one afternoon. Here’s the whole journey.

1. 1
   Register as a developer

   Sign in with your Google account from the Brewser toolbar — no approval queue, you’re a developer the moment you sign in. Your Google identity becomes your publisher identity, and every app you submit is tied to it.

   The same sign-in works on the Switch too, using a device-code flow, so your identity follows you across every platform Brewser runs on.

2. 2
   Package your app

   Bundle everything into a single .zip archive. A manifest.json describes your app — its name, ID, author, and metadata. Don’t have one? It’s generated automatically on submission. Bring your own and it’s validated against a shared schema.

   my-app.zip
   ├─ index.html
   ├─ app.js
   ├─ assets/
   └─ manifest.json  ← optional, auto-generated
3. 3
   Submit

   Upload your zip through the submission form on the developer portal. Your app lands in the staging area — a unlisted holding space tied to your account, so no one else sees your work-in-progress. Submit an update anytime; the latest submission always wins.

4. 4
   Verification

   Every submission passes automated security scanning — static analysis and taint tracking — before it can be approved. This keeps the catalogue trustworthy and makes sure your app actually runs on the console the way it does in the browser. It’s a manual pass, so it takes a little time — but it means what ships, works.

   Tested on real Switch hardware
5. 5
   Published

   Once approved, your app is promoted from staging into the public catalogue, where anyone can browse, launch, and enjoy it — on their PC, phone, or Switch. That’s it. You’re a Brewser publisher.

How the publishing system works

Behind the scenes, Brewser runs on a transparent, GitHub-backed pipeline.

Every submission is committed to a staging repository and recorded against your account. Verified apps are promoted into the published catalogue. The whole system runs on open, auditable infrastructure — your work is versioned, traceable, and never locked away behind a black box.