article I’m excited to announce that the new Watch app structure plan (WASP) has been released.
As the name suggests, this document provides a framework for developing apps for the Watch, allowing developers to work with the Watch in new and different ways.
Here’s what we’ve been working on this week:The main goals of the new WASP are to improve the user experience of the Watch app, to provide a consistent and simple structure for apps that use the Watch as a backend, and to provide easy access to new and existing Watch apps.
The new WASTP was built around a few core concepts:The Watch app should not require additional configuration to work as intended, and should not rely on the Watch’s APIs to perform specific tasks, including the notification display.
It should be easy to build applications that do not require the Watch to be running.
Apps should be lightweight, as they should not consume any resources or be tied to a specific app bundle.
The WASTS will be available in the App Store later this year.
For developers, this WAST is a good start to the next few months of work we’re doing.
It will enable us to build a consistent, clean, and modular design of the app that will allow developers to easily transition to using the Watch.
We will also continue to work closely with the watchOS team to deliver the most seamless experience for the watch as a whole.
As with any new feature release, we hope that the next release will contain a number of small but important improvements and bug fixes that we’ll announce later this week.
We’re committed to releasing WAST as soon as possible.
We also encourage you to check out our upcoming app updates for Watch, the Watch Hub, and the Watch Store for updates and fixes.
You can find out more about what we’re working on here .
You can also stay up to date on the WAST on GitHub repository.