The Apple Watch

They took the "Microsoft" route.

They refused to make hard decisions about what was right for users and use of this unique platform and it's all pointed in a bad direction for that lack of focus, attention to detail and execution.

Smart Watches -- particularly those that require a smart phone -- have about 2 seconds before you hit the "stylus moment". [1] But the watch demo was oddly fixated on long interactions (the most difficult way to text emoji to date) and stupid interactions (browsing pictures on a 1" screen?).

The cases where watch-interaction makes more (or primary) sense [2] were given very little screen time, or mere lip service. And, oddly enough, those cases seem to have been given more thought and have more obvious, natural, direct, and thus better interactions [3].

Enabling those complex interactions, that are going to be inefficient and annoying, is going to lead to an avalanche of apps that similarly invite users to do things fundamentally ill-suited to a watch. Poorly conceived apps, lazily-ported apps -- The ecosystem as a whole is going to suffer for having that around. [4]

And then there's the interaction methods. iOS was a boon for computer use because it's so obvious, direct and natural. Many/most people never really got the hang of click vs double-click vs right-click. Many struggled with the core indirection of pushing the pointer around the screen with their mouse and the whole "scroll down to push the page up" mess (that only makes sense if you grew up on keyboard-only interaction and the also-awkwardly-named "page up"/down keys).

Apple sweated the details, stripped away the distractions and non-essentials, and they nailed it.

But what does the watch bring? Quick-tap vs long-tap vs force-tap? Are they kidding? Undiscoverable hidden interaction zones in corner(s?) or off-screen-swipes to execute features with no articulated conceptual logic as to "what goes where" or how the (in)existence of those features is even conveyed? Those demo controls showed more arcane gestures than a Harry Potter movie.

And the crown? It zooms the screen, except when it doesn't. It scrolls lists, except when it doesn't. It manipulates input controls, except when it doesn't -- and only if you apply the appropriate tap to successfully shift focus to the desired input. This is a mode-switching UX nightmare.

Stated plainly -- that watch, that demo? -- they blew it.

They've got a few months where they could course-correct. They've got a review step where they could filter out "bad" apps to protect the ecosystem from what they accidentally enabled (and encouraged by focusing the demo on it).

But I am not optimistic that a group who could green-light that demo is capable of discerning the difference. I think Apple's fundamental "taste" is in question. [5]

[1] Jobs famously stated "if you see a stylus, they blew it." The key here is that "blew it" doesn't mean "they made a bad tablet". It means "they never understood mobile or touch." They never understood that the use cases and ergonomics require a fundamental re-thinking of interaction. They never understood that you can't just port over things that worked somewhere else and only make sense given prior experience with something else.

[2] e.g. when the phone itself is less accessible (while exercising, while in-bed, while hands are collecting purchased items), thus giving you longer than 2 seconds before the "I might as well have pulled out my phone" moment. e.g. when direct use of the phone would defeat the feature (to use the watch as remote viewfinder/shutter release for the phone's camera).

[3] notification triage; workout/stopwatch/timer start/stop; simple location-based interactions like payments, unlocking a hotel room door, etc. It all looked far more sane/natural/straightforward.

[4] We all just saw what happened with Microsoft's odd mode-shifting app circus on their Surface tablets. If you enable the "conceptually new, thus more difficult, but right" interaction method and "conceptually familiar, thus easier, and wrong" interaction method, how many devs are really going to put in the work to get it right? Recent experience suggests enough devs will take shortcuts that your users will become frustrated and your ecosystem stained.

[5] I don't think Apple's taste is definitely gone. But the notion that Apple might be "coasting on momentum" is no longer something I can laugh off. Not on a core design level.

And an alternative explanation to "they're coasting" on momentum, is that the Watch is pushing iphone/ipad interactions where they don't belong because Apple's captured by their own momentum. And that's far, far worse.

Of course, that doesn't mean you can't find someone dumb enough to unload it on for more than you paid it, but a collector isn't going to give you that value for it.

The Rolex Daytona is the exception to this rule though, but Submariners are mass-produced and common for luxury watches.

Source: I collect watches.

The Echo is now compatible with several Android phones as well. Given your description, I think you'd really like it.