Google Play: 12 testers for 14 days
With a personal developer account made after 13 November 2023, Google won't let you publish straight away. You first run a closed test with at least 12 testers, who have to stay opted in for 14 days in a row. Only then can you apply to release the app to everyone. Finding 12 people who'll install an unfinished app and keep it for two weeks is harder than it sounds.
Apple: a review team, and sometimes a long wait
Apple's App Review team checks every app and every update before it goes live. Apple says it reviews 90% of submissions within 48 hours, but it can sometimes take up to two weeks.
Apple also turns away apps that don't offer enough. Its guidelines say: "If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store." Your first small app may well be rejected for that. Build something that does a real job.
Test phones cost more than you expect
You need real phones to test on, and the cheapest ones won't always do. If your app uses the camera to sense depth or for augmented reality, many Android phones can't run it: Google's ARCore only works on phones that have passed Google's certification. So you end up buying better phones just for testing.
Dependencies keep breaking
Every app is built on dependencies: code written by other people that handles jobs like the camera or maps. That code keeps changing. Open a project after a few months and Xcode, Apple's developer tool, shows a long list of outdated items.
Often the problem isn't your code at all, it's a dependency. Sometimes you have to keep an old version because one of them was never updated, and upgrading would break your app. Then you spend hours looking for a replacement.
Getting past them
Getting past each of these is what we cover in a Practical AI session. The first session is free.