2
3 Comments

Why we stopped doing App Store admin by hand

On the apps we worked on, store admin landed on whoever had a free hour. Weekend reviews to answer, metadata to check before every submission, prices that had drifted out of sync with what was actually live in half the countries we shipped to.

The rejections cost the most. Apple adjusts its guidelines every few months, and a build that passed the last ten times comes back refused over one line somebody missed. Then you spend an afternoon in release notes working out which line it was.

We built Uprate to take that over. It submits builds, updates ASO, answers reviews, and manages pricing across 175+ territories.

It's open now.

posted toAvatar for product Uprate
Uprate
  1. 1
    The rejection problem feels like the strongest pain here. Are most teams using Uprate to save admin time, or mainly to avoid costly App Store mistakes?
    1. 1

      That's right, the problem is big... when the appstore rejects it, it's a real pain. Look, it's different for our users. Usually, they use it for ongoing work and keeping the entire application in good shape (reviews, time, pricing)

      1. 1
        That’s useful. So rejection is the sharpest pain, but the recurring value seems broader — keeping reviews, pricing, and the rest of the App Store presence in shape without the ongoing manual overhead.