Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Two weeks of dealing with Google as a developer

danfitdegree.hashnode.dev

Post reply on HN
Print view View original

51–60 of 340 posts

Re: Two weeks of dealing with Google as a developer

#51

Post by dekhn »

_yb2s wrote: post #25

As a scientist, I often have to deal with similar BS of a reviewer misunderstanding a submitted journal article, literally insisting we do something we already did, and explained in the paper. I try to just own the fact that I didn't make my explanation clear and visible enough, so I just submit an updated version along with a comment like "We thank the reviewer for pointing out that we didn't clearly articulate our…

Your solution for Reviewer 3 works, but often times, I just work with the editor to convince them the reviewer is confused.

Re: Two weeks of dealing with Google as a developer

#52

Post by TylerE »

typon wrote: post #44
danuker wrote: post #23

Earlier quoted context omitted.

Good thing web browsers aren't fully controlled by Google and Apple

This is why its the ethical responsibility of every dev to use Firefox when they can.

How’s the view from up on your pedestal?

Re: Two weeks of dealing with Google as a developer

#53

Post by typon »

kristopolous wrote: post #29

Not only all this but the system doesn't work. The play store is flooded with low quality baiting garbage. Somehow their onerous policies block out legitimate users and have a VIP line for spammers

This is what surprises me the most about these stories of dealing with Google/Apple app stores. Most of the apps that aren't produced by very well-known studios or large corporations are just trash. There are few gems here and there but its like digging through a landfill to find anything decent.

Re: Two weeks of dealing with Google as a developer

#55

Post by renewiltord »

CamperBob2 wrote: post #33
benlivengood wrote: post #15

Earlier quoted context omitted.

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.

That sounds a lot like Google's problem, not ours.

It appears that they've solved it, then. And now you have a problem.

Re: Two weeks of dealing with Google as a developer

#56

Post by orf »

> We confirm that your app has options to report and block abusive users but your app does not contain functionality to report objectionable content.

Isn’t this the crux of the issue? Are the not asking for a separate “objectionable content” report type, distinct from the generic “report” option? They also don’t seem to show what happens after you press report? Does the app give reporting options? Is “objectionable content” an explicit one of those?

Re: Two weeks of dealing with Google as a developer

#57

Post by Aeolun »

puffoflogic wrote: post #2

Idk, maybe I just speak bot but it seems obvious from the wording that the app needs to split out its "report" button into "report content" and "report user". I don't think they need to do different things, but it will check the box of > We confirm that your app has options to report and block abusive users but your app does not contain functionality to report objectionable content. To be clear, I don't think this wi…

If you have to long press the comment to bring up the report screen. How do you conclude that you are reporting a user? I'd find it more logical if that related to reporting the content.
Post reply on HN