Google Kills Android Things

Posted on December 18, 2020 by Paul Thurrott in Google, Smart Home with 7 Comments

Google Jumps Into IoT with Android Things

Google this week announced that it was killing its IoT platform, Android Things, less than two years after limiting its use to smart speakers and displays.

“We are turning down the Android Things Console for non-commercial use,” the Android Developer blog reveals. “Developers can continue to use the Android Things console to build images and serve OTA updates for their existing projects until January 5, 2022. At this point, the console will be turned down completely and all project data will be permanently deleted—including build configurations and factory images.”

Google released the first preview of Android Things in December 2016, positioning it as a mainstream IoT solution for developers who are familiar with Android. And it partnered with hardware makers to support the platform on Intel Edison, NXP Pico, and Raspberry Pi 3 computing boards. Then the 1.0 release arrived in May 2018, offering broader hardware support that included so-called “system on a module” (SoM) chipsets similar to Microsoft’s Azure Sphere.

But less than a year later, it was obvious that Android Things was a failure. Google revealed that it would limit the use of Android Things to smart speakers and smart displays only and it killed support for SoMs based on NXP, Qualcomm, and MediaTek designs.

It’s possible that Android Things’ greatest strength—being based on Android—was at least partially responsible for its downfall: Google only supported the system for three years, which is problematic enough for smartphones but a real Achilles’ Heel on embedded IoT solutions that customers would naturally expect to use for much longer than that.

Google is working to improve the Android support lifecycle for smartphones, but with this week’s announcement, it’s clear that it won’t or can’t do so for Android Things, even given its limited use cases. And so this era is coming to a close.

Google offers a few other solutions for the IoT space, but as Microsoft found previously with Windows, simply building new platforms based on your most successful platform doesn’t always guarantee success. And none of Google’s other IoT offerings are client hardware platforms, but instead ways to integrate with its cloud, Assistant, and Nest platforms. (A company called Coral does offer an AI solution for edge computing that’s based on a Google chipset, however.)

Tagged with , ,

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (7)

7 responses to “Google Kills Android Things”

  1. Avatar

    behindmyscreen

    Oh google.....You keep doing you buddy

  2. Avatar

    jimchamplin

    What do they have to do to improve Android lifecycles other than choose to support it longer?

  3. Avatar

    murray judy

    I think the title could be shortened to "Google Kills Things".

  4. Avatar

    stevek

    Now just waiting for the Google Kills Stadia article.

  5. Avatar

    jgt2105

    It's a lazy trope, as well as sounding just a bit tough on the ear, to wheel out the phrase 'google is killing.... '. Is there a particular journalistic requirement to user the 'killing'' word? I get it that Google are funking forever dropping or abandoning services and products, but please consider dropping the k word for this poor snowflake.

  6. Avatar

    jfgordon

    Given that, in over two decades, Google had real success with its "classic" web products only (search and ads, mail and drive, maps, and YouTube) it is still incredible to me that Windows Phone lost to Android.

  7. Avatar

    Michael Bodo

    Has it occurred to anyone that perhaps Google is abandoning this in favor of Fuchsia OS, which is pegged to be their OS of the future that runs the smart home? Why continue spending good money on something that no longer is in your long-term plans? Makes no sense. This is smart move on their part.

Leave a Reply