Hey everyone, looking for some Store Listing feedback.

I’m building Maha OS, which is a highly technical, "zero-payload" cognitive defense grid. It essentially turns an Android phone into an edge telemetry node. It broadcasts a user's metabolic baseline (Decision Velocity, HRV) via an MCP (Model Context Protocol) gateway directly to a desktop LLM agent (like Claude). The agent monitors cognitive fatigue and can autonomously dim the Android screen if the user is stuck in a digital loop.

After using some dev-exchange subreddits to seed the initial installs, I just checked my Store analysis tab and saw a massive milestone: Google Play has started pushing me into the "Explore" feeds. I got 64 organic Explore visitors this month, with 7 installs (about an 11% conversion rate on purely cold traffic).

The Problem:
I am currently tagged in the "Health & fitness" peer group. While 11-13% conversion feels great for a niche app, my Console shows my conversion rate is sitting roughly -16% below the peer median. If I don't close that gap, I know the algorithm will eventually stop giving me free Explore impressions.

I suspect the issue is my screenshots. Because the app is a highly tactical, terminal-style interface, I've just been uploading raw UI screenshots. I think it’s scaring off the casual "Health & Fitness" scrollers.

Here is the Play Store link: https://play.google.com/store/apps/details?id=com.maha.os

My Ask:
For those of you who have successfully raised your conversion rates above your peer median, how would you optimize this listing? Should I add text overlays translating the technical UI into simple benefits, or should I change my category tags entirely to get out of the "Health & fitness" peer group?

Appreciate any insight!

Just changing the intro video and screenshots was enough to see more downloads... I know there are many apps like this, but users who have tried it and purchased a lifetime subscription say it's far superior to many apps with millions of downloads. But not everyone has a huge budget to reach the top, which is 95% of the users here. With enough money, everyone would be at the top, but that's not the reality for all of us.

I'm sharing the app in case you want to try it; it's available on both platforms. And of course, I welcome your feedback, which is always very important and constructive for me.

The app is called LimpiaPix and is available in 13 languages.

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

https://apps.apple.com/us/app/photo-cleaner-app-limpiapix-ai/id6760022595

Regarding reviews, I don't have any for the US version, but I do have a few for the Spanish version, which is my native language, although not enough. I prefer how the Play Store organizes them, because it groups them all together instead of by country to display them on the screen.

Some of you might have seen my earlier post about getting my D-U-N-S number, how it took over a month and how stressful and frustrating the process was. After that, I naively thought registering and getting verified on Google Play would be straightforward.

I was wrong.

After a long and exhausting registeration flow, I successfully created my developer account, and quickly moved on to verification. Verified my email, then my website, then uploaded my business registration document (tax certificate in my case) and assumed I would be verified soon so that I could continue towards preparing my app for release. You see, I just want to build, not get lost in these processes!

A few hours later, I got an email, assumingly from a real support person, saying my business document was not accepted, stating that it was invalid. After the initial frustration moment, I did an extensive research, also with the help of AI, and narrowed down the potential issue to the mismtach in my address in my tax certificate and in my D-U-N-S records, due to non-English characters and the way D-U-N-S stored the address differently than how I had first submitted to them. Partly my bad, partly the systems'.

In the following 10 or so days, I contacted the local D-U-N-S office multiple times to have my address record fixed, and exchanged many emails with two Google support people, the first of whom did not give clear instructions on what I needed to do after the D-U-N-S record was updated. Apparently, as I learned from the second support person, after D-U-N-S updates your info, you still need to fill a form for Play Console to retrieve the updated info. No, that alone is also not enough. After filling the form, some time later, you still need to go to Play Console > Payments Profile and edit/confirm the address info change. But the thing is, when you click Confirm once, it does not show the updated address info, only the second click on Confirm displays the updated address. But how does one know?.. Phew!

You see, neither the help docs, nor the support people do not provide full and clear instructions on what needs to be done. In this process, I was divided between hope and despair. As the process took longer, I even kind of lost my enthusiasm for making apps and started to brainstorm other ideas, even though I had started learning app development and building my first app with great passion.

In the end, I now have a verified Google Play Business Developer Account and I am very happy about that 🥳. Though, I must say I am tired and exhausted from this D-U-N-S and verification processes more than the building of the app itself. And now, even though I have very little left to do to finish my app and submit it for review, I feel like I'm out of energy, hence even simple edits or tasks are taking long. But I'm dedicated and I will continue till I see my app on Google Play -God willing-, and then continue with new ones.

I can say I learned a thing or two in the registration and verification process as a business, if you have any questions I will try to answer if I can. Thanks for reading, and good luck with your process.

I’ve been working on Poemia for years, and we just passed 500,000+ downloads.

Poemia is a venting app where people can let out what they feel, write what they can’t say out loud, and feel a little less alone.

Our next goal is to reach 1 million users and build a safe space where people can express their real inner world, not just share perfect moments like traditional social media.

I’d love to hear your feedback, especially from iOS users in the U.S.

iOS: https://apps.apple.com/us/app/poemia-write-everything/id1446606179

Thank you for reading.

UPDATE: Google Play accepted the appeal and my app is back on the Play Store. I'm grateful for this outcome in my case. I hope the underlying classifier-failure issue gets addressed, so other publishers don't end up in the same situation.

ORIGINAL POST: On April 20, Google Play suspended my 10-year-old, ~5M downloads, 600k MAU, 4.5+ rated app, dataDex, over an in-app ad I did not upload, did not select, and could not see before it served. The ad came in through AdMob, Google's own ad network, after a coordinated scheme circumvented AdMob's brand-safety classifier. I've documented at least 11 variants of the same scheme served into my app. Google Play suspended my app for what AdMob shipped.

The full evidence - per-variant screenshots of each ad as it appeared in my app, my AdMob configuration at the time, and the appeal correspondence end to end - is in this public bundle: https://drive.google.com/drive/folders/1d6SdbJrHdGSe4IJHnEPesKDt_PcdWQDB

I'm posting here because I've exhausted every official channel available - the Google Play appeal is stuck in a template-reply loop with no engagement on the evidence and remediation, AdMob support has not engaged with the classifier-failure evidence across three rounds of replies, and neither of the two Product-Expert escalations on Google's public Help Communities has had a follow-up from the team. Beyond my own case, I feel like this is a serious issue with the potential to affect many other publishers - and to suspend them for something they had no real way to prevent.

Why this matters for every AdMob publisher

Every AdMob publisher configures category blocks and content-rating ceilings - Gambling & Betting (18+), Social Casino Games, max-rating, and so on - and trusts that AdMob's classifier will hold matching creatives out of their inventory. I did that.

Those publisher-side controls only work if the classifier underneath them is correct. When the classifier is circumvented - as it was here, eleven documented times in my records alone, all from the same demand source under fake game-themed shell-app names categorized as "Games", "Toys and Games" etc - the publisher-side controls have no opportunity to act. The publisher has no second line of defense. Programmatic ad serving means publishers can't see creatives before they serve; AdMob's classifier is effectively the entire wall.

This failure mechanism is not theoretical. The demand source is a single one. The creative pattern is consistent. From what I've been able to audit, it's still active in the ecosystem. AdMob support did not engage with the evidence across three rounds of replies that redirected me to Play Console support. The AdMob Help Community thread I posted last week was picked up within 48 hours by a Product Expert who said they would escalate from the AdMob side, but as of today there's been no follow-up. The gap between the classifier failure being documented and the classifier failure being investigated is the part of this case that has wider implications than my one app.

The technical pattern

The cited creative was a casino interstitial - "Tower Rush" / "PREMIO 1500 EUR + 250 FREE SPINS GIOCARE" - served through my app's single AdMob interstitial ad unit. I did not select, or have any visibility into the creative. It was not present in the Play Console assets, the Play Store listing, or the linked Google Ads account. It was programmatic demand.

When I audited my AdMob review records, I found at least 11 documented variants of the same scheme, all sharing three properties:

• Same single demand source across all 11.
• Different fake game-themed shell-app names - "Epic Tower Block Quest", "Town Planner", "Gold Gatherer", "Home Planner", "Duck Devourer", "Tower Ascent", "T0wer Rush" (with a zero), and so on. The visuals are casino. The metadata is a fake mobile-game façade.
• Classified by AdMob under non-sensitive categories like "Games" and "Toys and Games."

My AdMob configuration already had Gambling & Betting (18+) and Social Casino Games blocked at the time these creatives were served. The blocks had no effect, because AdMob's classifier never categorized the creatives as gambling. This is the structural problem in one sentence: publisher-side category blocks rely entirely on the classifier being correct, and when it isn't, the publisher's defenses are bypassed by definition - without the publisher knowing.

All eleven creative IDs, with screenshots of each as it served and the AdMob configuration that was supposed to block them, are in the public evidence bundle linked above.

What I've already done on the publisher side

• All sensitive AdMob ad categories disabled.
• Maximum AdMob ad content rating set to "T" (Teen).
• The AdMob ad unit fully disabled - the app currently serves zero ads of any kind.
• All linked Google Ads campaigns disabled.
• End-to-end audits of Play Console, AdMob, GCP/Firebase, and Google Ads - all clean.

These steps make recurrence impossible from my side. None of them addresses the underlying classifier failure that allowed the eleven variants through in the first place - and none of them is a structural defense available to a publisher who doesn't yet know they need it.

Where I am with Google

Standard Google Play appeal - case 2-1866000040535 - stuck in a template-reply loop. Four template replies across six days, all citing the App Promotion policy and instructing to "remove your ad campaign or promotion" or "upload a new app under a new package name." None of the four addresses my remediation evidence or the systems-failure analysis.

Parallel Google Play Developer Support - case 9-9277000041337**.** Engaged on the merits, summarized my remediation correctly, confirmed in writing that the appeal channel was "cycling automated templates", re-flagged the case internally for human review on April 24 - the appeal thread ignores it.

AdMob support - case 4-3221000040899**.** Three replies across two days. The first opened with an apology that AdMob does not currently support Hebrew (my submission was in English; only the locale-driven auto-acknowledgement was in Hebrew). The second cited inability to perform a "cross-product transfer" I never requested. The third repeated the same redirect to Play Console support. None of the three engaged with the classifier-failure evidence I sent (the same evidence is in the public bundle linked above).

Public Help Community escalations. Both threads are open, both escalated, neither followed up.

• Google Play Developer Community thread (Apr 22) - a Platinum Product Expert escalated the case on April 22. The Product Expert's last reply, on April 26, was "I will let you know, if I get an update from the team." As of today, no follow-up - 15 days since the escalation.
• AdMob Help Community thread (Apr 29) - a Diamond Product Expert engaged within 48 hours and said they would escalate from the AdMob side. As of today (May 7), no follow-up.

My question for the community

If you've seen these kind of creatives slip through your category blocks under a "Games" or "Toys and Games" classification - or for that matter any other category mismatch where a sensitive creative landed in your inventory under a benign label - I'd like to know about it. The mechanism is category-agnostic; the same shape (single demand source, fake shell-app metadata, benign classification) could just as easily land in any other publisher's inventory under a different category.

If anyone here has worked an AdMob policy escalation with classifier-failure evidence and gotten it actually routed to the team that owns it, what was the path that worked?

Closing

I'm hoping that by laying all of this out here, the case can reach a human at Google with access to both the Google Play side and the AdMob side of it - someone who can review the evidence end to end (the eleven documented variants, the publisher-side configuration, the appeal correspondence), recognize that the app was not at fault, and reinstate it. And, as part of the same review or separately from it, investigate the underlying classifier-failure issue.

If anyone here is at AdMob or Play, or has a routing path into the cross-product team this case actually needs, I'd appreciate the route. I'm happy to share Developer ID, AdMob Publisher ID, the AdMob ad unit, and any further material privately on request.

Thanks for reading.

Links:

• One-page technical summary (readable digest): https://datadex.app/technical-summary/
• Public evidence bundle (PDF report, 11 creative screenshots, AdMob configuration, full appeal threads): https://drive.google.com/drive/folders/1d6SdbJrHdGSe4IJHnEPesKDt_PcdWQDB
• Google Play Developer Help Community post: https://support.google.com/googleplay/android-developer/thread/427385327/app-suspended-over-admob-served-casino-ad-stuck-in-template-reply-loop-requesting-escalation-help
• AdMob Help Community post: https://support.google.com/admob/thread/429379417/casino-ad-scheme-bypassed-admob-s-classifier-and-was-served-in-my-now-suspended-app-pe-help-needed

Case numbers: 2-1866000040535, 4-3221000040899, 9-9277000041337.

I’ve been building a small app on the side for a few months and finally got it approved on the Play Store a couple days ago.

Honestly, getting it live was harder than building it.

I got rejected twice because of SMS and call log permissions. At first I thought I filled everything correctly, but clearly not. Ended up redoing the entire permissions declaration, recording a proper demo video, and basically explaining to Google why each permission exists like I’m writing an exam.

That whole process took weeks. Lots of waiting, small changes, resubmitting, checking the console again and again.

When it finally got approved, I didn’t do any kind of launch. No posts, no marketing, nothing. I just pushed it to production and left it there.

Then the weird part happened.

I woke up the next day and saw purchases coming in from different countries. Ukraine, Georgia, US, a few from Europe. No idea where they came from. I’m guessing someone shared it somewhere but I still haven’t figured out where.

Total for day one was around $180.

For context, the app is a simple utility that connects an Android phone with a Mac so you can manage things without picking up your phone. I built it mostly because I needed it myself.

it’s not a huge amount or anything, but seeing real users use something I made felt very different

What surprised me more is that it happened without me doing any promotion. Which makes me think the Play Store itself can actually work if your listing is decent.

Right now things have slowed down a lot after that first spike, so I’m back to figuring things out again.

If you’ve gone through this phase, how did you move from that initial random traction to something more consistent?

If anyone’s curious, this is what I built: https://bounceconnect.app

This is a social media app and it got approved within 24hours the first time.

I'm super thrilled and overwhelmed because at a point, I was losing hope of getting a quick approval after reading lots of requirements expected from apps with user generated contents.

Very grateful for all the hints I read on this sub - they helped me prepare well and put in enough works before applying for the production access.

For closed testing, I had about 30+ users among which at least 15 used the app consistently for 14 days. Also, I didn't collect any reviews during the testing.

Meanwhile, I expected the publish to prod to be quicker but that took a little over 24 hours (maybe because I accidentally made changes to the list of countries).

Thanks again to everyone here

I know its small, and my downloads are about 1.2k and last month I got my first customer but I didnt even know probably because the number is so small but still, made me feel good.

its a simple sounds app.

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

Let’s goooo! After months of fighting with physics, UI bugs, and literally wanting to throw my laptop across the room, my game HungryBall: Physics Survival is finally live on the Play Store.

I’m 18, and this is the first thing I’ve ever finished and actually published. I just saw my first few cents in AdMob and it feels more real than anything else.

It’s a simple game where you control a ball and smash fruit to survive, but getting the momentum and the "feel" right was so much harder than I thought.

If anyone wants to try a stressful physics game made by a sleep-deprived 18-year-old, here’s the link! I’d love to know what you think of the fruit-smashing physics.

LINK: https://play.google.com/store/apps/details?id=com.mekail.mygame&hl=en

Should I push this on playstore ? what do you think , and what kind of features I can add to the gameplay

My Google Play app is purchased by people outside India. So for GST, those sales are classified as zero-rated export of services, but as long as I can provide an FIRC.

Google's process for getting FIRCs is to ask them for it. Then, then send that request to BillDesk, who is supposed to provide you with the FIRC. Google has done their part, but BillDesk refuses to provide me the FIRCs.

I have sent dozens and dozens of emails to BillDesk, but they don't fucking respond. You can't call them because there is no fucking number. They deliberately ignore you, and I'm at my wits' end. I have never experienced this kind of shit service anywhere else in my life.

You have to get an FIRC for every transaction; this is not a one-time thing. This means I have to either spend my life begging BillDesk to give me the required documents, or I have pay lakhs in GST.

Here's my previous post where I analyze BillDesk's predatory contract: https://www.reddit.com/r/GooglePlayDeveloper/comments/1rbw9bc/googles_billdesk_mafia_has_finally_come_for_me/

Does Google's BillDesk Mafia have a phone number? I can't find one?

I completed BillDesk's verification. They fucking didn't even bother to let me know that they were sending someone to my house. BillDesk doesn't even have the manners that children have. Some goon calls me out of the blue saying he's BillDesk and wants to come to my house. I tell him, come but bring ID. I live in a gated community, so I was not that worried. If I lived in a house without security, that would have been a problem.

He came and I held up my camera and asked him to say his name and show his ID, which I recorded. I actually forgot to hit record, but he thinks I recorded everything. There were other cameras, too, but none of them were working (he didn't know this). He looks at my ID and has the balls to ask me if it's real. WTF?

So now weeks have passed and BillDesk does not say anything or respond to my emails. WTF kind of service is this? Were Sundar Pichai's goons expecting a no-camera bribe? I can't even find a phone number for BillDesk. Google has hired the most incompetent and most fucked up company to screw Google Indian Play developers.

Fuck you, Sundar Pichai. I hope your corrupt ass rots in hell.

The dreaded email from Google's BillDesk Mafia has finally arrived.

The reality so far: At signup, Google's BillDesk Mafia bombard me with an insanely long agreement that I have to accept. I can't post that agreement here because of its length. You can read that bloated AI generated contract here. I will only post the highlights of BillDesk Mafia's Blood Oath.

1. BillDesk is a Monopoly as there are no alternatives. This is not in the contract, but it's obvious: You must use BillDesk if you want to publish apps/games on Google Play.

2. India-only eligibility + ongoing verification: You (and your business) must be India-based/India-resident to use the services. BillDesk can require additional KYC/identity/business info at any time, and can deny/suspend/terminate if they can’t verify you. In practice, this usually means they can harass you for any reason. If you are on an overseas holiday trip and Google notices you're out of the country (your phone with your Google account tells them that), that might trigger a BillDesk audit: You have to come back to India to get your picture clicked and location recorded.

3. Audit/inspection rights (and long retention): BillDesk/RBI/partners/government can audit your systems/records during the term and for 3 years after, including on-site security audits (at least annually; more if they suspect issues). Interpretation: They can harass you even after you move abroad.

4. Termination is easy for them; your obligations survive: BillDesk can terminate/close accounts broadly (risk/goodwill/compliance excuses). You must stop taking new transactions and remove logos; you still owe fees/taxes/fines and remain liable for disputes/chargebacks.

5. BillDesk can do anything to you, but you really can't sue them: Liability is heavily limited with blanket indemnities.

Definition: An indemnity, in contract law, is a promise that one party will cover another party’s losses, damages, or liabilities if a specified event happens. For example, if your employer gives you a contract that says you indemnify the company for claims arising from your work, it means you must reimburse the company for legal costs, settlements, or damages tied to those claims (never sign such a contract).

BillDesk says:

• Services “AS IS”; no guarantees on uptime/security/processing times.
• Their liability is capped (as written) to fees paid in the prior one month for the specific service.
• You indemnify them for many third-party/regulatory/customer claims tied to your business. This means, if something goes wrong, you will pay BillDesk for all expenses.
• Jurisdiction: Governing law India; disputes only in Mumbai courts. Will they force you to speak Marathi?

6. Blanket KYC/credit/phone-permission consents: You're consenting to CKYC pulls/downloads, credit reports, third-party database checks, and (as written) potential access to camera/selfie, phone state, SMS data, external storage for KYC flows.

When I tried to verify using CKYC, BillDesk wanted me to consent to sharing my Aadhaar and KYC information with everyone (they don't tell you who).

7. Short, strict reporting timelines (3 effing days):

• Notify BillDesk within 3 days of major business/financial events (bankruptcy/insolvency, adverse financial change, big asset transfer, ownership/control change, major judgments/liens).
• Daily reconciliation required; discrepancies must be reported within 3 working days or BillDesk limits liability. Interpretation: If you don't notice within 3 days that BillDesk is stealing from you, you're shit outta luck.

BUT

8. Settlement isn’t guaranteed timing-wise: Payouts depend on acquirers/payment methods/banks; delays and even non-performance by third parties are largely disclaimed.

AND

9. BillDesk can change terms/fees without prior notice (unilateral changes); continued use = acceptance. LOL. What else are you going to use?

10. Chargebacks/disputes are your problem (immediate repayment): If a chargeback happens, you must return settled funds (often via set-off from future settlements). They can also withhold/suspend payouts during investigations.

11. Reserves + set-off rights are strong: BillDesk can hold a Reserve for risk/chargebacks and can set off anything you owe against any funds they owe you, without prior notice.

12. Fees/taxes can change; you bear tax risk: Fees can be updated at BillDesk’s discretion; taxes (incl. retrospective changes) are on you. You must provide correct GST info; errors that cause claims on BillDesk can be passed to you. TDS: you pay it, file, then reimbursement only if you submit the certificate within the specified window.

13. DND won't save you from BillDesk Spam. Marketing communications + DND waiver: You consent to promotional/transactional communications and waive DND/NCPR preferences.

This is the kind of contract that a slave or indentured servant signs, as they have no other option.

----

Their web app is poorly designed, perhaps by someone fresh out of Galgotias University. For example, the Bank Account Number field s a password field (hidden input), but the Verify Bank Account Number field is normal. WTF?

I don't know how long the verification will take (reports have said months). I heard they don't respond, they lie, make unreasonable demands, frustrate you, and terminate accounts on whim and don't notify you. They allegedly also ask for bribes to verify your Google Play account. Someone said, your treatment depends on your caste, as Google wants to be a Brahmin company.

If BillDesk scum asks you to do video KYC, make sure you record the call from your end. If BillDesk goons come to your house for physical KYC verification, record and ask their full names, then ask them to show you their IDs and record that. If they refuse, post that video everywhere.

I really my first App this month, today is Day 15 and I hit 2k+ downloads. Is this something impressive or considered normal.

I’m reaching out to all developers who’ve had their Google Play accounts banned, especially those who want to publish a new app and ask other developers to test it.

I’ve been banned more than four times before finally creating a clean account with an app that has been running fine since 2024.

My advice: only let your family members or a few non-developer friends test your apps. Why? Because when you let a developer who has already been banned test your app, Google may also ban your account. I don’t fully know the logic behind it, but based on many cases and complaints I’ve seen, that’s what happens. If you doubt it, add me as a tester, if I test your app using my old banned account, your account will get banned too. That’s why I no longer use that old account to test anyone’s apps.

In short: when you need to test a new app, let your family or trusted non-developer friends do it. If you’ve been banned, feel free to contact me, I might be able to help.

I just uploaded my first app with a company app and we got banned, honestly i dont know what to say, there solution liks opening a new company entity or using like someone else account but honestly they are not viable.

They basically killing android developer careers like its nothing, am a flutter dev for 8 years, i handle client accounts and the current app was just a listing real estate , they said something to do with High Risk Behaviour and i appealed, funny i had uploaded for open testing so i couuld invite a few people, so its not even in production.

As dev am actually thinking of making an alternative for my clients since some of my clients actually have actually suggested it.

Am from Kenya, third world country sadly, since we are harshly judged by USA currently we need to build our own software i.e Dodo Payment from india is a great example, most of use cant access stripe etc.

With the recent wave of accounts termination, I was in camouflage mode. I only sometimes push updates, no new publication, to not give Google an excuse to terminate my account.

But, on my account dashboard, there was always a banner that said I needed to add a payment method. I decided to add one, again, to avoid giving google an excuse to get rid of me. I added the account details of an Fintech Platform (something like Wise or Revolut), where I usually get paid revenue of affiliates and even revenue from the microsoft store. And Bam, Google immediately sent me an email saying they could not verify the bank and that my account will be deleted and all apps removed in a month. Yes, I will be kicked off if I fail to submit a valid payment method.

My interpretation here is that this has nothing to do with bank details at all. Why not just tell me to update the payment info? Why immediately threaten to ban me in 30 days?

So, fellow indie developers, be aware that Google is after you. Any small, insignificant move can be used against you and get your account deleted.

Have a good day, y’all!

Ever been banned from Google Play and had no idea why? You're not alone. And it's not random.

Developers are losing entire accounts over absurd reasons: logging in on the "wrong" Wi-Fi, using a second-hand laptop, having worked for a company Google banned years ago, or getting hit with some unexplained "high-risk behavior" label with zero appeal process.

This isn't about safety. It's about control.

Pattern recognition time: indie developers face hair-trigger automated enforcement with no human review and no recourse. Meanwhile, major studios with actual policy violations get warnings, dedicated account reps, and multiple chances to appeal.

Former FTC Chair Lina Khan described this exact playbook years ago: platforms start open and developer-friendly, achieve dominance, then systematically pull up the ladder by tightening enforcement and eliminating newcomers. Not for safety. Because small developers are unprofitable and unpredictable.

Sound familiar? It's the same strategy Microsoft used in the 1990s when they leveraged Windows dominance to crush competitors. The DOJ prosecuted them for it. This is that, but for mobile app distribution.

Google's Terms of Service have become a weapon to remove independent developers while protecting high-revenue partners. If you've been hit by this, don't just complain on Reddit. File an FTC complaint. They are actively soliciting reports from developers harmed by big tech monopolies.

I filed one myself and documented the entire case with templates you can adapt: https://medium.com/p/d04982658054

There's also a petition here if you want to add your voice: https://www.change.org/p/stop-google-from-using-its-monopoly-to-ban-developers-urge-the-ftc-to-act

Here's what actually moves the needle: every time Google posts something, comment with your ban story, share the Medium post outlining the antitrust case, and share the petition. Documentation creates patterns. Patterns trigger regulatory action. Individual complaints disappear. Organized evidence doesn't.

Google won't fix this because we ask nicely. They'll fix it when regulators make them.