Linked by Thom Holwerda on Fri 12th Jun 2015 10:37 UTC

When Android Wear came out over the course of last year, Google promised that the young, new platform would receive updates "early and often". While it wasn't said with so many words, it's easy to read between the lines: Google was going to make sure Android Wear users wouldn't face the same headaches as Android users when it comes to updates. Wear would be a more tightly controlled platform, built in such a way that updates could go straight to users' devices without meddling from carriers or roadblocks thrown up by crappy customisations.

Fast forward to June 2015, and Google has recently released Android Wear 5.1.1, which, despite its humble version number increase over 5.0.1, is a pretty significant update to the smartwatch platform. It enables WiFi on devices that support it, adds new ways to interact with your watch, and makes it easier to launch applications. All in all, it looks like a great update.

Sadly, I can only go by what others have told me, despite owning the poster Android Wear device - the Moto 360.

Permalink for comment 612487
To read all comments associated with this story, please click here.
RE: Comment by sb56637
by moondevil on Fri 12th Jun 2015 17:15 UTC in reply to "Comment by sb56637"
Member since:

That is one reason why my hobby development on Android is done in C++.

My hobby development is mostly geared towards gaming, so although constrained, I can survive with the NDK.

Additionally, by using external C++ libraries I can enjoy the same APIs, regardless of the Android version and also port the code to iOS and WP devices.

There is a price to pay though, as each APK tends to be much bigger than a Java only approach, plus one needs to either replicate UI Widgets or use JNI.

Reply Parent Score: 3