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.

Thread beginning with comment 612515
To read all comments associated with this story, please click here.
Comment by hobgoblin
by hobgoblin on Sat 13th Jun 2015 23:07 UTC
Member since:

Google is perhaps the posterboy of "devops", a constant churn of developer "shiny" over actual products.

It is a term originating in web development, supposed to symbolize a closer collaboration between ops (or sysadmins if you like) and developers.

But for my point of view at least it seems closer to devs gets a big club to hit ops with until they ok the use of some shiny new framework or language on production servers.

And on web you never "release" you just iterate. You write some code, push in front of people, and if something breaks you write and push more code. You don't do stable, maintenance, or anything like that.

And the web attitude is spreading to other parts of the IT world.

Reply Score: 2