Live data from Hacker News

Your app is not compliant with Google Play Policies: A story from hell

sylviavanos.nl

181–190 of 197 posts

Re: Your app is not compliant with Google Play Policies: A story from hell

#181
post #35

Earlier quoted context omitted.

I see this and think of all the millions of apps that the code controls. I don't know how many do fail validation, but it's clearly not a vast number, definitely under 1%. Given that they're also clearly training a model for this, based on a large number of inputs and rules, then this is pretty good. Their end goal is clearly to be able to remove humans from this process completely. Which is good - it's shitty work.…

I don't see apps that fail validation, and there are too many (shitty) apps anyway - more validation is good. You've failed to understand your own problem. You're seeing lots of shitty apps. That means the validation isn't working because part of the validation process is supposed to make sure apps are of sufficient quality. So no, you don't see apps that fail validation, you see apps that should have failed validati…

I don't see all the apps that applied. I just see the apps that passed validation. It's totally reasonable to assume that the apps that were rejected by the validation process are worse than the apps that were accepted.

Re: Your app is not compliant with Google Play Policies: A story from hell

#182

Earlier quoted context omitted.

I see this and think of all the millions of apps that the code controls. I don't know how many do fail validation, but it's clearly not a vast number, definitely under 1%. Given that they're also clearly training a model for this, based on a large number of inputs and rules, then this is pretty good. Their end goal is clearly to be able to remove humans from this process completely. Which is good - it's shitty work.…

> From my point of view as an entrepreneur, I approve. Sorry, I don't believe you here. If you were trying to get, say, a loan from the bank you've done business with for years but would only ever get vague replies and could never speak with a human, you'd be rightfully angry. There's nothing special about being an "entrepreneur" that makes this less problematic.

Devs aren't the customer here.

I work in a fintech and deal with banks all the time. We only ever get vague replies, and while we do speak to humans, they're not as helpful as you'd think. I'm rightfully angry. But there's nothing we can do because we're not the customer - we need to do business with them, we can't walk away, so we've got very little leverage.

Re: Your app is not compliant with Google Play Policies: A story from hell

#183

Earlier quoted context omitted.

I despise the tell them nothing approach and I think it's despicable, but that said I think there is a more legitimate reason than the lawyers. If the person is a spammer or otherwise not legit and you tell them what they did wrong, it's a lot easier to hack around the problem and beat the automated moderation and get your malware into the store. I don't think that justifies the harm it does to regular people, but it…

> If the person is a spammer or otherwise not legit and you tell them what they did wrong, it's a lot easier to hack around the problem and beat the automated moderation and get your malware into the store. Is it? Because spammers and malware writers are the only ones that already know what they did wrong - spamming and malware! While everyone else is left guessing.

They know in general, but they don't know exactly which check they tripped and why. That makes it harder to hunt down the detected part.

Re: Your app is not compliant with Google Play Policies: A story from hell

#184

Earlier quoted context omitted.

> Sounds to me like what you're saying is that the walled-garden approach of needing to approve every app that ever gets developed as a whole is what's infeasible without creating kafkaesque conditions dealing with their automation, and I fail to see how you've made a case for this automation being all that good in the first place, given that your main argument for it is that it's found "millions of vulns in apps ove…

They can’t really have their cake and eat it too. Either they have a system with zero false positives and they should have a review team for all the complaints of things that slipped through. Or they should aim for zero false negatives and have a review team for anything which gets stuck.

A false positive is "rejecting an app because of a behavior that isn't actually present." You've got them backwards.

Re: Your app is not compliant with Google Play Policies: A story from hell

#185
post #176

Earlier quoted context omitted.

> This kind of incompetence makes me seriously doubt that Google is doing anything to more substantially review apps for deeper security issues, either statically or at runtime. I actually know the team that does security vuln automation for Google Play. They've found millions of vulns in apps over the years. One of the challenges they face is precisely this sort of headline: how do you use static analysis to find vu…

> I actually know the team that does security vuln automation for Google Play. They've found millions of vulns in apps over the years. One of the challenges they face is precisely this sort of headline: how do you use static analysis to find vulns and ensure that you don't inundate users with false positives, forcing them down the admittedly limited support channels. Pay people to do tiered support. "but that costs m…

> Pay people to do tiered support.

This exists. You can sign up for a contract that will grant you various tiers of support.

Re: Your app is not compliant with Google Play Policies: A story from hell

#186
post #81

It just amazes me that developers try to cram editorializing into the title of the app, when you're already given a search word field and a description field in which to tell the world about your app. IRL nobody searches for "Cheerios - Toasted Whole Grain Oat Cereal for the Whole Family".

This is something Google does themselves. Their listing for Chrome is "Google Chrome: Fast & Secure", Keep is "Google Keep - Notes and Lists"

Re: Your app is not compliant with Google Play Policies: A story from hell

#187

Earlier quoted context omitted.

But the question is why you shouldn't be able to sideload an app at all. Having a curated store is pretty cool, and you can have that while also letting users install their own apps manually (even with barriers, making it as hard as they like).

Developers only put up with the curated app store because it's the only option. If there was an alternative, major companies would mostly choose to bypass the app store, leaving it a barren wasteland like the Mac app store. If Apple allowed sideloading but went out of their way to make it obnoxious enough that everything which could be would still go through the app store, you'd just have all of the exact same compla…

But that's not the case at all with Android and has never been. I don't think any of that would happen, the vast majority seems to stick with the default app store, while the rare technical user who wants to sideload has the freedom to do so, everyone wins.

Re: Your app is not compliant with Google Play Policies: A story from hell

#188

What OP unfortunately missed is a post like this: "Tell HN: You can't add “no ads” in your Play Store app's title" https://news.ycombinator.com/item?id=29497680

Sadly the feature to filter out apps that have ads or in app purchases does not exist. Probably on purpose. There are many utility apps with thousand of similar apps, most are garbage filled with ads but then there are a few made without app upselling or ads but until you find those you send a lot of time.

Yeah, I gave up on the Play Store very quickly, and so now it's just F-Droid and the occasional play store install with Aurora. I just feel like that if I need to spend energy either way, then I'm better off spending it in the FOSS ecosystem.

Re: Your app is not compliant with Google Play Policies: A story from hell

#189

Earlier quoted context omitted.

> If the person is a spammer or otherwise not legit and you tell them what they did wrong, it's a lot easier to hack around the problem and beat the automated moderation and get your malware into the store. Is it? Because spammers and malware writers are the only ones that already know what they did wrong - spamming and malware! While everyone else is left guessing.

They know in general, but they don't know exactly which check they tripped and why. That makes it harder to hunt down the detected part.

But you wouldn't tell them which check exactly - you only tell them "spamming/malware".

Re: Your app is not compliant with Google Play Policies: A story from hell

#190
post #174

Earlier quoted context omitted.

Could be, actually. The press sucks: a bunch of untrained people too lazy to get off their laptops and talk to people. I don't think Quora falls into that "spammer" category, though. No one is seeking to make any serious money from it, AFAICT.

If your product/brand is an answer on every relevant question, that's probably worth a lot.

So much money they're leaving on the table, then.

(Or maybe they're secretly raking it in. Who knows?)

Post reply on HN