Apple Blog

Watch OS 1.0.1 or the return of updates with unforgivable bugs

Last Tuesday, Apple released the first update of the Apple Watch: Watch OS 1.0.1. A software that aimed to improve the overall performance of the company’s first wearable . Having installed it from the first moment it was available, I can say that it fulfills what it promised.

The fluidity and speed have been significantly improved in the Apple Watch interface. Something of great importance in a device designed for fleeting interactions of just a handful of seconds. But this good news has become bitter over the days.

A heart sensor with too many gaps

Watch OS 1.0.1 or the return of updates with unforgivable bugs
Watch OS 1.0.1 or the return of updates with unforgivable bugs

Apple has approached its new watch as a very powerful tool for sports and physical activity quantification. While other products such as Fitbit are more focused on an audience with more specific sports needs, the Apple Watch aims to become the first mainstream quantifier .

A very ambitious goal for which this update does not help at all. Some users have begun to report gaps in the cardiac data collected by the Apple Watch. Apparently, this update is causing the Apple Watch to not record heartbeats every 10 minutes when we are not exercising.

Regularity has gone from every 10 minutes to several hours in some cases

In some users, much more time passes and there are cases of up to 9 hours between data and data. In my case you can see how there are gaps of up to one hour , when before the update I was almost 10 minutes old. However, when I activate the physical activity training app, the data is constantly and smoothly recorded.

Personally, I’m not so interested in this metric, but the anger of people who bought the Apple Watch because of its sports and heart measurement capabilities is more than understandable. There is a thread on the Apple forums that collects user issues in detail.

What if it affects the battery?

The Apple Watch always exceeded the day’s run time by far before the upgrade

Since the first day of using the Apple Watch, I have never had to worry about its battery. No matter how many hours I wore it or whether I had been using the training app. The Apple Watch has reached its charger at night after a busy day with 44% battery power more than once . There have even been days that I have slept with the Watch on, with its charge reaching around 20% by noon the next day.

My confidence in the drums was complete. Many users’ doubts about its autonomy were exaggerated. At least, until the day I updated the Apple Watch to version 1.0.1. Since then, I have had a couple of days with a drastic reduction of the battery . Just yesterday was the first day when I was told that I wanted to go into power saving mode (i.e. I had reached 10% of its charge).

9 días con el Apple Watch, lo brillante, lo bueno y lo malo.

Imágenes
My use of the Watch hasn’t changed these days. Which leads me to suspect whether the upgrade had anything to do with it. I haven’t found any discussion on the Apple forums about the issue and it may be rash to blame the new version of the operating system. However, one can’t help but wonder if this might happen in the future.

With integration on such interesting platforms as mobile payment, health, home automation and who knows what else will come in the future, the consequences of an upgrade with battery problems are compounded. It is no longer a question of not being able to talk on the phone, but of not being able to pay in the supermarket or enter your home. If Apple really wants us to forget about our keys or wallet forever, the doubts must disappear forever .

Update: during yesterday’s Apple Watch battery return to normal. Even reaching an amazing 65% before going to sleep and after wearing it all day (more than 16 hours with it). Anyway, I will follow its evolution with a magnifying glass.

New era of updates, with the usual errors

iOS users still have the bump in the road from iOS 8.0.1. The one that disabled Touch ID and cellular connectivity on the new iPhone 6 and 6 Plus. It took Apple just one hour to remove it and another 24 hours to release iOS 8.0.2 fixing the bug, but the damage was already done .

It takes a long time to gain the trust of users, but a sigh to lose it. On a device as personal as the Apple Watch, this trust is extremely fragile. Users’ tolerance for updates that tarnish the experience is going to be far less than what we’ve seen so far.

Apple had a clean slate with the Apple Watch. And it seems that is an opportunity he has missed . There are many reasons for these mistakes: it is a totally new device, Apple had never marketed a product in this way and we can even blame the new technologies it incorporates. But they would sound like an excuse.

Although I am happy with Yosemite (no problems since I installed the system from scratch last year) and iOS 8 after its recent polish, many users want to confirm the rumors and iOS 9 and OS X 10.11 to step on the brakes and focus on improving its stability . Hopefully Watch OS will also enter into those same plans.

At Apple

Similar Posts