Can Google's new Android Wear OS really signal the start of the "wearable" revolution?

The idea with Android Wear is to create a platform that not only grows as developers create more content for it, but also to give some uniformity to burgeoning wearables market, which, in its current form, is still fairly embryonic –– most consumers, like 70-80%, are still very much on the fence about whether or not wearable tech is actually a worthwhile investment. And it’ll take a coherent, strong platform backed up by excellent, engaging hardware to convince the multitude that wearable tech like the Moto 360 and its brethren are here to stay.

Google isn’t going to take Apple’s entry into the wearable space laying down. A source close to the company recently informed The Verge a big update to Google’s Android Wear platform is on the way –– and it’ll bring a bunch of new features into play. Chief among these apparent updates is Wi-Fi support, handy for when Bluetooth is being a sod, and gesture-based controls that will allow users to flick through notifications and Google Now cards simply by flicking their wrist. Google has also given the UX a much needed overhaul. The report claims applications will now be easier to access on the wrist. All of which sounds very good; Android Wear needs to be a hell of a lot more intuitive.

Google has now released API 23 SDK for Android Wear, meaning developers can begin fully optimising their applications for Android Marshmallow. Once they’ve been brought up to date, Android Wear applications will be able to tap into a bunch of new Android Marshmallow features such as vastly improved granular permissions, whereby users have more control over what their applications can and can’t access. For instance, a fitness application will now HAVE to ask for permission to use your location.

API 23 SDK also brings support for both round and not-round displays. The update means Android Wear will be able to tell whether it is being run on a smartwatch with a round face or, well, a not round face. Developers will also be able to use this tool to determine what resolution to have their apps set at. All in all, very useful tools for creators.

“We listened to your feedback and added new resource qualifiers for -round and -notround, so you can use the resource system to load the appropriate images, layouts, and strings based on the type of watch you are working with,” said Google in a statement. “You can also combine this with existing resource qualifiers -hdpi, -tvdpi, -280dpi, and -360dpi for the various Android Wear watches that are currently available.”

Developers can also use the same APIs used for Android phones to play audio files on the watch, though your smartwatch will need to support audio in the first place.