Story

App Store review times in 2026: why indie apps are stuck in 'Waiting for Review' for weeks

On 27 October 2026, Pittsburgh Modular shipped the Microvolt 3901 as a desktop instrument. The iOS version was planned for the same day. It reached the App Store on 12 November. Those dates, reported by Synth Anatomy, are a public example of App Store review times in late 2026: a planned launch, then weeks before the iOS app is on the store.

Apple’s distribution page says “App Review works around the clock”, and that it is “typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours.” On developer forums, in music-software threads, and in posts from people shipping a first version, the status line is “Waiting for Review”, and the reported wait is measured in weeks.

Building the app got fast. Shipping fast with AI made a first version cheap. The store gate is the slow part. Apple told MobileGamer.biz it has prioritised updates to apps already on the store, and that some new apps take longer when they need more scrutiny. The long waits written up since October are the ones small developers have been posting.

This was written on 14 November 2026 in Sydney. Sydney is on Australian Eastern Daylight Time, eleven hours ahead of UTC. Dates below follow the source. At the time of writing, the latest posts in this record, through 13 November, still describe apps sitting in Waiting for Review. A status can change the day after someone posts. Counts of days, rejections, and forum replies are what each source reported.

A timeline of App Store review times

The public record of the slowdown is a short calendar. Apple’s own averages and the waits developers describe are both on it.

When What is on the record
February 2026 A forum thread. At least 74 developers.
March 2026 Business Insider, in The Register's account.
April 2026 The Information: submissions from AI-made apps up 84%.
About 20 October 2026 Apple's statement to MobileGamer.biz.
22 October 2026 The Register. Updated 27 October with Apple's statement.
27 October 2026 Microvolt 3901 ships on desktop. iOS was planned that day.
12 November 2026 Microvolt reaches iOS. Synth Anatomy and AppWinners publish.
12–13 November 2026 A Hacker News thread, then more waiting posts on X.

The February thread, the March Business Insider report, the April figure, and the 22 October piece are in The Register. The same April figure, and Apple's statement reported around 20 October, are in MobileGamer.biz. The Microvolt dates are in Synth Anatomy, 12 November. The same day's roundup of queues and paperwork is AppWinners. The thread is Hacker News.

How long does App Store review take in 2026?

Apple publishes a standing page, and a set of averages from October. Developers are posting a third set of numbers.

The distribution page, linked above, still describes a review that usually finishes inside 24 hours for at least half of submissions, and inside 48 hours for 90 percent. MobileGamer.biz reported Apple’s own figures around 20 October: 378,000 submissions a week on average over the previous 12 weeks, an average review of 1.5 days across all apps, and 14 hours for minor updates. Apple said some new apps take longer when they need additional scrutiny, and that updates to existing apps have been prioritised.

The long individual reports below come from small developers, including the iOS release of a desktop instrument that had been planned for the same day as the desktop ship.

Synth Anatomy, on 12 November, estimated 10 to 20 new iOS music apps a day. That estimate is the site’s. The same piece said AudioThing, Igor Vasiliev, and Sugar Bytes had been stuck for weeks. AudioThing Materia had been in review for 25 days, with one rejection. Seconds, made with Hainbach, had been in review for 29 days and was still counting when the article ran. The same report is where the Microvolt dates sit: desktop on 27 October, iOS on 12 November, after a plan to ship both the same day.

Posts on X over the same week are self-reported, and they scatter.

Francisco Cantu, on 10 November, was on day 16: “Apple’s app review is the slowest, most frustrating part in app development”. @nkndy, on 8 November, was live after 12 days. @katyasamoilova, the same day, had been waiting 9 days and had used the time to pitch the app to Apple’s editors. @ArgileNoland, on 12 November, had been waiting 12 days, with the app already live on Google Play. @hollowtensor, on 11 November: “Same app, same code. Google Play: approved in 6 days. Apple App Store: 2+ months and still “Waiting for Review.””

On the Hacker News thread of 12 November, which stood at 194 points and 228 comments, Juvination wrote of getting one rejection, “and that took 20 days”.

Apple’s 1.5-day average and a 20-day rejection can both be true. The average Apple published mixes every submission, including the minor updates it put at 14 hours. The long individual reports are what the people waiting wrote down.

Why is App Store review taking so long?

Apple’s account is volume, plus a queue that puts updates first.

In the statement MobileGamer reported around 20 October, Apple said it had prioritised updates to existing apps, expanded automation, strengthened abuse detection, and put safeguards on repeated submissions that come back with the same unresolved issues. The 378,000-a-week figure is that statement’s, an average over the prior 12 weeks. So is the split between 1.5 days overall and 14 hours for a minor update. On the submissions that take longer, Apple’s line is specific: some new apps take longer when they need more scrutiny. MobileGamer’s own reporting, from small and mid-size game developers, was waits of weeks. An anonymous CEO told the site: “it’s gone back a decade in terms of approval times. Google is totally fine, though!”

The earlier trail is in The Register on 22 October, updated on 27 October. It describes forum threads titled “Stuck in Waiting for Review for about 3 weeks” and “Waiting for Review Megathread”, a February thread with at least 74 developers complaining, a March Business Insider report, and The Information’s April report of an 84 percent year-on-year jump in submissions from AI-made apps. MobileGamer cites that same April figure. In the 27 October update, an Apple spokesperson told The Register that every app is held to the same high standards for quality, privacy, and security, regardless of how it is built.

AppWinners, on 12 November, said the megathread had passed 118 replies, and linked it: thread 852670. The same piece links four other threads on the wait: 857223, 857137, 856235, and 857266.

The argument on Hacker News the same day ran in several directions.

billyp-rva wrote: “I’m not sure what Apple can do here; Pandora’s box is open and it won’t be closed.” hmokiguess pushed back on a developer in the thread, and wrote that there can be “a real case of AI spamming that same look and feel”. Those two treat the flood as real, and Apple’s problem as a hard one. A weekend of near-copies is already a familiar shape on Show HN, in the HackerTube clone wave. The wider claim that vibe coding is killing indie hacking is about how cheap a copy became.

ggoo put the blame on the review itself, and dated it before the current tools: “This is apple’s fault entirely, not AI’s. app store review sucked well before AI.”

locallost wrote: “basically no one will make any money or have any success off these vibe coded apps.” That is one commenter’s forecast. A separate tally of what payment-verified AI-built apps make is a different record, of apps that published a number. socalgal2 wrote: “Apple’s lock down is arguably incompatible with an AI enabled world.”

littlecranky67 took the other side of the Google comparison the anonymous CEO and @hollowtensor had offered. “Google’s process is far worse”. The reason in that comment is the commenter’s own experience: 12 beta testers for 14 consecutive days.

What does Guideline 4.3 “design spam” mean?

Some apps in the same season were rejected quickly, under a spam rule. The people who received the note believe a machine wrote it.

Guideline 4.3 is Apple’s spam rule. Section 4.3(a) tells a developer not to create multiple Bundle IDs of the same app. Section 4.3(b) tells them not to submit an app that is indistinguishable from what is already widely available. The second clause is the one that meets a store already full of similar tools. Whether indie hacking is oversaturated is the same pressure from the founder’s side: a generic shelf, crowded.

Marek Dendes, of CRUX Synth, wrote on Loopy Pro that CRUX was rejected four times in a row. The labels he recorded were “design spam”, “duplicates existing apps”, and “app generation template services”. His description of the speed: “goes from ‘Waiting for Review’ into ‘In Review’ and then instantly in second to ‘Rejected’”. He had appealed to the App Review Board. As of that post, which Synth Anatomy cited on 12 November, the appeals had been unanswered for about five days. He believes the review is automated. The post shows the labels and the instant he reported. Who sent the rejection sits outside the post.

Michael Hetrick, of Unfiltered Audio, wrote on the same forum that SRR was rejected four times, and that “the editor hallucinated that ‘Polyharmonic’ was an audio technology”. SRR MIDI was flagged as spam for similarity to SRR. He released an audio-only version after “over a month of back-and-forth”. He believes the check is automated. The posts show the rejection text and the speed he reported. They leave the author of the decision unstated.

Apple had already said, in the MobileGamer statement, that it had expanded automation. The spokesperson’s line to The Register, on 27 October, was that the standard is the same however the app was built. An expanded automated check, and a rejection a developer believes was automated, are two reports from the same season. Set side by side, they still leave the author of any single rejection unnamed.

Two other rejections turn on a test the developer disputed. nikanj described a rejection loop over the test account used for account deletion. AppWinners described Suan, a sleep-audio app, rejected on 3 November, 5 November, and 8 November. The last note showed a “no internet connection” error in onboarding. The developer says the app makes no network requests. Google Play had approved the same app. A further 4.3 case is in the same AppWinners piece: a small studio whose two games were rejected under that guideline. The studio answered nine questions on 28 October. As of 12 November, there had been no reply.

What can you do while your app is stuck in Waiting for Review?

The useful part is a short list. Each item is a path Apple has named, or a step a developer in this record took. The same record includes apps that stayed in place after the step.

  1. Plan a new app in weeks. Apple told MobileGamer that updates are prioritised and that some new apps take longer when they need more scrutiny. The page on Apple’s site puts at least half of all submissions under 24 hours. The average Apple gave MobileGamer for a minor update is 14 hours. The waits people reported for a submission that had not cleared are longer: Materia’s 25 days, Seconds at 29 days and counting as of 12 November, Microvolt’s iOS release on 12 November after a 27 October desktop ship, Cantu’s day 16, Juvination’s 20 days for a single rejection, and @nkndy’s approval at 12 days. @katyasamoilova used a 9-day wait to pitch Apple’s editors. That use of the gap is self-reported.

  2. Open App Store Connect and look for an agreement you have not accepted. @ziggydankworth, on 13 November, had been stuck for more than three weeks. The cause, in that post, was an updated Apple Developer Program agreement and terms in App Store Connect, left unaccepted. “No notification. No warning. Nothing.” That cause is self-reported. It is also a check that sits entirely on the developer’s side of the queue.

  3. Use the paths Apple named, and write down the date if an expedite is approved and the status stays put. MobileGamer’s account of Apple’s statement names the App Review Help portal, expedited review, and the bug-fix submission process. AppWinners reported approved expedites that leave the app where it was. In one case a sleep app was submitted on 29 October, the expedite was approved on 5 November, and there had been no movement when the piece ran on 12 November. @ArgileNoland reported that their site was down when they requested an expedite. That is their account of the request.

  4. On a 4.3 rejection, reply with concrete differences. Section 4.3(b) is about an app that is indistinguishable from what is already widely available, and the notes Dendes received said design spam, a duplicate, and an app-generation template. Hetrick’s MIDI build was flagged for similarity to his own audio app. A reply in Resolution Center can name the differences that note is missing. The same record shows those replies waiting. Dendes’s appeals to the App Review Board had been unanswered for about five days. The small studio in the AppWinners piece answered nine questions on 28 October and had no reply by 12 November. Suan’s last rejection named a “no internet connection” error. The developer says the app makes no network requests. That is a specific claim a reply can answer. The appeals and the nine answers above were still waiting when those reports were written.

  5. Ship one distinct app. Guideline 4.3(a) tells developers not to create multiple Bundle IDs of the same app. Several Bundle IDs of one app are the case that clause names. Hetrick’s MIDI companion, flagged as spam for similarity to SRR, is the neighbouring case under 4.3: a second build close enough to the first that review called it spam. One distinct app is the shape those two clauses describe. hmokiguess’s line, quoted above, is the version of that problem a commenter was willing to grant: a real run of apps with the same look and feel.

  6. Ship the web version, or the Android version, where the product still makes sense without iOS. @hollowtensor’s post is the same binary on both stores: Google Play in 6 days, Apple past two months and still waiting, as of 11 November. @ArgileNoland was live on Google Play during a 12-day Apple wait. AppWinners reported Google Play had approved Suan. The anonymous CEO’s line to MobileGamer was that Google is totally fine. littlecranky67’s reply on Hacker News is the other half, and it is that commenter’s experience: Google’s process is far worse, because of 12 beta testers for 14 consecutive days. A web or Play ship is a way to have a product in front of people during an Apple wait. It is a second review, with its own reported costs.

AppWinners also noted paperwork with dates of its own. Apple’s new age-rating questions run from 16 November 2026, with answers due by 12 January 2027. Google Play’s trader declaration is due by 1 February 2027. Those dates are from that piece. They sit in the same consoles as the agreements in item 2.

What do you think? How long did your last App Store review take, and would you ship a web version first now?

FAQ

Why is App Store review taking so long?

Apple told MobileGamer.biz, in a statement that site reported around 20 October 2026, that review is absorbing a flood of submissions: 378,000 a week on average over the previous 12 weeks. Apple said it has prioritised updates to existing apps, expanded automation, strengthened abuse detection, and added safeguards against repeated submissions that still carry the same unresolved issues. The average Apple gave was 1.5 days across all apps and 14 hours for minor updates, with some new apps taking longer when they need more scrutiny. The Information's April figure, as cited by MobileGamer and by The Register, was an 84 percent year-on-year jump in submissions from AI-made apps. The Register traces public complaints through a February forum thread of at least 74 developers, a March Business Insider report, and that April figure. On Hacker News on 12 November, billyp-rva wrote that Pandora's box is open, and hmokiguess wrote there can be a real case of AI spamming the same look and feel. ggoo wrote that review sucked well before AI, and that the fault is Apple's. Developer reports of multi-week waits are the reporters' own counts.

How long does App Store review take in 2026?

Apple's distribution page says App Review works around the clock and is typically reviewing at least 50 percent of submissions in less than 24 hours and 90 percent in less than 48 hours. Apple's figures to MobileGamer, reported around 20 October 2026, put the average at 1.5 days for all apps and 14 hours for minor updates, and said some new apps take longer when they need additional scrutiny. Reported waits on new apps run longer than that average. Synth Anatomy on 12 November reported AudioThing Materia at 25 days with one rejection, and Seconds, made with Hainbach, at 29 days in review and still counting as of that article. Pittsburgh Modular's Microvolt 3901 shipped as a desktop instrument on 27 October and reached iOS on 12 November, after a planned same-day release. Self-reported posts on X from 8 to 13 November describe 9 days, 12 days, 16 days, more than three weeks, and more than two months. Those figures are what each developer reported. They are a separate number from Apple's average.

What does Guideline 4.3 "design spam" mean?

Apple's Guideline 4.3 covers spam. Section 4.3(a) tells developers not to create multiple Bundle IDs of the same app. Section 4.3(b) tells them not to submit apps that are indistinguishable from what is already widely available. Marek Dendes of CRUX Synth wrote on Loopy Pro that CRUX was rejected four times in a row under the labels design spam, duplicates existing apps, and app generation template services. He described the status moving from Waiting for Review into In Review and then, in a second, to Rejected, and wrote that appeals to the App Review Board had gone unanswered for about five days. Michael Hetrick of Unfiltered Audio wrote that SRR was rejected four times, that an editor treated Polyharmonic as an audio technology, and that SRR MIDI was flagged as spam for similarity to SRR. He released an audio-only version after more than a month of back-and-forth. Both developers believe the review is automated. Their posts show the rejection text and the speed they saw. They do not establish that an automated system made the decision.

What can you do while your app is stuck in Waiting for Review?

Plan a new-app launch in weeks. Apple told MobileGamer that updates to existing apps are prioritised and that some new apps take longer, and the reported calendars here run from about nine days to more than a month. In App Store Connect, check for an Apple Developer Program agreement you have not accepted. On 13 November a developer posting as ziggydankworth reported a stall of more than three weeks from updated terms, with no notification. Apple pointed MobileGamer to the App Review Help portal, expedited review, and the bug-fix submission process. AppWinners reported a sleep app submitted on 29 October whose expedite was approved on 5 November and that had not moved by 12 November, so an approved expedite can sit. On a Guideline 4.3 rejection, reply with the concrete differences from the apps the note treats as the same, which is the line 4.3(b) draws. Replies can sit too: Dendes's appeal had been waiting about five days, and AppWinners described a small studio that answered nine questions on 28 October and had no reply by 12 November. Where a web or Android build fits, some developers shipped there while iOS waited. The same record includes a Hacker News comment that Google's process is far worse, citing 12 beta testers for 14 consecutive days in that commenter's experience. AppWinners also noted new Apple age-rating questions from 16 November 2026, to be answered by 12 January 2027.

Is Google Play faster than App Store review in 2026?

Some developers say yes, for the same build, and one Hacker News comment says the opposite. An anonymous CEO told MobileGamer that Google is totally fine. hollowtensor posted on 11 November that the same app and the same code was approved on Google Play in 6 days and was still Waiting for Review on Apple after more than two months. ArgileNoland posted on 12 November that their app was live on Google Play while Apple had been waiting 12 days. AppWinners reported that Google Play approved Suan, a sleep-audio app Apple had rejected three times. littlecranky67 wrote on the 12 November Hacker News thread that Google's process is far worse, and described a requirement of 12 beta testers for 14 consecutive days in their own experience. These are reports from the people who went through each store. At the time of writing they are not a measured comparison of the two queues.