Case Study: DocWala Passed Google Play Closed Testing

DocWala: PDF Document Scanner is our founder's own Android app. We ran its Google Play closed test with TestersFourteen testers, using the same CSV and opt-in link process as for clients. 37 tester emails were in the CSV and 22 testers installed the app. Google granted production access on the first application, and DocWala is now live.

Our own app, not a client's. DocWala belongs to Umashankar Kushwah, who runs TestersFourteen. We are saying this first because a case study about your own product is not the same as an independent client result, and you should read it with that in mind.

FactDocWala
AppDocWala: PDF Document Scanner (com.docwala.scanner)
DeveloperUmashankar Kushwah, founder of TestersFourteen
Testers in the CSV37
Testers who installed the app22
ResultProduction access on the first application
Google's minimum12 testers, each one opted in for 14 continuous days (App testing requirements)

What is DocWala?

DocWala: PDF Document Scanner is an Android app published on Google Play under the package name com.docwala.scanner. Its developer is Umashankar Kushwah. Before it could apply for production access, it went through a Google Play closed test, and it is now live. You can see the app on its Google Play listing.

Why is this our own app?

This is the first case study we have published, and we only publish cases we can describe with real numbers. The founder's own app is one we can describe completely. That has one advantage: every number on this page is real. It also has a clear limit: the developer and the testing service are the same person, so this is not independent proof. It is a description of what happened.

How was the closed test run?

We ran it the same way we run a client test. We prepared a CSV file of tester emails, and it was uploaded to the closed testing email list in Play Console with Google's Upload CSV file option. Then the closed testing opt-in link went to our testers, who joined the test and installed the app on their own Android devices.

The CSV held 37 tester emails, and 22 testers installed the app. Those are the only two numbers we have for the test, so they are the only two on this page. Installing the app and being opted in are separate steps in Google's process, and the 22 is an install count. Our how we test page describes each step of the process in full.

What happened when we applied?

After the closed test, we applied for production access from the Dashboard in Play Console. Google granted production access on the first application, and DocWala is now live on Google Play. Our guide to applying for production access walks through the same form, section by section.

What does this show, and what doesn't it?

It shows that our process ran end to end for one real app: a tester CSV, an opt-in link, testers installing the app, and an application that Google approved the first time.

It does not show more than that. It is one app, and it is our own. Results depend on the app, and Google decides every production access application, so no case study, including this one, can tell you what will happen with yours. We do not promise production access to anyone.

How can you run the same test?

Choose a package on our pricing page: Basic (₹1,000, 12 testers), Pro (₹2,000, 20+ testers) or Max (₹3,000, 30+ testers), paid 50% to start and 50% on day 14. We send you a CSV of tester emails, you upload it in Play Console and send us your opt-in link, and testers usually start joining within 10 minutes. To start, contact us by email or WhatsApp.

When your 14 days are complete, our production access questionnaire answers guide has a fill-in template for each question Google asks.

Umashankar also wrote about this test on dev.to.