I realise Jobs needed a push to get to the open app system, and was originally against it - or at least for something that was more like the Widget system on OS X, and not so much like the Objective-C monster the App Store turned into.
But my point - which apparently no one understands here - is that the products were always conceived originally, from the top, as part of a strategy that included a stack of support services and interactions with a user community.
I'm not seeing that on offer here.
Of course WATCH does apps. That was always a given. But the App Store is saturated, and once devs have produced the obligatory new watch faces, fitness, dating and friend-finding apps, my guess is that the opportunities for doing something compelling, original and gotta-have-that are smaller than they were with the original iPhone.
There will be an exception, or maybe four or five. There will not be thousands of potential gotta-have-that apps to match those that are available in the iPhone/iPad app store.
Apple has always been one of the few tech companies that understands that you don't sell hardware, or software - you sell a complete package of unique and exclusive benefits that happens to run on a hardware device.
That worked for the original Mac, then the OS X Mac, then the iPod, then the iPhone, then the iPad. All had obvious user benefits that were so intuitively compelling they barely needed explanation, and which were enhanced and supported over time with software services that made the package even stronger.
I'd be interested to know what the downvoters on this thread believe is the equivalent user benefit and software support package for WATCH.
I don't believe 'It does apps too and there's even an API, so therefore there's an ecosystem' is the most insightful answer to that question, or that it's what users are looking for to persuade them this is a must-have device.