Hi All,
I've been an owner of the Apple Watch since Day 1. I have to say that even given it's limitations, I am really enjoying it. I have been a die hard mechanical watch fanatic since I was a teenager, yet the Apple Watch has won "wrist time" 98% of the time. I keep reading all of these posts/articles about how the watch is a gigantic failure that no one wants, however, I don't think they realize that Apple is essentially beta testing the watch...AND getting their users to pay for it!
When it comes to agile development, the best case scenario is that users pay for your product while you are testing, measuring, and learning. This is the case with the watch, as Apple is clearly making a solid profit from the watches they have sold. While it's not enough to cause a significant uptick in their bottom line, that's not what they are worried about at this point.
At the moment, the Apple Watch is a very "basic" device. Based on my experience, as well as family/friends who I have talked to, most really only use a handful of features. I would say that the watch face (compilations), notifications, and the activity app are by far the most popular. Everyone I talk to hates the app screen. These are the types of findings that Apple is learning, and will likely take action on them so they can refine the software for the mainstream market.
I think native apps and new compilations are a huge step in the right direction. These will prevent us from waiting forever to get the information we "expect" quickly, as well as easier entry points into the apps (we c an now tap compilations to jump into an app). Personally, I think it would be a wise idea to have multiple "pages" of watch faces with different compilations, as this will provide quick access to bits of information and provide much easier access into apps...but that is besides the point.
What it all comes down to is that Apple is mostly interested in refining the basics. What if this version of the Apple Watch came with super advanced health sensors? I would venture to say that if this version was released with revolutionary sensors, the current software wouldn't hold up. If they can optimize the current software (less buggy, more reliable, improve UX/flows), the basics of the software will be the least of their concerns when they release a killer hardware feature.
People are thinking way too short term for this product. We've seen all the hires Apple has made for health sensors...new hardware is going to come eventually. When that does happen, the basics will "just work" and every day people will be able to seamlessly enjoy a watch that does 50 different things vs. a traditional watch that only does a fraction of that.
I predict the second and fourth generation Apple Watches are what will really get things moving in the wearable sector.
Interested to hear your thoughts.
I've been an owner of the Apple Watch since Day 1. I have to say that even given it's limitations, I am really enjoying it. I have been a die hard mechanical watch fanatic since I was a teenager, yet the Apple Watch has won "wrist time" 98% of the time. I keep reading all of these posts/articles about how the watch is a gigantic failure that no one wants, however, I don't think they realize that Apple is essentially beta testing the watch...AND getting their users to pay for it!
When it comes to agile development, the best case scenario is that users pay for your product while you are testing, measuring, and learning. This is the case with the watch, as Apple is clearly making a solid profit from the watches they have sold. While it's not enough to cause a significant uptick in their bottom line, that's not what they are worried about at this point.
At the moment, the Apple Watch is a very "basic" device. Based on my experience, as well as family/friends who I have talked to, most really only use a handful of features. I would say that the watch face (compilations), notifications, and the activity app are by far the most popular. Everyone I talk to hates the app screen. These are the types of findings that Apple is learning, and will likely take action on them so they can refine the software for the mainstream market.
I think native apps and new compilations are a huge step in the right direction. These will prevent us from waiting forever to get the information we "expect" quickly, as well as easier entry points into the apps (we c an now tap compilations to jump into an app). Personally, I think it would be a wise idea to have multiple "pages" of watch faces with different compilations, as this will provide quick access to bits of information and provide much easier access into apps...but that is besides the point.
What it all comes down to is that Apple is mostly interested in refining the basics. What if this version of the Apple Watch came with super advanced health sensors? I would venture to say that if this version was released with revolutionary sensors, the current software wouldn't hold up. If they can optimize the current software (less buggy, more reliable, improve UX/flows), the basics of the software will be the least of their concerns when they release a killer hardware feature.
People are thinking way too short term for this product. We've seen all the hires Apple has made for health sensors...new hardware is going to come eventually. When that does happen, the basics will "just work" and every day people will be able to seamlessly enjoy a watch that does 50 different things vs. a traditional watch that only does a fraction of that.
I predict the second and fourth generation Apple Watches are what will really get things moving in the wearable sector.
Interested to hear your thoughts.
