Two weeks of dealing with Google as a developer • Hacker News Board

Re: Two weeks of dealing with Google as a developer

#81

Post by zakki » Thu, Nov 17, 2022, 12:30 AM UTC

dekhn wrote: post #51

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

Genuine question, which one is easier: - convince editor - write something that reviewer will understand

Re: Two weeks of dealing with Google as a developer

#82

Post by sgjohnson » Thu, Nov 17, 2022, 12:32 AM UTC

0xbadcafebee wrote: post #46

cwkoss wrote: post #17

Earlier quoted context omitted.

A union for customers of monolithic tech companies who provide negligent support could be cool.

Sounds like in this case it needs to be a craft union or industrial union: a union made up of laborers of a craft or industry (in this case, mobile app developers). Get enough developers of high-profile apps on board, and now you have negotiating power. If they balk, make a union-controlled app store, threaten to sell apps only on the union store.

No post body was provided.

Re: Two weeks of dealing with Google as a developer

#83

Post by the42thdoctor » Thu, Nov 17, 2022, 12:32 AM UTC

It seems like an algorithm evaluates your app and the support guy simply sends you the result. He has no saying in the process. It's dumb I know, but it's what looks like.

Re: Two weeks of dealing with Google as a developer

#84

Post by _yb2s » Thu, Nov 17, 2022, 12:32 AM UTC

zakki wrote: post #81

dekhn wrote: post #51

Earlier quoted context omitted.

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

Genuine question, which one is easier: - convince editor - write something that reviewer will understand

The editor reads the reviewer comments and replies also. In most cases replying to the reviewer like I suggest will allow the editor to realize it was the reviewers mistake, and they won't even bother sending it back to the reviewer... but if they do you've targeted both strategies with one response.

Re: Two weeks of dealing with Google as a developer

#85

Post by Grimburger » Thu, Nov 17, 2022, 12:32 AM UTC

ncallaway wrote: post #5

I think at least one thing worth a try is: make a tiny, relatively inconsequential change, and submit it again. If you had a 93% success ratio before, you've got pretty good odds that you'll get a new reviewer on the next update and it'll be approved. Maybe something like the copy change puffoflogic recommended. Just make any tiny change in the area, re-submit the app, and hope you get lucky with a better reviewer.

That's the sad thing about this story, it really just sounds like Goodhart's law in action, a certain % of apps need to get rejected/reviewed/appealed each month.

Re: Two weeks of dealing with Google as a developer

#86

Post by tenarshins » Thu, Nov 17, 2022, 12:32 AM UTC

human wrote: post #16

If the future of customer-service is full of AI like “Anthony”, I’m moving to the woods.

You are much too late. The woods are already full of people who escaped.

Re: Two weeks of dealing with Google as a developer

#87

Post by Vt71fcAqt7 » Thu, Nov 17, 2022, 12:33 AM UTC

TylerE wrote: post #49

TheBrokenRail wrote: post #39

Earlier quoted context omitted.

At least on Android you can install alternate app stores like F-Droid. All you have to do is allow apps to be installed from unknown sources. If you use Apple, you're just out of luck unless you want to mess with whatever hacky workaround is popular this week.

I have never felt the need to do so on iOS. I cannot say the same about Android.

Can you share more about your experience with android?

Re: Two weeks of dealing with Google as a developer

#88

Post by [deleted] » Thu, Nov 17, 2022, 12:33 AM UTC

smt88 wrote: post #31

Tenoke wrote: post #20

Earlier quoted context omitted.

It's more like if you could only drive approved cars on the regular roads.. which is already the case but regulated by the government instead.

My car happily drives on private roads, and even dirt and gravel, without government approval.

[deleted]

Re: Two weeks of dealing with Google as a developer

#89

Post by imron » Thu, Nov 17, 2022, 12:34 AM UTC

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.

Google already fixed the problem from their end

Re: Two weeks of dealing with Google as a developer

#90

Post by ksec » Thu, Nov 17, 2022, 12:34 AM UTC

Consider it for a moment that "Nothing" is now actually a brand name for Android Phone. I had a small pause to try and compute what is going on in the headline.

But on to the article. I believe most of Apple or Google apologist were suggesting something similar to Macrumors comments. It is their App Store. They can do whatever they want with it. If you are so unhappy, go and create something yourself.