Application lifecycle handling
Updated: Jul 23, 2026
In order to successfully develop for Quest devices using the Horizon OS, developers should understand lifecycle events exposed by the Horizon OS. Immersive apps are required to handle lifecycle events to release on the Horizon Store, due to i.e.
VRC.Quest.Functional.2 and
VRC.Quest.Input.4. Correctly handling lifecycle events will allow your app to provide a better user experience.
Application Pause events are sent when the Horizon OS expects the application to stop simulating, rendering, and accepting input. These events occur when the app is still loaded by the OS, but the user cannot see the app or interact with it. Applications should not allow any interactions by the paused user. See
VRC.Quest.Functional.2 for more details.
The Horizon OS can support multiple running applications at once. For instance, a user playing an immersive game may keep a 2D Browser window containing a walkthrough visible while playing. In this scenario, although both the browser window and the immersive game are visible to the user, only one application is expected to respond to user input at a time. When the Horizon OS detects user intent to send input to a different app, it sends Input focus events to the app that is losing focus, and the app gaining focus (if applicable).
Apps are required to stop rendering any tracked controllers/hands, and ignore all input, upon losing input focus (see
VRC.Quest.Input.4). However, it is up to the app developer to determine how losing input focus affects audio, rendering, and simulation. For instance, single-player action games may wish to pause entirely on losing input focus, while immersive video players may wish to continue video playback.
HMD mount & unmount events are sent when the user physically puts on or removes the headset. Once a headset is unmounted, an Application pause event will be sent after the amount of time configured under Settings > Power > Auto Sleep, unless the user re-mounts their headset first.
Although it is not a VRC requirement to act on these events, applications may wish to display a Pause menu or mark a user as inactive on unmount.
Unity applications can listen or check for the following common events sent by the Horizon OS.
When the application is initialized:
HMD MountedInput Focus Acquired
HMD unmount and mount quickly
When a user removes the HMD, then quickly puts it back on
- When HMD is removed:
HMD Unmounted - When HMD is replaced:
HMD Mounted
HMD unmount and mount with a delay
When a user removes the HMD, waits for the amount of time configured under Settings > Power > Auto Sleep, then puts it back on
- When HMD is removed:
HMD Unmounted Then, after the configured amount of time:
Input Focus LostApplication Paused
When HMD is replaced:
HMD MountedApplication UnpausedInput Focus Acquired
Application PausedInput Focus Lost
Application UnpausedInput Focus Acquired
When Universal Menu is opened:
When User selects “resume”, or closes Universal Menu:
Input Focus Acquired