Shipping my first React Native app to Google Play
Publishing Taskly to the Google Play Store was one of the most meaningful milestones in my developer journey. It was my first React Native app, and taking it from an idea to a live production release taught me more than any tutorial ever could.
Why I built Taskly
I wanted to build something practical - an app that people could actually use day to day. Taskly started as a simple productivity idea, but it quickly became my learning ground for React Native architecture, real-device testing, release management, and the full Play Store launch process.
The part I didn't expect: shipping is hard
Building the app was one challenge. Shipping it was a completely different one.
I registered for a Google Play Console Individual Developer Account and got to work preparing my first release. One requirement I didn't fully appreciate at the time was the closed testing period that Google requires before granting production access to new apps.
I thought I was doing enough. I invited a few friends and colleagues to the closed testing track, watched the installs come in, and waited out the 14-day window.
After the waiting period, I applied for production access.
It got rejected.
Google's feedback was clear: more meaningful testing was needed.
Starting over - properly this time
That rejection was frustrating. But looking back, it was exactly the push I needed.
Instead of rushing through the process again, I took the time to do it properly:
- I created a WhatsApp group specifically for my closed testers so I could communicate directly, share updates, and actually ask for feedback
- I encouraged real usage rather than just passive installs
- I set up a ClickUp workspace to track issues - bugs, feature requests, priorities, fix cycles, and retesting
- I went through proper testing iterations and documented the progress
It changed everything. The testing felt structured and intentional. I could clearly show improvement over time rather than just pointing at an install count.
Getting approved
After running a proper closed testing cycle and iterating on real feedback, I applied again.
This time, it was approved.
Seeing Taskly go live on the Play Store was genuinely one of those moments where I sat back and felt proud. It wasn't just about the app. It was about learning the full real-world process, including the part where you fail, adjust, and try again.
What I took away from this
Closed testing should be active, not passive. Installs alone don't count. Google wants to see real engagement and real feedback cycles.
A communication channel matters. The WhatsApp group made it easy to collect honest feedback quickly. Testers felt involved rather than just being a number.
Issue tracking turns chaos into progress. Keeping a ClickUp board meant I could turn feedback into tasks, track fixes, and have a clear record of how the app improved over time.
Rejection is part of the process. It wasn't a dead end - it was just a signal to do the work more thoroughly.
Taskly is more than just my first React Native app. It represents persistence, process, and what it actually takes to ship software the right way.
And honestly, I'm really happy to say: I released my first mobile app to Google Play.