Live data from Hacker News

Two weeks of dealing with Google as a developer

danfitdegree.hashnode.dev

241–250 of 340 posts

Re: Two weeks of dealing with Google as a developer

#241

You seem to have missed a detail in their replies "We confirm that your app has options to report and block abusive users but your app does not contain functionality to report objectionable content." You complain that they haven't answered the specifics of your emails yet you've actually failed to address theirs. Unpopular opinion but it seems like their response was reasonable tbf.

I agree, the author is conflating the ability to report and block a user due to their content and the ability to report specific content of that user. All they had to do is add a link to report the specific contentId that user created. The author was blinded by frustration and didn’t read.

This could be clarified by a quick phone call to a Google developer support engineer.

If Google is "too big" to run a competent support department then it should be broken up.

Re: Two weeks of dealing with Google as a developer

#242
post #156

Earlier quoted context omitted.

> Getting angry and adversarial They didn't get angry and adversarial, they just explained and asked for clarification. Of course, kafkaesque bureaucracies don't like that, so making a random trivial change and obsequiously resubmitting is still probably the approach to use if you want to stay in business. Google these days is like something out of Brazil .

I have a google pay support thread open. 49 exchanges. The features they keep telling me to use literally do not exist. They just keep posting the same canned response and then ignoring my response that the feature hasn’t been implemented. Then it gets passed to a new person who ignores previous happenings on the thread and repeats. It’s the most kafkaesque thing I’ve ever experienced. I’m going to print it out and b…

Don't forget to publish an article about it and post it to HN, I'm sure many of us are interested.

Re: Two weeks of dealing with Google as a developer

#243
post #179

Earlier quoted context omitted.

Cos users want mobile apps. When Roam research and Obsidian launched, one of the biggest thing people were ranting about was that their lack of mobile apps. Simple. Google also is dominating the browser market. Not to mention, I see Manifest v3 as something in this direction. They just don't have the exact amount of control they do in Play store is all. So my question is, how long are you gonna run?

Sorry, what does the last sentence mean, gonna run?

I believe the parent is offering their explanation that for scenarios that require sustained usage, end users vastly prefer mobile apps to web apps.

There’s a disparity between mobile and web apps in terms of user experience which is why they ended by asking for how long are you gonna run i.e. ignore the difference in user experience by investing in a web app while your competitors embrace it by investing in a mobile app that offers a superior user experience.

Re: Two weeks of dealing with Google as a developer

#244
post #156
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…

> Getting angry and adversarial They didn't get angry and adversarial, they just explained and asked for clarification. Of course, kafkaesque bureaucracies don't like that, so making a random trivial change and obsequiously resubmitting is still probably the approach to use if you want to stay in business. Google these days is like something out of Brazil .

Having recently interacted with Google I have no idea why anyone would choose to do business with them unless they absolutely have to.

Every interaction with them you can feel the disdain they have for human interaction. It makes me wish I was doing business with comcast instead.

Re: Two weeks of dealing with Google as a developer

#245
post #44
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.

For some reason Firefox has horrendous issues on older devices. On my Win7 company-issued laptop a fresh window from a fresh FF install grabs 3.2 out of 4GB of RAM. On my phone (2GB RAM) it gets into a crash loop where trying to type into the address bar or load a new page crashes the browser. Data loss due to crashes is less frequent than when I was running Chrome, but spending 10 minutes every few days repeatedly restarting the browser is gradually getting me to move to Brave.

Re: Two weeks of dealing with Google as a developer

#248
post #156

Earlier quoted context omitted.

> Getting angry and adversarial They didn't get angry and adversarial, they just explained and asked for clarification. Of course, kafkaesque bureaucracies don't like that, so making a random trivial change and obsequiously resubmitting is still probably the approach to use if you want to stay in business. Google these days is like something out of Brazil .

Examples of angry and adversarial: > Who do I contact if Anthony is not doing his job correctly? > This is becoming a joke at this point. > So I just have to close my business because one person in the review team is having a bad day? > Like is this serious?

Exactly - that is just venting anger and the reviewer is likely to pass and go on to the next App. Unfortunately a) the app guidelines/rules are often vague and discretionary and b) App reviewers have hundreds or thousands of apps to review a day and don't have the time to think about borderline cases.

With app stores it's guilty until proven innocent/compliant - I've found (particularly with Apple) that taking time to resubmit saying how you are now compliant (making sure you tick all the requirements) is much quicker than waiting days for them to turn around a no again.

Re: Two weeks of dealing with Google as a developer

#249
I don't get why the publisher is confused. Google confirmed that they understood the existence of a block button, but they want an additional report button so that the app providers can curate the users. Do you really have to go to HN to figure out your company emails?

Re: Two weeks of dealing with Google as a developer

#250
post #156

Earlier quoted context omitted.

> Getting angry and adversarial They didn't get angry and adversarial, they just explained and asked for clarification. Of course, kafkaesque bureaucracies don't like that, so making a random trivial change and obsequiously resubmitting is still probably the approach to use if you want to stay in business. Google these days is like something out of Brazil .

Examples of angry and adversarial: > Who do I contact if Anthony is not doing his job correctly? > This is becoming a joke at this point. > So I just have to close my business because one person in the review team is having a bad day? > Like is this serious?

Those aren't angry or adversarial and Google deserve much worse.
Post reply on HN