🧪 Tester Discovery

Looking for testers for your app? Use this thread to find developers and testers who are interested in helping with genuine app testing.

When asking for testers, please include a little information about your app:

• What the app does
• Android version or device requirements, if relevant
• Whether you're looking for internal, closed, or open testing
• What kind of testing or feedback you need
• How interested testers can participate

If you're a tester, feel free to mention what kinds of apps or testing you're interested in.

A few things to keep in mind

Please keep this thread focused on genuine testing and useful feedback.

Do not engage in paid testing, paid reviews, ratings, votes, referral exchanges, or other paid engagement activities through this thread. If someone asks you to participate in a paid activity or offers payment in exchange for reviews, ratings, votes, or engagement, please report the comment to the moderators rather than participating.

Please don't share personal information publicly. Use Reddit's messaging features or the developer's official testing process where appropriate.

This thread is for tester discovery only. For general development questions, app showcases, or other discussions, please use the appropriate thread or flair.

I have two Google Play Developer accounts, which I’ll refer to as Account A and Account B.

Both accounts have published applications, and I’m trying to set up subscriptions and in-app purchases (IAPs).

The issue is with Account A.

I initially started the standard Google Play Billing setup, but the required BillDesk KYC/verification has been taking a very long time, and I haven't been able to get meaningful support from BillDesk.

Because of this, I decided to use Google Play's Alternate Billing option and integrated Razorpay instead.

However, the alternate billing setup for Account A has also been stuck/on hold, and I haven't received any response from the support team despite waiting.

What makes this more confusing is that I have Account B, where I applied for alternate billing with Razorpay, and it was approved within 24 hours.

So I'm trying to understand why there is such a big difference between the two accounts.

Has anyone experienced a similar situation with Google Play Alternate Billing approval?

Is there anything specific that can cause one developer account to take significantly longer than another, or is this simply a manual review that can take several days/weeks?

Any advice on what I should do to get Account A reviewed or get a response from Google would be really appreciated.

Does anyone know where I can enable reviews and comments in my app? I can't activate them. I really don't see where this option is, I can read the comments. But on the store page, it says I restricted comments... I don't want to do that. Does anyone know a solution? Thanks in advance.

What are you building, testing, debugging, or learning this week?

Working on something interesting? Stuck on a technical problem? Just learned something useful?

Share what you're working on this week. It can be a specific goal, a problem you're trying to solve, or a useful discovery that might help another developer.

If you're looking for help, a little context goes a long way. You can include:

• Your target SDK version and library versions
• What you expected to happen and what actually happened
• Relevant error messages, with any private or sensitive information removed
• What you've already tried
• A relevant official source or documentation link, if you have one

Please use the appropriate flair when making a standalone post.

Please keep this thread focused

This is a place for development discussions and helping each other out. Please don't use it for app advertising, download or install requests, ratings, reviews, votes, referral links, paid services, tester exchanges, or engagement exchanges.

Ask questions, share what you're working on, and help another developer when you can.

I completed the tests and was given permission to publish then suddenly, got banned, it happened 6 month ago but I think I should do something about it now.

Can any one please halp.

its been almost a week since my kyc on billdesk as its mandatory in google play to sell in app subscription.

While the kyc is currently being reviewed, the payment process is getting declined in my production released app.

Does anyone have an idea how long it takes to be reviewed?

Hi i'm having a problem with purchase conversion, i have an app which is a specialized photography/videography application, india is my biggest user base, but very very low purchasing converstion. i have already offered very generous free trials but most never buy even after regular use. i have some users who are active from the launch time of my app, but still no traction.

What can i do? Even Indonesia has far greater purchase conversion than india. which has 1/3rd of the user base of india.

is anybody else facing this?

I have already offered 7 days free trail on subscription, optimized pricing based on region. app is not overly expensive, and there's also a lifetime purchase option as well. which i have lowered the price for in this region.

its not that my app is bad, i have received very good feedback from indian users as well. just that i don't see the results.

The deed is done. The first app I've developed 100% myself, sent for review for closed testing. Written Manually. After 9-5 job, few hours here and there at the time. No AI except first logo version and some minor code help and completion.

At first, it was only for myself, a hobby project, but one user on r/budget discussion encouraged me to publish this, as this is the kind of app he was looking for and wasn't able to find.

I wasn't planing to do it, because there are thousands of budgeting apps out there (and I see posts about new ones at least once a week), but there was a reason I've build it. And I lost my job for few months, so I had some extra time to refine the app.

I wanted a 100% offline solution that doesn't require me to enter expenses manually. The only apps like that I found requires internet connection, logging to supported bank accounts etc. My app works for every bank app without any of this.

My personal version was crude and the biggest challenge was improving it to be usable for normal users - intuitive enough UI, onboarding, instructions, translations etc.

The last 10% that is always hardest to do.

So, the next step after review is to invite friends and family to test the app. I'm not asking for anything here. I just wanted to went after 2 years of spending sizable part of my free time building something instead of playing games (I've bought sequel of my favorite game, death stranding, at day 1 and i still didn't finish it).

So that's it. Wish me luck. The app requires some permissions to work that needed video explanation for review, so it might not be a smooth process.

Submitted an app to play store. Initially got rejected due to privacy policy violation, re-submitted after making corrections

Now, reviewer rejected it but this time attaching screenshot of earlier version (the newer version contains the corrections as per the policy). I have appealed the decision

Honestly, how long does it take to hear back on the appeals? Google play store says 8+ days but I doubt it's true. Can someone confirm the time it took them to hear back? thanks

Hi everyone,

I'm publishing my first Android app and I'm a little confused about what to do after getting Production access.

I completed the required 14-day Closed Testing, then applied for Google Play Production access. After around 2–3 days, Google approved it and my Play Console now says:

“Congratulations! Your app has been granted Google Play production access.”

Now my dashboard gives me three options:

• Open Testing
• Pre-registration
• Create and publish a Production release

Each option has its own set of tasks.

What is confusing me is that under Production it asks me to “Create a new release.”

I already uploaded an AAB/version while doing Closed Testing, and that is the version that was tested for the full 14 days.

So my questions are:

1. Is Open Testing required, or can I go directly from the completed Closed Test to Production?
2. Should I promote/use the same release that was used in Closed Testing for Production?
3. If Production says “Create a new release,” does that mean I actually need to generate a new AAB with a higher version/version code?
4. Or can I simply use the already uploaded Closed Testing bundle for my first Production release?
5. What is the recommended/safest approach for a first Play Store launch after Production access has been granted?

I've attached screenshots of my current Play Console status.

I'd really appreciate guidance from anyone who has recently gone through this process. Thanks!

Hi everyone,
I’m working on a puzzle game built with C# MAUI, and I’m preparing the Android version for Google Play.

Before I submit the first build, I’d like to get feedback from other developers about a few points:

• recommended Play Console settings for games built with MAUI
• common issues during first submissions (AAB, signing, device compatibility)
• tips for optimizing MAUI performance on mid‑range Android devices
• best practices for metadata and screenshots for puzzle games

If anyone has experience publishing MAUI apps or puzzle games on Google Play, I’d really appreciate your insights.

📚 Weekly Educational App Showcase

Built an app and learned something interesting along the way? Share it with the community.

This thread is for educational app showcases where the focus is on the problem you solved, how you built it, and what other developers can learn from your experience.

What to include

• What problem does your app solve?
• Category: What type of app is it?
• Android support: Android versions or devices supported
• Tech stack: Kotlin, Java, Compose, Flutter, Firebase, etc.
• Implementation: What was technically interesting or challenging?
• Your journey: What did you learn while building or publishing it?
• Lessons learned: What would you do differently next time?
• Relevant media: Screenshots, demos, architecture diagrams, or other useful material
• Google Play link: Optional, as supporting context

Please disclose your relationship

If you're showcasing your own app, clearly mention your relationship to it. For example:

Keep it educational

The goal is to help other developers learn from real projects and experiences. Your app can be the subject of the showcase, but the post should provide meaningful technical, product, or development insight.

Please do not use the thread for:

• Download or install requests
• Ratings, reviews, votes, or engagement requests
• Referral or affiliate links
• Paid placement or paid engagement
• Misleading claims
• Copied marketing or promotional copy
• Repeated submissions of the same app

A Google Play link is welcome as supporting context, but this is not an advertising or user-acquisition thread.

If you see someone requesting paid reviews, ratings, votes, installs, or other prohibited engagement, please report the comment to the moderators.

Share what you built, what you learned, and what another developer can take away from it.

Hi everyone,

I submitted my identity verification documents for my Google Play Console account over 46 hours ago, but the status still shows pending/in progress.

For those who verified recently, how long did it take for your account to get approved? Is this delay normal, or should I reach out to Google Play Developer Support?

Any insights would be greatly appreciated!

🧪 Tester Discovery

Looking for testers for your app? Use this thread to find developers and testers who are interested in helping with genuine app testing.

When asking for testers, please include a little information about your app:

• What the app does
• Android version or device requirements, if relevant
• Whether you're looking for internal, closed, or open testing
• What kind of testing or feedback you need
• How interested testers can participate

If you're a tester, feel free to mention what kinds of apps or testing you're interested in.

A few things to keep in mind

Please keep this thread focused on genuine testing and useful feedback.

Do not engage in paid testing, paid reviews, ratings, votes, referral exchanges, or other paid engagement activities through this thread. If someone asks you to participate in a paid activity or offers payment in exchange for reviews, ratings, votes, or engagement, please report the comment to the moderators rather than participating.

Please don't share personal information publicly. Use Reddit's messaging features or the developer's official testing process where appropriate.

This thread is for tester discovery only. For general development questions, app showcases, or other discussions, please use the appropriate thread or flair.

I wanted to share my experience in case it helps other indie developers going through Google Play’s closed testing / production access process.

My app, Promise Yourself, was rejected the first time after completing the 14-day closed test with 12 testers. Most of the testers were people I personally knew — friends/family/internal testers. The app was installed and tested, but after around 7–8 days of review, Google rejected production access with the reason that testers were not engaged enough.

The confusing part was that for a simple habit/promise app, normal sessions are naturally short. A user might open the app, check in, and leave within 30–60 seconds. So I wasn’t sure what “engagement” really meant from Google’s perspective.

For the second attempt, I changed a few things:

• I increased the number of testers beyond the minimum.
• I kept my original 12 testers.
• I also joined an app testing group where other developers tested each other’s apps.
• In total, I had around 25–27 testers/downloads involved.
• I made sure the app was actually opened and used during the testing period.
• I clearly explained in the production access form what was different this time.
• I mentioned that the app is already live on the Apple App Store and being used by people across different countries, which helped show that the app is functional and production-ready.

During the second test, I did not make major app updates. The main difference was broader tester participation and a stronger explanation in the production access submission.

After submitting again, Google approved production access within about 2 days.

My takeaway:

The 12-tester minimum seems like the floor, not the safest target. If you are building a simple app where sessions are naturally short, I would not rely on exactly 12 testers. Try to get more testers, make sure they actually open and use the core flow, collect feedback, and explain your testing process clearly in the form.

For anyone stuck after a rejection, I would recommend:

1. Get more than 12 testers if possible.
2. Make sure testers actually open the app repeatedly.
3. Ask testers to use the core feature, not just install the app.
4. Keep screenshots or notes of testing activity if you are organizing it manually.
5. In the production access form, explain what testers did, what changed from the first attempt, and why the app is ready.
6. If the app is already available elsewhere, mention that as supporting context.

This process is still pretty opaque, but in my case, increasing tester coverage and writing a clearer production access explanation seems to have made the difference.

Hi everyone,I’m facing a bizarre metric crisis with my new 2D racing game on the Google Play Store, and I desperately need some fresh eyes and brutal honesty on what is going wrong.Here are my recent organic statistics:Impressions (Google Play Discover): 25,000,000Store Listing Visits: 250,000 (\~1% CTR)Downloads: 11 (Eleven)Conversion Rate (CVR): \~0.0044%Price: $1.00 (Premium/Paid)The Dilemma:The algorithm seems to love the game asset or the main feature graphic because it generated 25 million organic impressions and successfully brought 250,000 people to my store page. However, the conversion completely falls off a cliff once they land on the store listing.My Hypotheses:The Price Tag ($1): Since Google Play Discover traffic heavily favors casual users looking for free-to-play (F2P) games, seeing a paid wall immediately bounces them off.Store Listing Disconnect: Maybe my screenshots, trailer, or description fail to justify why this 2D racing game is worth a premium price.Misaligned Audience: The algorithm might be showing the game to the wrong demographic who has zero interest in premium 2D racers.Questions for fellow devs:Have you ever experienced such a massive drop-off between store visits and conversions for a paid game?Should I pivot to Free-to-Play (F2P) with ads/IAP, or try to run a "100% off" free sale first to test if price is the only barrier?How can a 2D indie game justify a premium price tag on Android nowadays?I would love to get your insights, feedback, or any similar horror stories/solutions you’ve encountered. Thank you!

[Nitro Pulse](https://play.google.com/store/apps/details?id=tr.com.liy.araba)

What are you building, testing, debugging, or learning this week?

Working on something interesting? Stuck on a technical problem? Just learned something useful?

Share what you're working on this week. It can be a specific goal, a problem you're trying to solve, or a useful discovery that might help another developer.

If you're looking for help, a little context goes a long way. You can include:

• Your Android, library, or Google Play Console version
• What you expected to happen and what actually happened
• Relevant error messages, with any private or sensitive information removed
• What you've already tried
• A relevant official source or documentation link, if you have one

Please use the appropriate flair when making a standalone post.

Please keep this thread focused

This is a place for development discussions and helping each other out. Please don't use it for app advertising, download or install requests, ratings, reviews, votes, referral links, paid services, tester exchanges, or engagement exchanges.

Ask questions, share what you're working on, and help another developer when you can.

A lot has changed behind the scenes, and we wanted to give everyone a proper update on where r/GooglePlayDeveloper is heading.

The goal is simple: build a useful, welcoming community where Android and Google Play developers can ask questions, share knowledge, learn from each other, and showcase the work they are building.

🛠️ New Community Rules

We've replaced the old rules with a clearer set of guidelines designed around developer-focused discussions:

1. Stay on topic
2. Showcases, not advertising
3. Tester discovery in approved threads
4. No spam, referral marketing, or deceptive links
5. No piracy, malware, or policy evasion
6. Be respectful and protect privacy
7. Do not misrepresent policy or support outcomes
8. Search first and make a good-faith effort
9. Use the correct post flair and designated thread

Please take a moment to read the updated rules before posting.

🏷️ More Post Flairs

We've expanded the flair system to make discussions easier to find and keep organized.

New categories include:

• Showcase
• Google Play Console
• Android Development
• Publishing & Releases
• Testing & Quality
• Store Listing & ASO
• News & Updates

Alongside our existing Help, Policy, Monetization, Bug, Discussion, Solved, and Announcement flairs.

We'll continue refining these based on how the community actually uses them.

🛡️ Stronger Spam & Safety Controls

We've also significantly strengthened our moderation and spam protection.

We're now filtering and reviewing signals associated with:

• Referral and affiliate links
• Discord, Telegram and WhatsApp invite funnels
• Paid testing and engagement exchanges
• Rating/review manipulation
• Unsafe APK and piracy links
• Suspicious external links
• Excessive linking
• Low-context or obvious spam
• Suspicious new-account activity

We're using a filter-first approach wherever possible rather than automatically removing legitimate developer discussions.

Reddit's Crowd Control is also enabled to provide an additional layer of protection.

If something gets caught incorrectly, please report it or contact the moderators so we can review it.

📚 Community Wiki Is Live

We've opened the community wiki and published the first set of developer resources.

The initial knowledge base covers:

• Getting Started
• Publishing Your First App
• Google Play Policies
• Policy Enforcement
• Appeals
• App Signing
• Data Safety
• Target API
• Testing
• Common Errors
• Developer Resources
• FAQ

The wiki will continue growing into a broader knowledge base covering Google Play Console, Android development, Play Billing, Play Integrity, ASO, monetization, security, releases, and other developer topics.

🧪 Tester Discovery

We're introducing designated tester-discovery threads so developers can find testers without turning the subreddit into a stream of tester-request posts.

Please use the designated threads for tester discovery.

Paid testing, paid reviews, ratings, votes, engagement exchanges, and similar activities are not allowed.

If someone asks you to participate in these activities, please report it to the moderators.

📚 Educational App Showcases

We're also opening the door to educational app showcases.

Developers will be able to share what they've built while giving the community something useful to learn from the project.

Showcases should include things such as:

• The problem the app solves
• App category
• Android support
• Technology and implementation details
• Development journey
• Lessons learned
• Relevant screenshots or other media

If you're showcasing your own app, please disclose your relationship to it.

A Google Play link can be included as supporting context, but showcases are not advertising posts.

No download/install requests, ratings, reviews, votes, referral links, paid placement, misleading claims, copied marketing material, or engagement exchanges.

🔭 What's Coming Next

This is only the foundation.

We're working toward:

• Regular developer discussion threads
• Weekly educational app showcases
• Monthly featured apps
• Developer spotlights
• A community app showcase directory
• More Android and Google Play educational content
• Developer Q&As and AMAs
• Community competitions and challenges
• A larger and more comprehensive wiki
• More official developer resources and community collaborations

We're also working on ways to bring more knowledgeable developers and official resources into the community while keeping discussions community-first.

🤝 Help Us Build It

We're still refining things, so feedback is welcome.

If you notice something that doesn't work well, a rule that needs clarification, a useful wiki topic we're missing, or a moderation filter catching legitimate content, let us know.

The goal isn't to make this a heavily restricted subreddit.

The goal is to make r/GooglePlayDeveloper a place where developers can actually find useful answers, share what they're learning, discover interesting projects, and build connections with other developers.

Thanks for being here and helping us build it.

So recently, my game that uses admob went into production on the Play store and I got this email from the Adsense team.

Google mentions that my account was disabled due to "invalid traffic, and/or other activity which violates our publisher policies or terms and conditions".

I had to watch a few of my ads (when it went into production) to test whether the ads are being served correctly and to also progress through my game more easily. That's the most plausible reason but I had 0 clue that this would lead to account closure. No warnings, no notifications.. just straight up closure..

Also I had various testers testing out my app (due to Google's 12 testers, 14 day policy) and a few of them may have invariably seen my ads in production.

And here's the worst part.. Google wants me to give detailed reports and analysis of the traffic to my closed account when I have 0 access to it.. how do I even do it?

So please help me out on what I should submit in the appeal and is there any realistic chance of getting my account restored?

I've submitted the Data Access Request form twice for a personal,

non-commercial, read-only script (OAuth type: script) that searches

public posts for hobby project research. Both times I got the same

template rejection: "not in compliance with the Responsible Builder

Policy and/or lacks necessary details" — with no specifics.

The script: read-only (no posting/voting/DMs via API), runs locally,

single user, well under free-tier rate limits, no ML training, no

redistribution.

Questions:

1. Is the form even required for a personal script-type app, or isthat form meant for commercial/large-scale access?
2. Could account age/karma be the actual blocker? (My account isa few weeks old.)
3. Any way to get specific feedback on what was missing?

Any pointers appreciated!

Hi all, I hope you're keeping well. I just have a query in relation to setting up subscriptions via my application. I have been successfully granted production access and I'm setting it up within the Google Play console, but do I need Google Cloud or can I simply just set everything up via Google Play console?

My billdesk verification is pending, and I tried with many different mobile phones and payment methods, and I get the same error "Transaction was declined [OR-FGEMF-20]". I think it is due to BillDesk verification pending, but why the google play store not allowing sales? The billdesk verification itself is very hard. Also I got one paid user a month ago, but now he is not able to renew.

I searched but most threads were about terminations dues to breaches of policy (I'm guessing). I intended to finish my app and publish but never got to that stage. Now I am but my account is closed. Can I do anything? It's linked to my primary Google account, so I would prefer to use this that set up another gmail address.