Waiting for Review

Version 1.16 was looking sharp. Quentin and I were genuinely proud of what we had on our hands.

A real solo mode — the Solo Quest. A Daily Quest to give players a reason to come back every day. The duel mode still there for those who want it. A few items, a basic streak system, and our brand new avatars on top of it all. We had also done a full pass on the design, and for the first time, we were actually satisfied with how the app looked. We even integrated an effect inspired by Apple's liquid glass style — a small thing, but the kind of detail that makes the whole UI feel alive.

We were ready.

After nights of polishing bugs, chasing tiny visual inconsistencies, and obsessing over details only we would ever notice, we were ready to move from a closed beta to an open beta. Anyone with a TestFlight link could join. We capped it at 200 players to keep things manageable, but it was a real opening of the doors.

Submitted

Monday morning. We push the build. We hit submit.

And then, the words every iOS developer learns to dread:

Waiting for review.

"Okay," I told myself. "It'll be fast. Apple says 72 hours max."

Three days later, nothing. The status hadn't moved. Nobody on the Apple side had so much as glanced at the build.

"They said 72 hours, right?"

Five days later, the status finally flipped to Under Review. Relief, but also a fresh wave of dread — because what if it gets rejected? What then? Do we wait another eight days for a second pass? The whole approval cycle hangs over your head like a coin toss with a one-week delay.

The wait

The waiting itself is bad. But what's worse is the powerlessness. You spent weeks pouring everything you had into a build. You stayed up late. You polished the corners. You poured your guts into something you genuinely believe is good — and then it just sits there, untouched, in a queue.

Meanwhile, the beta launch we had announced kept slipping. The momentum we had built up was leaking out, day by day. Every morning I'd refresh the App Store Connect dashboard hoping for movement, and every morning the same status stared back. It's a kind of frustration that's hard to explain to anyone who hasn't shipped on iOS.

Honestly, this approval cycle is brutal for small teams. It creates a friction that nobody really talks about — not the technical kind, but the emotional kind. The kind that makes you doubt the schedule, doubt the plan, doubt yourself a little.

Approved

And then, finally, the email landed.

Approved. Ready to test.

The beta could begin.