You come back, one year!
The wearables market isn’t an easy one; and its one that for many, still remains untamed. I spent a great deal of time last year covering the wearables market.
- Microsoft Band Part 1
- Microsoft Band Part 2
- Fitbit Surge
- Pebble Time
- Olio Model One
- Apple Watch:
The first device I reviewed in this year long series was the Microsoft Band. In the end, at least before the Apple Watch was released, I considered it to be the go to device that I would have recommended to everyone, largely because (it had)
- An inexpensive point of entry
- A cross platform set of apps
- An easy to use UI and smartphone app
When, a year later, Microsoft released Band 2, I felt vindicated – at least for my initial recommendation – because a second release of Band meant that Microsoft intended to stay in the market, at least for a while.
Yeah… about that…
Microsoft announced earlier this week that it is pulling Band 2 from all of its Stores and won’t be releasing a Band 3 this year.
Later, Microsoft also removed Band’s SDK from their site, which makes sense, since they’re no longer selling the device. They also appear to have disbanded the software team that was tasked with bringing Band in to Windows 10 as a native device and the hardware team responsible for design and engineering of Band hardware.
The one thing that Microsoft is NOT doing, however is dropping Microsoft Health. Microsoft still intends to provide that software and service to users of other fitness bands.
However, Apple Watch users, or those MS Health users looking to switch to Apple Watch, shouldn’t get their hopes up. It’s very unlikely that Apple will provide an API that would permit 3rd party support of Apple Watch with Microsoft Health or any other health monitoring application.
So you can put Microsoft Band into the heap of dead and dying tech revealed recently, including, of course, Blackberry manufactured hardware.