This article appears to be incorrect in stating that, "Android is unusual in that it is defined as a device, not a host". As I commented earlier, that would be ridiculous!
In fact, it is only the "Accessory" mode in which Android is the Device - there is also a Host mode:
@Selinz: NO! It means exactly that you can *not* hook up *any* of your current USB "accessories" to *any* Android device!
This means that you are going to have to get a whole new set of accessories - just for use with your Android device(s)!
It's hard enough getting technical people to realise this - how on earth are Google going to explain it to consumers?!
It will also vastly increase the design complexity of the devices - as they will have to provide a USB *Host* stack.
Sounds like utter madness to me!
Should be good business for the likes of http://www.vinculum.com though...!
Android device being a USB device makes sense to me since it shall not allow being drawn power. Yet, how does it work with regular USB device such as keyboard and mouse?
Personally, I am more interested in the 915MHz Open source wireless mesh protocol. What would be the benefit over Zigbee and Z-wave? Cost apparently? What else?
Why didn't they just use USB OTG in Android? Connectivity of mobile devices to peripherals is exactly what OTG was developed for. It makes no sense that an Android tablet or smartphone must be a USB device, which means the peripheral must be the USB host.
That part of the USB device and host relation is tricky. I mean, usually we identify the host as the bigger device and the accesories as the smaller ones. If an accessory is connected to the Android phone, it will be a little odd to remember that it's the accessory the one playing the host and not the phone.
Anyway, it sounds very interesting.
That part of "no NDA and no fees" sounds intimidating for the market. There must be somekind of control out there. Otherwise... what will become of Android? a world of no warranties?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.