I was going to reply to you and say the same thing: it&#x27;s extremely similar to the initial iPhone 3rd party developer story, and for the same reasons. Apple is pretty predictable, really.<p>I know how WatchKit works, I was in on some of those meetings... Trust me, everyone at Apple had the same concerns you expressed and they still do. It will get better over time.<p>Also note that some built-in Apple apps <i>do</i> use WatchKit.<p>And I would still argue that allowing 3rd party code to run on the watch instead of in an extension on the phone would be just another example of an internal-only feature being opened up to the public. It&#x27;s the same pattern. I realize that&#x27;s a significant &quot;feature&quot;, but so was the switch from html+js to native apps on the phone. And those significant advances go through the same decision process as smaller ones: do we feel comfortable opening up this feature to 3rd parties? what are the risks? have we used it enough internally to feel confident? has it iterated enough internally that we consider it stable enough to release (because it&#x27;s hard to change after release)? etc.