Publishing to the web is one click. App stores are a different animal — packaging formats, listings, privacy declarations, review queues — and that's exactly the kind of tedium agents should eat.
What the agents do per store
| Store | Artifact | Automated by agents | Stays in your hands |
|---|---|---|---|
| Google Play | .aab via the real Android toolchain | Listing copy & graphics, privacy declarations, upload, draft release staging | One-time developer fee, console-gated first-app steps, final rollout click |
| Chrome Web Store | Extension .zip | Package upload, listing copy, screenshots, permission justifications, privacy tab autofill | Account connection, publish confirmation |
| Firefox Add-ons | Extension .zip | The whole thing — upload, validation, version, listing. No console visit needed | Account connection |
Your name on the listing, not ours
When you ship a build to a store, the Ship team packages the real artifact, writes the listing copy and graphics from your build, fills the privacy declarations from what the app actually does (claims are checked against the source — a "collects no data" declaration is only made when the code really makes no network calls), and submits — through your developer account, because the publisher of record should be you, not us.
The honest caveats
Two things no platform can promise. Store review is the store's decision; agents prepare the strongest submission but can't guarantee approval. And store developer registration (Google's one-time fee, for instance) stays in your hands. Everything between those two ends — the part that used to take an afternoon of forms — is agent work now.