You are on page 1of 5

watchOS Process

Management
watchOS App States
State Description

Not running The app has no running processes.

The app is running in the foreground, and


maybe executing some code. However, it is
Inactive
not receiving actions from controls or
gestures.
The app is running in the foreground, and is
Active receiving actions from controls or
gestures.
A background app has small amount of
Background background execution time. It’s so that the
app can perform background tasks.

A suspended app is in memory but is not


executing code. watchOS always suspends
Suspended
background apps when they do not have
any pending task.
Examples of App States
Situation App State

Running on screen Active

Running in the dock Inactive

Running as frontmost app Inactive

Running a background task/session Background


How watchOS Deals with
Background and Suspended Apps

• watchOS purges suspended apps without warning.

• An app which enters background state should save any data to recreate its
current state; as once it’s suspended, it can be purged anytime!

• watchOS tries its best to keep frequently used apps in memory, allowing
them to resume as quickly as possible, and also saving battery life.

• watchOS specifically preserves (in memory) the most recently executed


app, apps in the dock, etc. If such an app is purged due to memory
limitations, watchOS relaunches them as soon as more memory gets
available.
Facts about watchOS Apps
• watchOS apps primarily runs in the foreground to limit impact on system resources.
• Background apps may be playing music, supporting workouts, helping with navigation, etc.
• An app may run in the background based on a schedule, but watchOS reserves every right
to delay it or throttle the process based on the availability of the system resources.
• 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.
• If the app is currently running—either active and onscreen, or inactive and the frontmost
app—the system immediately delivers the data to the app. If the app is in the background,
the system wakes the app within 10 minutes to deliver the data.
• If the user raises their wrist while the app is still the frontmost app, the system
automatically activates and displays the app.
• If the user lowers their wrist, the active app running on screen will quickly transition to
inactive, and finally the background state.

You might also like