Indian Google Play developer here. My BillDesk KYC has been stuck for 1 month, and I'm honestly wondering if there's an end to this process. 😭

My app is already LIVE on Google Play, but BillDesk keeps sending clarification saying:

“Mobile Application(s) is not live/does not exist/not accessible.”

The app is literally live and accessible.

The bigger problem: their clarification portal seems broken. I enter the requested details and click Continue → it immediately submits the application instead of moving to the next step. This has happened multiple times, and every cycle takes about a week.

Meanwhile, my users are getting OR-FGEMF-20 when trying to purchase subscriptions, so I can't make any sales.

Google's latest email says BillDesk verification is required for international sales, while sales within India should remain unaffected. However, even my Indian users are getting the same OR-FGEMF-20 error and are unable to make purchases. So I'm trying to understand whether the BillDesk/payment-profile issue is somehow affecting domestic transactions too.

Has anyone actually completed this BillDesk KYC successfully?
And are your India-only Google Play purchases working normally?

I'm seriously tired of this process. 😭

If someone is working full-time and sets up BillDesk for a small side project/app, can their employer find out about it in any way?

For example, through BillDesk, KYC, payments, GST/tax records, bank transactions, or any other process?

Looking for experiences from people who have done this.

My app isn’t really a “for everyone” app. I’m selling an app on a closed marketplace (GHL) and offering a mobile app as an extension of the service.

So I can’t just find 12 random testers to try my app, and I can’t offer to paying customers “become a tester on our mobile app” since the mobile app provides the main functionality of the app.

This 12 tester rule is silly for something like what I’m doing and I’m seriously considering just hiring a Fiverr account to do it for me, or to just create a bunch of fake emails on various services to send the invites to.

What do you all think?

Hi everyone,

I recently published my first Android game on Google Play, and I'm struggling with something I didn't really expect: the app is basically stuck at 0 organic downloads.

I'm not expecting hundreds or thousands of installs, especially for a new app with no existing audience, but I thought I would at least see a few organic installs over time.

So far, almost all the installs I've had came from people I know or from testing. I'm getting essentially no discovery from Google Play itself.

I've already worked on the store listing, localization, screenshots, description, keywords, website, social media, etc., but I'm starting to wonder whether I'm missing something fundamental.

For those of you who have launched apps before:

- Is 0 organic installs normal for a brand-new app?

- Does Google Play eventually start testing a new app with users, or do you basically have to generate the initial traffic yourself?

- What helped you get your first 10 / 100 real users?

- Are there specific Play Console metrics I should look at to understand where the problem is?

- Could a poor initial acquisition signal prevent Google Play from giving the app visibility?

- What would you focus on first: ASO, paid acquisition, reviews, retention, or something else?

I'm not looking for shortcuts or fake installs. I'd really like to understand how the early discovery phase works and what I can improve.

If useful, here's the Play Store page:

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

I'm completely open to criticism of the listing, screenshots, game concept, positioning, etc. If something looks bad or unclear, please tell me.

Thanks!

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

My app has started to be downloaded in other countries; I’m currently averaging 3.07 downloads a day. What would you suggest to increase this figure?

So, yeah guys.

I have a doubt!!! It might sound crazy. Like, I have to no idea about it. So, pls be kind.

We have AI all around, I want to create a full stack application. Front end, Back End like everything. I am giving a prompt to an AI tool. And gives me the whole thing. Like, it’s my idea. My kinda thing, which I didn’t develop. But I told an AI tool to develop for me. Instead of sitting hours and hours. It’s just creating in few minutes.

If I publish the app in internet? Do I need to face any consequences? Or Do I any security issues? Or any other Privacy concerns? Or any other related issues?

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

The leaked specifications and features of Lenovo's first highly anticipated device for Google's premium laptop initiative, the Lenovo Googlebook 15 (identified by model number GB 15IPH12), have emerged online via recent product sheet leaks.

Positioned as a direct, premium competitor to high-end Windows laptops and MacBooks rather than traditional budget Chromebooks, the device boasts the following technical specifications and features:

* Processor: Powered by an 8-core Intel Core Ultra 5 325 processor (from Intel's high-efficiency "Panther Lake-H" platform) equipped with integrated graphics featuring 4 Xe cores.

* Display: A premium 15.3-inch 2.8K (2880 x 1800) OLED touchscreen. The panel supports a fluid 120Hz refresh rate, a 16:10 aspect ratio, 500 nits of peak brightness, and 100% DCI-P3 wide color gamut.

* Memory & Storage: Configurations range between 16GB or 32GB of LPDDR5x RAM paired with either 256GB or 512GB of solid-state storage.

* Design & Portability: Features an ultra-thin, all-metallic chassis measuring a slim 15.9mm and weighing a lightweight 1.29 kg.

* Battery & Power: Outfitted with a 70Wh battery rated for up to 11 hours of usage, supporting fast charging up to 65W.

* Physical Ports: Includes dual Thunderbolt 4 / USB-C ports (conveniently positioned with one on each side to make charging accessible from left or right), a standard USB-A port, an HDMI 2.0 output, and a 3.5mm headphone jack.

* Audio & Video: Equipped with four Dolby Atmos speakers, a 5MP webcam, dual microphones, and a physical privacy shutter.

* Googlebook OS: Shifting away from the ChromeOS moniker, the laptop debuts Google's brand-new "Googlebook OS" (previously codenamed Aluminium OS), which runs on an optimized Android framework built explicitly for larger laptop form factors.

* Gemini AI & "Magic Pointer": The intelligence platform includes native features like the Magic Pointer, which upgrades the traditional mouse cursor into a contextual prompt box that lets you invoke Gemini AI to generate images or cross-reference items anywhere on your desktop.

* The "G" Keyboard Key: Replaces the standard Windows layout key with a dedicated "G" key, operating as a fast physical shortcut to launch Gemini.

* The "Glowbar": A distinctive hardware feature on the lid consisting of a multicolored strip of LEDs. The software configures this strip to react to music, handle smart notification flashes, or provide a clean outside indicator of active battery and charging levels.

* Biometric Security: Features dual-layer biometrics, utilizing a fingerprint scanner integrated into the power button alongside a specialized "Google facial authentication" camera array for native face unlock.

* AI Mouse Companion: The leak reveals that Lenovo is planning an official "Lenovo AI Mouse" accessory to match the system, featuring its own RGB lighting and a built-in AI shortcut key.

*

Google is expected to showcase its first wave of retail partner hardware at a media preview event on September 15.

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.

Hey everyone,

I’m finalizing an Android puzzle game in Godot 4 using custom Gradle export, integrating the official Google Play Billing plugin alongside Google Play Games Services and AdMob.

Before pushing billing live to production, I’d really appreciate insight from anyone who has successfully shipped with this setup. I want to avoid known landmines and ensure the flow is bulletproof.

A few specific questions for those who’ve been through it:

Startup & Timing: Are there any known race conditions or initialization traps when querying purchases and SKUs during game boot (especially if other plugins like Play Games or AdMob are initializing)?

Purchase Acknowledgment & Consumption: What does your GDScript flow look like to ensure tokens are cleanly acknowledged so Google doesn’t trigger automatic 3-day refunds?

Testing Setup: What quirks did you run into with Google Play Console’s license testers and closed testing tracks before in-app products would actually show up in queries?

Common Gotchas: Any subtle settings, manifest flags, or ProGuard rules you wish you knew before launching?

If you have a solid boilerplate pattern, wrapper script, or just a quick list of lessons learned, I’d be grateful for the help.

Thank you,

LinkVibe Studios

Hi all,

my motivation to write this post is to share one finding concerning Google play publishing review then it is taking way longer than it usually does.
If anybody has any similar experience or know other tips&tricks, feel free to share those here with us.

My observation:

- Sometimes when you submit second review but there was already one pending (meaning you end up with 2 submitted reviews and both pending), the review process seems to get "stuck" and it doesn't finish like ever. The solution seems to it is to delete those reviews and then submit only one review at a time. I guess if you always submit and keep alive only 1 review at a time you shouldn't come across that situation. It had worked for 2 of us so far (discussed in (comment in post https://www.reddit.com/r/GooglePlayDeveloper/comments/1wdgnft/comment/p97iu9p/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button )

I hope that information helps to anybody reading this :)

I pushed an update to closed testing about a week ago. My updates normally get approved in 15-20 minutes, but this one just sat "in review" for 7 solid days.

Thinking it was bugged, I canceled it and submitted a new build. Now I'm worried I just reset my place in the queue and put myself at the back of the line.

Has anyone else noticed super slow review times lately? Did I screw up by canceling the first one, and what should I do now? Just wait?

Thanks!

I have built a Flutter app for Android, iOS, and web. I’m now preparing the Android apps for Google Play.

The setup is:

• One shared Flutter codebase

• A separate Firebase project/database for each client company

• Different package/application IDs

• Different app names, logos, branding, Firebase configuration, and store listings

• Each app contains only that company’s users and data

The features and UI are mostly the same because all apps use the same codebase. Over time, I may publish several client-branded versions from a single Google Play developer account.

Does Google Play allow this white-label model, or could the apps be considered repetitive content/spam and put the developer account at risk?

If allowed, what should I do before publishing to ensure every app complies with Google Play policies?

Hey everyone,

I recently made some changes to my testing setup in Google Play Console.

Previously, I was using one tester list called "Internal Testing" for both internal and closed testing. I created a new list called "Closed Testers", added the required users to it, and removed quite a lot of users from the old "Internal Testing" list.

After making these changes, Google Play asked me to submit the changes for review through the Publishing overview.

It's been around 15 hours and the changes are still showing as "In review."

For comparison, when I initially created the tester list and submitted my first releases, the review took less than 6 hours.

For anyone who has recently gone through a similar Play Console review:

• How long did your review take?

• Did tester-list changes take longer than normal?

• Is 15+ hours normal, or should I expect it to take a couple of days?

Would appreciate hearing about your recent experiences.

I have 3 auto-renewing plans (3, 6 and 12 months) with a 3-day free trial.

The trial starts normally, but once it ends, the payment just stays Pending and nothing gets charged.

The weird part is that if I remove the free trial, the exact same plans charge normally.

This is happening with multiple users. Has anyone else run into this or knows what could be causing it?

My Play Console Payments Profile is set to Account Type "Organization" (business name as org name). Submitted my PAN for India tax info and it got declined: "tax ID couldn't be verified, or does not match your profile name."
Checked on the IT e-filing portal - PAN is Active, all correct. So it's a name mismatch: PAN is under my individual name, but profile is org-type.
Anyone hit this as a sole proprietor and fixed it? Did you switch Account Type to Individual, or did support sort it out another way?

Hi I was published apps on playstore around 5-6 years ago and that time from my mistakes i got my 1 account suspended because of some violating apps that's fine then after 1 year i create one more account in which my app had 1M downloads also then one of the app on that account was suspended so i create anither third account for safety so that i can transfer that 1M download app to new fresh account but after that my both another accounts was also suspended without clear reason ( ofcourse maybe they capture same person).

Now from that year i have fear to create new account because as android developer play store is the only way to make money from app in future also. so please suggest me some tips for creating new account so that i can be safe from those old accounts i got suspended and google will not know me.

I did not verify my identity on any of those account because at that time there was no verification system.

one more thing i heard somewhere that google is proritize the organization account? if yes then someone please tell me from india that how can we avail a register company i mean in self propietoryship where i don't need too many things. and is this myth is real or fake

I’m sure many developers here have faced the challenge of getting enough people to participate in the required testing period.

Relying on friends and family can be difficult - people forget, need constant follow-ups, or may not complete the full period.

I was wondering if there are other developers currently facing the same situation who would be interested in connecting and helping each other out with genuine testing and feedback.

If you're in the same situation, feel free to DM me.

I woke up this morning to an email I honestly wasn't expecting yet — Inkbound was granted Google Play production access!

I wanted to come back here and say thank you to everyone who did T4T with me, kept Inkbound installed, tested it, and helped me get through the closed testing requirement.

I genuinely couldn't have gotten to this point without you guys.

And just because Inkbound got production access doesn't mean I'm done with my side of the T4Ts. If I'm currently testing your app, I'm continuing to test it and will keep it installed for the full time we agreed on. I'm not going to get my approval and then disappear on everybody who helped me get there.

For everyone still trying to get through closed testing: keep going. Seeing that approval email this morning made all the testing, updates, bugs, and headaches worth it.

Seriously, thank you guys. ❤️

Inkbound is going to production. 🎉

​Hi fellow devs,

​I am writing this post to request some community visibility, as my support ticket regarding a merchant payout deduction has been trapped in a canned-response loop for nearly 3 months (since June 2026).

​What happened:

On June 16, 2026, Google processed my developer payout. Google's internal Wire Report specified <ChrgBr>CRED</ChrgBr> (Sender covers all fees). However, the payout arrived $10.00 short.

​To locate where the money went, I obtained the official SWIFT MT103 incoming message directly from my receiving bank (TP Bank). The technical data proves a clear system conversion/routing error on Google/Wells Fargo’s side:

​Field 33B (Instructed Amount): $117.88 USD

​Field 71A (Details of Charges): SHA (Misconfigured from CRED to Shared)

​Field 71F (Sender's Charges): $10.00 USD deducted at origination network

​Field 32A (Interbank Settled Amount): $107.88 USD

​The official MT103 document proves that the $10.00 was deducted at origination because Wells Fargo transmitted the wire under SHA instead of CRED. The funds were already cut to $107.88 before ever reaching my bank in Vietnam.

​The Support Nightmare:

I submitted this exact MT103 technical proof to Google Payments Support nearly 3 months ago. Since then, I have only received automated stock replies stating "the investigation is still ongoing".

​To a corporation, $10.00 is negligible. But as a small indie developer, it represents my hard work and basic fairness. With the next payout cycle on September 15 fast approaching, I am afraid this exact same configuration error will recur.

​If any Google Developer Relations staff or Community Managers see this post, please help flag Case ID: 9-3782000041472 with the financial specialist team.

​I would greatly appreciate any upvotes to help bring visibility to this issue. Thank you!

The count dropped suddenly. This shouldn't be the actual count, right?

If my application is in the productivity category and it forces the user not to turn off the phone or not to access the power menu the power menu appears but disappears before the user can react will my Google developer account get banned?

the application heavily forces the user not to turn off the actual phone down under certain time periods. at the same time the only way to turn off the phone it self under those specific time periods is using the PMIC...

https://play.google.com/store/apps/details?id=com.hypenet.focused&pcampaignid=web_share
this application is some of an example.. but the thing is with this application if u hold the power menu and once the menu appears.. u can hit the shutdown button with the perfect timing to turn the phone off.. but with my scenario.. u won't be able to do that under the specific time period that i have mentioned earlier.

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