First submissions are waiting weeks in App Store review. Work backward from the day you need to be live
Apple says most apps are reviewed within a day or two. Developers have spent weeks telling each other otherwise. If your launch has a date attached, the wait is now something you plan for, not something you find out about.

Apple's published goal is to review half of submissions in under 24 hours and 90 percent in under 48, but since October developers and press have reported first submissions waiting two to three weeks or longer, and approved expedite requests that didn't move. If an app has to be live on a date, count backward from that date with a review wait you can't predict, submit early, and release manually once approved.
The promise and the reports
Apple's own help page says App Review works around the clock, with the goal of reviewing at least half of submissions in under 24 hours and 90 percent in under 48. For most updates that may still be roughly true. For some first submissions, it isn't what developers have been describing since October.
On October 22, The Register collected forum posts with titles like "Stuck in Waiting for Review for about 3 weeks" and "since October 8," and one developer who said they'd been waiting since September 19. It noted that similar complaints had appeared in February, some about bug fixes to apps already approved. Apple's statement, added October 27, said the company continues to evolve its review process to support developers embracing the latest tools. A mobile-games newsletter the next day carried a studio boss saying review times "have gone back a decade," and said Google Play's review times remain solid, according to its sources.
None of this is Apple's data. It's developers reporting their own waits. But it's consistent enough that a launch plan shouldn't assume the 48-hour number.
The Register also pointed to earlier coverage tying slow reviews to a surge of AI-coded apps, including a report that submissions were up 84 percent in April. Apple hasn't said that's the cause, and neither can we. What matters for you is smaller: whatever the reason, the queue is longer than the help page says, and it isn't yours to control.
What an expedite will and won't do
Apple lets you request an expedited review for something like a critical bug or timing a release to an event. The help page says the app has to be submitted for review first, and the request is judged "as allowed by availability and demand." It also says to reserve expedites for genuine urgency.
AppWinners' November 12 roundup reported the complaint that made this week's news: Apple approving an expedite and the app staying in "Waiting for Review" anyway. One developer's sleep app was submitted October 29, had an expedite approved November 5 and still hadn't moved when they posted. Another had an expedite approved November 10 with no change in status. The community tracking thread had passed 118 replies.
The same roundup described developers receiving rejections one issue at a time, including one who reported three in six days, each raising a new point after the last was fixed. You can't count on a single pass, so don't build a calendar that needs one.
Treat an expedite as a request, not a lever. If your plan only works when the expedite works, it's not a plan.
Sequence of work
Counting backward from a launch day
- Launch day
The date customers have been told. Everything else is counted from here.
- Release approval
Hold the approved version and release it yourself, so approval and launch are separate decisions.
- Review wait
Unknown. Apple's goal is a day or two; developers report weeks for some first submissions.
- Submit
Notes filled in, a demo account that works, every required answer completed.
- Build freeze
Earlier than feels necessary, so a rejection costs a day and not a deadline.
A launch date is a promise to your customers. The review queue made no such promise.
Count backward
Start with the day customers will see the app, and subtract. Leave a day or two for the release itself. Subtract a review wait you can't predict: likely shorter for an update to an established app, though The Register noted multi-week waits on bug fixes too, and, from the current reports, potentially weeks for a first submission. Subtract the time to fix one rejection and resubmit, because the November reports include developers getting rejections one issue at a time. Subtract the build freeze.
Here's an illustrative example. Say you've promised customers an app on December 15. Release the day before. Assume a pessimistic three-week review. Allow three days to fix one rejection and resubmit, and a four-day freeze before you submit. Counting back, you'd need to submit around Monday, November 16, which is nearly here. If your build isn't frozen, the date has already moved.
Where you land is probably earlier than the date on your marketing plan. That's the useful finding. Either the date moves, or the submission does.
Two small things make a first try more likely to count. Fill in the Notes field and provide a demo account or demo mode for anything behind a login, which Apple's own page tells you to do. And set the version to release manually after approval, so a surprise approval on a Saturday doesn't launch something your support team isn't ready for. We wrote about that single-attempt mindset in Apple's reviewer gets one try at your app.
A launch date is a promise to your customers. The review queue made no such promise. So the slack has to live in your calendar, not in your customers' patience.
Have a plan B for the wait
While the app waits, the web version, the waitlist page or the next update can keep moving. Tell customers a window, not a day, until approval arrives. Give support a short holding message. If a partner or press piece depends on the date, say now that it may slip and why.
Another date is coming. Apple's App Store Connect adds two age-rating questions on November 16, about shared location and dating features, and every app must have its answers in by January 12, 2027. They have to be completed when you submit an update or change the age-rating answers, so build the questions into your next submission and not a separate scramble.
Keep a record of what you submitted and when. If a review takes longer than you assumed, a dated note of the build, the notes you gave the reviewer and any reply from Apple makes the next conversation shorter. It also shows your team, afterward, which assumption turned out to be wrong, so the next calendar is better than this one.
A last practical point: don't let the submission be the first time anyone outside the team sees the app. Ask a colleague or a friendly customer to install the build from TestFlight and try the main path before you send it. Most surprises that cost a rejection cycle show up in the first ten minutes of a fresh pair of eyes.
Decision guide
Two ways to spend the wait
| Consideration | Without a plan B | With one |
|---|---|---|
| Customers | Told a date you don't control | Told a window, with the date confirmed once approved |
| Marketing | Scheduled to a launch day | Built to move when approval comes |
| Support | Hears about it from customers first | Has a holding message ready |
| The wait itself | Refreshing App Store Connect | Finishing the web version, the waitlist or the next update |
What we'd do this week
List every app, version and date you've promised. Beside each, write the review wait you're assuming. If it's 48 hours, ask yourself what that number is based on. Move the submission earlier where you can, and put a real plan B beside every date you can't.
If you're launching an app or an update this season and want a second pair of eyes on the calendar and the submission, that's part of our mobile applications work. Talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.