I've built mobile apps before, but always for clients or employers. DroolFinder is the first app I've built and shipped entirely for myself, which meant going through the full App Store and Google Play submission process as the developer, owner, and publisher all at once.
Most of what I thought I knew about that process turned out to be wrong.
The app is called DroolFinder. The idea is simple: you take a photo of a dog, and the app uses AI to identify the breed and give you information about it. It's the kind of app that's fun, immediately useful, and hopefully something dog lovers will enjoy pulling out when they see a particularly interesting looking dog at the park.
Building it was its own journey, but that's a post for another day. This one is about what happened after the build, when I had to actually ship the thing.
The Reputation
If you've spent any time in developer circles, you already know the reputation. Apple is the walled garden. The control freaks. The company that famously rejects apps for vague policy violations, forces you through an opaque review process, and maintains an iron grip on what gets onto their platform. Google Play, by contrast, is supposed to be the more open, more developer friendly alternative. You upload your APK, fill out a few fields, and you're done.
That's the narrative anyway.
And I believed it going in. I had mentally prepared for Apple to be the hard part. I figured I'd spend a week going back and forth with reviewers, getting cryptic rejection emails, and updating screenshots to meet some obscure guideline I'd missed. Google I expected to be done in an afternoon.
I was wrong about both.
Submitting to Apple
I'm not going to pretend the App Store submission process is frictionless. Setting up your Apple Developer account, navigating App Store Connect, getting your certificates and provisioning profiles sorted, dealing with Xcode... there's friction. There's definitely friction. But that friction is largely a one time setup cost, and once you're through it, the actual submission experience is surprisingly straightforward.
You fill out your app metadata, upload your screenshots, write your privacy policy, answer some questions about your app's content and data collection practices, and submit. Then you wait.
I submitted DroolFinder and expected to hear nothing for at least a week. Instead, Apple reviewed and approved it in about 3 days. No rejection. No requests for more information. No cryptic feedback about guideline violations. Just a notification that the app was approved and live on the App Store.
I actually checked my email twice because I thought I'd misread it.
Submitting to Google Play
This is where things got interesting.
Google Play has a process that I genuinely did not know existed until I was already in the middle of it. To get an app in front of real users, you have to go through a series of testing tracks.
Internal testing is available immediately, but that's limited to a small list of email addresses you manually add. To move to closed testing, which is the step before production, you need a minimum of 12 testers who have to actively opt in to your test via a link.
And here's the kicker: you have to run that closed testing period for a minimum of 14 days before you're even eligible to apply for production access.
Fourteen days. Mandatory. No exceptions.
So before Google will even consider letting your app go live to the general public, you need to recruit at least a dozen people, get them to opt into your test, and then wait two weeks. For a solo developer shipping a side project, finding 12 people willing to install and test your app isn't always trivial, and the mandatory waiting period means you can't move fast even if everything else is perfect.
For me the struggle was most of my friends and family were iPhone users, not Android users. So finding 12 people without paying for testers on Android was a real genuine struggle. I get why they make you do it, but it's annoying.
On top of that, there's a questionnaire you have to fill out when applying for production access. It covers things like your app's purpose, target audience, whether it's designed for children, your data handling practices, and more. Some of this overlaps with the Data Safety section you fill out earlier in the process, which makes the whole thing feel a bit redundant and bureaucratic.
They ask you how you get your testers, how engaged the testers were, what issues they flagged and feedback you received from them, whether you paid for testers and a bunch of other questions.
After you submit your production access application, a human reviewer has to approve it. So you're waiting on that too. I've been ironically waiting at this step longer than it took for Apple to approve my app and publish it to the App Store.
By the time DroolFinder will be live on Google Play, it will have been a significantly longer process than Apple, which is genuinely not a sentence I expected to type.
So What's Actually Going On Here?
I think the reputation of Apple as the uniquely restrictive platform is outdated, or at least incomplete. Apple has historically earned that reputation, and there are still plenty of horror stories about apps being rejected for questionable reasons. The 30% cut, the anti-competitive arguments, the Epic Games saga, all of that is real and worth discussing. I'm not here to defend Apple as a company.
But specifically talking about the experience of submitting a straightforward, consumer app to both stores for the first time in 2026? Apple was faster, clearer, and honestly less painful than Google. The closed garden, at least at the gate, was easier to walk through than I expected.
Google's approach makes sense from a quality control perspective. The mandatory testing period is presumably designed to catch bugs and ensure a baseline level of quality before apps go wide. The questionnaire helps them categorise and moderate content.
I get the reasoning.
But the effect for a solo developer is that your launch timeline is dictated by a 14 day calendar countdown that starts only after you've recruited enough testers, which adds real friction and unpredictability to the process. This might explain why a lot of apps I see that launch are iOS first.
What I'd Tell Someone Building Their First App
Don't fear Apple as much as the reputation suggests. Get your developer account set up early because that takes a bit of time, sort out your certificates, and follow the submission guidelines carefully. If your app is legitimate and you've done the basics right, the review process might genuinely surprise you.
For Google, start recruiting your 12 testers before you think you need them. The moment your app is in a usable state, get people opted into your closed testing track and start that 14 day clock. If you wait until your app is polished and ready to launch before thinking about testers, you're adding at least two weeks to your timeline whether you like it or not.
DroolFinder is available now on the App Store and hopefully soon on Google Play. If you see a dog you can't identify, you know what to do.