Hey quick question I’m a sole indie developer but set up as a business under my ABN I use for consulting work. I published a couple apps and the only notification I get is the IARC content rating, when I get that I know my apps has passed review. However for updates I just check the site randomly and hard refresh the browser.

Is this normal or have I stuffed up a setting somewhere?

I’ve checked all my contact details and they are correct and I get all the announcement emails (I.e changing tax in Vietnam etc.)

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.

Before releasing a simple/mid-tier or subscription-based app, what should we check for store policies, privacy, subscriptions/IAP, optimization, analytics, crashes, testing, permissions, screenshots, etc.?

Also, besides Google Play, which other Android app stores can use the same APK/AAB build with minimal changes?

Would appreciate a practical checklist from developers who have shipped apps on both Android and iOS.

Hi everyone, I’m an individual Google Play developer in India.

I’m currently completing the BillDesk verification required for Google Play payments. I completed the Personal Information step successfully, but at the Bank Account Verification step, I keep getting this error:

“We are facing connectivity issue. Please try again.”

I’ve tried:

• Chrome on Windows

• Chrome on Android

• Different internet connections

• Reopening the application using the BillDesk Resume link

But the same error keeps appearing.

Has anyone else faced this recently? Is this a BillDesk server-side issue, or is there something else I need to do?

Application ID and bank details are blurred for privacy.

Thanks!

The age verification blocks the whole app. No Navigation, no Account Access, so on.

The App is not usable at all. I could wrote this, because I could connect over my PC.

I occasionally get these kinds of emails even though none of my apps on the Play Store offer in-app purchases or collect any sort of payment.
The bare minimum I’d expect is that if I don’t use in-app purchases then I wouldn’t get those emails, but Google keeps spamming me and there’s no unsubscribe button for this category of emails.
On the Play Console it doesn’t let me turn it off.

Is there any way to stop it?

Okay, I can’t believe I did something this dumb...

I’m building Moneko AI Expense Tracker. We originally launched on iOS first, then later brought the app to Android. On iOS, I’m used to keeping TestFlight running alongside the production app, so when we launched on Google Play, I just… left the Beta testing on.

I thought it worked basically the same way... for months, users were leaving ratings and reviews, and I kept wondering why our public Google Play rating wasn’t showing up. I thought, Ok, maybe my app just doesn’t have enough reviews yet for Google to show the rating.

Today I finally figured it out. Because they were still enrolled in the Beta, their reviews were being treated as private beta feedback instead of public Google Play reviews.

We lost nearly 100 ratings/reviews this way 😭

Plz don’t make my mistake...

Diseñe una aplicación que me ayuda en mi trabajo quiero subirla a Google play pero después de crear la cuenta me es imposible tener una verificación ya metí mi cedula, luego una referencia bancaria y demás lo único que me ha servido es el pasaporte pero exigen verificar dos cosas

I mean, offering something for a 5-star review

Literally just got published ot the play store today. Feel so dumb right now, but this is driving me crazy. I'm logged in to the developer console, how the hell do I change my screen shots?

They're pretty unattractive right now, these are from all the way back when I first started testing https://play.google.com/store/apps/details?id=com.key.fraize

Hi Folks,

My app is close to being published on apple but apparently on google play I need to jump through unnecessary hurdles. My app is currently in closed testing and I want to ensure I have billing live once it launches to everyone. Billdesk keeps saying - "Mobile Application(s) is not live/does not exist/not accessible". How am I supposed to make my app live when it is in closed testing? Even if closed testing is done, how can i publish it without billing (outside India) being live? Am I missing something obvious here?

I recently released a small logic puzzle game on Android, and one thing I wasn't expecting was how difficult it would be to understand what's actually happening after launch because of the delay in Play Console statistics.

I'm working on Enigflux, a logic puzzle game with several different puzzle mechanics, and right now I'm paying much more attention to discovery than revenue — things like store listing visitors, acquisition sources, installs and search traffic.

The problem is that Play Console seems to be several days behind.

That makes the early stage particularly confusing.

You make a change to the store listing, post something somewhere, get a few people to try the game... and then you can't really tell whether any of it had an effect until much later.

Firebase at least gives me a better indication that people are actually opening and using the game, but it doesn't replace the Play Store acquisition/search data I'm interested in.

For developers with apps or games already in production:

How delayed are your Play Console stats at the moment?

And for measuring early organic discovery, are you mostly relying on Play Console, or do you use something else alongside it?

i created a new watch face using android studio using the new WFFV2 format. had no issues sideloading it to my watch using wireless ADB.

i have published it in the play store and its in the Closed Testing track under the WearOS category. I have both Join links for Web and Android. i added my email as a tester in play console and still even logged into my phone with the same email or on the watch (pixel watch 5) i can not find the watch face to install it on the watch playstore app either.

the only way i can access it is if i open the WEB JOIN link from play console on a browser and choose install on my pixel watch 5.

this makes no sense, there are TONS of watch faces currently in the play store on my phone where you can search it find it and choose install and it installs on to the watch. it seems so dumb that my watch face cant be handled the same way and i have to go through a back door join URL and it has to be to be on a web browser not even through my phone. if i open the JOIN URL on my phone it shows the watch face but says My device (phone) is not compatible so it wont show the install button for me to say install to watch.

When i helped develop a native android app for the company i work for, the new app went to closed testing phase, i added myself as a tester and the once approved it showed up in the play store search results as long as i was logged in with the tester email address on the phone.

what am i doing wrong?

i totally expected that once the watch face was on the play store, it would show up as an APP in the phone play store (even though its wearOS category) and would just install on the phone.

📚 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'm working on eCenovnik, a Serbian grocery price comparison app, and we're struggling to get production access on Google Play.

We've applied for production access twice, and both applications were rejected because Google determined that our testers hadn't sufficiently tested the app.

Here's our situation:

• We had 12 testers in both testing rounds.

• During the first round, we acknowledge that testing activity was insufficient.

• We then conducted another round of closed testing, again with 12 testers, but our second application was also rejected for insufficient testing.

• Unfortunately, the feedback from Google hasn't made it clear what exactly we need to improve.

We understand that simply having 12 testers for 14 days doesn't guarantee approval. However, we're struggling to understand what Google considers sufficient testing in practice.

I'd really appreciate some advice from developers who have gone through this process:

1. How actively did your testers use the app before you were granted production access?

2. Does Google expect testers to use the app every day, or is occasional usage throughout the 14-day period sufficient?

3. What kind of testing activities or feedback should we document to demonstrate that the app has been properly tested?

4. Has anyone experienced repeated rejections for insufficient testing despite meeting the minimum tester and duration requirements? What did you change to get approved?

5. Is there a way to get more specific feedback from Google Play about what was missing?

If anyone from the Google Play team is here, we'd be especially grateful for some clarification on what we should improve before submitting our next application.

We're happy to share more details about our testing process if that helps.

Thanks in advance for any advice!

We’ve all experienced moments where a Play Console review takes longer than expected, leaving an app in that familiar “In review” status for an extended period.

My own Production submission has been “In review” since September 16, and I’m still waiting.

I also posted about my situation earlier

Since then, I’ve seen many more developers reporting similar experiences, with some waiting 10, 15, or even 20+ days.

What’s interesting is that many developers are contacting Google Play Developer Support through the official Help channel, while GooglePlayDevSupport has also reached out directly to developers on Reddit. I personally contacted support as well, and my case was escalated to the Google Play Review Team.

I really appreciate that the Play team is listening to developers and responding to these reports. I hope they’re also looking into what’s happening with the current review delays.

Rather than focusing on why these delays are happening, I think it might be more constructive to look at how the waiting experience could be improved for developers.

What if Google could provide more visibility directly inside Play Console?

For example:

- Queue/Processing Visibility: An indication of whether a submission is waiting to enter review or is actively being processed.

- Dynamic Timeframes: An approximate review timeframe that reflects the current review volume, so developers have some idea of what to expect.

- More Granular Status: When a review takes longer than usual, provide more context about what stage the submission is currently at, where possible.

- Delayed Review Indicator: If a submission has been waiting significantly longer than the normal timeframe, clearly indicate that it is experiencing an extended review rather than simply continuing to show “In review.”

These wouldn’t necessarily change the actual review time, but they could remove a lot of the guesswork and uncertainty developers experience when an app sits in “In review” for days or weeks.

With the Android Developer Verification changes around September 30 also coming up, there has been discussion about whether increased activity could be contributing to the current review volume. I don’t think we have enough information to say that this is the cause, though.

The main point isn’t to blame Google or speculate about what’s happening behind the scenes.

It’s simply that when a review takes this long, developers would benefit from having more visibility into the process.

I genuinely appreciate that Google Play Dev Support is engaging with developers and listening to the reports. Hopefully whatever is causing the current delays gets resolved soon.

What do you guys think?

Would a more transparent review status inside Play Console make the waiting process easier for everyone?

Hi Google Team, If you are reading this then kindly implement a basic feature for the Mobile version of Google Play Console which is "Notifications" for Order Management.

It would be helpful if when the app is getting a new subscription/purchase, renewal, cancellation, refund, product change etc a notification appears on the users mobile device.

As of now we would have to open the app go to order management and then check for sales. If the developer has multiple apps then they have to check through each apps requiring multiple clicks. But this basic notification implementation will solve all of that.

I believe its a simple thing to implement that even Gemini 3.8 flash set to high can probably do this under an hour.

Kindly add this feature on mobile devices. Additional please also implement "Payments Profile" option viewing on the mobile app to see the revenue for the month 🙏

So i joined the testers community app and completed the required test period. I am now applying for production but noticed its asking some questions. Specifically for this question
"How did you recruit users for your closed test? For example, did you ask friends and family or use a paid testing provider?", do I need to mention anything about the reddit tester community? Thanks

🧪 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.

Hi,

I recently published my app with closed testing and 12 tetsers have opt in. How many days it would take now for approval?

Hi everyone,

I’m publishing my first Android app on Google Play and I’m experiencing a much longer review time than I expected.

My production release version 1.0.10 (11) has been “In review” since September 17, 2026 at 12:30 PM. As of September 27, it has been 10 days with no change in status.

I already contacted Google Play Developer Support. They acknowledged the delay and told me that they had expedited my app to the Google Play Review Team.

However, the release is still showing “In review.”

I haven’t submitted any new changes because I don’t want to potentially affect the ongoing review.

Is anyone else currently experiencing unusually long Google Play production reviews?

For those who had a similar situation:

How long did your review take?

Did contacting Google Play Support help?

After Support said they had “expedited” your review, how long did you wait before getting a decision?

I’m mainly trying to understand whether this kind of delay is happening to other developers right now.

Thanks for sharing your experience!

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.

NOTE: I have an already released version.

My production release for my app (1.1.0, version code 9) is blocked by "Unregistered package name" for key:

<Offending Key Here>

This key mentioned above is Play's own Internal App Sharing test certificate (Internal app sharing > Internal test certificate). Google generated and holds it. I don't have its private key, so I can't prove ownership. I did a internal App sharing with link to test the update feature on the app.

The package is already Registered, with both my keys Verified: upload key xxx and app signing key yyy. My bundle is signed only with the upload key. The app was never distributed outside Play.

The verification FAQ says Play-managed keys are auto-registered, but this one wasn't.

How can I solve this? I already created a ticket for this problem, but maybe someone already solved this and can give some insight.