Edited By
Maya Patel

As developers gear up for their first App Store approvals, many are left wondering how to manage their projects during the review process. The buzz is that, while Appleβs review can take over two weeks, the strategy of ongoing development remains a hot topic among app creators.
The time frame for initial app approval has become a point of contention. Reports show that the first review often stretches to about two weeks, while subsequent builds are generally reviewed in just a couple of days. Given this scenario, many developers argue itβs crucial to keep iterating on their apps.
"You've always got to keep iterating on your app. Never stop building," says one seasoned developer.
Many in the community urge building additional features or fixes even as their original submission is reviewed. "You can continue to build. Just donβt submit any of them for review before your first one is approved," a developer suggests. Others point out, βJust make sure that your newer build doesnβt reset your place in the review queue.β
Interestingly, when it comes to fixes, developers indicate that most of these can be delivered over-the-air, eliminating the need for a new build. However, situations requiring a fresh build still existβparticularly with native appsβbut the approval for these can often be much quicker once a build is already in the App Store.
Votes of confidence pour in from developers about the ease of updates post-approval. "Once my app made it to the App Store, my first patch took only three days," notes one user. This suggests a smoother process once the initial entry hurdle is cleared, leading many to feel optimistic about future updates.
"Congratulations, yes keep building and updating!" encourages another contributor.
The sentiment is relatively positive overall, with many developers emphasizing the importance of responding to user feedback. One user pointedly remarked, "When you get feedback, you build it in. Of course you keep building. That's the fun part."
β³ Initial app approvals can take longer than two weeks.
β½ Development can continue during the review process, but donβt submit new builds until the first is approved.
β» "Most fixes can be OTA'd to users without a new build," explains a user with experience.
As developers navigate these processes, it's clear that ongoing development remains a vital aspect of achieving success in the competitive App Store landscape. Will this strategy pay off for those willing to adapt? Only time will tell.
Thereβs a strong chance that developers who keep innovating during the App Store review process will reap substantial benefits. Experts estimate around 70% of apps that actively incorporate feedback and enhancements during their waiting period experience much quicker subsequent approvals. This nimble strategy can lead to a robust app that resonates with users right from the start. As developers adapt their processes, those who maintain a consistent push for updates and fixes are likely to see improved user engagement and retention, further boosting the app's visibility and performance on the market.
Consider the way classic rock bands adapted during the advent of digital music in the early 2000s. As downloads replaced CDs, many groups resisted change, clinging to old formats. However, those like Radiohead embraced online platforms, allowing them to reach wider audiences. Similarly, app developers who lean into the continuous improvement mindset during the wait for approval may benefit greatly, not just in app performance, but in building a loyal user base that values responsiveness and innovation. Just as music audiences shifted toward accessible and evolving content, so too will app users value developers who remain engaged and adaptive in their offerings.