Will a Freely Distributed OS for Smartwatches Succeed?

It seems that crowdfunded smartwatches have grown to be popular again, with Vachen and AGENT Smartwatch starting their Kickstarter campaigns and accompanied by Boddie and Emopulse closely behind. With all the choices in smartwatches today, we the buyer, are spoiled for choice. You’ve got a large variety of features, os’s and watch designs. Just how do we select the one we want? Perhaps one of these has features you think are actually important to you nevertheless, you hate the look or vice versa. Will there be a way to have our cake and eat it?

Perhaps we can learn a bit from what watchmakers have been doing for years. Companies like Tag Heuer, Seiko, Swatch and many others produce a good selection of wristwatch models year after year. On the surface, they will have absolutely nothing in common, some have a stainless casing, other are covered in Swarovski crystals, some show the date, others barely have any numbers in it. Looking past the surface reveals similar or even identical clock movements that power these watches. As these movements are constitute a complex and intricate network of springs, counterweights and gears, one can understand that watchmakers would like to use a design for as long as possible. It would you need to too long to design a fresh movement for every new design of a wrist watch.

Hence, using modules in watch design is important to getting models off the designing table to the manufacturing floor as quickly as possible. The fewer movements needed to cater to a large range of watches the better it really is for the watchmakers.

In a way, this is what Google has done with Android along with. Google has created a usable and flexible operating system that smart phone makers may take, tweak and ship with their hardware. By creating a base OS which might be dispatched to handsets that hold vastly different hardware, Google has had the opportunity to make sure that Android-powered handsets now outnumber the wildly popular Apple iPhone. Now, you can obtain an Android smart phone in a number of models with different technical specifications and prices you could pick and choose which hardware suits you best, knowing that the software experience will undoubtedly be mainly similar.

For smartwatches, it has not been the case. For each and every smartwatch out there, you will find a proprietary operating system that powers it. Therefore the user experience is vastly different for each smartwatch model. It also means that the makers of the smartwatches need to split their efforts and resources into two parts, watch design and OS development. While app development can often be “outsourced” to third party developers, the program development kit (SDK) should be created and this takes time and resources as well.

The various smartwatch makers have taken different approaches to handle this. To begin with, barnklocka gps has put plenty of effort into the creation of its SDK and contains garnered a decent developer community so far and also have also partnered popular big-name app developers like the RunKeeper. However, Pebble doesn’t look all that classy, it could are a sports watch or could be worn with casual wear, nonetheless it doesn’t really have the look to match office wear. Imagine if more was done on the look side of things? Would the program side took a productivity hit? Imagine if they used a pre-made smartwatch OS?

The Agent smartwatch alternatively is trying to juggle either well as well. Secret Labs, the creator of the Agent knows electronics and software very well, but are no experts in watch design. So that they partnered with House of Horology, which creates really nice timepieces. Together, they hope to have the ability to tackle the electronics and the look areas of the smartwatch together. That is definitely commendable and an excellent strategy, but would this mean delays in the production cycle since it takes time to tweak the operating-system and functionality. Secret Labs did however use the Microsoft.NET Micro Framework as a base for its operating system. Is this the start to utilizing a distributed OS for smartwatches?

What we need is one of the established software companies to spearhead this. A little time player may not cut it because not many will utilize an OS that might not be around if the business goes under. The OS ought to be produced by Google, Apple or Microsoft, so as to give weight to the program. It will also provide trust to developers that the OS will undoubtedly be supported for years to come. These companies will be able to utilize their expertise in software development to generate an OS that’ll be in a position to perform under different hardware conditions, maximize battery life while providing usability and functionality, all at exactly the same time looking great on the watch face.

Leave a Reply