An object that manages behaviors that are shared among all of your app’s interface controllers.
- watchOS 2.0+
Every WatchKit extension has a single extension object that is created and managed by the system. You use the extension object to perform app-level tasks such as opening URLs and getting the root interface controller of your app.
As relevant events occur within your WatchKit app, the extension object notifies its delegate of those events. Your delegate object can implement the methods it needs to provide an appropriate response to life cycle events, to handle notifications, or to handle Handoff–related behaviors. For more information about the methods of the delegate, see
Frontmost App Behaviors
If your watchOS app is the frontmost app, the system displays it when the user raises their wrist.
An app becomes the frontmost app if it is running when the user drops their wrist. The app briefly transitions to the background and is suspended, as normal. However, if the user raises their wrist again while the app is still the frontmost app, the system automatically resumes and displays the app.
If the user dismisses the app in some other way (for example, by pressing the crown or by covering the screen), the app does not remain the frontmost app.
By default, an app remains the frontmost app for two minutes after the user drops their wrist. Users can configure this behavior using Settings > General > Wake Screen.
You can also request additional time as the frontmost app by setting the extension's
is property to
In watchOS 4, the frontmost app gains the following additional advantages:
Can play haptic feedback from the background.
Wakes from the background to receive notifications.
Wakes immediately upon the completion of a background transfer from a
URLSessiontask or Watch Connectivity session.
For example, when the frontmost app receives a notification, rather than displaying the notification alert, it could play haptic feedback or a custom sound and then update its user interface.
Workout, location, and audio-recording apps appear to behave similarly to the frontmost app. However, these apps continue to run in the background throughout the entire workout, location, or recording session.
For more information, see
Receiving Background Data
When the system receives background data, it may not immediately wake the watchOS app to process that data. Instead, it may delay delivery of the data to preserve battery life.
When the system receives background data from either a
URLSession task or a Watch Connectivity session:
All apps (watchOS 3 and earlier). There is no guarantee on when the system will wake the app to deliver the data. In some cases, the app may not receive the data until the user launches the app.
Frontmost apps (watchOS 4 and later). The system wakes the app immediately to deliver the data.
All other apps (watchOS 4 and later). The system wakes the app within 10 minutes to deliver the data.