Google I/O 2014: Android Meets the Internet of Things with Android Wear, Android Auto, and Google Fit

DZone 's Guide to

Google I/O 2014: Android Meets the Internet of Things with Android Wear, Android Auto, and Google Fit

· IoT Zone ·
Free Resource

There was lots of exciting material to be covered during the Google I/O 2014 keynote from San Francisco, and DZone was busy during the almost three hours presentation live-tweeting the whole presentation. There was a lot of exciting news about the next version of Android, including Android 5.0's new runtime and user experience. Similarly exciting news came from the Google Cloud segment of the presentation, which revealed an incredible new Big Data pipeline service called Google Cloud Dataflow.

But for me, the news I was waiting for centered about Google finally showing off a bit more about Android Wear, and potentially releasing an opponent for Apple's Homekit in the home automation realm. The actual result was a bit surprising: instead, we got the full release of Android Wear SDKs, including the live launch of two new Samsung and LG smartwatches, the long-awaited health and exercise monitoring tool Google Fit, and a previously unheard of Android Auto.

Android Wear and some new hardware

We've known about Android Wear for a while now, and Google has already shown off some rendering of what the software will look like on the gorgeous new Moto 360 smartwatch. However, we've been waiting a while for the Android Wear SDK--but we knew it was coming, and it stole the show at I/O. Sundar Pichai announced at the SXSW event that the SDK would be showing up (most likely) at Google I/O.

"In about two weeks, you will see us launch the first SDK for what we think of as Android for wearables. When we think of wearables, we think of it as a platform. We see a world of sensors... Sensors can be small and powerful, and gather a lot of information that can be useful for users. We want to build the right APIs for this world of sensors."

Demonstrated on stage were some of the neat tricks that Android Wear has in store for smartphone users, including a security feature that recognizes users based on paired smartwatches that bypass their phone PINs. Also, the "material design" focus of Android L (5.0) has been carried through to Android Wear--the result is a pretty slick interface, simple user experience, and a set of full APIs made available to developers.

Also, the gadget-gifting of the conference happened this time with a choice of the two new smartwatches released mid-conference, the LG G watch and the Samsung Gear Live. Attendees now only could pick a watch at the keynote, but they also are all going to receive a Moto 360--by far one of the most anticipated smartwatches out there--when it releases in a couple months. Talk about developer perks.

(Picture from Mashable)

Google Fit's health monitoring and Android Auto's screen casting

Still very important new additions came towards the middle-to-end of the keynote, including the previously teased Google Fit, an answer to Apple's Healthkit announcement which is now a few weeks old. The health monitoring suite works with Android wear and mobile devices to collect healthcare and environmental data normally acquired through fitness bands and other wearables. Considering it's a single set of APIs, and it allows users to combine services with other apps, it's going to be a strong contender in the health data monitoring environment of Google's new smartwatches.


And not to be forgotten--on the contrary, it's actually a pretty big reveal. Android Auto was on the scene, and it's basically what you would expect--Google Now for your car's computer screen. And there's nothing wrong with that. Actually, it's pretty sweet. It's a simplified version of Android 5.0, and it's going to be available "soon" as an SDK. Google announced over 40 new partners joining their Open Automobile Alliance, which would give Google even more traction in the automobile industry--something that could play favorably with Google's existing interest in cars (as illustrated... well, everywhere).


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}