Google has become too unreliable

Diggs

Well-Known Member
Reaction score
3,564
Location
Wisconsin
I used to be a fan of Google and it's products but they have become so untrustworthy that I refuse to to invest any time or effort in their products (especially new ones) any more. They continue to shut down services and apps at a record pace and I just hope the services of theirs I use continue to survive. Even those apps and services of theirs I use get nerfed and boinked by poor revisions. It's like there is a new manager for each service/app every year that feels a need to make their mark for better but usually worse.

https://arstechnica.com/gadgets/2019/04/googles-constant-product-shutdowns-are-damaging-its-brand/
 
"...but to have one of your new executives face questions of "When will your new product shut down?" must be embarrassing for Google."
It does not appear to be that embarrassing, if at all. Google does not care.

While understandably frustrating for developers and all other involved parties in building and investing in Google based products, from a business perspective, Google does not care to keep maintaining unpopular or poorly used technologies. We practice this approach in our businesses everyday, no? We cut out any unproductive service/product whenever possible in our businesses when the majority of customers have little to no interest in them, no? The market (the customers) decide whether the products are useful and good. Based on poor usage, the products are not good, or are no longer as good, in meeting their needs.

As far as their brand, I doubt Google is too worried. They have humangous amounts of capital available to advertise any new products /services and convince people to try anything new, especially when it is free or near free.

Personally, I am annoyed and frustrated with their software bugs and ridiculous approach in policing businesses, more importantly, legit businesses. Plus, their entire support experience out of India is simply unacceptable by modern customer service standards. It may be acceptable for more underdeveloped nations in other parts of the world, but for the United States/Canada, sorry, not a chance. And not because any of us necessarily think so, it is our customers that have been brought/programmed to have such high customer service expectations.
 
Last edited:
i loved google inbox. Now am stuck with the gmail app. It is better than before but inbox was my favorite. If i didn't have so much time and effort invest in getting my google stuff just right i would totally jump to office 365. Which i have so i can be comfortable and used to both.
 
Get off Google, use O365. There are issues sure, but Microsoft actually cares, and the product evolution has taken a vastly superior trajectory over the last two years. Then there's Azure behind it... which honestly can do anything.
 
I'm torn about this. Or more accurately I don't really care. Probably because nothing of Google's that I actually use on a daily basis has ever been shut down. But shut down Search, Gmail, Calendar, Android, or Voice - and I will FREAK out. :)

As I look through the unsurprising product obituaries, I see three main categories.
1. Internal competitors to Google's already successful products (lnbox vs Gmail for example).
2. Pie in the sky or cutting edge stuff that probably only existed to see what might stick.
3. Products that were doomed to failure from the start and anyone on Technibble probably could have predicted it if only Google had asked us. (Wave, Reader, Google+).

In the scheme of a mega-company, of which that description doesn't even come close to what Google is, they're going to have many trials and errors. And short term successes that become not worth supporting. And dogs kept on life support far longer than they should be.

Not really any surprises here, nor deprecated products to lament over other than by comparatively very small segments of their ginormous user base. Maybe the lesson is not to switch to anything "Google" that competes with an already hugely successful product like Facebook for example. Or appears to be a solution in search of a problem (Allo?).
 
The thing is... Wave, Reader, and Google+ all still exist, they've just been folded into something else. Google actually rarely kills anything, they just fold it up into something else.

But still, their dev process gives me a headache, even Microsoft with all their Q/A issues have been vastly more consistent... which is pretty telling.
 
But shut down Search, Gmail, Calendar, Android, or Voice - and I will FREAK out.

That's the problem. They removed functionality from the latest updates to Voice and Contacts. Too often they take one step forward and two steps back. I'm staying away and recommending to my clients to do the same or at the very least be very wary......
 
I'd rather they just admit they are putting an end to a product than just letting it linger on for years with no updates.

Inbox was a piss off. It came out then in 6 months it was gone. Not sure what they were thinking with it or where they saw it going.

Sent from my SM-G870W using Tapatalk
 
The thing is... Wave, Reader, and Google+ all still exist, they've just been folded into something else. Google actually rarely kills anything, they just fold it up into something else.
.

I think this is a key point to Google's strategy. They roll out random crap to test the waters and then (theoretically, hopefully, maybe, someday) implement the better ideas back into existing products.
 
"...but to have one of your new executives face questions of "When will your new product shut down?" must be embarrassing for Google."
It does not appear to be that embarrassing, if at all. Google does not care.

While understandably frustrating for developers and all other involved parties in building and investing in Google based products, from a business perspective, Google does not care to keep maintaining unpopular or poorly used technologies.

I hope at some it at some point bites them in the ass. It does not care about those other parties is also the message and which is the message I get from the article. "Do no evil" was their slogan, right? IMO it is pretty evil, not in a biblical sense maybe, to get people to invest time, effort and money in products and services and then abandon them just like that. Read the Reddit threads the article links too and see how they treat app developers. One reason they get away with it. It is called monopoly.

Personally I am not a fan of them. No real alternative I guess, but I think their search sucks too.
 
I hate to be an apologist for Google, so please don't take it that way, but this reporting is dog sh**.

Developers gamble on a platform's stability even more than consumers do. Consumers might trust a service with their data or spend money on hardware, but developers can spend months building an app for a platform. They need to read documentation, set up SDKs, figure out how APIs work, possibly pay developer startup fees, and maybe even learn a new language. They won't do any of this if they don't have faith in the long-term stability of the platform.

There is a stark difference between a platform, product and App. Hey dopey, nobody is writing Apps for Apps. Google+ and YT Annotations and 95% of everything else they list in there has nothing to do with developers, nor could it.. so no, devs are not shaking in their boots. What a retard.

"...developers can spend months building an app for a platform... ...They won't do any of this if they don't have faith in the long-term..."

...and seeing as most of the actual "platforms" where developers could use API's, that got axed, lasted for 7-8-9-10 years. I would say that developers should be happy with their results. Maybe the author should have another column lambasting Microsoft for cancelling MSDOS, or Apple for the Lisa II. Putz.

Hardware manufacturers and other company partners need to be able to trust a company, too. Google constantly asks hardware developers to build devices dependent on its services. These are things like Google Assistant-compatible speakers and smart displays, devices with Chromecast built in, and Android and Chrome OS devices.

OK, so which piece of hardware from a developer no longer works? It's a red-herring.. Google killed production of their OWN Chromecast Audio device... only because "Chromecast" already does what people want and more for what, $35? Did Google kill Chromecast all together or stop audio streaming? No. Did any 3rd party developers get hurt? No. Do Chromecast Audio devices still work? Yes.

Imagine the risk Volvo is taking by integrating the new Android Auto OS into its upcoming Polestar 2: vehicles need around five years of development time and still need to be supported for several years after launch.

Don't forget Audi and Fiat, too, which already have new models in production with Android Auto

OMG, IMAGINE THE RISK! Yeah, because the alternative, Apple's CarPlay, has been just an outstanding example of "no-risk"? Apple CarPlay, the platform that doesn't allow 3rd party apps(No risk there, for sure!).

Let's see what the public consensus of Apple CarPlay is:
CarPlay has seriously ruined any experience I have with any any factory infotainment system now
How Apple CarPlay made me hate my iPhone
Apple CarPlay.. Why does it suck so bad?
CarPlay sucks or what?

Sick and disgusted: The worst tech failures of 2018
APPLE IOS 12 CARPLAY: DOESN'T PLAY WELL WITH OTHERS: Users rejoiced when they heard that iOS 12's CarPlay would finally add support for third-party mapping and navigation apps, such as Google Maps and Waze. But then we found out that they would not be treated like equal citizens in the same way Apple's Maps does and would not have hands-free support for third-party intelligent agents such as Google Assistant as their preferred voice control (as opposed to Siri).

Ah, that must be the stability the 3rd party developers are looking forward to, as the author suggests.

Meanwhile Google is:
Off the back of the news that Google will allow third-party app developers to get their hands on Android Automotive, the tech giant revealed more details overnight at its enormous tech conference, Google I/O 2019, that may shake Apple to its core

With so many shutdowns, tracking Google's bodycount has become a competitive industry on the Internet. Over on Wikipedia, the list of discontinued Google products and services is starting to approach the size of the active products and services listed. There are entire sites dedicated to discontinued Google products, like killedbygoogle.com, The Google Cemetery, and didgoogleshutdown.com.

A competitive industry of tracking failures? What, for the 8-12 items in a year? LOL! I hope they don't hurt anything while updating their website databases! There are entire sites dedicated to many other companies and their failures, cancellations and antiquity. Whoopdy doo!

I think we're seeing a lot of the consequences of Google's damaged brand in the recent Google Stadia launch. A game streaming platform from one of the world's largest Internet companies should be grounds for excitement, but instead, the baggage of the Google brand has people asking if they can trust the service to stay running.

Why should a game-streaming service be grounds for excitement? Are there other examples of game-streaming? Were they exciting or are they almost defunct? How are Steam and NVIDIA's streaming services doing from 2014? Hmmm.

How did the author determine that, "baggage of the Google brand" is the problem? Is there a problem? Who is asking, "if they can trust the service to stay running"?

upload_2019-5-10_23-4-27.png


upload_2019-5-10_23-6-15.png

popular-client-chart.png

There doesn't look like there is a problem.

Maybe a better question would be, if the author was a real reporter, "Why would 'Gamers', the target audience, want Stadia?". It sucks.
Maybe people don't like the idea of paying 2x or 3x the cost of a Console(or more) with permanent games to only lease a Stadia license... all at worse frame rates and latency. Maybe that? How about the fact that not everyone has Gigabit fiber service to their house... nor wants to pay the high rates for that service... further adding to the cost of "game streaming".


As for Inbox.. sorry, what a piece of garbage. Most of the time the emails I wanted to see were buried under a bunch of emails I didn't want to see. What's up with the Social Media look where I can only see 1 or 2 "emails" at a time? Then it always wanted to show me "old things" "on time" - like bills.. F that. When my bill comes in I want to see it and plan for it and pay it.. I don't want Inbox holding it back for 12 days only to notify me that a bill is coming due in 3 days. All of the useful features of Inbox have been in Gmail since 2017.

The author of the column keeps saying and inferring that "Google kills loved platforms and projects before their time and without warning"; says this for Inbox... but...

Speculation of Google killing Inbox came as early as 2017 and Google announced they would be killing Inbox due to lack of users in September of 2018 - plenty of warning:
https://www.androidheadlines.com/20...s-google-killed-inbox-over-lack-of-users.html
Approximately a quarter of its stateside user base launches Inbox at least once per day, with its number of daily active users averaging around 850,000 people over the last week and no significant changes in this regard being observed compared to August. While those metrics may imply remarkable user loyalty, Inbox has actually been losing momentum for some time now, with its user base shrinking by nearly two-thirds over the last twelve months alone.

Ouch. 850,000 per WEEK, out of hundreds of millions of users. That's only 121K per day.

I keep getting told that were all Capitalists, but when it comes to things like Google.. Eh, F capitalism... Google should do *this* and *that* 'cause I like it. Screw shareholders or performance numbers and evidence we have a failed product - make it anyway! Mmmkay! So, we're all voting for Bernie Sanders then, right? I kid I kid!

From the author under the 'How Did We Get Here?' section: "Google's strategy of having multiple teams" is a bad thing.. as if companies in general don't have "multiple teams". LOL! Isn't that basically the structure of a Corporation? A collection of individuals, divided into groups, working on common but often different goals? FIRE BAD! GOOGLE , BAD!
 
Here's a list of killed apps/services for the last 5 years that get's the author and the OP in a tiffy.
I'll be interested to see what other services others find "too unreliable". Pulled from the https://gcemetery.co/ site.

The way I see it, The BLUE and BLACK items are the only ones you could have a problem with:
goog.le
Save To Chrome (Extension)
Chrome Apps (Extension)
Google Spaces
Google Portfolios
Trendalyzer
Panoramio
Hangouts on air
Google Maps Engine
Google Catalogs
GDrive Hosting
Questions & Answers
Google Schemer


2019 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D

Fabric (Always Beta; R&D; Rolled into "Firebase")
Fusion Tables (Rolled into Docs)
Inbox by Gmail (Orig. designed as a invite-only 6-month R&D test to improve Gmail; Rolled into Gmail; all your email is still there)
Google+ (Failed platform; no use; cited a software error as partial reasoning)

goo.gl
Google Allo (Internal testbed for Android phone SMS App; R&D)
Mr. Jingles (A Warning message; notification widget for March 7th. But why did it end!?!?)
YT Annotations (rapid fall in use; users found it annoying; abused; incomp. with mobile)
Chromecast Audio (Hardware; Production stop - service is "Chromecast"; low sales)



2018 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D

Android Nearby (Failed; system for notifying user of nearby attractions; ads)
Tez (For India - Killed by India's Banking System) should not be in list
Google Goggles (circa 2010; obsolete - rolled into Google Lens and Google Photos)
Save to Chrome (Extension)
Encrypted Search (Replaced by HTTPS)
QPX Express API (Not enough adoption/demand)
Chrome Apps (circa 2010 Extension/Web App; Still to be in ChromeOS)
Google Site Search (circa 2008; Largely un-needed and unused; XSS flaws)
News and Weather (Renamed Google News)
Reply (pre-defined replies; Rolled into Gmail and Android OS)

GSA (16 Year old hardware)


2017 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D
|

Google Tango (Augmented Reality project R&D from 2014 - rolled into ARcore)
Google Spaces
Google Talk (IM; No use; Rolled into Hangouts - All contacts, settings remain across to Hangouts)
Google Portfolios (Circa 2006 Google Finance feature)
Hands Free (Small scale test of voice-only Mobile Payments for South Bay area)
Trendalyzer (circa 2007 data visualization)
Glass OS (Google Glass R&D OS)
Chromebook Pixel (2013 hardware replaced by Pixelbook)


2016 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D
|

Project Ara (2014 R&D modular smartphone)
Panoramio (Replaced by Google Maps Views)
Google Code (circa 2006 Open Source project hosting; still avail at Google Code Archive)
Picasa (circa 2002 software)

Hangouts on Air (replaced by YouTube Live)
Freebase (circa 2007 software replaced by Knowledge Graph API)
MyTracks (circa 2009 GPS tracking; App only; no service req'd.. can still be APK sideloaded)
Google Swiffy (Web based SWF flash to HTML5; obsoleted)

Google Showtimes (Movie showtime app; No use; rolled into Google search)
Pie.co (group chat; acquired and hired for engineering team) should not be in list
Google Now (Personal Assistant; replaced with "Cards")
Nexus Player (low sales; Chromecast replaces)
Google Compare (failed; Adwords competes; shops for CC/mortgage/insurance offers)
Google Maps Engine (2013-2016; map overlay API)
Songza (merged with Google Play Music)
Revolv (3rd party; Nest acquired) should not be in list
Google Nexus (Hardware; time obsoleted; replaced by Pixel)


2015 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D
|

Google Moderator (issue tracking framework; no use)
Helpouts by Google (No use; online help collab service)

Google Catalogs
Android @Home (Smart dev framework; IFTTT's origin; before standardization; R&D)
GDrive Hosting (Self web-hosting app)
Google Earth API (Free beta service only; R&D)
BebaPay (Killed by Government) should not be in list
Flu Trends (During a bad flu scare; specialized)
Timeful (3rd party acquisition; iOS to-do app; still avail) should not be in list
Google Play Edition (Hardware; Phone; time obsoleted)
Google Glass (Beta Only; R&D)


2014 - COLOR KEY: No prob. | Mmkay | Questionable | No Use | Obsolete | BAD ITEM | R&D
|

Orkut (Circa 2004 Social Network; no use)
Questions & Answers
Google WiFi (Municipal WIFI; replaced with new WIFI; For Corporate HQ area) should not be in list
Google Schemer (Rolled into Google+)
SlickLogin (3rd party company buyout; Israeli voice verification software) should not be in list
BufferBox (3rd party buyout) should not be in list
Bump! (3rd party buyout by Google; becomes Google Photos/Android Camera) should not be in list

Quickoffice (Now Google Docs)
Google TV (Renamed Android TV)
Youtube My Speed (Replaced by "Video Quality Report")

Chrome Frame (2000's frame handling for legacy browsers)
WildFire Interactive (Integrated into "DoubleClick" Ad Network)
Google Notifier (circa 2005 email notification tool;obsolete)
 
Last edited:
Well, too much to address, just two or three points.

If anyone loves Google then i am fine with that, but I don't.

Android vs Apple car stuff. I know little about it, but in itself it does not matter if Apple car stuff sucks because it is not the point IMO. If developers as the article suggests have a problem with Google then I don't see what Apple has got to do with that.

APIs staying more or less consistent over years has up and down sides. Example, I still can boot my 2014 laptop with a DOS boot disk and access the hard disk using extended int13h interrupts which the tool I wrote like 20> years ago needs. So from a software developer point of view that is awesome. At the same time it is true that partially because the desire of backward compatibility the legacy BIOS has limited other developments for years. But APIs that are solid and supported over a period of decades are what developers like I guess. There are Windows APIs that were there 20 years ago that still work. I wrote a file system defragger I think 12 years ago, still works today using the same defrag API built into Windows. Now that does build confidence for a developer.

And an API changing every so often or completely being dropped could be regarded as unreliable. If one manufacturer that offers those APIs does that repeatedly then yes at some point there will be little confidence if you again introduce something new.

Something that is not mentioned in the article is Google Search. Me as user but also as owner of a website find Google highly unreliable and unpredictable. From a user point of view, I often do not get what I am searching for. Not entirely Google's fault I guess as the amount of information grows and keeps growing. But still where I would give Google Search results an 8 out of 10 maybe 10 years ago, it would now be a 5 at best.

If Google decides we all need to go HTTPS or their browser will tell you have a bad bad website, even if you have a website that does not handle any customer data, passwords, does not require the user to fill out webforms and what not, then there is little you can do. And I am no expert of web security, or encryption but I do not feel the web has gotten safer. The same stupid people still fall for the same stupid tricks to get their data and passwords stolen.

As a website owner you can't ignore Google, at the same time I curse them 10 times a week on average. I have had issues in the past where Google erroneously flagged my domain as suspicious or whatever they called it. Supposedly easily identified using webmaster tools .. Not. The list of issues was empty. No pages that triggered it, no software I hosted, nada. No information whatsoever about what it was that triggered this. Support is non existent apart from forums manned by volunteers. An absolute nightmare which I entirely blame Google form and not the people who are friendly enough to help out in those forums. But they had nothing. They had no means of logging in somewhere to look into it. Or resolve it.

Again, there are pros and cons with Google Search being so dominant. The main pro is that you have only Google to deal with. The con is that you have only Google to deal with.

So, I can feel the guy's (who write the article) pain. If his analysis of how we got here is 100% right or not I don't care about. It however resonates with my experiences with Google and how I view them. IMO it is no longer people with an ideal to build the best search engine ever, it's going for the big money now and if that means sacrificing some core values then that's okay.
 
Last edited:
If anyone loves Google then i am fine with that, but I don't.
You don't have to love Google, but if you hate them, it still doesn't give you (the author) the right to make unsubstantiated sh*t up to further your personal hate-case.

Android vs Apple car stuff. I know little about it, but in itself it does not matter if Apple car stuff sucks because it is not the point IMO. If developers as the article suggests have a problem with Google then I don't see what Apple has got to do with that.

That's the problem. Context. There are basically two players in the car infotainment systems. Apple and Google. That makes Apple relevant when the author assigns "risk" to one but not others. Risk is inherent, it's a risk/benefit ratio that tells the actual story. The author says:
Watching Android Things chop off a major segment of its market nine months after launch would certainly make me nervous to develop anything based on Android Things. Imagine the risk Volvo is taking by integrating the new Android Auto OS into its upcoming Polestar 2
So, what *things* were developers developing for.. that was chopped off in 9 months? Nothing I can see, and nothing he lists. So that's a made-up supposition.

So Volvo has 3 choices, they can go Google, Apple, or some sh*tty Delphi OEM system.
OEM sucks. Need I say more?
Apple, until very recently had ZERO devs and the system IS/WAS closed off to Apple Inc. only. So for the author to infer that "switching to Google from Apple" is risky for developers... WHAT DEVELOPERS!? The non-existent developer? Then, when Apple just very recently opened up CarPlay to devs, they give them a huge phallic shaft when they find out that Apple still holds all the keys and features for their software, whereas devs barely get any API at all... negating the desire to develop for CarPlay. (Exactly what Apple wants)

Then, you have Google. Open Source, API fully developed and open. They are even going to let the car manufacturers tailor the system to their vehicles so that hardware (like windows, AC, etc) can be controlled from Android Auto. No such thing or even plans of any sort from Apple. That's the "risky" choice? On what planet? Even if Google killed the project, it's open source. so the manufacturers could carry on development and updates without Google.

Go look at Apple's CarPlay Developer page.. the API calls can fit on a business card(only 17 calls total). Only works for navigation apps and devs have no control over UI. Oh, and it will cost the devs $299 annually for the iOS SDK

Now, go over to Android Auto's developer page.. full support for everything and you can even write an App for AA right now... for nothing.

APIs staying more or less consistent over years has up and down sides. Example, I still can boot my 2014 laptop with a DOS boot disk and access the hard disk using extended int13h interrupts which the tool I wrote like 20> years ago needs. So from a software developer point of view that is awesome.
And this is where you and the author are confused. int13h is a hardware interrupt based on the x86 architecture.. not an API.
If you want to compare Oranges to Oranges... well, Android runs on ARM and those interrupts have been in place since 1979.. just one year after the 1978 x86 architecture release on the 8086. So, for all intents and purposes, ARM, hence Android, are just as supported now as they were in 1978.

But APIs that are solid and supported over a period of decades are what developers like I guess. There are Windows APIs that were there 20 years ago that still work.

There are more Windows API's that DO NOT work than there are that will, which brings me to my next point.. SOME Windows API's of the past work now only because specifically built compatibility, abstraction layers and memory pointer maps... all made specifically to make sure that old API calls were handled and passed to the newer API calls. Here's a list of API's that if a program were to use.. likely WOULD NOT work: Deprecated Shell APIs

So, where is that an issue for Google? Where does it say that Google can't build compatibility in for older API's? (They have!)

On another note... Android has basically guaranteed that no app can stop functioning by having APK's built on what amounts to Java and everything is run in containers with their resources/OS resources defined by the Hyperviser.. It's cross-platform.. Windows, OSX, Linux.. they all run your applications as if it were on the phone. Hmmmm. Sounds horrible for devs!? (sarcasm)

And an API changing every so often or completely being dropped could be regarded as unreliable. If one manufacturer that offers those APIs does that repeatedly then yes at some point there will be little confidence if you again introduce something new.
It could, but you OR the author has to show where that has been the case.. not simply say that it is a problem. According to the very article and the huge list of "defunct Google Services" I typed above.. not very much has been done away with that people are actually using or that were publicly available or that even had API's to program to.... it's a straw-man argument. Where were developers hurt in the past?

If "Google’s shutdowns cast a shadow over the entire company" and developers are on the fence, then I would not expect to see this:

upload_2019-5-13_18-1-24.png

So, how does the author expect to explain that away?

How is it that (from what I can find in data) from 2014-2018 more developers are entering Android development YoY while Apple is shedding developers?

upload_2019-5-13_18-5-40.png


So by that text below the last graph... Which one would you pick as a developer? So, now can we call the author "full of sh*t"?
 
Last edited:
"You don't have to love Google, but if you hate them, it still doesn't give you (the author) the right to make unsubstantiated sh*t up to further your personal hate-case."

Last time I checked, at least where I live, he has that right legally.

"new Android Auto OS into its upcoming Polestar 2
So, what *things* were developers developing for.. that was chopped off in 9 months? Nothing I can see, and nothing he lists. So that's a made-up supposition."


I think, but that's me, that imagine should be read as 'what if' in this context.

"APIs staying more or less consistent over years has up and down sides. Example, I still can boot my 2014 laptop with a DOS boot disk and access the hard disk using extended int13h interrupts which the tool I wrote like 20> years ago needs. So from a software developer point of view that is awesome.
And this is where you and the author are confused. int13h is a hardware interrupt based on the x86 architecture.. not an API."


Yeah I know that and I am not confused. Fits my working definition of an API close enough.

"So, where is that an issue for Google? Where does it say that Google can't build compatibility in for older API's? (They have!)"

I am sure they have.

"On another note... Android has basically guaranteed that no app can stop functioning by having APK's built on what amounts to Java and everything is run in containers with their resources/OS resources defined by the Hyperviser.. It's cross-platform.. Windows, OSX, Linux.. they all run your applications as if it were on the phone. Hmmmm. Sounds horrible for devs!? (sarcasm)"

I have no idea what you're talking about. Lack of knowledge on the subject on my part. I am sure you have a lot of valid points. I admit I am biased when it comes to Google so the article resonates with me, personal perception and experiences.

"So by that text below the last graph... Which one would you pick as a developer? So, now can we call the author "full of sh*t"?"

If you want to do that, be my guest. It's a numbers game based on having to chose between two evils maybe. As such numbers don't say a lot.

Speaking of numbers, it is also perception. Seem to be plenty of comments below article that tend to agree with the author. https://arstechnica.com/gadgets/201...-shutdowns-are-damaging-its-brand/?comments=1

So, it may be that it does reflect bad on the brand. So, you may be factually correct on a number of things, perception is doing the damage.
 
Last edited:
@Joep All valid points my friend.

I guess it all comes down to.. there are plenty of things to hate about Google that are valid criticisms. There is no need to "make stuff up".

It's kind of like US Politics.. talk about everything that doesn't matter, get the people up in a frenzy... then with the other hand, do whatever you like against the will of the people (or the law).

If you want to "fix google" or anything else, start by addressing real issues instead of non-existent ones. My opinion. :)
 
Great Scott! You mean focus on reality and actionable information and evidence? That's crazy talk!

As for Google, can you really trust a company that produced one of the world's most commonly used operating systems, but then failed to provide a patching mechanism for it powerful enough to actually patch the stuff in question...

And don't give me any BS about that being the carriers' fault, that's bunk. Google made the OS, Google is responsible for the OS, and we all have wifi for a reason. (Apple does this, and nailed it)
 
And don't give me any BS about that being the carriers' fault, that's bunk. Google made the OS, Google is responsible for the OS, and we all have wifi for a reason. (Apple does this, and nailed it)
No, it's Google's fault.. and the carriers. Google gave the carriers that concession in order to help further their brand and market it to carriers.

Excellent write-up at Ars:
Let’s not mince words: Google created Android’s update problem. The company's response to the threat of iOS was to cede a lot of control over the operating systems to carriers and phone makers in the name of amassing as much market share as possible. But times have changed—every competing first- and third-party smartphone operating system from anyone other than Apple is either stalled or dead, giving Google political leverage it didn’t have a few years ago. Plus, Project Treble makes it more technically feasible for Google to update Android directly without fear of bricking the underlying hardware.

So, yes, ultimately Google prob. shouldn't have done that when looking at the long-haul... that being said, Google updates the OS constantly and it is "released". It's the carriers that bumble-fart around and give BS excuses about their network. It's the carriers that have essentially 'locked' the phone.

There are technical and political reasons why Android updates don’t come directly from Google. On the technical side, carriers need to do their own validation and testing to prevent network problems, and OEMs need to make sure that their skins and other differentiating features work with new Android versions before releasing them. Politically, OEMs and carriers don’t want to become “dumb” conduits for Google’s software and services, since it reduces their ability to differentiate themselves from their competitors, and they don’t want to be subject to Google’s every whim or demand.

Updates are changing now.. and have been changing. Ever since stagefright..

Starting in late 2015, Google began releasing monthly security patches for Android that were different from normal OS updates. The patches didn’t increment the operating system version, and they made no changes to APIs or other underlying features. They were totally separate from the underlying Android version, and newer versions of Android even track the monthly patch level (e.g. “December 1, 2016”) separately from the OS version (e.g. “Android 7.1.1”).
The security updates were Google’s response to the “Stagefright” vulnerability, and the monthly patches aim to improve the state of Android security by making it easier to plug holes without requiring a major update. And as in Windows and macOS, Google releases these updates for several older Android versions (Google’s site currently says updates are supported on anything running the circa-2013 version 4.4 and newer).

Well, Google was in that written contract with the carriers, but now that contract expired and in 2018 Google has started to tighten up ship:
Google mandates two years of security updates for popular phones in new Android contract
Every month, a security team at Google releases a new set of patches for Android — and every month, carriers and manufacturers struggle to get them installed on actual phones. It’s a complex, long-standing problem, but confidential contracts obtained by The Verge show many manufacturers now have explicit obligations about keeping their phones updated written into their contract with Google.
The terms cover any device launched after January 31st, 2018 that’s been activated by more than 100,000 users. Starting July 31st, the patching requirements were applied to 75 percent of a manufacturer’s “security mandatory models.” Starting on January 31st, 2019, Google will require that all security mandatory devices receive these updates.
Manufacturers have to patch flaws identified by Google within a specific timeframe. By the end of each month, covered devices must be protected against all vulnerabilities identified more than 90 days ago. That means that, even without an annual update minimum, this rolling window mandates that devices are regularly patched. Additionally, devices must launch with this same level of bug fix coverage. If manufacturers fail to keep their devices updated, Google says it could withhold approval of future phones, which could prevent them from being released.


You can argue if that's enough or not.. and I would be more for a "full control" - no carriers, handset makers in the way.
But you can't deny things are changing rapidly from the 30+ year culture of the cell-phone carrier.

I agree with you that Apple did it "right", but they had to negotiate a less-than desirable deal that neither Apple, nor the carrier wanted. The "cabal" of telecom companies denied the concessions Apple wanted. AT&T, Verizon, Sprint, etc.

Cingular wireless was a company about to go out-of business, so they took a final battle-cry by Cingular chief executive Stan Sigman signing a SECRET multi-year exclusive deal with Apple in 2005 before they even saw concept drawings or a prototype. This was a company in dire straights.. Cingular failed before the iPhone hit shelves and was acquired by AT&T.

When AT&T purchased Cingular, they inherited the legally-binding, secret, Apple deal.

So, on the Apple side, while in hind-sight it looks like a brilliant move, etc.. it's more likely that the chips fell in the right spots; chance. The 2 years that AT&T was required to carry the iPhone exclusively proved to be a sound partnership.. but if it were not for the contract signed by a dying company and Apple that had been turned away from AT&T (and almost everyone else), what would have happened? What if Cingular simply failed without a buyer? The contract would have failed. If AT&T knew about the secret exclusive deal prior, would they have still purchased Cingular knowing they would be agreeing to a deal they previously denied?

All good questions, but in the past.

I suppose my final point would be that companies have to act accordingly to the market and market conditions. When Apple released the iPhone, there was no competition in that space and the carriers are stiffs.. so Apple just has to sign ANY crap contract they can get.

Fast-forward a few years when Google releases Android and the market conditions are much different and Google has much less leverage with providers and their contracts... and while they could go the way of Apple... the goal is to compete.. and they weren't going to do that with a secret 'Apple Deal' because of the carrier cabal. So they bent to carriers and it is what it is.

It doesn't make it right, but there is more to the story than "Google". In fact, you can say it sucks and I'll be right there with you.
 
Back
Top