It's unfortunate that such detailed instructions are needed to understand and use some of the functionality of the Apple Watch. Apple used to pride itself on making UI's that were so simple and intuitive that no operating instructions were needed.
While undoubtably the best Smart Watch around, there are aspects of the UI that are more convoluted and complex than they perhaps ought to be.
But to paraphrase Steve, making things really simple is actually really hard.
Do you have an Apple Watch? I do–for just a few days now. And my experience so far is that it is about as simple as it can be without being needlessly handicapped. If it was simpler, it would likely have to be neutered in ways that would make it frivolous/pointless. I've always had a problem with the word "simple" anyway.
Words are important, and "simple" is just one of those words that is misused and misinterpreted. Making things "simple" is too often an axiom that designers hide behind, a cool catchphrase that helps create an air of exclusivity, a badge of honor that separates those who are "in the know" from everyone else. When pure "simplicity" is the highest value, it can sometimes serve when it comes to the aesthetic aspects of design. But championing simplicity over everything else is too often a form of castration when it comes to designing functionality or UIs.
Making a DEVICE, OBJECT or INTERFACE simple looking for simple's sake is selfish and object/designer centric. Designers fall all over themselves about "beautifully simple devices" that are often completely useless in everyday use. Making a device simple to USE is a more user-focused approach, and in my mind a more helpful way to practice functional design. But two values that are even better than "simplicity", especially when it comes to designing functionality and UI, are "ease" and "efficiency". If there is an action I'm going to do dozens of times a day, is it worth having to do a little upfront learning once so that that action becomes as easy and efficient for me as possible? Sometimes the answer is yes (as much as that hurts the ears of the "I never use a manual" crowd). Apple often errs on the side of obviousness and object simplicity, but there are times when it actually creates more steps, and more effort by the user on an ongoing basis. Making an object or interface "simple looking" is nice. Making is "simple/disoverable" is even better. But the best kind of functional design balances "simple/discoverable" with "easy" and "efficient" on an ongoing/daily basis.
I think the Apple Watch is as simple as this kind of device can be. And happily, for the first time, Apple seems to have conceded a very small amount of upfront learning in order to create greater ongoing ease of use and functional efficiency. Which I consider institutional progress.
