Dual-mode app states

An app must maintain a dual-mode state that indicates whether it is in AppConnect Mode. It stores this state persistently, so that when it next launches, it knows how to behave. The possible states are:

•Undecided

The app has initialized for the first time and has not yet decided whether to run in AppConnect Mode or Non-AppConnect Mode.

•AppConnect Mode

The app is running as an AppConnect app. It supports the AppConnect features, such as authorization and data loss prevention policies.

•Non-AppConnect Mode

The app is running as a regular app.

•Pending AppConnect Mode

The app changes to this state if the device user explicitly requests a change to AppConnect Mode using the app’s user interface. For example, device users in an enterprise sometimes have installed and used an app before the enterprise requires it as an AppConnect app. In this state, the app is waiting for an event from the AppConnect Cordova Plugin to find out whether AppConnect components are managing the app.

The following diagram summarizes the state transitions that a dual-mode app implements. See High-level dual-mode app behavior for more information about these state transitions.

Figure 1. Dual-mode app state transitions