Not sure what you're trying to say here - Android Things was always targeted at relatively powerful devices. Things where people right now use stripped down tablets or massacre AOSP Android to make it do things like power a touchscreen kiosk device. It was never really capable of working on a smart scale or CCTV camera type thing - it was always a best fit for a phone-like hardware powering a display.
And it is a decently nice platform to work with for those use-cases - certanly better than most of the others. It has almost all Android APIs available.
Android Things was, but its predecessor Brillo was targeted at less powerful devices (though not down to microcontroller level).
an android things kit costs the same as a pocophone, what demand was it seeking to fulfil that wasn't easily fixed by an app on a low cost smartphone?
I assume Brillo was a victim of internal politics, where did not play as intended.
Re:An Update on Android Things
by dpacmittal on Wednesday February 13, 2019 @12:09AM
(#19150604)
Even sim cards and credit cards run JVM, so I don't think Java is a major concern here.
No, then again why go with Android J++, when you can go with a better embedded Linux distribution and using proper Java?
Assuming that one is going with Java.
For other languages there are better alternatives anyway.
I suppose the fundamental issue is that embedded systems are massively cost constrained, so they're always going to use custom hardware, and that hardware is going to vary a lot. Smart scales can get away with an M3 microcontroller, whereas a smart CCTV camera is going to need a proper SoC with lots of RAM, some kind of DSP etc. Good luck making an OS that works on both of those.