Every app you ship, every asset it needs, in one place.
AppOps is the system of record for your app catalogue: icons, screenshots and feature graphics with full version history, store copy for every locale you publish in, and the team roles that keep a release from being approved by the wrong person.
- Versioned assets
- Per-locale store copy
- Organization roles
- Immutable history
What it does
The boring parts of shipping, handled properly
Most release tooling fails at the edges — the eleventh locale, the tablet screenshot nobody uploaded, the person who left the company. AppOps is built around those edges.
One catalogue, not a folder tree
Bundle IDs, platforms and store metadata live in rows, not filenames. Deleting a folder can no longer orphan a release.
Assets that keep their history
Icons, screenshots and feature graphics are versioned per app. Every upload is attributable and every earlier version is still there.
Screenshots sized for the store
Phone, 7-inch and 10-inch tablet classes are tracked explicitly, so the gap that only shows up at review is caught at upload.
Every icon size, from one upload
Upload a single square master and it is rendered into the App Store, Play and browser sizes by name — flattened opaque, which is the part both stores reject you for.
Store copy in every locale
Title, subtitle, keywords and description per locale, side by side, so a missing translation is visible before release not after.
Roles that match your team
Organizations, memberships and the last-owner guard mean there is always someone accountable, and never a silent dead end.
Uploads that do not stall
Direct-to-storage uploads with background processing, so a large screenshot set does not tie up a request while it moves.
How it works
Four steps, and none of them need a spreadsheet
- 1
Register your apps
Add each bundle once. Everything else — assets, copy, releases — hangs off that record.
- 2
Upload against the app
Drag in artwork. Device class, dimensions and version number are recorded as it lands.
- 3
Fill in every locale
Work through the languages you publish in. Anything still untranslated is flagged, not assumed.
- 4
Cut the release
The app page shows you exactly what is current and what is stale. Then it ships.
About
We build the tool we kept wishing existed
AppOps started as an internal tool: a team shipping several apps a quarter, losing track of which screenshot set matched which store, and finding out about a missing tablet size from a review email. It is now the release system we use ourselves, built on the assumption that release operations deserve the same rigor as the code that ships.
Optimise for the person shipping
Every screen answers one question: what do I do next? If it needs a paragraph to explain itself, it is wrong.
Deny by default
Access is granted per role, never inherited by accident, and a team can never remove its own last route to recovery.
Keep the history
Versions are append-only. Deleting the current asset changes what is current, not what happened.
Honest about failure
When something is wrong, we say what went wrong and where. Silent retries and swallowed errors cost more time than the bug did.
Contact
Tell us what you are trying to ship
Whether you are moving off a shared drive, tidying up a release process that grew by accident, or evaluating AppOps against something else — start here.
- A real reply from a person, not an autoresponder
- Usually within one business day