• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# Mission Management and Launch Type
2
3
4One UIAbility instance corresponds to one mission. The number of UIAbility instances is related to the UIAbility launch type, specified by **launchType**, which is configured in the **config.json** file in the FA model and the [module.json5](../quick-start/module-configuration-file.md) file in the stage model.
5
6
7The following describes how the mission list manager manages the UIAbility instanced started in different modes.
8- **singleton**: Only one UIAbility instance exists for an application.
9
10  **Figure 1** Missions and singleton mode
11
12  ![mission-and-singleton](figures/mission-and-singleton.png)
13
14- **multiton**: Each time **startAbility()** is called, a **UIAbility** instance is created in the application process.
15
16  **Figure 2** Missions and multiton mode
17
18  ![mission-and-multiton](figures/mission-and-standard.png)
19
20- **specified**: The ([onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant)) method of [AbilityStage](abilitystage.md) determines whether to create an instance.
21
22  **Figure 3** Missions and specified mode
23
24  ![mission-and-specified](figures/mission-and-specified.png)
25
26
27Each UIAbility instance corresponds to a mission displayed in **Recents**.
28
29
30Every mission retains a snapshot of the UIAbility instance. After the UIAbility instance is destroyed, the mission information (including the ability information and mission snapshot) is retained until the mission is deleted.
31
32
33> **NOTE**
34>
35> The **specified** mode is supported in the stage model only.
36
37