News for hackers. Stuff that matters.
Re:An Update on Android Things by wiremine on Tuesday February 12, 2019 @06:50PM (#19148928)
I'm a VP for a software consultancy focused on IoT: I'm not surprised it wasn't a success. I give them props for trying to leverage Android for IoT, but in the end I think it was a poor fit:

1. Most IoT devices are still based on smaller MCUs, not Linux. FreeRTOS and systems like it are where the majority of vendors go.

2. The smaller (but still sizable) market for embedded linux don't naturally gravitate to Java.

3. It was a subpar developer experience, IMHO. For example, see this link for a "Blinky" app, which is a sort of like the "hello world" for embedded:

https://medium.com/@monkeytypewritr/android-things-getting-t...

To put that in context, here's a blinky app in mbed, which is C++ based:

https://github.com/ARMmbed/mbed-os-example-blinky/blob/maste...

To be far: It's apples and oranges comparison (Mbed is for bare metal), but it gives you a taste for the amount of boilerplate Android Things required.

Now, if one of the major vendors invested in Rust? That would be interesting...

Re:An Update on Android Things by bschwindHN on Tuesday February 12, 2019 @10:31PM (#19150124)
Oh god, I hadn't heard of Android Things before this article, and I do some hobbyist IoT work. Writing that sort of hardware stuff in Java with the Android SDK looks downright depressing. I'm not surprised either.

I've enjoyed using Espressif's esp-idf project, though I wish Rust could target Xtensa processors. mbed looks nice as well!

Re:An Update on Android Things by jschwartzi on Wednesday February 13, 2019 @03:07AM (#19151323)
Hilariously if you want to actually use Android Things on anything besides their supported hardware you'd still have to write all the low-level code to make it work, plus the Java code to make it work in Android.

I hadn't heard of it before either and I'm pretty sure I work in their target market, but that's because they're doubling or tripling the amount of work I have to do to get something working relative to Embedded Linux.

Re:An Update on Android Things by TeMPOraL on Wednesday February 13, 2019 @02:39AM (#19151187)
Could be worse. Think embedded/IoT with node.js.
Re:An Update on Android Things by pjmlp on Wednesday February 13, 2019 @12:45AM (#19150755)
There are a couple of embedded domains using Java, mostly from MicroEJ, PTC, Aicas, IBM.

The big difference is that they are actually tailored for embedded development, with standard Java, real time support and not phone APIs trying to fit somewhere.

Additionally the NDK experience is relatively bad, forcing devs to download and manually compile NDK libraries, that are part of the SDK for Java, e.g. userspace drivers.

Finally, using something like yoctos + whatever language is still more flexible.

I never really understood the pivot from Brillo into Android Things.

Re:An Update on Android Things by on_and_off on Tuesday February 12, 2019 @11:07PM (#19150306)
To be even fairer : it seems that the goal was to allow the sizeable Android dev community to reuse some of the APIs they already know in the context of Android Things.

I am not saying that it makes a lot of sense .. I am an Android Engineer myself and the amount of boilerplate for that blinky sample makes me vomit but that's how it is.

Re:An Update on Android Things by PaulHoule on Tuesday February 12, 2019 @07:00PM (#19148999)
I think many people aren't aware of the comm ecosystems such as ZigBee which let you build very low cost devices that don't need to have Linux, an internet stack, CPU with MMU, etc.

They might call it "the internet of things" but often other protocols are involved.