← All posts
·3 min read·Kennedy Owusu

Two weeks in App Store review limbo

I submitted an app and then watched it sit. No status, no ETA, no human. Here's what that does to you as a solo founder — and why it's the whole reason I built what I built.

I submitted an app for review. Then I waited. Then I kept waiting.

Two weeks. No status beyond "In Review." No ETA. No human to ask. Just a page I refreshed more often than I'd like to admit, telling me the same thing every time.

If you've shipped on iOS, you know this specific flavor of helplessness. It isn't the length exactly — plenty of things take two weeks. It's the powerlessness. There is nothing you can do. You can't nudge it, you can't escalate it in any way that reliably matters, you can't even find out whether it's stuck on something real or just sitting in a queue. Your app, the thing you built, is behind a door you don't have a key to, and you just have to stand there.

What it does to a solo founder

When you're a team, review limbo is annoying. When you're one person, it's a special kind of paralysis, because everything was waiting on that submission. I had a demo I couldn't finalize, a plan I couldn't move, a launch shape that assumed the app would be out. And all of it froze — not because I'd done anything wrong, but because I'd handed my timeline to a queue I couldn't see into.

The worst part is the second-guessing. Is it stuck because of something I did? Should I withdraw and resubmit and lose my place? Is silence bad news forming, or just silence? You start negotiating with a process that isn't listening.

The reframe that actually helped

Here's the thing that eventually broke the spell: the review was blocking less than I thought. I'd let one frozen submission freeze my whole head, and when I actually listed what genuinely depended on it, the list was short. Most of what I'd put on hold could move in parallel. Limbo is partly real and partly a story you tell yourself, and untangling the two gave me most of my momentum back.

But the deeper lesson stuck harder, and it's this: the store review model means the gap between "I have the fix" and "my users have the fix" is not up to me. I can have a corrected build ready in minutes and still be days from a user seeing it — with no visibility, no control, standing at that same door.

Why this is the whole reason

That gap is exactly what I've spent months attacking.

Not by fighting Apple — you don't get to opt out of review, and you shouldn't try to. But by making the thing you fix most often — a bad string, a broken conditional, a wrong value, a small logic bug — something you can correct over the air, in seconds, inside the envelope your app was already approved for. So the fix reaches users at the speed you can write it, not the speed a queue decides to move.

I didn't set out to build a company because of one bad two-week wait. But every time I refreshed that page, the same thought got louder: this is absurd, and it doesn't have to be the only way. Standing powerless at a door you can't open is a great way to become very motivated to build a different door.

→ Start building

Try Koolbase

Backend-as-a-service for Flutter and React Native, with over-the-air code push built in.

Start Building