Advice for getting through Google Play app approval process (production release)

[MattWeiler]

I recently built an Android app but the Google Play store review process is a complete PITA.

For now, it's just an Android app, but if it's successful, I'd make an iOS version.

I just don't find it intuitive (lol, jk... If you watched WAN show today, you'll get it).

 

 

About My App

I built the app that allows users to digitize their favorite books and record different people reading them.

Then kids can have their favorite books read to them in the voice of a loved one. 

I also added the option of an "AI Reader" (I hate that term, but that can you do, that's what people expect).

 

Since I don't want to be sued, we don't provide any books, except for a few public domain books that I found online on some government run websites. I created a book store, in the app, through which you can download those free books. 

 

But the main expected use is for people to digitize their kids favorite books and then have loved ones record themselves reading the books. 

 

So far, my daughter and niece love the app and use it almost daily. 

Also, my 78 year old dad finds it easy to use when recording his voice.

 

I see the main users being:

1. Parents/grandparents who can't always be around for bedtime; either shift workers or maybe people deployed over seas.
2. People who want to keep recordings of loved ones, who have passed away.

 

I really built this app as a means to help my kids not forget what their grandfather sounds like. I know that sounds morbid, but my mom died 15 years ago, and sometimes I can't remember what she sounded like. My dad is turning 78 later this year and I'm just realistic.

 

I don't plan to make any money off of my app, maybe sometime in the future. But the apps current features would never be rug-pulled.

 

Before you ask, I find in-app ads to be just gross, especially in apps aimed at kids. We have a cheap Android tablet for our daughter, and almost every kids app has intrusive ads

 

 

My Issue

Since my android developer account is new, I'm not grandfathered in which means that before I can release my app publicly, I have to get 20 testers to participate in a closed test, which lasts for 14 convective days, during which time they have to regularly use my app.

 

Initially, finding 20 people was difficult since 50% of people are iOS users, and frankly I don't want to ask people who don't have kids to test my app that wouldn't be relevant to them.

 

I was able to get 21 people to casually use my app for the 14 days, but yesterday Google denied my request to release publicly saying that the testers didn't use the app enough... So now I have to start again with 20 people testing for 14 consecutive days, I guess more rigorously this time

 

 

Does anyone have any advice on how to get through this process smoothly?

 

 

If anyone would like to help me by testing my app, you can just join my Google group: 

app-testers-weilerhause@googlegroups.com

[Eigenvektor]

Maybe have a look here:

https://www.reddit.com/r/AndroidClosedTesting/

[MattWeiler]

8 hours ago, Eigenvektor said:

Maybe have a look here:

https://www.reddit.com/r/AndroidClosedTesting/

Thank you, I'll check it out

[Ekows10]

Please keep updating your post as this is exactly what I need. I don't have a 'shut up and take my money' gif to hand but if I did I'd post it.

 

[MattWeiler]

On 11/9/2024 at 3:36 PM, Ekows10 said:

Please keep updating your post as this is exactly what I need. I don't have a 'shut up and take my money' gif to hand but if I did I'd post it.

 

You could try this... I've heard that it can give good results. 

 

https://play.google.com/store/apps/details?id=com.testerscommunity

[MattWeiler]

On 11/9/2024 at 3:36 PM, Ekows10 said:

Please keep updating your post as this is exactly what I need. I don't have a 'shut up and take my money' gif to hand but if I did I'd post it.

 

I also found this thread that gives some good tips on getting your app approved

 

https://www.reddit.com/r/AndroidClosedTesting/comments/1gosk57/i_published_my_app_after_3_rejections_and_5/

[MattWeiler]

On 11/9/2024 at 3:36 PM, Ekows10 said:

Please keep updating your post as this is exactly what I need. I don't have a 'shut up and take my money' gif to hand but if I did I'd post it.

 

 I just applied for production after my 2nd closed test.

I'll update here with what happens.

 

This test I was able to get more testers and they actually left useful feedback.

I'm hoping that makes a difference.

 

I also released 3-4 new builds during the closed test which addresses bugs and suggestions identified by the testers.

In my 1st closed test I didn't release any new builds during the closed test, I believe this was part of what got me denied.

 

Also, I wrote far more for each section of the production application form... From what I've read online, you need to have at least 250 letters in each input box, with a maximum of 300.

 

[MattWeiler]

On 11/9/2024 at 3:36 PM, Ekows10 said:

Please keep updating your post as this is exactly what I need. I don't have a 'shut up and take my money' gif to hand but if I did I'd post it.

 

I applied for production yesterday, and I just got the email that it was approved.

 

I mostly followed the advice from the below post.

 

 

Below are my answers to the questions in the production application form:

I stuck as close to 300 characters as I could for each free-style question.

 

How did you recruit users for your closed test? For example, did you ask friends and family, or use a paid testing provider?
I initially reached out to my family and close friends whom I know are Android users and have children in the target age group for my application.
I also posted on some relevant Reddit subreddits and received a lot of interest and quite a few people tested my application with their children.

How easy was it to recruit testers for your app?
Neither difficult or easy

Describe the engagement you received from testers during your closed test
Include whether or not testers utilized all of the features in your app, and whether tester usage was consistent with how you would expect a real user to use your app. If not, describe the differences you would expect to see.
Testers provided detailed feedback on the app, identifying bugs and suggested improvements.
Thanks to their feedback, we released targeted updates which have resulted in a more intuitive and consistent interface.
The app was used in ways that we expected and utilizing all of the major features.

Provide a summary of the feedback that you received from testers. Include how you collected the feedback.
We gathered feedback by talking to testers via the Play Store feedback section.
The feedback was positive: they reported minor bugs and suggested new features such as some accessibility improvements, some changes to make the app more consistent and that we support more languages, improving usage.

Who is the intended audience of your app?
My app is expected to be used primarily by families.
Parents and grandparents are expected to create the content in the app which includes them recording themselves reading the stories.
Once the content has been created, their children/grandchildren can then use the app to playback the content.

Describe how your app provides value to users
My app allows people to record themselves reading their families favorite stories so that their children can listen to their loved ones reading their favorite stories even when they cannot be there. 
The app will be useful to children with loved ones who have died, work shifts or deployed over seas.

How many installs do you expect your app to have in your first year?
100K - 1M

What changes did you make to your app based on what you learned during your closed test?
Based on tester feedback, we optimized the interface to be more intuitive and consistent across the app. Additionally, we added support for roughly 40 languages to target a broader audience. We also added some requested features and fixed minor bugs to ensure a frictionless experience for our users.

How did you decide that your app is ready for production?
We decided the app is production ready due to its refined interface, seamless navigation and overwhelming positive feedback. We addresses all tester feedback, polished the design to meet usability and accessibility standards. Its stability and bug free experience makes the app ready for public use.

What did you do differently this time?
During this closed test, we incorporated tester feedback into the development cycle. We refined the interface, added new features and resolving all bugs. Our focus has been on usability and intuitive design, guided by tester feedback. Our app is now polished and responsive and meets users needs.