Your point is actually orthogonal to the OP&#x27;s.<p>The OP was claiming that Apple&#x27;s architecture is flawed and that once they realize the error of their ways, battery life will improve dramatically. That&#x27;s just not true.<p>Your point is that the public SDK limits 3rd party developers from doing some stuff that Apple can do with the private SDK. That is, of course, absolutely true.<p>Letting the public SDK (or at least parts of it) lag behind the private SDK, while certainly frustrating to 3rd party developers, is the right thing to do. The situation is exactly the same on the iPhone, iPad, and Apple TV. Apple has employed that strategy from the beginning with iOS, and they believe it to be the correct strategy, so they will almost certainly stick with it.<p>I don&#x27;t work at Apple any more (pushing toward launch on a startup!), but based on over 8 years of iOS history, I think it&#x27;s safe to say that the public watch SDK will get more powerful over time, as private-only features are deemed ready to release to 3rd parties.