Building
My Google Play Console Experience
What I learned while building Cropz Card, preparing it for testing, getting rejected, and finally publishing it on Google Play.

Aug 12, 2026 - 2 min read
Originally published on Medium
This post started as a real build story: how Cropz Card moved from a family business idea into an app published on Google Play.
The idea came from a simple problem. Wholesale dealers and retailers often share physical business cards, but customers do not always keep them. For farmers and shop customers, a digital card could be easier to save, open, and share. That became the starting point for Cropz Card.
Building the app was only the first part. The release process taught me that publishing is its own product challenge. I had to create a Google Play Developer account, register the app, prepare internal testing, organize closed testing, gather enough testers, answer detailed review questions, and wait through multiple review cycles.
The hardest lesson was patience. I originally expected publishing to take a few weeks. Instead, the process involved months of building, testing, rejection, fixes, and another round of waiting before the app finally reached production.
The experience made one thing clear: an app is not ready just because the code runs. Before users see it, the product has to survive testing, policies, store listing work, review feedback, security expectations, and a lot of small details that are easy to underestimate.
Cropz Card is now part of the build archive for this site because it represents an important milestone: not just building an app, but learning what it takes to actually release one.
- Cropz Card on Google Play: https://play.google.com/store/apps/details?id=in.cropz.cropz_app
- Cropz Card website: https://cropzcard.com/