Hacker News new | ask | show | jobs
by praxulus 1307 days ago
It'd be great if google offered an option for a video call with a reviewer for $500/hr as an escalation option for businesses who are getting nowhere with the regular process. Ideally you'd get a refund if you turned out to be correct, but I'd be happy even without that.
6 comments

That’s a terrible idea. What if instead they were held accountable to criminal and civil processes and if Google didn’t meet their end of a contract they were accountable for it.

They can offer their support via a legal accountability mechanism and not a paid-for escalation.

Funnily enough I once saw a post here with someone at fb I believe who had an entire side business like this for a couple hundred where they escalated issues to their pal in support.
It's done all over, I'm not even mad.
That sounds like you'd just create an incentive for reviewers to block more apps, and refuse to admit they were wrong.
IIRC there is already an option to pay Google 7500 $ or something for a new review? I can't remember exactly how it is dressed up to get around antitrust concerns, maybe as a security audit.
Although it's not app store review, Apple DTS is like that (but way cheaper). And I have to say the quality of developer support you get from it has been amazing for me.
Why $500 and not just enough to pay for the salary of that person, or just enough to even be profitable for Google?
How do you suggest to estimate "profit" on such a service when the downside is a risk (however small) of an almost 20 G$ fine by the EU?
I don't think the discussion is specifically to the GDPR issue, also such a service should reduce risks, not increase it.
Automated rules and policies are saving Google hundreds of millions of dollars an hour; they don't want to open the floodgates of spammers reverse-engineering ways to socially engineer the hapless app review humans.
>Automated rules and policies are saving Google hundreds of millions of dollars an hour

Surely this is exageration, right?

That sounds a lot like Google's problem, not ours.
It appears that they've solved it, then. And now you have a problem.
Actually it sounds like our problem, given the content of TFA.
Google already fixed the problem from their end