Merge remote-tracking branch 'upstream/OpenHarmony-3.2-Release' into OpenHarmony-3.2-Release

Signed-off-by: Nxsz233 <xushizhe@huawei.com>

CODEOWNERS

@@ -188,6 +188,7 @@ zh-cn/application-dev/key-features/multi-device-app-dev/ @lingminghw
 zh-cn/application-dev/database/ @ge-yafang
 zh-cn/application-dev/napi/native-window-guidelines.md @ge-yafang
 zh-cn/application-dev/napi/mindspore-lite-guidelines.md @ge-yafang 
+zh-cn/application-dev/napi/neural-network-runtime-guidelines.md @ge-yafang 
 zh-cn/application-dev/napi/rawfile_guidelines.md @ningningW
 zh-cn/application-dev/background-agent-scheduled-reminder/ @RayShih
 zh-cn/application-dev/background-task-management/ @ningningW
@@ -383,7 +384,7 @@ zh-cn/application-dev/reference/apis/js-apis-lightweightmap.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-lightweightset.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-linkedlist.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-list.md @ge-yafang
-zh-cn/application-dev/reference/apis/js-apis-logs.md @HelloCrease
+zh-cn/application-dev/reference/apis/js-apis-logs.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-media.md @zengyawen
 zh-cn/application-dev/reference/apis/js-apis-medialibrary.md @zengyawen
 zh-cn/application-dev/reference/apis/js-apis-mediaquery.md @HelloCrease
@@ -454,7 +455,7 @@ zh-cn/application-dev/reference/apis/js-apis-system-vibrate.md @ningningW
 zh-cn/application-dev/reference/apis/js-apis-telephony-data.md @zengyawen
 zh-cn/application-dev/reference/apis/js-apis-testRunner.md @RayShih
 zh-cn/application-dev/reference/apis/js-apis-thermal.md @zengyawen
-zh-cn/application-dev/reference/apis/js-apis-timer.md @HelloCrease
+zh-cn/application-dev/reference/apis/js-apis-timer.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-touchevent.md @ningningW
 zh-cn/application-dev/reference/apis/js-apis-treemap.md @ge-yafang
 zh-cn/application-dev/reference/apis/js-apis-treeset.md @ge-yafang

en/OpenHarmony-Overview.md

 # OpenHarmony Project
 
+> **NOTE**
+>
+> You are reading documents of OpenHarmony 3.2 Release. Obtain the [compatible SDK](../release-notes/OpenHarmony-v3.2-release.md#version-mapping) during your application development.
+
 ## Introduction
 
 OpenHarmony is an open-source project incubated and operated by the OpenAtom Foundation. The purpose of this project is to build an open-source, distributed operating system (OS) framework for smart devices in all scenarios of a fully-connected world.
@@ -189,7 +193,7 @@ For details about how to obtain the source code of OpenHarmony, see [Source Code
 
 ## How to Participate
 
-For details about how to join in the OpenHarmony community, see [OpenHarmony Community](https://gitee.com/openharmony/community/blob/master/README-EN.md)
+For details about how to join in the OpenHarmony community, see [OpenHarmony Community](https://gitee.com/openharmony/community/blob/master/README_EN.md)
 
 For details about how to contribute, see [How to contribute](contribute/how-to-contribute.md).
 

en/application-dev/IDL/idl-guidelines.md

@@ -3,7 +3,7 @@
 ## IDL Overview
 To ensure successful communications between the client and server, interfaces recognized by both parties must be defined. The OpenHarmony Interface Definition Language (IDL) is a tool for defining such interfaces. OpenHarmony IDL decomposes objects to be transferred into primitives that can be understood by the operating system and encapsulates cross-boundary objects based on developers' requirements.
 
-  **Figure 1** IDL interface description
+**Figure 1** IDL interface description
 
 ![IDL-interface-description](./figures/IDL-interface-description.png)
 
@@ -156,9 +156,11 @@ On DevEco Studio, choose **Tools > SDK Manager** to view the local installation
 
 Go to the local installation path, choose **toolchains > 3.x.x.x** (the folder named after the version number), and check whether the executable file of IDL exists.
 
-> **NOTE**: Use the SDK of the latest version. The use of an earlier version may cause errors in some statements.
+> **NOTE**
+>
+> Use the SDK of the latest version. The use of an earlier version may cause errors in some statements.
 
-If the executable file does not exist, download the SDK package from the mirror as instructed in the [Release Notes](../../release-notes). The following uses the [3.2 Beta5]((../../release-notes/OpenHarmony-v3.2-beta5.md#acquiring-source-code-from-mirrors) as an example.
+If the executable file does not exist, download the SDK package from the mirror as instructed in the [Release Notes](../../release-notes). The following uses [3.2 Beta5](../../release-notes/OpenHarmony-v3.2-beta5.md#acquiring-source-code-from-mirrors) as an example.
 
 For details about how to replace the SDK package, see [Guide to Switching to Full SDK](../quick-start/full-sdk-switch-guide.md).
 
@@ -176,6 +178,8 @@ You can use TS to create IDL files.
   interface OHOS.IIdlTestService {
       int TestIntTransaction([in] int data);
       void TestStringTransaction([in] String data);
+      void TestMapTransaction([in] Map<int, int> data);
+      int TestArrayTransaction([in] String[] data);
   }
 ```
 
@@ -183,7 +187,9 @@ Run the **idl -gen-ts -d *dir* -c dir/IIdlTestService.idl** command in the folde
 
 -*dir* next to **d** is the target output folder. For example, if the target output folder is **IIdlTestServiceTs**, run the **idl -gen-ts -d IIdlTestServiceTs -c IIdlTestServiceTs/IIdlTestService.idl** command in the folder where the executable file is located. The interface file, stub file, and proxy file are generated in the *dir* directory (**IIdlTestServiceTs** directory in this example) in the execution environment.
 
-> **NOTE**: The generated interface class file name must be the same as that of the .idl file. Otherwise, an error occurs during code generation.
+> **NOTE**
+>
+> The generated interface class file name must be the same as that of the .idl file. Otherwise, an error occurs during code generation.
 
 For example, for an .idl file named **IIdlTestService.idl** and target output directory named **IIdlTestServiceTs**, the directory structure is similar to the following:
 
@@ -203,6 +209,8 @@ The stub class generated by IDL is an abstract implementation of the interface c
 ```ts
 import {testIntTransactionCallback} from "./i_idl_test_service";
 import {testStringTransactionCallback} from "./i_idl_test_service";
+import {testMapTransactionCallback} from "./i_idl_test_service";
+import {testArrayTransactionCallback} from "./i_idl_test_service";
 import IIdlTestService from "./i_idl_test_service";
 import rpc from "@ohos.rpc";
 
@@ -211,8 +219,8 @@ export default class IdlTestServiceStub extends rpc.RemoteObject implements IIdl
         super(des);
     }
     
-    async onRemoteRequestEx(code: number, data, reply, option): Promise<boolean> {
-        console.log("onRemoteRequestEx called, code = " + code);
+    async onRemoteMessageRequest(code: number, data, reply, option): Promise<boolean> {
+        console.log("onRemoteMessageRequest called, code = " + code);
         switch(code) {
             case IdlTestServiceStub.COMMAND_TEST_INT_TRANSACTION: {
                 let _data = data.readInt();
@@ -231,6 +239,29 @@ export default class IdlTestServiceStub extends rpc.RemoteObject implements IIdl
                 });
                 return true;
             }
+            case IdlTestServiceStub.COMMAND_TEST_MAP_TRANSACTION: {
+                let _data = new Map();
+                let _dataSize = data.readInt();
+                for (let i = 0; i < _dataSize; ++i) {
+                    let key = data.readInt();
+                    let value = data.readInt();
+                    _data.set(key, value);
+                }
+                this.testMapTransaction(_data, (errCode) => {
+                    reply.writeInt(errCode);
+                });
+                return true;
+            }
+            case IdlTestServiceStub.COMMAND_TEST_ARRAY_TRANSACTION: {
+                let _data = data.readStringArray();
+                this.testArrayTransaction(_data, (errCode, returnValue) => {
+                    reply.writeInt(errCode);
+                    if (errCode == 0) {
+                        reply.writeInt(returnValue);
+                    }
+                });
+                return true;
+            }
             default: {
                 console.log("invalid request code" + code);
                 break;
@@ -241,17 +272,23 @@ export default class IdlTestServiceStub extends rpc.RemoteObject implements IIdl
     
     testIntTransaction(data: number, callback: testIntTransactionCallback): void{}
     testStringTransaction(data: string, callback: testStringTransactionCallback): void{}
+    testMapTransaction(data: Map<number, number>, callback: testMapTransactionCallback): void{}
+    testArrayTransaction(data: string[], callback: testArrayTransactionCallback): void{}
 
     static readonly COMMAND_TEST_INT_TRANSACTION = 1;
     static readonly COMMAND_TEST_STRING_TRANSACTION = 2;
+    static readonly COMMAND_TEST_MAP_TRANSACTION = 3;
+    static readonly COMMAND_TEST_ARRAY_TRANSACTION = 4;
 }
 ```
 
-You need to inherit the interface class defined in the IDL file and implement the methods in the class. The following code snippet shows how to inherit the **IdlTestServiceStub** interface class and implement the **testIntTransaction** and **testStringTransaction** methods.  
+You need to inherit the interface class defined in the IDL file and implement the methods in the class. The following code snippet shows how to inherit the **IdlTestServiceStub** interface class and implement the **testIntTransaction**, **testStringTransaction**, **testMapTransaction**, and **testArrayTransaction** methods.  
 
 ```ts
 import {testIntTransactionCallback} from "./i_idl_test_service"
 import {testStringTransactionCallback} from "./i_idl_test_service"
+import {testMapTransactionCallback} from "./i_idl_test_service";
+import {testArrayTransactionCallback} from "./i_idl_test_service";
 import IdlTestServiceStub from "./idl_test_service_stub"
 
 
@@ -265,6 +302,14 @@ class IdlTestImp extends IdlTestServiceStub {
     {
         callback(0);
     }
+    testMapTransaction(data: Map<number, number>, callback: testMapTransactionCallback): void
+    {
+        callback(0);
+    }
+    testArrayTransaction(data: string[], callback: testArrayTransactionCallback): void
+    {
+        callback(0, 1);
+    }
 }
 ```
 
@@ -320,11 +365,28 @@ function callbackTestStringTransaction(result: number): void {
   }
 }
 
+function callbackTestMapTransaction(result: number): void {
+  if (result == 0) {
+    console.log('case 3 success');
+  }
+}
+
+function callbackTestArrayTransaction(result: number, ret: number): void {
+  if (result == 0 && ret == 124) {
+    console.log('case 4 success');
+  }
+}
+
 var onAbilityConnectDone = {
   onConnect:function (elementName, proxy) {
     let testProxy = new IdlTestServiceProxy(proxy);
+    let testMap = new Map();
+    testMap.set(1, 1);
+    testMap.set(1, 2);
     testProxy.testIntTransaction(123, callbackTestIntTransaction);
     testProxy.testStringTransaction('hello', callbackTestStringTransaction);
+    testProxy.testMapTransaction(testMap, callbackTestMapTransaction);
+    testProxy.testArrayTransaction(['1','2'], callbackTestMapTransaction);
   },
   onDisconnect:function (elementName) {
     console.log('onDisconnectService onDisconnect');

en/application-dev/Readme-EN.md

@@ -17,7 +17,6 @@
       - Application Package Structure
         - [Application Package Structure in Stage Model)](quick-start/application-package-structure-stage.md)
         - [Application Package Structure in FA Model](quick-start/application-package-structure-fa.md)
-        - [HAR File Structure](quick-start/har-structure.md)
       - Multi-HAP Mechanism
         - [Multi-HAP Design Objectives](quick-start/multi-hap-objective.md)
         - [Multi-HAP Build View](quick-start/multi-hap-build-view.md)
@@ -25,6 +24,11 @@
         - [Multi-HAP Usage Rules](quick-start/multi-hap-rules.md)
         - [Multi-HAP Operation Mechanism and Data Communication Modes](quick-start/multi-hap-principles.md)
       - [Application Installation and Uninstallation Process](quick-start/application-package-install-uninstall.md)
+      - Shared Package
+        - [Shared Package Overview](quick-start/shared-guide.md)
+        - [HAR](quick-start/har-package.md)
+        - HSP
+          - [In-Application HSP Development](quick-start/in-app-hsp.md)
     - Application Configuration Files in Stage Model
       - [Application Configuration File Overview (Stage Model)](quick-start/application-configuration-file-overview-stage.md)
       - [app.json5 Configuration File](quick-start/app-configuration-file.md)
@@ -37,18 +41,46 @@
     - [Resource Categories and Access](quick-start/resource-categories-and-access.md)
   - Learning ArkTS
     - [Getting Started with ArkTS](quick-start/arkts-get-started.md)
-    - ArkTS Syntax (Declarative UI)
-      - [Basic UI Description](quick-start/arkts-basic-ui-description.md)
+    - Basic Syntax
+      - [Basic Syntax Overview](quick-start/arkts-basic-syntax-overview.md)
+      - [Declarative UI Description](quick-start/arkts-declarative-ui-description.md)
+      - Custom Component
+        - [Creating a Custom Component](quick-start/arkts-create-custom-components.md)
+        - [Page and Custom Component Lifecycle](quick-start/arkts-page-custom-components-lifecycle.md)
+      - [\@Builder: Custom Builder Function](quick-start/arkts-builder.md)
+      - [\@BuilderParam: @Builder Function Reference](quick-start/arkts-builderparam.md)
+      - [\@Styles: Definition of Resusable Styles](quick-start/arkts-style.md)
+      - [\@Extend: Extension of Built-in Components](quick-start/arkts-extend.md)
+      - [stateStyles: Polymorphic Style](quick-start/arkts-statestyles.md)
     - State Management
-        - [Basic Concepts](quick-start/arkts-state-mgmt-concepts.md)
-        - [State Management with Page-level Variables](quick-start/arkts-state-mgmt-page-level.md)
-        - [State Management with Application-level Variables](quick-start/arkts-state-mgmt-application-level.md)
-      - [Dynamic UI Element Building](quick-start/arkts-dynamic-ui-elememt-building.md)
-      - [Rendering Control](quick-start/arkts-rendering-control.md)
-      - [Restrictions and Extensions](quick-start/arkts-restrictions-and-extensions.md)
+      - [State Management Overview](quick-start/arkts-state-management-overview.md)
+      - Component State Management
+        - [\@State: State Owned by Component](quick-start/arkts-state.md)
+        - [\@Prop: One-Way Synchronization from Parent to Child Components](quick-start/arkts-prop.md)
+        - [\@Link: Two-Way Synchronization Between Parent and Child Components](quick-start/arkts-link.md)
+        - [\@Provide and \@Consume: Two-Way Synchronization with Descendant Components](quick-start/arkts-provide-and-consume.md)
+        - [\@Observed and \@ObjectLink: Observing Attribute Changes in Nested Class Objects](quick-start/arkts-observed-and-objectlink.md)
+      - Application State Management
+        - [Application State Management Overview](quick-start/arkts-application-state-management-overview.md)
+        - [LocalStorage: UI State Storage](quick-start/arkts-localstorage.md)
+        - [AppStorage: Application-wide UI State Storage](quick-start/arkts-appstorage.md)
+        - [PersistentStorage: Application State Persistence](quick-start/arkts-persiststorage.md)
+        - [Environment: Device Environment Query](quick-start/arkts-environment.md)
+      - Other State Management Features
+        - [Overview of Other State Management Features](quick-start/arkts-other-state-mgmt-functions-overview.md)
+        - [\@Watch: Getting Notified of State Variable Changes](quick-start/arkts-watch.md)
+        - [$$ Syntax: Two-Way Synchronization of Built-in Components](quick-start/arkts-two-way-sync.md)
+    - Rendering Control
+      - [Rendering Control Overview](quick-start/arkts-rendering-control-overview.md)
+      - [if/else: Conditional Rendering](quick-start/arkts-rendering-control-ifelse.md)
+      - [ForEach: Rendering of Repeated Content](quick-start/arkts-rendering-control-foreach.md)
+      - [LazyForEach: Lazy Data Loading](quick-start/arkts-rendering-control-lazyforeach.md)
+
+
 - Development
   - [Application Models](application-models/Readme-EN.md)
   - [UI Development](ui/Readme-EN.md)
+  - [Web](web/Readme-EN.md)
   - [Notification](notification/Readme-EN.md)
   - [Window Manager](windowmanager/Readme-EN.md)
   - [WebGL](webgl/Readme-EN.md)
@@ -82,6 +114,7 @@
     - [ArkTS and JS APIs](reference/apis/Readme-EN.md)
     - [Error Codes](reference/errorcodes/Readme-EN.md)
     - Native APIs
+      - [Native APIs](reference/native-apis/Readme-EN.md)
       - [Standard Libraries](reference/native-lib/third_party_libc/musl.md)
       - [Node_API](reference/native-lib/third_party_napi/napi.md)
 - [FAQs](faqs/Readme-EN.md)

en/application-dev/ability-deprecated/fa-dataability.md

@@ -116,7 +116,7 @@ Example URIs:
    | "name"       | Ability name, corresponding to the **Data** class name derived from **Ability**.                    |
    | "type"       | Ability type, which is **Data** for a Data ability.                |
    | "uri"        | URI used for communication.                                             |
-   | "visible"    | Whether the Data ability is visible to other applications. When this parameter is set to **true**, the Data ability can communicate with other applications.|
+   | "exported"    | Whether the Data ability is visible to other applications. When this parameter is set to **true**, the Data ability can communicate with other applications.|
 
    **config.json configuration example**
 
@@ -128,7 +128,7 @@ Example URIs:
        "srcLanguage": "ets",
        "description": "$string:description_dataability",
        "type": "data",
-       "visible": true,
+       "exported": true,
        "uri": "dataability://ohos.samples.etsdataability.DataAbility"
     }]
    ```

en/application-dev/ability-deprecated/fa-formability.md

@@ -25,7 +25,7 @@ Carry out the following operations to develop the widget provider based on the [
 1. Implement lifecycle callbacks by using the **LifecycleForm** APIs.
 2. Create a **FormBindingData** instance.
 3. Update a widget by using the **FormProvider** APIs.
-4. Develop the widget UI pages.
+4. Develop the widget UI page.
 
 ## Available APIs
 
@@ -231,7 +231,7 @@ You should override **onDestroy** to implement widget data deletion.
        }
 ```
 
-For details about how to implement persistent data storage, see [Lightweight Data Store Development](../database/database-preference-guidelines.md).
+For details about how to implement persistent data storage, see [Data Persistence by User Preferences](../database/data-persistence-by-preferences.md).
 
 The **Want** object passed in by the widget host to the widget provider contains a flag that specifies whether the requested widget is normal or temporary.
 
@@ -355,7 +355,7 @@ You can set router and message events for components on a widget. The router eve
 1. Set the **onclick** field in the HML file to **routerEvent** or **messageEvent**, depending on the **actions** settings in the JSON file.
 2. Set the router event.
    - **action**: **"router"**, which indicates a router event.
-   - **abilityName**: target ability name, for example, **com.example.entry.MainAbility**, which is the default UIAbility name in DevEco Studio for the FA model.
+   - **abilityName**: target ability name, for example, **com.example.entry.MainAbility**, which is the default main ability name in DevEco Studio for the FA model.
    - **params**: custom parameters of the target ability. Set them as required. The value can be obtained from **parameters** in **want** used for starting the target ability. For example, in the lifecycle function **onCreate** of the main ability in the FA model, **featureAbility.getWant()** can be used to obtain **want** and its **parameters** field.
 3. Set the message event.
    - **action**: **"message"**, which indicates a message event.

en/application-dev/ability-deprecated/stage-ability-continuation.md

@@ -49,11 +49,9 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
      ```
      
    
-
-
    - Configure the application startup type.
    
-     If **launchType** is set to **standard** in the **module.json5** file, the application is of the multi-instance launch type. During ability continuation, regardless of whether the application is already open, the target starts the application and restores the UI page. If **launchType** is set to **singleton**, the application is of the singleton launch type. If the application is already open, the target clears the existing page stack and restores the UI page. For more information, see "Launch Type" in [Ability Development](./stage-ability.md).
+        If **launchType** is set to **multiton** in the **module.json5** file, the application is of the multi-instance launch type. During ability continuation, regardless of whether the application is already open, the target starts the application and restores the UI page. If **launchType** is set to **singleton**, the application is of the singleton launch type. If the application is already open, the target clears the existing page stack and restores the UI page. For more information, see "Launch Type" in [Ability Development](./stage-ability.md).
         
         Configure a multi-instance application as follows:
         
@@ -62,7 +60,7 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
           "module": {
             "abilities": [
               {
-             "launchType": "standard"
+                "launchType": "multiton"
               }
             ]
           }
@@ -83,8 +81,6 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
         }
         ```
         
-     
-     
    - Apply for the distributed permissions.
      
         Declare the **DISTRIBUTED_DATASYNC** permission in the **module.json5** file for the application.
@@ -96,8 +92,6 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
                },
         ```
      
-     
-
         This permission must be granted by the user in a dialog box when the application is started for the first time. To enable the application to display a dialog box to ask for the permission, add the following code to **onWindowStageCreate** of the **Ability** class:
      
         ```javascript
@@ -139,7 +133,6 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
    
 
 
-
 2. Implement the **onContinue()** API.
 
    The **onContinue()** API is called by the initiator to save the UI component state variables and memory data and prepare for continuation. After the application completes the continuation preparation, the system must return either **OnContinueResult.AGREE(0)** to accept the continuation request or an error code to reject the request. If this API is not implemented, the system rejects the continuation request by default.
@@ -155,7 +148,7 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
 
    You can obtain the target device ID (identified by the key **targetDevice**) and the version number (identified by the key **version**) of the application installed on the target device from the **wantParam** parameter of this API. The version number can be used for compatibility check. If the current application version is incompatible with that on the target device, **OnContinueResult.MISMATCH** can be returned to reject the continuation request.
 
-   Example
+   Example:
 
    ```javascript
         onContinue(wantParam : {[key: string]: any}) {
@@ -168,8 +161,6 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
         }
    ```
 
-   
-
 3. Implement the continuation logic in the **onCreate()** or **onNewWant()** API.
 
    The **onCreate()** API is called by the target. When the ability is started on the target device, this API is called to instruct the application to synchronize the memory data and UI component state, and triggers page restoration after the synchronization is complete. If the continuation logic is not implemented, the ability will be started in common startup mode and the page cannot be restored.
@@ -178,11 +169,9 @@ The code snippets provided below are all from [Sample](https://gitee.com/openhar
    
    After data restore is complete, call **restoreWindowStage** to trigger page restoration.
    
-   
-
    You can also use **want.parameters.version** in the **want** parameter to obtain the application version number of the initiator.
 
-   Example
+   Example:
    
    ```javascript
     import Ability from '@ohos.application.Ability';
@@ -211,9 +200,9 @@ For a singleton ability, use **onNewWant()** to achieve the same implementation.
 
 Use distributed objects.
 
-Distributed objects allow cross-device data synchronization like local variables. For two devices that form a Super Device, when data in the distributed data object of an application is added, deleted, or modified on a device, the data for the same application is also updated on the other device. Both devices can listen for the data changes and online and offline states of the other. For details, see [Distributed Data Object Development](../database/database-distributedobject-guidelines.md).
+Distributed objects allow cross-device data synchronization like local variables. For two devices that form a Super Device, when data in the distributed data object of an application is added, deleted, or modified on a device, the data for the same application is also updated on the other device. Both devices can listen for the data changes and online and offline states of the other. For details, see [Sharing Distributed Data Objects](../database/data-sync-of-distributed-data-object.md).
 
-In the ability continuation scenario, the distributed data object is used to synchronize the memory data from the local device to the target device.
+In the ability continuation scenario, the distributed data object is used to synchronize the memory data from the local device to the target device. For details, see [Distributed Data Object Development](../database/database-distributedobject-guidelines.md).
 
 - In **onContinue()**, the initiator saves the data to be migrated to the distributed object, calls the **save()** API to save the data and synchronize the data to the target device, sets the session ID, and sends the session ID to the target device through **wantParam**.
 
@@ -249,8 +238,6 @@ In the ability continuation scenario, the distributed data object is used to syn
         });
   ```
 
-  
-
 - The target device obtains the session ID from **onCreate()**, creates a distributed object, and associates the distributed object with the session ID. In this way, the distributed object can be synchronized. Before calling **restoreWindowStage**, ensure that all distributed objects required for continuation have been associated.
 
   ```javascript
@@ -284,8 +271,6 @@ In the ability continuation scenario, the distributed data object is used to syn
      }
   ```
   
-   
-  
 ### More Information
 
 1. Timeout
@@ -295,15 +280,11 @@ In the ability continuation scenario, the distributed data object is used to syn
 
 2. By default, the system supports page stack information migration, which means that the page stack of the initiator will be automatically migrated to the target device. No adaptation is required.
 
-
-
 ### Restrictions
 
 1.   The continuation must be performed between the same ability, which means the same bundle name, module name, and ability name. For details, see [Application Package Structure Configuration File](../quick-start/module-configuration-file.md).
 2.    Currently, the application can only implement the continuation capability. The continuation action must be initiated by the system.
 
-
-
 ### Best Practice
 
 For better user experience, you are advised to use the **wantParam** parameter to transmit data smaller than 100 KB and use distributed objects to transmit data larger than 100 KB.

en/application-dev/ability-deprecated/stage-ability.md

@@ -12,7 +12,7 @@ An ability can be launched in the **standard**, **singleton**, or **specified**
 
 | Launch Type    | Description    |Action            |
 | ----------- | -------  |---------------- |
-| standard    | Standard mode  | A new instance is started each time an ability starts.|
+| multiton    | Multi-instance mode| A new instance is started each time an ability starts.|
 | singleton   | Singleton mode  | The ability has only one instance in the system. If an instance already exists when an ability is started, that instance is reused.|
 | specified   | Instance-specific| The internal service of an ability determines whether to create multiple instances during running.|
 
@@ -71,7 +71,7 @@ To create Page abilities for an application in the stage model, you must impleme
    ```js
    import Ability from '@ohos.application.Ability'
    ```
-4. Implement the lifecycle callbacks of the **UIAbility** class. The default relative path generated by the APIs is **entry\src\main\ets\MainAbility\MainAbility.ts**.
+4. Implement the lifecycle callbacks of the **UIAbility** class. The default relative path generated by the APIs is **entry\src\main\ets\entryability\EntryAbility.ts**.
 
    In the **onWindowStageCreate(windowStage)** API, use **loadContent** to set the application page to be loaded. For details about how to use the **Window** APIs, see [Window Development](../windowmanager/application-window-stage.md).
    ```ts
@@ -114,6 +114,7 @@ The following example shows how an application obtains the bundle code directory
 
 ```ts
 import AbilityStage from "@ohos.application.AbilityStage"
+
 export default class MyAbilityStage extends AbilityStage {
     onCreate() {
         console.log("MyAbilityStage onCreate")
@@ -188,7 +189,7 @@ export default class MainAbility extends Ability {
 ```
 ## Starting an Ability
 ### Available APIs
-The **Ability** class has the **context** attribute, which belongs to the **AbilityContext** class. The **AbilityContext** class has the **abilityInfo**, **currentHapModuleInfo**, and other attributes as well as the APIs used for starting abilities. For details, see [AbilityContext](../reference/apis/js-apis-ability-context.md).
+The **Ability** class has the **context** attribute, which belongs to the **AbilityContext** class. The **AbilityContext** class has the **abilityInfo**, **currentHapModuleInfo**, and other attributes as well as the APIs used for starting abilities. For details, see [AbilityContext](../reference/apis/js-apis-inner-application-applicationContext.md).
 
 **Table 3** AbilityContext APIs
 |API|Description|

en/application-dev/ability-deprecated/stage-call.md

@@ -47,40 +47,45 @@ The table below describes the ability call APIs. For details, see [Ability](../r
 ## How to Develop
 The procedure for developing the ability call is as follows:
 1. Create a callee ability.
-
 2. Access the callee ability.
 
 ### Creating a Callee Ability
 For the callee ability, implement the callback to receive data and the methods to marshal and unmarshal data. When data needs to be received, use **on()** to register a listener. When data does not need to be received, use **off()** to deregister the listener.
-**1. Configure the ability launch type.**
+
+1. **Configure the ability launch type.**
 
    Set **launchType** of the callee ability to **singleton** in the **module.json5** file.
 
-|JSON Field|Description|
-|:------|:------|
-|"launchType"|Ability launch type. Set this parameter to **singleton**.|
+   |JSON Field|Description|
+   |:------|:------|
+   |"launchType"|Ability launch type. Set this parameter to **singleton**.|
 
-An example of the ability configuration is as follows:
-```json
-"abilities":[{
+   An example of the ability configuration is as follows:
+   
+   ```json
+   "abilities":[{
        "name": ".CalleeAbility",
-    "srcEntrance": "./ets/CalleeAbility/CalleeAbility.ts",
+       "srcEnty": "./ets/CalleeAbility/CalleeAbility.ts",
        "launchType": "singleton",
        "description": "$string:CalleeAbility_desc",
        "icon": "$media:icon",
        "label": "$string:CalleeAbility_label",
-    "visible": true
-}]
-```
-**2. Import the Ability module.**
-```ts
-import Ability from '@ohos.app.ability.UIAbility'
-```
-**3. Define the agreed sequenceable data.**
+       "exported": true
+   }]
+   ```
+   
+2. **Import the ability module.**
+
+   ```ts
+   import Ability from '@ohos.app.ability.UIAbility';
+   ```
+
+3. **Define the agreed sequenceable data.**
 
    The data formats sent and received by the caller and callee abilities must be consistent. In the following example, the data formats are number and string. The code snippet is as follows:
-```ts
-export default class MySequenceable {
+
+   ```ts
+   export default class MySequenceable {
        num: number = 0
        str: string = ""
    
@@ -100,16 +105,18 @@ export default class MySequenceable {
            this.str = messageParcel.readString()
            return true
        }
-}
-```
-**4. Implement Callee.on and Callee.off.**
+   }
+   ```
+
+4. **Implement Callee.on and Callee.off.**
 
    The time to register a listener for the callee ability depends on your application. The data sent and received before the listener is registered and that after the listener is deregistered are not processed. In the following example, the **MSG_SEND_METHOD** listener is registered in **onCreate** of the ability and deregistered in **onDestroy**. After receiving sequenceable data, the application processes the data and returns the data result. You need to implement processing based on service requirements. The code snippet is as follows:
-```ts
-const TAG: string = '[CalleeAbility]'
-const MSG_SEND_METHOD: string = 'CallSendMsg'
 
-function sendMsgCallback(data) {
+   ```ts
+   const TAG: string = '[CalleeAbility]'
+   const MSG_SEND_METHOD: string = 'CallSendMsg'
+   
+   function sendMsgCallback(data) {
        console.log('CalleeSortFunc called')
    
        // Obtain the sequenceable data sent by the caller ability.
@@ -120,9 +127,9 @@ function sendMsgCallback(data) {
        // Process the data.
        // Return the sequenceable data result to the caller ability.
        return new MySequenceable(receivedData.num + 1, `send ${receivedData.str} succeed`)
-}
+   }
    
-export default class CalleeAbility extends Ability {
+   export default class CalleeAbility extends Ability {
        onCreate(want, launchParam) {
            try {
                this.callee.on(MSG_SEND_METHOD, sendMsgCallback)
@@ -138,20 +145,23 @@ export default class CalleeAbility extends Ability {
                console.error(TAG, `${MSG_SEND_METHOD} unregister failed with error ${JSON.stringify(error)}`)
            }
        }
-}
-```
+   }
+   ```
 
 ### Accessing the Callee Ability
-**1. Import the Ability module.**
-```ts
-import Ability from '@ohos.app.ability.UIAbility'
-```
-**2. Obtain the Caller object.**
+1. **Import the Ability module.**
+
+   ```ts
+   import Ability from '@ohos.app.ability.UIAbility';
+   ```
+
+2. **Obtain the Caller object.**
 
    The **context** attribute of the ability implements **startAbilityByCall** to obtain the **Caller** object for communication. The following example uses **this.context** to obtain the **context** attribute of the ability, uses **startAbilityByCall** to start the callee ability, obtain the **Caller** object, and register the **onRelease** listener of the caller ability. You need to implement processing based on service requirements. The code snippet is as follows:
-```ts
-// Register the onRelease listener of the caller ability.
-private regOnRelease(caller) {
+
+   ```ts
+   // Register the onRelease listener of the caller ability.
+   private regOnRelease(caller) {
        try {
            caller.on("release", (msg) => {
                console.log(`caller onRelease is called ${msg}`)
@@ -160,9 +170,9 @@ private regOnRelease(caller) {
        } catch (error) {
            console.log(`caller register OnRelease failed with ${error}`)
        }
-}
+   }
    
-async onButtonGetCaller() {
+   async onButtonGetCaller() {
        try {
            this.caller = await context.startAbilityByCall({
                bundleName: 'com.samples.CallApplication',
@@ -177,11 +187,13 @@ async onButtonGetCaller() {
        } catch (error) {
            console.log(`get caller failed with ${error}`)
        }
-}
-```
+   }
+   ```
+
    In the cross-device scenario, you need to specify the ID of the peer device. The code snippet is as follows:
-```ts
-async onButtonGetRemoteCaller() {
+
+   ```ts
+   async onButtonGetRemoteCaller() {
        var caller = undefined
        var context = this.context
    
@@ -202,13 +214,15 @@ async onButtonGetRemoteCaller() {
        }).catch((error) => {
            console.error(`get remote caller failed with ${error}`)
        })
-}
-```
+   }
+   ```
+
    Obtain the ID of the peer device from **DeviceManager**. Note that the **getTrustedDeviceListSync** API is open only to system applications. The code snippet is as follows:
-```ts
-import deviceManager from '@ohos.distributedHardware.deviceManager';
-var dmClass;
-function getRemoteDeviceId() {
+
+   ```ts
+   import deviceManager from '@ohos.distributedHardware.deviceManager';
+   var dmClass;
+   function getRemoteDeviceId() {
        if (typeof dmClass === 'object' && dmClass != null) {
            var list = dmClass.getTrustedDeviceListSync()
            if (typeof (list) == 'undefined' || typeof (list.length) == 'undefined') {
@@ -220,13 +234,15 @@ function getRemoteDeviceId() {
        } else {
            console.log("MainAbility onButtonClick getRemoteDeviceId err: dmClass is null")
        }
-}
-```
+   }
+   ```
+
    In the cross-device scenario, your application must also apply for the data synchronization permission from end users. The code snippet is as follows:
-```ts
-import abilityAccessCtrl from '@ohos.abilityAccessCtrl.d.ts';
 
-requestPermission() {
+   ```ts
+   import abilityAccessCtrl from '@ohos.abilityAccessCtrl.d.ts';
+   
+   requestPermission() {
        let context = this.context
        let permissions: Array<string> = ['ohos.permission.DISTRIBUTED_DATASYNC']
        let atManager = abilityAccessCtrl.createAtManager();
@@ -235,29 +251,32 @@ requestPermission() {
        }).catch((error) => {
            console.log("Failed to request permission from user with error: "+ JSON.stringify(error))
        })
-}
-```
-**3. Send agreed sequenceable data.**
+   }
+   ```
+
+3. **Send agreed sequenceable data.**
 
    The sequenceable data can be sent to the callee ability with or without a return value. The method and sequenceable data must be consistent with those of the callee ability. The following example describes how to send data to the callee ability. The code snippet is as follows:
-```ts
-const MSG_SEND_METHOD: string = 'CallSendMsg'
-async onButtonCall() {
+
+   ```ts
+   const MSG_SEND_METHOD: string = 'CallSendMsg'
+   async onButtonCall() {
        try {
            let msg = new MySequenceable(1, 'origin_Msg')
            await this.caller.call(MSG_SEND_METHOD, msg)
        } catch (error) {
            console.log(`caller call failed with ${error}`)
        }
-}
-```
+   }
+   ```
 
    In the following, **CallWithResult** is used to send data **originMsg** to the callee ability and assign the data processed by the **CallSendMsg** method to **backMsg**. The code snippet is as follows:
-```ts
-const MSG_SEND_METHOD: string = 'CallSendMsg'
-originMsg: string = ''
-backMsg: string = ''
-async onButtonCallWithResult(originMsg, backMsg) {
+
+   ```ts
+   const MSG_SEND_METHOD: string = 'CallSendMsg'
+   originMsg: string = ''
+   backMsg: string = ''
+   async onButtonCallWithResult(originMsg, backMsg) {
        try {
            let msg = new MySequenceable(1, originMsg)
            const data = await this.caller.callWithResult(MSG_SEND_METHOD, msg)
@@ -270,13 +289,15 @@ async onButtonCallWithResult(originMsg, backMsg) {
        } catch (error) {
            console.log(`caller callWithResult failed with ${error}`)
        }
-}
-```
-**4. Release the Caller object.**
+   }
+   ```
+
+4. **Release the Caller object.**
 
    When the **Caller** object is no longer required, use **release()** to release it. The code snippet is as follows:
-```ts
-releaseCall() {
+
+   ```ts
+   releaseCall() {
        try {
            this.caller.release()
            this.caller = undefined
@@ -284,5 +305,5 @@ releaseCall() {
        } catch (error) {
            console.log(`caller release failed with ${error}`)
        }
-}
-```
+   }
+   ```
\ No newline at end of file

en/application-dev/ability-deprecated/stage-formextension.md

@@ -135,7 +135,7 @@ To create a widget in the stage model, you need to implement lifecycle callbacks
   | Name   | Description                                                        | Data Type  | Default Value Allowed          |
   | ----------- | ------------------------------------------------------------ | ---------- | -------------------- |
   | name        | Name of the Extension ability. This field must be specified.                | String    | No                  |
-  | srcEntrance | Path of the Extension ability lifecycle code. This field must be specified.| String    | No                  |
+  | srcEnty     | Path of the Extension ability lifecycle code. This field must be specified.| String    | No                  |
   | description | Description of the Extension ability. The value can be a string or a resource index to descriptions in multiple languages.| String    | Yes (initial value: left empty)|
   | icon        | Index of the Extension ability icon file.                  | String    | Yes (initial value: left empty)|
   | label       | Descriptive information about the Extension ability presented externally. The value can be a string or a resource index to the description.| String    | Yes (initial value: left empty)|
@@ -150,7 +150,7 @@ To create a widget in the stage model, you need to implement lifecycle callbacks
      ```json
   "extensionAbilities": [{
       "name": "FormAbility",
-      "srcEntrance": "./ets/FormAbility/FormAbility.ts",
+      "srcEnty": "./ets/FormAbility/FormAbility.ts",
       "label": "$string:form_FormAbility_label",
       "description": "$string:form_FormAbility_desc",
       "type": "form",
@@ -242,7 +242,7 @@ You should override **onDestroy** to implement widget data deletion.
        }
 ```
 
-For details about how to implement persistent data storage, see [Lightweight Data Store Development](../database/database-preference-guidelines.md).
+For details about how to implement persistent data storage, see [Persisting Preferences Data](../database/data-persistence-by-preferences.md).
 
 The **Want** object passed in by the widget host to the widget provider contains a flag that specifies whether the requested widget is normal or temporary.
 

en/application-dev/ability-deprecated/stage-serviceextension.md

@@ -33,8 +33,8 @@ OpenHarmony does not support creation of a Service Extension ability for third-p
         "icon": "$media:icon",
         "description": "service",
         "type": "service",
-        "visible": true,
-        "srcEntrance": "./ets/ServiceExtAbility/ServiceExtAbility.ts"
+        "exported": true,
+        "srcEnty": "./ets/ServiceExtAbility/ServiceExtAbility.ts"
     }]
    ```
 

en/application-dev/application-dev-guide-for-gitee.md

@@ -24,6 +24,8 @@ First thing first, familiarize yourself with the two cornerstone frameworks in O
 All applications should be developed on top of these frameworks.
 
 Then, equip yourself for developing the key features, with the following guidelines:
+
+- [Web](web/web-component-overview.md)
 - [Notification](notification/Readme-EN.md)
 - [Window Manager](windowmanager/Readme-EN.md)
 - [WebGL](webgl/Readme-EN.md)
@@ -32,7 +34,8 @@ Then, equip yourself for developing the key features, with the following guideli
 - [Connectivity](connectivity/Readme-EN.md)
 - [Telephony Service](telephony/Readme-EN.md)
 - [Data Management](database/Readme-EN.md)
-- [Background Task Management](task-management/Readme-EN.md)
+- [File Management](file-management/Readme-EN.md)
+- [Task Management](task-management/Readme-EN.md)
 - [Device Management](device/Readme-EN.md)
 - [Device Usage Statistics](device-usage-statistics/Readme-EN.md)
 - [DFX](dfx/Readme-EN.md)
@@ -40,7 +43,6 @@ Then, equip yourself for developing the key features, with the following guideli
 - [Application Test](application-test/Readme-EN.md)
 - [IDL Specifications and User Guide](IDL/idl-guidelines.md)
 - [Using Native APIs in Application Projects](napi/Readme-EN.md)
-- [File Management](file-management/medialibrary-overview.md)
 
 ### Tools
 
@@ -66,7 +68,6 @@ They are organized as follows:
     - [Standard Library](reference/native-lib/third_party_libc/musl.md)
     - [Node_API](reference/native-lib/third_party_napi/napi.md)
 
-
 ### Readme
 
 For details about the principles and basic information of each subsystem, see the README file in [docs/en/readme](../readme).

en/application-dev/application-dev-guide.md

 # Application Development Overview
 
+> **NOTE**
+>
+> You are reading documents of OpenHarmony 3.2 Release. Obtain the [compatible SDK](../release-notes/OpenHarmony-v3.2-release.md#version-mapping) during your application development.
+
 The application development documents provide reference for you to develop applications using the APIs provided by OpenHarmony. They walk you through how to use JavaScript APIs to develop applications on the standard system.
 
 The documents are carefully organized as follows:
 
-### Getting Started
+## Getting Started
 
 [Here](quick-start/start-overview.md) you'll learn how to quickly get started with OpenHarmony application development.
 
@@ -12,7 +16,7 @@ Browse the documents on the instructions for quickly building your first applica
 
 Check out the development fundamentals, which comprise descriptions of the package structure configuration file for OpenHarmony applications and the instructions for use of resource files.
 
-### Development
+## Development
 
 To facilitate your application development, we provide development guidelines for key features.
 
@@ -24,48 +28,46 @@ First thing first, familiarize yourself with the two cornerstone frameworks in O
 All applications should be developed on top of these frameworks.
 
 Then, equip yourself for developing the key features, with the following guidelines:
+
+- [Web](web/web-component-overview.md)
 - [Notification](notification/notification-overview.md)
 - [Window Manager](windowmanager/window-overview.md)
 - [WebGL](webgl/webgl-overview.md)
-- [Media](media/audio-overview.md)
+- [Media](media/media-application-overview.md)
 - [Security](security/userauth-overview.md)
 - [Connectivity](connectivity/ipc-rpc-overview.md)
 - [Telephony Service](telephony/telephony-overview.md)
-- [Data Management](database/database-mdds-overview.md)
-- [Background Task Management](task-management/background-task-overview.md)
-- [Device Management](device/usb-overview.md)
+- [Data Management](database/data-mgmt-overview.md)
+- [File Management](file-management/file-management-overview.md)
+- [Task Management](task-management/background-task-overview.md)
+- [Device](device/usb-overview.md)
 - [Device Usage Statistics](device-usage-statistics/device-usage-statistics-overview.md)
 - [DFX](dfx/hiappevent-guidelines.md)
 - [Internationalization](internationalization/international-overview.md)
 - [Application Test](application-test/arkxtest-guidelines.md)
 - [OpenHarmony IDL Specifications and User Guide](IDL/idl-guidelines.md)
 - [Using Native APIs in Application Projects](napi/napi-guidelines.md)
-- [File Management](file-management/medialibrary-overview.md)
 
-### Tools
+## Tools
 
 DevEco Studio is a high-performance integrated development environment (IDE) recommended for developing OpenHarmony applications.
 [Here](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-deveco-studio-overview-0000001263280421) you can learn everything about DevEco Studio, including how to use this tool to create a project and sign, debug, and run an application.
 
-### Hands-On Tutorials
+## Hands-On Tutorials
 
 To make you better understand how functions work together and jumpstart your application development projects, we provide stripped-down, real-world [samples](https://gitee.com/openharmony/applications_app_samples/blob/OpenHarmony-3.2-Release/README.md) and [codelabs](https://gitee.com/openharmony/codelabs).
 
-### API References
+## API References
 
 API references encompass all components and APIs available in OpenHarmony, helping you use and integrate APIs more effectively.
 
 They are organized as follows:
 
-- [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/Readme-EN.md)
-
-- [Component Reference (JavaScript-based Web-like Development Paradigm)](reference/arkui-js/Readme-EN.md)
-
-- [JS Service Widget UI Components](reference/js-service-widget-ui/Readme-EN.md)
-
-- [JS and TS APIs](reference/apis/js-apis-ability-dataUriUtils.md)
-
+- [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/ts-components-summary.md)
+- [Component Reference (JavaScript-compatible Web-like Development Paradigm- ArkUI.Full)](reference/arkui-js/Readme-EN.md)
+- [Component Reference (JavaScript-compatible Web-like Development Paradigm- ArkUI.Lite)](reference/arkui-js-lite/Readme-EN.md)
+- [JS Service Widget UI Components](reference/js-service-widget-ui/js-service-widget-file.md)
+- [JS and TS APIs](reference/apis/development-intro.md)
 - Native APIs
   - [Standard Library](reference/native-lib/third_party_libc/musl.md)
   - [Node_API](reference/native-lib/third_party_napi/napi.md)
-

en/application-dev/application-models/Readme-EN.md

@@ -17,19 +17,43 @@
     - ExtensionAbility Component
       - [ExtensionAbility Component Overview](extensionability-overview.md)
       - [ServiceExtensionAbility](serviceextensionability.md)
-      - [DataShareExtensionAbility (for System Applications Only)](datashareextensionability.md)
-      - [FormExtensionAbility (Widget)](widget-development-stage.md)
       - [AccessibilityExtensionAbility](accessibilityextensionability.md)
       - [EnterpriseAdminExtensionAbility](enterprise-extensionAbility.md)
       - [InputMethodExtensionAbility](inputmethodextentionability.md)
-      - [WindowExtensionAbility](windowextensionability.md)
+      - [WindowExtensionAbility (for System Applications Only)](windowextensionability.md)
+    - Service Widget Development in Stage Model
+      - [Service Widget Overview](service-widget-overview.md)
+      - Developing an ArkTS Widget
+        - [ArkTS Widget Working Principles](arkts-ui-widget-working-principles.md)
+        - [ArkTS Widget Related Modules](arkts-ui-widget-modules.md)
+        - ArkTS Widget Development
+          - [Creating an ArkTS Widget](arkts-ui-widget-creation.md)
+          - [Configuring Widget Configuration Files](arkts-ui-widget-configuration.md)
+          - [Widget Lifecycle Management](arkts-ui-widget-lifecycle.md)
+          - Widget Page Development
+            - [Widget Page Capability Overview](arkts-ui-widget-page-overview.md)
+            - [Using Animations in the Widget](arkts-ui-widget-page-animation.md)
+            - [Applying Custom Drawing in the Widget](arkts-ui-widget-page-custom-drawing.md)
+          - Widget Event Development
+            - [Widget Event Capability Overview](arkts-ui-widget-event-overview.md)
+            - [Redirecting to a UIAbility Through the router Event](arkts-ui-widget-event-router.md)
+            - [Launching a UIAbility in the Background Through the call Event](arkts-ui-widget-event-call.md)
+            - [Updating Widget Content Through the message Event](arkts-ui-widget-event-formextensionability.md)
+            - [Updating Widget Content Through the router or call Event](arkts-ui-widget-event-uiability.md)
+          - Widget Data Interaction
+            - [Widget Data Interaction Overview](arkts-ui-widget-interaction-overview.md)
+            - [Configuring a Widget to Update Periodically](arkts-ui-widget-update-by-time.md)
+            - [Updating Local and Online Images in the Widget](arkts-ui-widget-image-update.md)
+            - [Updating Widget Content by State](arkts-ui-widget-update-by-status.md)
+            - [Updating Widget Content by Widget Host (for System Applications Only)](arkts-ui-widget-content-update.md)
+      - [Developing a JS Widget](js-ui-widget-development.md)
     - [AbilityStage Component Container](abilitystage.md)
     - [Context](application-context-stage.md)
     - Want
       - [Want Overview](want-overview.md)
       - [Matching Rules of Explicit Want and Implicit Want](explicit-implicit-want-mappings.md)
       - [Common action and entities Values](actions-entities.md)
-      - [Using Explicit Want to Start an Ability](ability-startup-with-explicit-want.md)
+      - [Using Explicit Want to Start an Application Component](ability-startup-with-explicit-want.md)
       - [Using Implicit Want to Open a Website](ability-startup-with-implicit-want.md)
       - [Using Want to Share Data Between Applications](data-share-via-want.md)
     - [Component Startup Rules](component-startup-rules.md)
@@ -37,8 +61,9 @@
       - [Continuation Overview](inter-device-interaction-hop-overview.md)
       - [Cross-Device Migration (for System Applications Only)](hop-cross-device-migration.md)
       - [Multi-device Collaboration (for System Applications Only)](hop-multi-device-collaboration.md)
-  - IPC
-    - [Process Model](process-model-stage.md)
+    - [Subscribing to System Environment Variable Changes](subscribe-system-environment-variable-changes.md)
+  - Process Model
+    - [Process Model Overview](process-model-stage.md)
     - Common Events
       - [Introduction to Common Events](common-event-overview.md)
       - Common Event Subscription
@@ -48,14 +73,16 @@
         - [Unsubscribing from Common Events](common-event-unsubscription.md)
       - [Publishing Common Events](common-event-publish.md)
     - [Background Services](background-services.md)
-  - Inter-Thread Communication
-    - [Thread Model](thread-model-stage.md)
+  - Thread Model
+    - [Thread Model Overview](thread-model-stage.md)
     - [Using Emitter for Inter-Thread Communication](itc-with-emitter.md)
     - [Using Worker for Inter-Thread Communication](itc-with-worker.md)
   - Mission Management
     - [Mission Management Scenarios](mission-management-overview.md)
-    - [Mission Management and Launch Type](mission-management-launch-type.md)
+    - [Mission and Launch Type](mission-management-launch-type.md)
     - [Page Stack and MissionList](page-mission-stack.md)
+    - [Setting the Icon and Name of a Mission Snapshot](mission-set-icon-name-for-task-snapshot.md)
+  - [Application Configuration File](config-file-stage.md)
 - FA Model Development
   - [FA Model Development Overview](fa-model-development-overview.md)
   - FA Mode Application Components
@@ -92,12 +119,12 @@
     - [Context](application-context-fa.md)
     - [Want](want-fa.md)
     - [Component Startup Rules](component-startup-rules-fa.md)
-  - IPC
-    - [Process Model](process-model-fa.md)
+  - Process Model
+    - [Process Model Overview](process-model-fa.md)
     - [Common Events](common-event-fa.md)
     - [Background Services](rpc.md)
-  - Inter-Thread Communication
-    - [Thread Model](thread-model-fa.md)
+  - Thread Model
+    - [Thread Model Overview](thread-model-fa.md)
     - [Inter-Thread Communication](itc-fa-overview.md)
   - [Mission Management](mission-management-fa.md)
 - Development of Component Interaction Between the FA Model and Stage Model

en/application-dev/application-models/ability-startup-with-explicit-want.md

-# Using Explicit Want to Start an Ability
+# Using Explicit Want to Start an Application Component
 
+When a user touches a button in an application, the application often needs to start a UIAbility component to complete a specific task. If the **abilityName** and **bundleName** parameters are specified when starting a UIAbility, then the explicit Want is used. 
 
-When a user touches a button in an application, the application often needs to start a UIAbility component to complete a specific task. The following describes how to use explicit Want to start a UIAbility component in an application.
+## Using Explicit Want
 
-
-## How to Develop
-
-1. In a project of the stage model, create an ability and a page, named **callerAbility** and **Index.ets**, respectively. Use the **windowStage.loadContent()** method in the **onWindowStageCreate** function in the **callerAbility.ts** file to bind the two.
-   
-   ```ts
-   // ...
-       // callerAbility.ts
-       onWindowStageCreate(windowStage) {
-           // Main window is created, set main page for this ability
-           console.info('[Demo] EntryAbility onWindowStageCreate')
-           // Bind callerAbility with a paged named Index
-           windowStage.loadContent('pages/Index')
-       }
-   // ...
-   ```
-
-2. Repeat the preceding operation to create another ability named **calleeAbility**.
-
-3. Add a button to the **Index.ets** page of **callerAbility**.
-   
-   ```ts
-   // ...
-     build() {
-       Row() {
-         Column() {
-           Text('hello')
-           .fontSize(50)
-           .fontWeight(FontWeight.Bold)
-           // A new button with will call explicitStartAbility() when clicked.
-           Button("CLICKME")
-           .onClick(this.explicitStartAbility) // For details about explicitStartAbility, see the sample code below.
-           // ...
-         }
-         .width('100%')
-       }
-       .height('100%')
-     }
-   // ...
-   ```
-
-4. Override the **onClick** method and use explicit Want to start **calleeAbility** in the method. The **bundleName** field can be obtained from the **AppScope > app.json5** file of the project. The **abilityName** field can be obtained from the **yourModuleName > src > main > module.json5** file of the corresponding module.
-   
-   ```ts
-   import common from '@ohos.app.ability.common';
-   
-   // ...
-     async explicitStartAbility() {
-       try {
-         // Explicit want with abilityName specified.
-         let want = {
-           deviceId: "",
-           bundleName: "com.example.myapplication",
-           abilityName: "calleeAbility"
-         };
-         let context = getContext(this) as common.UIAbilityContext;
-         await context.startAbility(want);
-         console.info(`explicit start ability succeed`);
-       } catch (error) {
-         console.info(`explicit start ability failed with ${error.code}`);
-       }
-     }
-   // ...
-   ```
-
-5. When you touch **CLICKME**, the corresponding page is displayed.
-
-   <img src="figures/startAbilityWtExplicitWant.PNG" alt="startAbilityWtExplicitWant" style="zoom: 80%;" />
+The user touches a button in the application to start the UIAbility component to complete a specific task. To start the UIAbility component in explicit Want mode, the **abilityName** and **bundleName** parameters must be specified. For details, see [Starting UIAbility in the Same Application](uiability-intra-device-interaction.md#starting-uiability-in-the-same-application).

en/application-dev/application-models/ability-startup-with-implicit-want.md

 # Using Implicit Want to Open a Website
 
-
-## Prerequisites
-
-One or more browsers are installed on your device.
-
-The **module.json5** of a browser application is as follows:
+This section uses the operation of using a browser to open a website as an example. It is assumed that one or more browser applications are installed on the device. To ensure that the browser application can work properly, configure the [module.json5 file](../quick-start/module-configuration-file.md) as follows:
 
 ```json
-"skills": [
+{
+  "module": {
+    ...
+    "abilities": [
+      {
+        ...
+        "skills": [
           {
             "entities": [
+              "entity.system.home",
               "entity.system.browsable"
-      // ...
+              ...
             ],
             "actions": [
+              "action.system.home",
               "ohos.want.action.viewData"
-        // ...
+              ...
             ],
             "uris": [
               {
@@ -24,54 +27,51 @@ The **module.json5** of a browser application is as follows:
                 "host": "www.test.com",
                 "port": "8080",
                 // Prefix matching is used.
-        "pathStartWith": "query",
-        "type": "text/*"
+                "pathStartWith": "query"
               },
               {
                 "scheme": "http",
-        // ...
+                ...
               }
-      // ...
+              ...
             ]
-  },
-]
+          }
+        ]
+      }
+    ]
+  }
+}
 ```
 
+In the initiator UIAbility, use implicit Want to start the browser application.
 
-## How to Develop
-
-1. Use the custom function **implicitStartAbility** to start an ability.
+```ts
+import common from '@ohos.app.ability.common';
 
-   ```ts
-       async implicitStartAbility() {
-           try {
-               let want = {
+function implicitStartAbility() {
+  let context = getContext(this) as common.UIAbilityContext;
+  let wantInfo = {
     // Uncomment the line below if you want to implicitly query data only in the specific bundle.
-                   // bundleName: "com.example.myapplication",
-                   "action": "ohos.want.action.viewData",
+    // bundleName: 'com.example.myapplication',
+    'action': 'ohos.want.action.viewData',
     // entities can be omitted.
-                   "entities": [ "entity.system.browsable" ],
-                   "uri": "https://www.test.com:8080/query/student",
-                   "type": "text/plain"
-               }
-               let context = getContext(this) as common.UIAbilityContext;
-               await context.startAbility(want)
-               console.info(`explicit start ability succeed`)
-           } catch (error) {
-               console.info(`explicit start ability failed with ${error.code}`)
+    'entities': ['entity.system.browsable'],
+    'uri': 'https://www.test.com:8080/query/student'
   }
-        }
-   ```
-
-     The matching process is as follows:
-   1. If **action** in the passed **want** parameter is specified and is included in **actions** under **skills**, the matching is successful.
-
-   2. If **entities** in the passed **want** parameter is specified and is included in **entities** under **skills**, the matching is successful.
+  context.startAbility(wantInfo).then(() => {
+    ...
+  }).catch((err) => {
+    ...
+  })
+}
+```
 
-   3. If **uri** in the passed **want** parameter is included in **uris** under **skills**, which is concatenated into `https://www.test.com:8080/query*` (where \* is a wildcard), the matching is successful.
+The matching process is as follows:
 
-   4. If **type** in the passed **want** parameter is specified and is included in **type** under **skills**, the matching is successful.
+1. If **action** in the passed **want** parameter is specified and is included in **actions** under **skills** of the application component to match, the matching is successful.
+2. If **entities** in the passed **want** parameter is specified and is included in **entities** under **skills** of the application component to match, the matching is successful.
+3. If **uri** in the passed **want** parameter is included in **uris** under **skills** of the application component to match, which is concatenated into https://www.test.com:8080/query* (where * is a wildcard), the matching is successful.
 
-2. When there are multiple matching applications, a dialog box is displayed for you to select one of them. 
+If there are multiple matching applications, the system displays a dialog box for you to select one of them. The following figure shows an example.
 
-   ![stage-want1](figures/stage-want1.png)
+![](figures/ability-startup-with-implicit-want1.png)
\ No newline at end of file

en/application-dev/application-models/abilitystage.md

@@ -12,7 +12,7 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
 
 1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **myabilitystage**.
 
-2. In the **myabilitystage** directory, right-click and choose **New > ts File** to create a file named **MyAbilityStage.ts**.
+2. In the **myabilitystage** directory, right-click and choose **New > TypeScript File** to create a file named **MyAbilityStage.ts**.
 
 3. Open the **MyAbilityStage.ts** file, and import the dependency package of AbilityStage. Customize a class that inherits from AbilityStage, and add the required lifecycle callbacks. The following code snippet adds the **onCreate()** lifecycle callback.
    
@@ -24,12 +24,23 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
        // When the HAP of the application is loaded for the first time, initialize the module.
      }
      onAcceptWant(want) {
-           // Triggered only for the ability with the specified launch type.
+       // Triggered only for the UIAbility with the specified launch type.
        return "MyAbilityStage";
      }
    }
    ```
    
+4. In the [module.json5 file](../quick-start/module-configuration-file.md), set **srcEntry** to specify the code path of the module as the entry for loading the HAP.
+   ```json
+   {
+     "module": {
+       "name": "entry",
+       "type": "entry",
+       "srcEntry": "./ets/myabilitystage/MyAbilityStage.ts",
+       ...
+     }
+   }
+   ```
 
 [AbilityStage](../reference/apis/js-apis-app-ability-abilityStage.md) has the lifecycle callback [onCreate()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageoncreate) and the event callbacks [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant), [onConfigurationUpdated()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonconfigurationupdate), and [onMemoryLevel()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonmemorylevel).
 
@@ -54,4 +65,3 @@ When an application is switched to the background, it is cached in the backgroun
     }
   }
   ```
-

en/application-dev/application-models/accessibilityextensionability.md

-# AccessibilityExtensionAbility Development
+# AccessibilityExtensionAbility
 
 The **AccessibilityExtensionAbility** module provides accessibility extension capabilities based on the **ExtensionAbility** framework. You can develop your accessibility applications by applying the **AccessibilityExtensionAbility** template to enhance usability.
 
@@ -12,11 +12,28 @@ The **AccessibilityExtensionAbility** module provides accessibility extension ca
 
 This document is organized as follows:
 
-- [Creating an AccessibilityExtAbility File](#creating-an-accessibility-extension-service)
+- [AccessibilityExtensionAbility Overview](#accessibilityextensionability-overview)
+- [Creating an Accessibility Extension Service](#creating-an-accessibility-extension-service)
 - [Processing an Accessibility Event](#processing-an-accessibility-event)
 - [Declaring Capabilities of Accessibility Extension Services](#declaring-capabilities-of-accessibility-extension-services)
 - [Enabling a Custom Accessibility Extension Service](#enabling-a-custom-accessibility-extension-service)
 
+## AccessibilityExtensionAbility Overview
+
+Accessibility is about giving equal access to everyone so that they can access and use information equally and conveniently under any circumstances. It helps narrow the digital divide between people of different classes, regions, ages, and health status in terms of information understanding, information exchange, and information utilization, so that they can participate in social life more conveniently and enjoy the benefits of technological advances.
+
+AccessibilityExtensionAbility is an accessibility extension service framework. It allows you to develop your own extension services and provides a standard mechanism for exchanging information between applications and extension services. You can make use of the provided capabilities and APIs to develop accessibility features for users with disabilities or physical limitations. For example, you can develop a screen reader for users with vision impairments.
+
+Below shows the AccessibilityExtensionAbility framework.
+
+![AccessibilityFramework](figures/AccessibilityFramework.png)
+
+1. Accessibility app: extension service application developed based on the AccessibilityExtensionAbility framework, for example, a screen reader application.
+2. Target app: application assisted by the accessibility app.
+3. AccessibilityAbilityManagerService (AAMS): main service of the AccessibilityExtensionAbility framework, which is used to manage the lifecycle of accessibility apps and provide a bridge for information exchange between accessibility apps and target apps.
+4. AccessibilityAbility (AAkit): ability that is used by the accessibility app to build an extension service ability operating environment and that provides interfaces for the accessibility app to query and operate the target app, including performing click/long press operations.
+5. AccessibilitySystemAbilityClient (ASACkit): used by the target app to send accessibility events, such as content change events, to AAMS, and respond to the instructions (such as performing click/long press operations) sent by the accessibility app through AAMS.
+
 ## Creating an Accessibility Extension Service
 
 You can create an accessibility extension service by creating a project from scratch or adding the service to an existing project.
@@ -37,15 +54,15 @@ import AccessibilityExtensionAbility from '@ohos.application.AccessibilityExtens
 
 class AccessibilityExtAbility extends AccessibilityExtensionAbility {
     onConnect() {
-        console.log('AccessibilityExtAbility onConnect');
+        console.info('AccessibilityExtAbility onConnect');
     }
 
     onDisconnect() {
-        console.log('AccessibilityExtAbility onDisconnect');
+        console.info('AccessibilityExtAbility onDisconnect');
     }
 
     onAccessibilityEvent(accessibilityEvent) {
-        console.log('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
+        console.info('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
     }
 }
 
@@ -66,9 +83,9 @@ You can process the service logic for accessibility events in the **onAccessibil
 
 ```typescript
 onAccessibilityEvent(accessibilityEvent) {
-    console.log('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
+    console.info('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
     if (accessibilityEvent.eventType === 'pageStateUpdate') {
-        console.log('AccessibilityExtAbility onAccessibilityEvent: pageStateUpdate');
+        console.info('AccessibilityExtAbility onAccessibilityEvent: pageStateUpdate');
         // TODO: Develop custom logic.
     }
 }
@@ -79,13 +96,13 @@ You can also process physical key events in the accessibility extension service.
 
 ## Declaring Capabilities of Accessibility Extension Services
 
-After developing the custom logic for an accessibility extension service, you must add the configuration information of the service to the corresponding module-level **module.json5** file in the project directory. In the file, the **srcEntrance** tag indicates the path to the accessibility extension service. Make sure the value of the **type** tag is fixed at **accessibility**. Otherwise, the connection to the service will fail.
+After developing the custom logic for an accessibility extension service, you must add the configuration information of the service to the corresponding module-level **module.json5** file in the project directory. In the file, the **srcEntry** tag indicates the path to the accessibility extension service. Make sure the value of the **type** tag is fixed at **accessibility**. Otherwise, the connection to the service will fail.
 
 ```json
 "extensionAbilities": [
   {
     "name": "AccessibilityExtAbility",
-    "srcEntrance": "./ets/AccessibilityExtAbility/AccessibilityExtAbility.ts",
+    "srcEntry": "./ets/AccessibilityExtAbility/AccessibilityExtAbility.ts",
     "label": "$string:MainAbility_label",
     "description": "$string:MainAbility_desc",
     "type": "accessibility",
@@ -116,3 +133,4 @@ To enable or disable an accessibility extension service, run the following comma
 In the preceding commands, **AccessibilityExtAbility** indicates the name of the accessibility extension service, **com.example.demo** indicates the bundle name, and **rg** indicates the capabilities (**r** is short for retrieve).
 
 If the service is enabled or disabled successfully, the message "enable ability successfully" or "disable ability successfully" is displayed.
+

en/application-dev/application-models/actions-entities.md

 # Common action and entities Values
 
-The [action](../reference/apis/js-apis-ability-wantConstant.md#wantconstantaction) field specifies the common operation (such as viewing, sharing, and application details) to be performed by the caller. In implicit Want, you can define this field and use it together with **uri** or **parameters** to specify the operation to be performed on the data, for example, viewing URI data. For example, if the URI is a website and the action is **ohos.want.action.viewData**, the ability that supports website viewing is matched. Declaring the **action** field in Want indicates that the invoked application should support the declared operation. The **actions** field under **skills** in the configuration file indicates the operations supported by the application.
+The **action** field specifies the common operation (such as viewing, sharing, and application details) to be performed by the caller. In implicit [Want](../reference/apis/js-apis-app-ability-want.md), you can define this field and use it together with **uri** or **parameters** to specify the operation to be performed on the data, for example, viewing URI data. For example, if the URI is a website and the action is **ohos.want.action.viewData**, the application component that supports website viewing is matched. Declaring the **action** field in [Want](../reference/apis/js-apis-app-ability-want.md) indicates that the invoked application is expected to support the declared operation. The **actions** field under **skills** in the configuration file indicates the operations supported by the application.
 
-
-**Common action Values**
+The following **action** values are available:
 
 
 - **ACTION_HOME**: action of starting the application entry component. It must be used together with **ENTITY_HOME**. The application icon on the home screen is an explicit entry component. Users can touch the icon to start the entry component. Multiple entry components can be configured for an application.
@@ -14,14 +13,13 @@ The [action](../reference/apis/js-apis-ability-wantConstant.md#wantconstantactio
 
 - **ACTION_VIEW_MULTIPLE_DATA**: action of launching the UI for sending multiple data records.
 
-The [entities](../reference/apis/js-apis-ability-wantConstant.md#wantconstantentity) field specifies the additional category information (such as browser and video player) of the target ability. It is a supplement to **action** in implicit Want. You can define this field to filter application categories, for example, browser. Declaring the **entities** field in Want indicates that the invoked application should belong to the declared category. The **entities** field under **skills** in the configuration file indicates the categories supported by the application.
-
+The **entities** field specify the category information (such as browser and video player) of the target application component. It is a supplement to **action** in implicit Want. You can define this field to filter application categories, for example, browser. Declaring the **entities** field in Want indicates that the invoked application should belong to the declared category. The **entities** field under **skills** in the configuration file indicates the categories supported by the application.
 
-**Common entities Values**
+The following **entities** values are available:
 
 
 - **ENTITY_DEFAULT**: default category, which is meaningless.
 
-- **ENTITY_HOME**: abilities with an icon displayed on the home screen.
+- **ENTITY_HOME**: application components with an icon displayed on the home screen.
 
 - **ENTITY_BROWSABLE**: browser type.

en/application-dev/application-models/app-deviceconfig-switch.md

@@ -22,7 +22,7 @@ OpenHarmony has reconstructed the [deviceConfig](../quick-start/deviceconfig-str
 | deviceConfig in the FA Model| Description| Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | deviceConfig| Device information.| / | This tag is no longer available in the stage model. In the stage model, device information is configured under the **app** tag.|
-| process | Name of the process running the application or ability. If the **process** attribute is configured in the **deviceConfig** tag, all abilities of the application run in this process. You can set the **process** attribute for a specific ability in the **abilities** attribute, so that the ability can run in the particular process.| / | The stage model does not support the configuration of process names.|
+| process | Name of the process running the application or UIAbility. If the **process** attribute is configured in the **deviceConfig** tag, all UIAbilities of the application run in this process. You can set the **process** attribute for a specific UIAbility in the **abilities** attribute, so that the UIAbility can run in the particular process.| / | The stage model does not support the configuration of process names.|
 | keepAlive | Whether the application is always running. This attribute applies only to system applications and does not take effect for third-party applications.| / | The stage model does not support changing of the model control mode for system applications.|
 | supportBackup | Whether the application supports data backup and restore.| / | This configuration is not supported in the stage model.|
 | compressNativeLibs | Whether the **libs** libraries are packaged in the HAP file after being compressed.| / | This configuration is not supported in the stage model.|

en/application-dev/application-models/application-component-configuration-fa.md

@@ -22,7 +22,7 @@ When developing an application, you may need to configure certain tags to identi
           "actions": ["action.system.home"]
         }
       ]
-      // ...
+      ...
     }
   ```
 

en/application-dev/application-models/application-component-configuration-stage.md

 # Application- or Component-Level Configuration (Stage Model)
 
+When developing an application, you may need to configure certain tags to identify the application, such as the bundle name and application icon. This topic describes key tags that need to be configured during application development.
 
-When developing an application, you may need to configure certain tags to identify the application, such as the bundle name and application icon. This topic describes key tags that need to be configured during application development. Icons and labels are usually configured together. There is the application icon, application label, entry icon, and entry label, which correspond to the **icon** and **label** fields in the [app.json5 file](../quick-start/app-configuration-file.md) and [module.json5 file](../quick-start/module-configuration-file.md). The application icon and label are used in **Settings**. For example, they are displayed in the application list in **Settings**. The entry icon is displayed on the device's home screen after the application is installed. The entry icon maps to a [UIAbility](uiability-overview.md) component. Therefore, an application can have multiple entry icons and labels. When you touch one of them, the corresponding UIAbility page is displayed.
+Icons and labels are usually configured together. There is the application icon, application label, entry icon, and entry label, which correspond to the **icon** and **label** fields in the [app.json5 file](../quick-start/app-configuration-file.md) and [module.json5 file](../quick-start/module-configuration-file.md).
 
+The application icon and label are used in **Settings**. For example, they are displayed in the application list in **Settings**. The entry icon is displayed on the device's home screen after the application is installed. The entry icon maps to a [UIAbility](uiability-overview.md) component. Therefore, an application can have multiple entry icons and entry labels. When you touch one of them, the corresponding UIAbility page is displayed.
 
-  **Figure 1** Icons and labels 
+**Figure 1** Icons and labels
 
 ![application-component-configuration-stage](figures/application-component-configuration-stage.png)
 
@@ -26,7 +28,7 @@ When developing an application, you may need to configure certain tags to identi
     "app": {
       "icon": "$media:app_icon",
       "label": "$string:app_name"
-        // ...
+      ...
     }
   }
   ```
@@ -40,7 +42,7 @@ When developing an application, you may need to configure certain tags to identi
   ```json
   {
     "module": {
-      // ...
+      ...
       "abilities": [
         {
           // The information starting with $ is the resource value.
@@ -61,6 +63,35 @@ When developing an application, you may need to configure certain tags to identi
     }
   }
   ```
+  OpenHarmony strictly controls applications without icons to prevent malicious applications from deliberately configuring no icon to block uninstall attempts.
+
+  To hide an application icon from the home screen, you must configure the **AllowAppDesktopIconHide** privilege. For details, see [Application Privilege Configuration Guide](../../device-dev/subsystems/subsys-app-privilege-config-guide.md). The rules for displaying the entry icon and entry label are as follows:
+
+  1. The HAP file contains UIAbility configuration.
+    * An entry icon is set in the **abilities** field of the **module.json5** file.
+      * The application does not have the privilege to hide its icon from the home screen.
+        * The system uses the icon configured for the UIAbility as the entry icon and displays it on the home screen. Touching this icon will direct the user to the home page of the UIAbility.
+        * The system uses the label configured for the UIAbility as the entry label and displays it on the home screen. If no label is configured, the system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+      * The application has the privilege to hide its icon from the home screen.
+        * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+    * No entry icon is set in the **abilities** field of the **module.json5** file.
+      * The application does not have the privilege to hide its icon from the home screen.
+        * The system uses the icon specified in the **app.json5** file as the entry icon and displays it on the home screen. Touching this icon will direct the user to the application details page, as shown below.
+        * The system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+      * The application has the privilege to hide its icon from the home screen.
+        * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+
+  2. The HAP file does not contain UIAbility configuration.
+    * The application does not have the privilege to hide its icon from the home screen.
+      * The system uses the icon specified in the **app.json5** file as the entry icon and displays it on the home screen. Touching this icon will direct the user to the application details page, as shown below.
+      * The system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+    * The application has the privilege to hide its icon from the home screen.
+      * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+
+  **Figure 2** Application details page
+
+  ![Application details page](figures/application_details.jpg)
+
 - **Configuring application version declaration**
   
   To declare the application version, configure the **versionCode** and **versionName** fields in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. **versionCode** specifies the version number of the application. The value is a 32-bit non-negative integer. It is used only to determine whether a version is later than another version. A larger value indicates a later version. **versionName** provides the text description of the version number.

en/application-dev/application-models/application-model-description.md

@@ -12,7 +12,6 @@ Along its evolution, OpenHarmony has provided two application models:
 The stage model is designed based on the following considerations, which make it become the recommended model:
 
 1. **Designed for complex applications**
-   
    - In the stage model, multiple application components share an ArkTS engine (VM running the programming language ArkTS) instance, making it easy for application components to share objects and status while requiring less memory.
    - The object-oriented development mode makes the code of complex applications easy to read, maintain, and scale.
 
@@ -38,7 +37,7 @@ The stage model is designed based on the following considerations, which make it
 
    The stage model redefines the boundary of application capabilities to well balance application capabilities and system management costs.
 
-   - Diverse application components (such as widgets and input methods) for specific scenarios.
+   - Diverse application components (such as service widgets and input methods) for specific scenarios.
    - Standardized background process management. To deliver a better user experience, the stage model manages background application processes in a more orderly manner. Applications cannot reside in the background randomly, and their background behavior is strictly managed to minimize malicious behavior.
 
 
@@ -52,8 +51,8 @@ The table below describes their differences in detail.
 
 | Item| FA model| Stage model|
 | -------- | -------- | -------- |
-| **Application component**| 1. Component classification<br>![fa-model-component](figures/fa-model-component.png)<br/>- PageAbility: has the UI and supports user interaction For details, see [PageAbility Component Overview](pageability-overview.md).<br>- ServiceAbility: provides background services and has no UI. For details, see [ServiceAbility Component Overview](serviceability-overview.md).<br>- DataAbility: provides the data sharing capability and has no UI. For details, see [DataAbility Component Overview](dataability-overview.md).<br>2. Development mode<br>Application components are specified by exporting anonymous objects and fixed entry files. You cannot perform derivation. It is inconvenient for capability expansion. | 1. Component classification<br>![stage-model-component](figures/stage-model-component.png)<br/> - UIAbility: has the UI and supports user interaction. For details, see [UIAbility Component Overview](uiability-overview.md).<br>- ExtensionAbility: provides extension capabilities (such as widget and input methods) for specific scenarios. For details, see [ExtensionAbility Component Overview](extensionability-overview.md).<br>2. Development mode<br>The object-oriented mode is used to provide open application components as classes. You can derive application components for capability expansion. |
-| **Process model**| There are two types of processes:<br>1. Main process<br>2. Rendering process<br>For details, see [Process Model (FA Model)](process-model-fa.md).| There are three types of processes:<br>1. Main process<br>2. ExtensionAbility process<br>3. Rendering process<br>For details, see [Process Model (Stage Model)](process-model-stage.md).|
-| **Thread model**| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and each application component instance runs in an independent ArkTS engine instance.<br>2. Thread model<br>Each ArkTS engine instance is created on an independent thread (non-main thread). The main thread does not have an ArkTS engine instance.<br>3. Intra-process object sharing: not supported.<br>For details, see [Thread Model (FA Model)](thread-model-fa.md).| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and all application component instances share one ArkTS engine instance.<br>2. Thread model<br>The ArkTS engine instance is created on the main thread.<br>3. Intra-process object sharing: supported.<br>For details, see [Thread Model (Stage Model)](thread-model-stage.md).|
+| **Application component**| 1. Component classification<br>![fa-model-component](figures/fa-model-component.png)<br>- PageAbility: has the UI and supports user interaction For details, see [PageAbility Component Overview](pageability-overview.md).<br>- ServiceAbility: provides background services and has no UI. For details, see [ServiceAbility Component Overview](serviceability-overview.md).<br>- DataAbility: provides the data sharing capability and has no UI. For details, see [DataAbility Component Overview](dataability-overview.md).<br>2. Development mode<br>Application components are specified by exporting anonymous objects and fixed entry files. You cannot perform derivation. It is inconvenient for capability expansion.| 1. Component classification<br>![stage-model-component](figures/stage-model-component.png)<br>- UIAbility: has the UI and supports user interaction. For details, see [UIAbility Component Overview](uiability-overview.md).<br>- ExtensionAbility: provides extension capabilities (such as widget and input methods) for specific scenarios. For details, see [ExtensionAbility Component Overview](extensionability-overview.md).<br>2. Development mode<br>The object-oriented mode is used to provide open application components as classes. You can derive application components for capability expansion.|
+| **Process model**| There are two types of processes:<br>1. Main process<br>2. Rendering process<br>For details, see [Process Model Overview (FA Model)](process-model-fa.md). | There are three types of processes:<br>1. Main process<br>2. ExtensionAbility process<br>3. Rendering process<br>For details, see [Process Model Overview (Stage Model)](process-model-stage.md). |
+| **Thread model**| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and each application component instance runs in an independent ArkTS engine instance.<br>2. Thread model<br>Each ArkTS engine instance is created on an independent thread (non-main thread). The main thread does not have an ArkTS engine instance.<br>3. Intra-process object sharing: not supported.<br>For details, see [Thread Model Overview (FA Model)](thread-model-fa.md). | 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and all application component instances share one ArkTS engine instance.<br>2. Thread model<br>The ArkTS engine instance is created on the main thread.<br>3. Intra-process object sharing: supported.<br>For details, see [Thread Model Overview (Stage Model)](thread-model-stage.md). |
 | **Mission management model**| - A mission is created for each PageAbility component instance.<br>- Missions are stored persistently until the number of missions exceeds the maximum (customized based on the product configuration) or users delete missions.<br>- PageAbility components do not form a stack structure.<br>For details, see [Mission Management Scenarios](mission-management-overview.md).| - A mission is created for each UIAbility component instance.<br>- Missions are stored persistently until the number of missions exceeds the maximum (customized based on the product configuration) or users delete missions.<br>- UIAbility components do not form a stack structure.<br>For details, see [Mission Management Scenarios](mission-management-overview.md).|
 | **Application configuration file**| The **config.json** file is used to describe the application, HAP, and application component information.<br>For details, see [Application Configuration File Overview (FA Model)](../quick-start/application-configuration-file-overview-fa.md).| The **app.json5** file is used to describe the application information, and the **module.json5** file is used to describe the HAP and application component information.<br>For details, see [Application Configuration File Overview (Stage Model)](../quick-start/application-configuration-file-overview-stage.md).|

en/application-dev/application-models/arkts-ui-widget-configuration.md

+# Configuring Widget Configuration Files
+
+
+Widget-related configuration includes **FormExtensionAbility** configuration and widget configuration.
+
+
+1. Configure FormExtensionAbility information under **extensionAbilities** in the [module.json5 file](../quick-start/module-configuration-file.md). For a FormExtensionAbility, you must specify **metadata**. Specifically, set **name** to **ohos.extension.form** (fixed), and set **resource** to the index of the widget configuration information.
+
+   Example configuration:
+
+   
+   ```json
+   {
+     "module": {
+       ...
+       "extensionAbilities": [
+         {
+           "name": "EntryFormAbility",
+           "srcEntry": "./ets/entryformability/EntryFormAbility.ts",
+           "label": "$string:EntryFormAbility_label",
+           "description": "$string:EntryFormAbility_desc",
+           "type": "form",
+           "metadata": [
+             {
+               "name": "ohos.extension.form",
+               "resource": "$profile:form_config"
+             }
+           ]
+         }
+       ]
+     }
+   }
+   ```
+
+2. Configure the widget configuration information. In the **metadata** configuration item of FormExtensionAbility, you can specify the resource index of specific configuration information of the widget. For example, if resource is set to **$profile:form_config**, **form_config.json** in the **resources/base/profile/** directory of the development view is used as the profile configuration file of the widget. The following table describes the internal field structure.
+
+   **Table 1** form_config.json file
+
+   | Field| Description| Data Type| Default Value Allowed|
+   | -------- | -------- | -------- | -------- |
+   | name | Class name of the widget. The value is a string with a maximum of 127 bytes.| String| No|
+   | description | Description of the widget. The value can be a string or a resource index to descriptions in multiple languages. The value is a string with a maximum of 255 bytes.| String| Yes (initial value: left empty)|
+   | src | Full path of the UI code corresponding to the widget. For an ArkTS widget, the full path must contain the widget file name extension, for example, **./ets/widget/pages/WidgetCard.ets**. For a JS widget, the full path does not need to contain the widget file name extension, for example, **./js/widget/pages/WidgetCard**.| String| No|
+   | uiSyntax | Type of the widget.<br>- **arkts**: ArkTS widget<br>- **hml**: JS widget| String| Yes (initial value: **hml**)|
+   | window | Window-related configurations.| Object| Yes|
+   | isDefault | Whether the widget is a default one. Each UIAbility has only one default widget.<br>- **true**: The widget is the default one.<br>- **false**: The widget is not the default one.| Boolean| No|
+   | colorMode | Color mode of the widget.<br>- **auto**: auto-adaptive color mode<br>- **dark**: dark color mode<br>- **light**: light color mode| String| Yes (initial value: **auto**)|
+   | supportDimensions | Grid styles supported by the widget.<br>- **1 * 2**: indicates a grid with one row and two columns.<br>- **2 * 2**: indicates a grid with two rows and two columns.<br>- **2 * 4**: indicates a grid with two rows and four columns.<br>- **4 * 4**: indicates a grid with four rows and four columns.| String array| No|
+   | defaultDimension | Default grid style of the widget. The value must be available in the **supportDimensions** array of the widget.| String| No|
+   | updateEnabled | Whether the widget can be updated periodically.<br>- **true**: The widget can be updated at a specified interval (**updateDuration**) or at the scheduled time (**scheduledUpdateTime**). **updateDuration** takes precedence over **scheduledUpdateTime**.<br>- **false**: The widget cannot be updated periodically.| Boolean| No|
+   | scheduledUpdateTime | Scheduled time to update the widget. The value is in 24-hour format and accurate to minute.<br>**NOTE**<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| String| Yes (initial value: The widget cannot be updated periodically.）|
+   | updateDuration | Interval to update the widget. The value is a natural number, in the unit of 30 minutes.<br>If the value is **0**, this field does not take effect.<br>If the value is a positive integer *N*, the interval is calculated by multiplying *N* and 30 minutes.<br>**NOTE**<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| Number| Yes (initial value: **0**)|
+   | formConfigAbility | Link to a specific page of the application. The value is a URI.| String| Yes (initial value: left empty)|
+   | formVisibleNotify | Whether the widget is allowed to use the widget visibility notification.| String| Yes (initial value: left empty)|
+   | metadata | Metadata of the widget. This field contains the array of the **customizeData** field.| Object| Yes (initial value: left empty)|
+
+   Example configuration:
+
+   
+   ```json
+   {
+     "forms": [
+       {
+         "name": "widget",
+         "description": "This is a service widget.",
+         "src": "./ets/widget/pages/WidgetCard.ets",
+         "uiSyntax": "arkts",
+         "window": {
+           "designWidth": 720,
+           "autoDesignWidth": true
+         },
+         "colorMode": "auto",
+         "isDefault": true,
+         "updateEnabled": true,
+         "scheduledUpdateTime": "10:30",
+         "updateDuration": 1,
+         "defaultDimension": "2*2",
+         "supportDimensions": [
+           "2*2"
+         ]
+       }
+     ]
+   }
+   ```

en/application-dev/application-models/arkts-ui-widget-content-update.md

+# Updating Widget Content by Widget Host (for System Applications Only)
+
+
+Widgets that are updated periodically are subject to the scheduled time or interval settings. To offer more flexible updates, the widget host can provide a button to proactively trigger a widget update. Specifically, the widget host calls the [requestForm](../reference/apis/js-apis-app-form-formHost.md#requestform) API to request a widget update. The system then calls the [onUpdateForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform) lifecycle callback in the FormExtensionAbility of the widget provider. In the callback, the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) API can be used to update the widget content. For details about the **onUpdateForm** lifecycle callback, see [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md).
+
+```ts
+import formHost from '@ohos.app.form.formHost';
+
+@Entry()
+@Component
+struct WidgetCard {
+  formId = ...; // Widget ID
+
+  build() {
+    Button (`Update Widget`)
+      .type(ButtonType.Capsule)
+      .width('50%')
+      .height(50)
+      .onClick(() => {
+        console.info('FormAbility update form click');
+        // formId is the ID of the widget to be updated.
+        formHost.requestForm(this.formId.toString()).then(() => {
+          console.info('Succeeded in requestForming.');
+        });
+      })
+
+    ...
+  }
+}
+```

en/application-dev/application-models/arkts-ui-widget-creation.md

+# Creating an ArkTS Widget
+
+To create an ArkTS widget in an existing application project, perform the following steps:
+
+1. Create a widget.
+
+   ![WidgetProjectCreate1](figures/WidgetProjectCreate1.png)
+
+2. Select a widget template based on the actual service scenario.
+
+   ![WidgetProjectCreate2](figures/WidgetProjectCreate2.png)
+
+3. Set **Language** to **ArkTS** and click **Finish**.
+
+   ![WidgetProjectCreate3](figures/WidgetProjectCreate3.png)
+
+After an ArkTS widget is created, the following widget-related files are added to the project directory: **EntryFormAbility.ts** (widget lifecycle management file), **WidgetCard.ets** (widget page file), and **form_config.json** (widget configuration file).
+
+![WidgetProjectView](figures/WidgetProjectView.png)

en/application-dev/application-models/arkts-ui-widget-event-call.md

+# Launching a UIAbility in the Background Through the call Event
+
+
+There may be cases you want to provide in a widget access to features available in your application when it is running in the foreground, for example, the play, pause, and stop buttons in a music application widget. This is where the **call** capability of the **postCardAction** API comes in handy. This capability, when used in a widget, can start the specified UIAbility of the widget provider in the background. It also allows the widget to call the specified method of the application and transfer data so that the application, while in the background, can behave accordingly in response to touching of the buttons on the widget.
+
+
+Generally, buttons are used to trigger the **call** event. Below is an example.
+
+
+- In this example, two buttons are laid out on the widget page. When one button is clicked, the **postCardAction** API is called to send a **call** event to the target UIAbility. Note that the **method** parameter in the API indicates the method to call in the target UIAbility. It is mandatory and of the string type.
+  
+  ```ts
+  @Entry
+  @Component
+  struct WidgetCard {
+    build() {
+      Column() {
+        Button ('Feature A')
+          .margin('20%')
+          .onClick(() => {
+            console.info('call EntryAbility funA');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funA' // Set the name of the method to call in the EntryAbility.
+              }
+            });
+          })
+  
+        Button ('Feature B')
+          .margin('20%')
+          .onClick(() => {
+            console.info('call EntryAbility funB');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funB', // Set the name of the method to call in the EntryAbility.
+                'num': 1 // Set other parameters to be transferred.
+              }
+            });
+          })
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+
+- The UIAbility receives the **call** event and obtains the transferred parameters. It then executes the target method specified by the **method** parameter. Other data can be obtained in readString mode. Listen for the method required by the **call** event in the **onCreate** callback of the UIAbility.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  
+  function FunACall(data) {
+    // Obtain all parameters transferred in the call event.
+    console.log('FunACall param:' + JSON.stringify(data.readString()));
+    return null;
+  }
+  
+  function FunBCall(data) {
+    console.log('FunACall param:' + JSON.stringify(data.readString()));
+    return null;
+  }
+  
+  export default class CameraAbility extends UIAbility {
+    // If the UIAbility is started for the first time, the onCreate lifecycle callback is triggered after the call event is received.
+    onCreate(want, launchParam) {
+      try {
+        // Listen for the method required by the call event.
+        this.callee.on('funA', FunACall);
+        this.callee.on('funB', FunBCall);
+      } catch (error) {
+            console.log('register failed with error. Cause: ' + JSON.stringify(error));
+      }
+    }
+  
+    // Deregister the listener when the process exits.
+    onDestroy() {
+        try {
+            this.callee.off('funA');
+            this.callee.off('funB');
+        } catch (error) {
+            console.log('register failed with error. Cause: ' + JSON.stringify(error));
+        }
+    }
+  };
+  ```

en/application-dev/application-models/arkts-ui-widget-event-formextensionability.md

+# Updating Widget Content Through the message Event
+
+
+On the widget page, the **postCardAction** API can be used to trigger a message event to start a FormExtensionAbility, which then updates the widget content. The following is an example of this widget update mode.
+
+
+- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the event to the FormExtensionAbility.
+  
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    @LocalStorageProp('title') title: string = 'init';
+    @LocalStorageProp('detail') detail: string = 'init';
+  
+    build() {
+      Column() {
+        Button ('Update')
+          .onClick(() => {
+            postCardAction(this, {
+              'action': 'message',
+              'params': {
+                'msgTest': 'messageEvent'
+              }
+            });
+          })
+        Text(`${this.title}`)
+        Text(`${this.detail}`)
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+  
+- Call the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) API to update the widget in the **onFormEvent** callback of the FormExtensionAbility.
+  
+  ```ts
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+  import formProvider from '@ohos.app.form.formProvider';
+  
+  export default class EntryFormAbility extends FormExtensionAbility {
+    onFormEvent(formId, message) {
+      // Called when a specified message event defined by the form provider is triggered.
+      console.info(`FormAbility onEvent, formId = ${formId}, message: ${JSON.stringify(message)}`);
+      let formData = {
+        'title':'Title Update Success.', // Matches the widget layout.
+        'detail':'Detail Update Success.', // Matches the widget layout.
+      };
+      let formInfo = formBindingData.createFormBindingData(formData)
+      formProvider.updateForm(formId, formInfo).then((data) => {
+        console.info('FormAbility updateForm success.' + JSON.stringify(data));
+      }).catch((error) => {
+        console.error('FormAbility updateForm failed: ' + JSON.stringify(error));
+      })
+    }
+  
+    ...
+  }
+  ```
+
+  The figure below shows the effect.
+  
+  ![WidgetUpdatePage](figures/WidgetUpdatePage.png)

en/application-dev/application-models/arkts-ui-widget-event-overview.md

+# Widget Event Capability Overview
+
+The ArkTS widget provides the **postCardAction()** API for interaction between the widget internal and the provider application. Currently, this API supports the router, message, and call events and can be called only in the widget.
+
+![WidgetPostCardAction](figures/WidgetPostCardAction.png)
+
+**Definition**: postCardAction(component: Object, action: Object): void
+
+**Parameters**
+
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| component | Object | Yes| Instance of the current custom component. Generally, **this** is transferred.|
+| action | Object | Yes| Action description. For details, see the following table.|
+
+**Description of the action parameter**
+
+| Key | Value | Description|
+| -------- | -------- | -------- |
+| "action" | string | Action type.<br>- **"router"**: redirection to the specified UIAbility of the widget provider.<br>- **"message"**: custom message. If this type of action is triggered, the [onFormEvent()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onformevent) lifecycle callback of the provider FormExtensionAbility is called.<br>- **"call"**: launch of the widget provider in the background. If this type of action is triggered, the specified UIAbility of the widget provider is started in the background, but not displayed in the foreground. This action type requires that the widget provider should have the [ohos.permission.KEEP_BACKGROUND_RUNNING](../security/permission-list.md#ohospermissionkeep_background_running) permission.|
+| "bundleName" | string | Name of the target bundle when **action** is **"router"** or **"call"**. This parameter is optional.|
+| "moduleName" | string | Name of the target module when **action** is **"router"** or **"call"**. This parameter is optional.|
+| "abilityName" | string | Name of the target UIAbility when **action** is **"router"** or **"call"**. This parameter is mandatory.|
+| "params" | Object | Additional parameters carried in the current action. The value is a key-value pair in JSON format. For the **"call"** action type, the **method** parameter must be set and its value type must be string. This parameter is mandatory.|
+
+
+Sample code of the **postCardAction()** API:
+
+```typescript
+Button ('Jump')
+  .width('40%')
+  .height('20%')
+  .onClick(() => {
+    postCardAction(this, {
+      'action': 'router',
+      'bundleName': 'com.example.myapplication',
+      'abilityName': 'EntryAbility',
+      'params': {
+        'message': 'testForRouter' // Customize the message to send.
+      }
+    });
+  })
+
+Button ('Start in Background')
+  .width('40%')
+  .height('20%')
+  .onClick(() => {
+    postCardAction(this, {
+      'action': 'call',
+      'bundleName': 'com.example.myapplication',
+      'abilityName': 'EntryAbility',
+      'params': {
+        'method': 'fun', // Set the name of the method to call. It is mandatory.
+        'message': 'testForcall' // Customize the message to send.
+      }
+    });
+  })
+```
+
+
+Read on to learn the typical widget development scenarios that can be implemented through widget events.

en/application-dev/application-models/arkts-ui-widget-event-router.md

+# Redirecting to a UIAbility Through the router Event
+
+The **router** capability of the **postCardAction** API can be used in a widget to quickly start a specific UIAbility of the widget provider. By leveraging this capability, an application can provide in the widget multiple buttons, each of which targets a different target UIAbility. For example, a camera widget can provide the buttons that redirect the user to the UIAbility for taking a photo and the UIAbility for recording a video.
+
+![WidgerCameraCard](figures/WidgerCameraCard.png)
+
+
+Generally, a button is used to start a page.
+
+
+- Design two buttons on the widget page. When one of the buttons is clicked, **postCardAction** is called to send a router event to the specified UIAbility, with the content to be transferred defined in the event.
+  
+  ```ts
+  @Entry
+  @Component
+  struct WidgetCard {
+    build() {
+      Column() {
+        Button ('Function A')
+          .margin('20%')
+          .onClick(() => {
+            console.info('Jump to EntryAbility funA');
+            postCardAction(this, {
+              'action': 'router',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'targetPage': 'funA' // Process the information in the EntryAbility.
+              }
+            });
+          })
+  
+        Button ('Function B')
+          .margin('20%')
+          .onClick(() => {
+            console.info('Jump to EntryAbility funB');
+            postCardAction(this, {
+              'action': 'router',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'targetPage': 'funB' // Process the information in the EntryAbility.
+              }
+            });
+          })
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+
+- The UIAbility receives the router event and obtains parameters. It then starts the page specified in the received message.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  import window from '@ohos.window';
+  
+  let selectPage = "";
+  let currentWindowStage = null;
+  
+  export default class CameraAbility extends UIAbility {
+    // If the UIAbility is started for the first time, the onCreate lifecycle callback is triggered after the router event is received.
+    onCreate(want, launchParam) {
+      // Obtain the targetPage parameter passed in the router event.
+      console.info("onCreate want:" + JSON.stringify(want));
+      if (want.parameters.params !== undefined) {
+        let params = JSON.parse(want.parameters.params);
+        console.info("onCreate router targetPage:" + params.targetPage);
+        selectPage = params.targetPage;
+      }
+    }
+    // If the UIAbility is running in the background, the onNewWant lifecycle callback is triggered after the router event is received.
+    onNewWant(want, launchParam) {
+      console.info("onNewWant want:" + JSON.stringify(want));
+      if (want.parameters.params !== undefined) {
+        let params = JSON.parse(want.parameters.params);
+        console.info("onNewWant router targetPage:" + params.targetPage);
+        selectPage = params.targetPage;
+      }
+      if (currentWindowStage != null) {
+        this.onWindowStageCreate(currentWindowStage);
+      }
+    }
+  
+    onWindowStageCreate(windowStage: window.WindowStage) {
+      let targetPage;
+      // Start the page specified by targetPage.
+      switch (selectPage) {
+        case 'funA':
+          targetPage = 'pages/FunA';
+          break;
+        case 'funB':
+          targetPage = 'pages/FunB';
+          break;
+        default:
+          targetPage = 'pages/Index';
+      }
+      if (currentWindowStage === null) {
+        currentWindowStage = windowStage;
+      }
+      windowStage.loadContent(targetPage, (err, data) => {
+        if (err && err.code) {
+          console.info('Failed to load the content. Cause: %{public}s', JSON.stringify(err));
+          return;
+        }
+      });
+    }
+  };
+  ```

en/application-dev/application-models/arkts-ui-widget-event-uiability.md

+# Updating Widget Content Through the router or call Event
+
+
+On the widget page, the **postCardAction** API can be used to trigger a router or call event to start a UIAbility, which then updates the widget content. The following is an example of this widget update mode.
+
+## Updating Widget Content Through the router Event
+
+- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the **router** event to the FormExtensionAbility.
+  
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    @LocalStorageProp('detail') detail: string = 'init';
+  
+    build() {
+      Column() {
+        Button ('Jump')
+          .margin('20%')
+          .onClick(() => {
+            console.info('postCardAction to EntryAbility');
+            postCardAction(this, {
+              'action': 'router',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'detail': 'RouterFromCard'
+              }
+            });
+          })
+        Text(`${this.detail}`).margin('20%')
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+  
+- In the **onCreate()** or **onNewWant()** lifecycle callback of the UIAbility, use the input parameter **want** to obtain the ID (**formID**) and other information of the widget, and then call the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) API to update the widget.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import formProvider from '@ohos.app.form.formProvider';
+  import formInfo from '@ohos.app.form.formInfo';
+  
+  export default class EntryAbility extends UIAbility {
+    // If the UIAbility is started for the first time, the onCreate lifecycle callback is triggered after the router event is received.
+    onCreate(want, launchParam) {
+      console.info('Want:' + JSON.stringify(want));
+      if (want.parameters[formInfo.FormParam.IDENTITY_KEY] !== undefined) {
+        let curFormId = want.parameters[formInfo.FormParam.IDENTITY_KEY];
+        let message = JSON.parse(want.parameters.params).detail;
+        console.info(`UpdateForm formId: ${curFormId}, message: ${message}`);
+        let formData = {
+          "detail": message +': onCreate UIAbility.', // Matches the widget layout.
+        };
+        let formMsg = formBindingData.createFormBindingData(formData)
+        formProvider.updateForm(curFormId, formMsg).then((data) => {
+          console.info('updateForm success.' + JSON.stringify(data));
+        }).catch((error) => {
+          console.error('updateForm failed:' + JSON.stringify(error));
+        })
+      }
+    }
+    // If the UIAbility is running in the background, the onNewWant lifecycle callback is triggered after the router event is received.
+    onNewWant(want, launchParam) {
+      console.info('onNewWant Want:' + JSON.stringify(want));
+      if (want.parameters[formInfo.FormParam.IDENTITY_KEY] !== undefined) {
+        let curFormId = want.parameters[formInfo.FormParam.IDENTITY_KEY];
+        let message = JSON.parse(want.parameters.params).detail;
+        console.info(`UpdateForm formId: ${curFormId}, message: ${message}`);
+        let formData = {
+          "detail": message +': onNewWant UIAbility.', // Matches the widget layout.
+        };
+        let formMsg = formBindingData.createFormBindingData(formData)
+        formProvider.updateForm(curFormId, formMsg).then((data) => {
+          console.info('updateForm success.' + JSON.stringify(data));
+        }).catch((error) => {
+          console.error('updateForm failed:' + JSON.stringify(error));
+        })
+      }
+    }
+  
+    ...
+  }
+  ```
+
+## Updating Widget Content Through the call Event
+
+- When using the **call** event of the **postCardAction** API, the value of **formId** must be updated in the **onAddForm** callback of the FormExtensionAbility.
+  
+   ```ts
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   
+   export default class EntryFormAbility extends FormExtensionAbility {
+     onAddForm(want) {
+      let formId = want.parameters["ohos.extra.param.key.form_identity"];
+      let dataObj1 = {
+        "formId": formId
+      };
+      let obj1 = formBindingData.createFormBindingData(dataObj1);
+      return obj1;
+    }
+    
+     ...
+   };
+   ```
+
+- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the event to the UIAbility.
+  
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    @LocalStorageProp('detail') detail: string = 'init';
+    @LocalStorageProp('formId') formId: string = '0';
+  
+    build() {
+      Column() {
+        Button ('Start in Background')
+          .margin('20%')
+          .onClick(() => {
+            console.info('postCardAction to EntryAbility');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funA',
+                'formId': this.formId,
+                'detail': 'CallFromCard'
+              }
+            });
+          })
+        Text(`${this.detail}`).margin('20%')
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+  
+- Listen for the method required by the **call** event in the **onCreate** callback of the UIAbility, and then call the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) API in the corresponding method to update the widget.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import formProvider from '@ohos.app.form.formProvider';
+  import formInfo from '@ohos.app.form.formInfo';
+  
+  const MSG_SEND_METHOD: string = 'funA'
+  
+  // After the call event is received, the method listened for by the callee is triggered.
+  function FunACall(data) {
+    // Obtain all parameters transferred in the call event.
+    let params = JSON.parse(data.readString())
+    if (params.formId !== undefined) {
+      let curFormId = params.formId;
+      let message = params.detail;
+      console.info(`UpdateForm formId: ${curFormId}, message: ${message}`);
+      let formData = {
+        "detail": message
+      };
+      let formMsg = formBindingData.createFormBindingData(formData)
+      formProvider.updateForm(curFormId, formMsg).then((data) => {
+        console.info('updateForm success.' + JSON.stringify(data));
+      }).catch((error) => {
+        console.error('updateForm failed:' + JSON.stringify(error));
+      })
+    }
+    return null;
+  }
+  export default class EntryAbility extends UIAbility {
+    // If the UIAbility is started for the first time, the onCreate lifecycle callback is triggered after the call event is received.
+    onCreate(want, launchParam) {
+      console.info('Want:' + JSON.stringify(want));
+      try {
+         // Listen for the method required by the call event.
+        this.callee.on(MSG_SEND_METHOD, FunACall);
+      } catch (error) {
+        console.log(`${MSG_SEND_METHOD} register failed with error ${JSON.stringify(error)}`)
+      }
+    }
+    ...
+  }
+  ```

en/application-dev/application-models/arkts-ui-widget-image-update.md

+# Updating Local and Online Images in the Widget
+
+
+Typically, a widget includes local images or online images downloaded from the network. To obtain local and online images, use the FormExtensionAbility. The following exemplifies how to show local and online images on a widget.
+
+
+1. For the widget to download online images, declare the **ohos.permission.INTERNET** permission for the widget. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md).
+
+2. Update local files in the **onAddForm** lifecycle callback of the EntryFormAbility.
+   
+   ```ts
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import formProvider from '@ohos.app.form.formProvider';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   import request from '@ohos.request';
+   import fs from '@ohos.file.fs';
+   
+   export default class EntryFormAbility extends FormExtensionAbility {
+     ...
+     // When the widget is added, a local image is opened and transferred to the widget page for display.
+     onAddForm(want) {
+       // Assume that the local image head.PNG is in the tmp directory of the current widget.
+       let tempDir = this.context.getApplicationContext().tempDir;
+       // Open the local image and obtain the FD after the image is opened.
+       let file;
+       try {
+         file = fs.openSync(tempDir + '/' + 'head.PNG');
+       } catch (e) {
+         console.error(`openSync failed: ${JSON.stringify(e)}`);
+       }
+       let formData = {
+         'text': 'Image: Bear',
+         'imgName': 'imgBear',
+         'formImages': {
+           'imgBear': file.fd
+         },
+         'loaded': true
+       }
+       // Encapsulate the FD in formData and return it to the widget page.
+       return formBindingData.createFormBindingData(formData);
+     }
+   
+     ...
+   }
+   ```
+
+3. Update online images in the **onFormEvent** lifecycle callback of the EntryFormAbility.
+   
+   ```ts
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import formProvider from '@ohos.app.form.formProvider';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   import request from '@ohos.request';
+   import fs from '@ohos.file.fs';
+   
+   export default class EntryFormAbility extends FormExtensionAbility {
+     // When the message event is triggered on the widget page, an online image is downloaded and transferred to the widget page for display.
+     onFormEvent(formId, message) {
+       let formInfo = formBindingData.createFormBindingData({
+         'text': 'Updating...'
+       })
+       formProvider.updateForm(formId, formInfo)
+       // Note: After being started with the triggering of the lifecycle callback, the FormExtensionAbility can run in the background for only 5 seconds.
+       // When possible, limit the size of the image to download. If an image cannot be downloaded within 5 seconds, it will not be updated to the widget page.
+       let netFile = 'https://xxxx/xxxx.png'; // Specify the URL of the image to download.
+       let tempDir = this.context.getApplicationContext().tempDir;
+       let fileName = 'file' + Date.now();
+       let tmpFile = tempDir + '/' + fileName;
+       request.downloadFile(this.context, {
+         url: netFile, filePath: tmpFile, enableMetered: true, enableRoaming: true
+       }).then((task) => {
+         task.on('complete', function callback() {
+           console.info('ArkTSCard download complete:' + tmpFile);
+           let file;
+           try {
+             file = fs.openSync(tmpFile);
+           } catch (e) {
+             console.error(`openSync failed: ${JSON.stringify(e)}`);
+           }
+           let fileInfo = {};
+           fileInfo[fileName] = file.fd;
+           let formData = {
+             'text': 'Image:' + fileName,
+             'imgName': fileName,
+             'formImages': fileInfo,
+             'loaded': true
+           };
+           let formInfo = formBindingData.createFormBindingData(formData)
+           formProvider.updateForm(formId, formInfo).then((data) => {
+             console.info('FormAbility updateForm success.' + JSON.stringify(data));
+           }).catch((error) => {
+             console.error('FormAbility updateForm failed: ' + JSON.stringify(error));
+           })
+         })
+         task.on('fail', function callBack(err) {
+           console.info('ArkTSCard download task failed. Cause:' + err);
+           let formInfo = formBindingData.createFormBindingData({
+             'text':'Update failed.'
+           })
+           formProvider.updateForm(formId, formInfo)
+         });
+       }).catch((err) => {
+         console.error('Failed to request the download. Cause: ' + JSON.stringify(err));
+       });
+     }
+   
+     ...
+   };
+   ```
+
+4. On the widget page, use the **\<Image>** component to display the widget content transferred from the EntryFormAbility.
+
+   ```ts
+   let storage = new LocalStorage();
+   @Entry(storage)
+   @Component
+   struct WidgetCard {
+     @LocalStorageProp('text') text: string = 'Loading...';
+     @LocalStorageProp('loaded') loaded: boolean = false;
+     @LocalStorageProp('imgName') imgName: string = 'name';
+   
+     build() {
+       Column() {
+         Text(this.text)
+           .fontSize('12vp')
+           .textAlign(TextAlign.Center)
+           .width('100%')
+           .height('15%')
+   
+         Row() {
+           if (this.loaded) {
+             Image('memory://' + this.imgName)
+               .width('50%')
+               .height('50%')
+               .margin('5%')
+           } else {
+             Image('common/start.PNG')
+               .width('50%')
+               .height('50%')
+               .margin('5%')
+           }
+         }.alignItems(VerticalAlign.Center)
+         .justifyContent(FlexAlign.Center)
+   
+         Button ('Update')
+           .height('15%')
+           .onClick(() => {
+             postCardAction(this, {
+               'action': 'message',
+               'params': {
+                 'info': 'refreshImage'
+               }
+             });
+           })
+       }
+       .width('100%').height('100%')
+       .alignItems(HorizontalAlign.Center)
+       .padding('5%')
+     }
+   }
+   ```
+
+> **NOTE**
+> - The **\<Image>** component displays images in the remote memory based on the **memory://** identifier in the input parameter (**memory://fileName**). The value of **fileName** must be consistent with the key in the object (**'formImages': {key: fd}**) passed by the EntryFormAbility.
+> 
+> - The **\<Image>** component determines whether to update the image by comparing the values of **imgName** consecutively passed by the EntryFormAbility. It updates the image only when the values are different.

en/application-dev/application-models/arkts-ui-widget-interaction-overview.md

+# Widget Data Interaction
+
+
+The ArkTS widget framework provides the **updateForm()** and **requestForm()** APIs to proactively trigger widget updates.
+
+
+![WidgetLocalStorageProp](figures/WidgetLocalStorageProp.png)
+
+
+| API| System Capability| Constraints|
+| -------- | -------- | -------- |
+| updateForm | No| 1. Invoked by the provider.<br>2. Allows only the widget provider to update its own widgets. It cannot be used to update widgets by other providers.|
+| requestForm | Yes| 1. Invoked by the host.<br>2. Allows only the widget host to update the widgets added to it. It cannot be used to update widgets added to other hosts.|
+
+The following describes the typical use cases of widget updates:
+
+- [Configuring a Widget to Update Periodically](arkts-ui-widget-update-by-time.md)
+- [Updating Local and Online Images](arkts-ui-widget-image-update.md)
+- [Updating Widget Content by State](arkts-ui-widget-update-by-status.md)
+- [Updating Widget Content by Widget Host (for System Applications Only)](arkts-ui-widget-content-update.md)

en/application-dev/application-models/arkts-ui-widget-lifecycle.md

+# Widget Lifecycle Management
+
+
+When creating an ArkTS widget, you need to implement the [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) lifecycle APIs.
+
+
+1. Import related modules to **EntryFormAbility.ts**.
+   
+   ```ts
+   import formInfo from '@ohos.app.form.formInfo';
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   import formProvider from '@ohos.app.form.formProvider';
+   ```
+
+2. In **EntryFormAbility.ts**, implement the [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) lifecycle APIs, including **onAddForm**, whose **want** parameter can be used to obtain the widget information through [FormParam](../reference/apis/js-apis-app-form-formInfo.md#formparam).
+   
+   ```typescript
+   import formInfo from '@ohos.app.form.formInfo';
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   import formProvider from '@ohos.app.form.formProvider';
+   
+   export default class EntryFormAbility extends FormExtensionAbility {
+     onAddForm(want) {
+       console.info('[EntryFormAbility] onAddForm');
+       // Obtain the unique widget ID formId from the want parameter.
+       let formId: string = want.parameters[formInfo.FormParam.IDENTITY_KEY];
+       // Called when the widget is created. The widget provider should return the widget data binding class.
+       let obj = {
+         'title': 'titleOnAddForm',
+         'detail': 'detailOnAddForm'
+       };
+       let formData = formBindingData.createFormBindingData(obj);
+       return formData;
+     }
+   
+     onCastToNormalForm(formId) {
+       // Called when the form provider is notified that a temporary form is successfully
+       // converted to a normal form.
+       // Called when the widget host converts the temporary widget into a normal one. The widget provider should do something to respond to the conversion.
+       console.info(`[EntryFormAbility] onCastToNormalForm, formId: ${formId}`);
+     }
+   
+     onUpdateForm(formId) {
+       // Override this method to support scheduled updates, periodic updates, or updates requested by the widget host.
+       console.info('[EntryFormAbility] onUpdateForm');
+       let obj = {
+         'title': 'titleOnUpdateForm',
+         'detail': 'detailOnUpdateForm'
+       };
+       let formData = formBindingData.createFormBindingData(obj);
+       formProvider.updateForm(formId, formData).catch((err) => {
+         if (err) {
+           // Print errors.
+           console.error(`[EntryFormAbility] Failed to updateForm. Code: ${err.code}, message: ${err.message}`);
+           return;
+         }
+       });
+     }
+   
+     onChangeFormVisibility(newStatus) {
+       // Called when the form provider receives form events from the system.
+       // The callback is performed only when formVisibleNotify is set to true and the application is a system application.
+       console.info('[EntryFormAbility] onChangeFormVisibility');
+     }
+   
+     onFormEvent(formId, message) {
+       // Called when a specified message event defined by the form provider is triggered.
+       // If the widget supports event triggering, override this method and implement the trigger.
+       console.info('[EntryFormAbility] onFormEvent');
+     }
+   
+     onRemoveForm(formId) {
+       // Called to notify the form provider that a specified form has been destroyed.
+       // Called when the corresponding widget is deleted. The input parameter is the ID of the deleted card.
+       console.info('[EntryFormAbility] onRemoveForm');
+     }
+   
+     onConfigurationUpdate(config) {
+       // Called when the system configuration is updated.
+       console.info('[EntryFormAbility] configurationUpdate:' + JSON.stringify(config));
+     }
+   
+     onAcquireFormState(want) {
+       // Called to return a {@link FormState} object.
+       // Called when the widget provider receives the status query result of a widget. By default, the initial state of the widget is returned.
+       return formInfo.FormState.READY;
+     }
+   }
+   ```
+
+
+> **NOTE**
+>
+> The FormExtensionAbility cannot reside in the background. It persists for 5 seconds after the lifecycle callback is completed and exist if no new lifecycle callback is invoked during this time frame. This means that continuous tasks cannot be processed in the widget lifecycle callbacks. For the service logic that may take more than 5 seconds to complete, it is recommended that you [start the application](arkts-ui-widget-event-uiability.md) for processing. After the processing is complete, use [updateForm()](../reference/apis/js-apis-app-form-formProvider.md#updateform) to notify the widget of the update.

en/application-dev/application-models/arkts-ui-widget-modules.md

+# ArkTS Widget Related Modules
+
+**Figure 1** ArkTS widget related modules
+
+![WidgetModules](figures/WidgetModules.png)
+
+
+- [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md): provides lifecycle callbacks invoked when a widget is created, destroyed, or updated.
+
+- [FormExtensionContext](../reference/apis/js-apis-inner-application-formExtensionContext.md): provides context for FormExtensionAbilities. You can use the APIs of this module to start FormExtensionAbilities.
+
+- [formProvider](../reference/apis/js-apis-app-form-formProvider.md): provides APIs related to the widget provider. You can use the APIs to update a widget, set the next update time for a widget, obtain widget information, and request a widget release.
+
+- [formInfo](../reference/apis/js-apis-app-form-formInfo.md): provides types and enums related to the widget information and state.
+
+- [formBindingData](../reference/apis/js-apis-app-form-formBindingData.md): provides APIs for widget data binding. You can use the APIs to create a **FormBindingData** object and obtain related information.
+
+- [Page layout (Card.ets)](arkts-ui-widget-page-overview.md): provides APIs for a declarative paradigm UI.
+  - [Capabilities exclusive to ArkTS widgets](arkts-ui-widget-event-overview.md): include the **postCardAction** API used for interaction between the widget internal and the provider application and can be called only in the widget.
+  - [ArkTS widget capability list](arkts-ui-widget-page-overview.md#page-capabilities-supported-by-arkts-widgets): contain the APIs, components, events, attributes, and lifecycle callbacks that can be used in ArkTS widgets.
+
+- [Widget configuration](arkts-ui-widget-configuration.md): includes FormExtensionAbility configuration and widget configuration.
+  - Configure the FormExtensionAbility information under **extensionAbilities** in the [module.json5 file](../quick-start/module-configuration-file.md).
+  - Configure the widget configuration information (**WidgetCard.ets**) in the [form_config.json](arkts-ui-widget-configuration.md) file in **resources/base/profile**.

en/application-dev/application-models/arkts-ui-widget-page-animation.md

+# Using Animations in the Widget
+
+
+To make your ArkTS widget more engaging, you can apply animations to it, including [explicit animation](../reference/arkui-ts/ts-explicit-animation.md), [attribute animation](../reference/arkui-ts/ts-animatorproperty.md), and [component transition](../reference/arkui-ts/ts-transition-animation-component.md). Just note the following restrictions when using the animations in ArkTS widgets.
+
+
+**Table 1** Restrictions on animation parameters
+
+| Name| Description| Description|
+| -------- | -------- | -------- |
+| duration | Animation playback duration| The maximum value is 1 second. If a larger value is set, the animation is still played for 1 second.|
+| tempo | Animation playback speed.| Do not set this parameter in the widget. Use the default value 1.|
+| delay | Animation delay duration.| Do not set this parameter in the widget. Use the default value 0.|
+| iterations | Number of times that the animation is played.| Do not set this parameter in the widget. Use the default value 1.|
+
+The following sample code implements the animation effect of button rotation:
+
+![WidgetAnimation](figures/WidgetAnimation.gif)
+
+```ts
+@Entry
+@Component
+struct AttrAnimationExample {
+  @State rotateAngle: number = 0;
+
+  build() {
+    Column() {
+      Button('change rotate angle')
+        .onClick(() => {
+          this.rotateAngle = 90;
+        })
+        .margin(50)
+        .rotate({ angle: this.rotateAngle })
+        .animation({
+          curve: Curve.EaseOut,
+          playMode: PlayMode.AlternateReverse
+        })
+    }.width('100%').margin({ top: 20 })
+  }
+}
+```

en/application-dev/application-models/arkts-ui-widget-page-custom-drawing.md

+# Applying Custom Drawing in the Widget
+
+
+You can apply custom drawing in your ArkTS widget to create a more vibrant experience. Use the [Canvas](../reference/arkui-ts/ts-components-canvas-canvas.md) component to create a canvas on the widget, and then use the [CanvasRenderingContext2D](../reference/arkui-ts/ts-canvasrenderingcontext2d.md) object to draw custom graphics on the canvas. The following code snippet draws a smiling face in the center of a canvas.
+
+```ts
+@Entry
+@Component
+struct Card {
+  private canvasWidth: number = 0;
+  private canvasHeight: number = 0;
+  // Initialize CanvasRenderingContext2D and RenderingContextSettings.
+  private settings: RenderingContextSettings = new RenderingContextSettings(true);
+  private context: CanvasRenderingContext2D = new CanvasRenderingContext2D(this.settings);
+
+  build() {
+    Column() {
+      Row() {
+        Canvas(this.context)
+          .margin('5%')
+          .width('90%')
+          .height('90%')
+          .onReady(() => {
+            console.info('[ArkTSCard] onReady for canvas draw content');
+            // Obtain the actual width and height of the canvas in the onReady callback.
+            this.canvasWidth = this.context.width;
+            this.canvasHeight = this.context.height;
+            // Draw the background of the canvas.
+            this.context.fillStyle = 'rgba(203, 154, 126, 1.00)';
+            this.context.fillRect(0, 0, this.canvasWidth, this.canvasHeight);
+            // Draw a red circle in the center of the canvas.
+            this.context.beginPath();
+            let radius = this.context.width / 3;
+            let circleX = this.context.width / 2;
+            let circleY = this.context.height / 2;
+            this.context.moveTo(circleX - radius, circleY);
+            this.context.arc(circleX, circleY, radius, 2 * Math.PI, 0, true);
+            this.context.closePath();
+            this.context.fillStyle = 'red';
+            this.context.fill();
+            // Draw the left eye of the smiling face.
+            let leftR = radius / 4;
+            let leftX = circleX - (radius / 2);
+            let leftY = circleY - (radius / 3.5);
+            this.context.beginPath();
+            this.context.arc(leftX, leftY, leftR, 0, Math.PI, true);
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
+            // Draw the right eye of the smiling face.
+            let rightR = radius / 4;
+            let rightX = circleX + (radius / 2);
+            let rightY = circleY - (radius / 3.5);
+            this.context.beginPath();
+            this.context.arc(rightX, rightY, rightR, 0, Math.PI, true);
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
+            // Draw the mouth of the smiling face.
+            let mouthR = radius / 2.5;
+            let mouthX = circleX;
+            let mouthY = circleY + (radius / 3);
+            this.context.beginPath();
+            this.context.arc(mouthX, mouthY, mouthR, Math.PI, 0, true);
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
+          })
+      }
+    }.height('100%').width('100%')
+  }
+}
+```
+
+The figure below shows the effect.
+
+![WidgetCanvasDemo](figures/WidgetCanvasDemo.png)
\ No newline at end of file

en/application-dev/application-models/arkts-ui-widget-page-overview.md

+# Widget Page Capability Overview
+
+
+You can leverage the ArkUI declarative paradigm to develop ArkTS widget pages. The following widget pages are automatically generated by a DevEco Studio template. You can adjust the pages based on the real-world service scenarios.
+
+
+![WidgetPreviewPage](figures/WidgetPreviewPage.png)
+
+
+ArkTS widgets have full capabilities of JS widgets, with added animation and custom drawing capabilities plus partial support for components, events, animations, data management, and state management capabilities of the [declarative paradigm](../reference/arkui-ts/ts-components-summary.md). For details, see [Page Capabilities Supported by ArkTS Widgets](#page-capabilities-supported-by-arkts-widgets).
+
+
+## Page Capabilities Supported by ArkTS Widgets
+
+For details about the page capabilities supported by ArkTS widgets, see [Learning ArkTS](../quick-start/arkts-create-custom-components.md) and [ArkTS-based Declarative Development Paradigm](../reference/arkui-ts/ts-components-summary.md).
+
+Only the APIs marked with "supported in ArkTS widgets" can be used for ArkTS widgets. Pay special attention to the capability differences with applications.
+
+For example, the following description indicates that the @Component decorator can be used in ArkTS widgets.
+
+![WidgetSupportApi](figures/WidgetSupportApi.png)

en/application-dev/application-models/arkts-ui-widget-update-by-status.md

+# Updating Widget Content by State
+
+
+There are cases where multiple copies of the same widget are added to the home screen to accommodate different needs. In these cases, the widget content needs to be dynamically updated based on the state. This topic exemplifies how this is implemented. In the following example, two weather widgets are added to the home screen: one for displaying the weather of London, and the other Beijing, both configured to be updated at 07:00 every morning. The widget provider detects the target city, and then displays the city-specific weather information on the widgets.
+
+
+- Widget configuration file: Configure the widget to be updated at 07:00 every morning.
+  
+  ```json
+  {
+    "forms": [
+      {
+        "name": "widget",
+        "description": "This is a service widget.",
+        "src": "./ets/widget/pages/WidgetCard.ets",
+        "uiSyntax": "arkts",
+        "window": {
+          "designWidth": 720,
+          "autoDesignWidth": true
+        },
+        "colorMode": "auto",
+        "isDefault": true,
+        "updateEnabled": true,"scheduledUpdateTime": "07:00",
+        "updateDuration": 0,
+        "defaultDimension": "2*2",
+        "supportDimensions": ["2*2"]
+      }
+    ]
+  }
+  ```
+
+- Widget page: A widget has different states and needs to be updated by state. When the state changes, **postCardAction** is called to notify the EntryFormAbility.
+  
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    @LocalStorageProp('textA') textA: string = 'To be updated...';
+    @LocalStorageProp('textB') textB: string ='To be updated...';
+    @State selectA: boolean = false;
+    @State selectB: boolean = false;
+  
+    build() {
+      Column() {
+        Row() {
+          Checkbox({ name: 'checkbox1', group: 'checkboxGroup' })
+            .select(false)
+            .onChange((value: boolean) => {
+              this.selectA = value;
+              postCardAction(this, {
+                'action': 'message',
+                'params': {
+                  'selectA': JSON.stringify(value)
+                }
+              });
+            })
+          Text ('State A')
+        }
+  
+        Row() {
+          Checkbox({ name: 'checkbox2', group: 'checkboxGroup' })
+            .select(false)
+            .onChange((value: boolean) => {
+              this.selectB = value;
+              postCardAction(this, {
+                'action': 'message',
+                'params': {
+                  'selectB': JSON.stringify(value)
+                }
+              });
+            })
+          Text ('State B')
+        }
+  
+        Row() {// Content that is updated only in state A
+          Text ('State A:')
+          Text(this.textA)
+        }
+  
+        Row() { // Content that is updated only in state B
+          Text ('State B:')
+          Text(this.textB)
+        }
+      }.padding('10%')
+    }
+  }
+  ```
+  
+- EntryFormAbility: The widget state data is stored in the local database. When the update event callback is triggered, the current widget state is obtained through **formId**, and then content is updated based on the state obtained.
+  
+  ```ts
+  import formInfo from '@ohos.app.form.formInfo'
+  import formProvider from '@ohos.app.form.formProvider';
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+  import dataStorage from '@ohos.data.storage'
+  
+  export default class EntryFormAbility extends FormExtensionAbility {
+    onAddForm(want) {
+      let formId = want.parameters[formInfo.FormParam.IDENTITY_KEY];
+      let isTempCard: boolean = want.parameters[formInfo.FormParam.TEMPORARY_KEY];
+      if (isTempCard === false) {// If the widget is a normal one, the widget information is persisted.
+        console.info('Not temp card, init db for:' + formId);
+        let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+        storeDB.putSync('A' + formId, 'false');
+        storeDB.putSync('B' + formId, 'false');
+        storeDB.flushSync();
+      }
+      let formData = {};
+      return formBindingData.createFormBindingData(formData);
+    }
+  
+    onRemoveForm(formId) {
+      console.info('onRemoveForm, formId:' + formId);
+      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+      storeDB.deleteSync('A' + formId);
+      storeDB.deleteSync('B' + formId);
+    }
+  
+    // If the widget is a temporary one, it is recommended that the widget information be persisted when the widget is converted to a normal one.
+    onCastToNormalForm(formId) {
+      console.info('onCastToNormalForm, formId:' + formId);
+      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+      storeDB.putSync('A' + formId, 'false');
+      storeDB.putSync('B' + formId, 'false');
+      storeDB.flushSync();
+    }
+  
+    onUpdateForm(formId) {
+      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+      let stateA = storeDB.getSync('A' + formId, 'false').toString()
+      let stateB = storeDB.getSync('B' + formId, 'false').toString()
+      // Update textA in state A.
+      if (stateA === 'true') {
+        let formInfo = formBindingData.createFormBindingData({
+          'textA': 'AAA'
+        })
+        formProvider.updateForm(formId, formInfo)
+      }
+      // Update textB in state B.
+      if (stateB === 'true') {
+        let formInfo = formBindingData.createFormBindingData({
+          'textB': 'BBB'
+        })
+        formProvider.updateForm(formId, formInfo)
+      }
+    }
+  
+    onFormEvent(formId, message) {
+      // Store the widget state.
+      console.info('onFormEvent formId:' + formId + 'msg:' + message);
+      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+      let msg = JSON.parse(message)
+      if (msg.selectA != undefined) {
+        console.info('onFormEvent selectA info:' + msg.selectA);
+        storeDB.putSync('A' + formId, msg.selectA);
+      }
+      if (msg.selectB != undefined) {
+        console.info('onFormEvent selectB info:' + msg.selectB);
+        storeDB.putSync('B' + formId, msg.selectB);
+      }
+      storeDB.flushSync();
+    }
+  };
+  ```
+
+
+> **NOTE**
+>
+> When the local database is used for widget information persistence, it is recommended that [TEMPORARY_KEY](../reference/apis/js-apis-app-form-formInfo.md#formparam) be used to determine whether the currently added widget is a normal one in the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) lifecycle callback. If the widget is a normal one, the widget information is directly persisted. If the widget is a temporary one, the widget information is persisted when the widget is converted to a normal one ([onCastToNormalForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#oncasttonormalform)). In addition, the persistent widget information needs to be deleted when the widget is destroyed ([onRemoveForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onremoveform)), preventing the database size from continuously increasing due to repeated widget addition and deletion.

en/application-dev/application-models/arkts-ui-widget-update-by-time.md

+# Configuring a Widget to Update Periodically
+
+Before configuring a widget to update periodically, enable the periodic update feature by setting the **updateEnabled** field to **true** in the **form_config.json** file.
+
+The widget framework provides the following modes of updating widgets periodically:
+
+
+- Set the update interval: The widget will be updated at the specified interval by calling [onUpdateForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform). You can specify the interval by setting the [updateDuration](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update once an hour.
+  
+  > **NOTE**
+  >
+  > **updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.
+  
+  ```json
+  {
+    "forms": [
+      {
+        "name": "widget",
+        "description": "This is a service widget.",
+        "src": "./ets/widget/pages/WidgetCard.ets",
+        "uiSyntax": "arkts",
+        "window": {
+          "designWidth": 720,
+          "autoDesignWidth": true
+        },
+        "colorMode": "auto",
+        "isDefault": true,
+        "updateEnabled": true, // Enable the periodic update feature.
+        "scheduledUpdateTime": "10:30",                               
+        "updateDuration": 2, // Set the interval to update the widget. The value is a natural number, in the unit of 30 minutes.
+        "defaultDimension": "2*2",
+        "supportDimensions": ["2*2"]
+      }
+    ]
+  }
+  ```
+  
+- Set the scheduled update time: The widget will be updated at the scheduled time every day. You can specify the time by setting the [scheduledUpdateTime](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update at 10:30 a.m. every day.
+  
+  > **NOTE**
+  >
+  > **updateDuration** takes precedence over **scheduledUpdateTime**. For the **scheduledUpdateTime** settings to take effect, set **updateDuration** to **0**.
+  
+  
+  ```json
+  {
+    "forms": [
+      {
+        "name": "widget",
+        "description": "This is a service widget.",
+        "src": "./ets/widget/pages/WidgetCard.ets",
+        "uiSyntax": "arkts",
+        "window": {
+          "designWidth": 720,
+          "autoDesignWidth": true
+        },
+        "colorMode": "auto",
+        "isDefault": true,
+        "updateEnabled": true, // Enable the periodic update feature.
+        "scheduledUpdateTime": "10:30", // Set the scheduled time to update the widget.
+        "updateDuration": 0,
+        "defaultDimension": "2*2",
+        "supportDimensions": ["2*2"]
+      }
+    ]
+  }
+  ```
+  
+- Set the next update time: The widget will be updated next time at the specified time. You can specify the time by calling the [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime) API. The minimum update interval is 5 minutes. For example, you can configure the widget to update within 5 minutes after the API is called.
+  
+  ```ts
+  import formProvider from '@ohos.app.form.formProvider';
+  
+  let formId = '123456789'; // Use the actual widget ID in real-world scenarios.
+  try {
+    // Configure the widget to update in 5 minutes.
+    formProvider.setFormNextRefreshTime(formId, 5, (err, data) => {
+      if (err) {
+        console.error(`Failed to setFormNextRefreshTime. Code: ${err.code}, message: ${err.message}`);
+        return;
+      } else {
+        console.info('Succeeded in setFormNextRefreshTimeing.');
+      }
+    });
+  } catch (err) {
+    console.error(`Failed to setFormNextRefreshTime. Code: ${err.code}, message: ${err.message}`);
+  }
+  ```
+
+
+When periodic update is triggered, the system calls the [onUpdateForm()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform) lifecycle callback of the FormExtensionAbility. In the callback, [updateForm()](../reference/apis/js-apis-app-form-formProvider.md#updateform) can be used to update the widget by the provider. For details about how to use **onUpdateForm()**, see [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md).
+
+
+> **NOTE**
+> 1. Each widget can be updated at the specified interval for a maximum of 50 times every day, including updates triggered by setting [updateDuration](arkts-ui-widget-configuration.md) or calling [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime). When the limit is reached, the widget cannot be updated in this mode again. The number of update times is reset at 00:00 every day.
+> 
+> 2. The same timer is used for timing updates at the specified interval. Therefore, the first scheduled update of widgets may have a maximum deviation of 30 minutes. For example, the first widget A (updated every half an hour) is added at 03:20. The timer starts and triggers an update every half an hour. The second widget B (updated every half an hour) is added at 03:40. When the timer event is triggered at 03:50, widget A is updated, and widget B will be updated at 04:20 next time.
+> 
+> 3. Updates at the specified interval and updates at the scheduled time are triggered only when the screen is on. When the screen is off, the update action is merely recorded. When the screen is on, the update action is performed.

en/application-dev/application-models/arkts-ui-widget-working-principles.md

+# ArkTS Widget Working Principles
+
+
+## Implementation Principles
+
+**Figure 1** ArkTS widget implementation principles
+
+![WidgetPrinciple](figures/WidgetPrinciple.png)
+
+- Widget host: an application that displays the widget content and controls the widget location. Only the system application can function as a widget host.
+
+- Widget provider: an application that provides the widget content to display and controls how widget components are laid out and how they interact with users.
+
+- Widget Manager: a resident agent that manages widgets in the system. It provides the [formProvider](../reference/apis/js-apis-app-form-formProvider.md) and [formHost](../reference/apis/js-apis-app-form-formHost.md) APIs as well as the APIs for widget management, usage, and periodic updates.
+
+- Widget rendering service: a service that manages widget rendering instances. Widget rendering instances are bound to the [widget components](../reference/arkui-ts/ts-basic-components-formcomponent.md) on the widget host on a one-to-one basis. The widget rendering service runs the widget page code **widgets.abc** for rendering, and sends the rendered data to the corresponding widget component on the widget host.
+
+  **Figure 2** Working principles of the ArkTS widget rendering service 
+![WidgetRender](figures/WidgetRender.png)
+
+Unlike JS widgets, ArkTS widgets support logic code running. The widget page code **widgets.abc** is executed by the widget rendering service, which is managed by the Widget Manager. Each widget component of a widget host corresponds to a rendering instance in the widget rendering service. Rendering instances of a widget provider run in the same virtual machine operating environment, and rendering instances of different widget providers run in different virtual machine operating environments. In this way, the resources and state data are isolated between widgets of different widget providers. During development, pay attention to the use of the [globalThis](uiability-data-sync-with-ui.md#using-globalthis-between-uiability-and-page) object. Use one **globalThis** object for widgets from the same widget provider, and different **globalThis** objects for widgets from different widget providers.
+
+
+## Advantages of ArkTS Widgets
+
+As a quick entry to applications, ArkTS widgets outperform JS widgets in the following aspects:
+
+- Improved development experience and efficiency, thanks to the unified development paradigm
+  
+  ArkTS widgets share the same declarative UI development framework as application pages. This means that the page layouts can be directly reused in widgets, improving development experience and efficiency.
+  
+  **Figure 3** Comparison of widget project structures
+  
+  ![WidgetProject](figures/WidgetProject.png)
+  
+- More widget features
+  - Animation: ArkTS widgets support the [attribute animation](../reference/arkui-ts/ts-animatorproperty.md) and [explicit animation](../reference/arkui-ts/ts-explicit-animation.md) capabilities, which can be leveraged to deliver a more engaging experience.
+  - Custom drawing: ArkTS widgets allow you to draw graphics with the [\<Canvas>](../reference/arkui-ts/ts-components-canvas-canvas.md) component to present information more vividly.
+  - Logic code execution: The capability to run logic code in widgets means that service logic can be self-closed in widgets, expanding the use cases of widgets.
+
+
+## Constraints on ArkTS Widgets
+
+Compared with JS widgets, ArkTS widgets provide more capabilities, but they are also more prone to malicious behavior. To account for the impact on the widget host – typically the home screen, ArkTS widgets are subject to the following restrictions:
+
+- The .so file cannot be loaded.
+
+- The native programming language cannot be used for development.
+
+- Only [partial](arkts-ui-widget-page-overview.md) components, events, animations, data management, state management, and API capabilities of the declarative paradigm are supported.
+
+- The event processing of the widget is independent of that of the widget host. To prevent gesture conflicts, avoid using swipers in the widget when the widget host supports left and right swipes.
+
+In addition, ArkTS widgets do not support the following features:
+
+- Importing modules
+
+- Instant preview
+
+- Breakpoint debugging.
+
+- Hot reload

en/application-dev/application-models/common-event-overview.md

@@ -7,8 +7,7 @@ OpenHarmony provides Common Event Service (CES) for applications to subscribe to
 Common events are classified into system common events and custom common events.
 
 
-- System common events: defined in CES. Only system applications and system services can publish system common events, such as HAP installation, update, and uninstall. For details about the supported system common events, see [Support](../reference/apis/js-apis-commonEventManager.md#support).
-
+- System common events: defined in CES. Currently, only system applications and system services can publish system common events, such as HAP installation, update, and uninstall. For details about the supported system common events, see [System Common Events](../reference/apis/commonEventManager-definitions.md).
 - Custom common events: customized by applications to implement cross-process event communication.
 
 
@@ -16,9 +15,7 @@ Common events are also classified into unordered, ordered, and sticky common eve
 
 
 - Unordered common events: common events that CES forwards regardless of whether subscribers receive the events and when they subscribe to the events.
-
-- Ordered common events: common events that CES forwards based on the subscriber priority. CES forwards common events to the subscriber with lower priority only after receiving a reply from the previous subscriber with higher priority. Subscribers with the same priority receive common events in a random order.
-
+- Ordered common events: common events that CES forwards based on the subscriber priority. CES preferentially forwards an ordered common event to the subscriber with higher priority, waits until the subscriber receives the event, and then forwards the events to the subscriber with lower priority. Subscribers with the same priority receive common events in a random order.
 - Sticky common events: common events that can be sent to a subscriber before or after they initiate a subscription. Only system applications and system services can send sticky common events, which remain in the system after being sent. The sends must first request the **ohos.permission.COMMONEVENT_STICKY** permission. For details about the configuration, see [Permission Application Guide](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file). 
 
 

en/application-dev/application-models/common-event-static-subscription.md

@@ -2,45 +2,51 @@
 
 ## When to Use
 
-A static subscriber is started once it receives a target event published by the system or application. At the same time, the **onReceiveEvent** callback is triggered, in which you can implement the service logic. For example, if an application needs to execute some initialization tasks during device power-on, the application can subscribe to the power-on event in static mode. After receiving the power-on event, the application is started to execute the initialization tasks. Subscribing to a common event in static mode is achieved by configuring a declaration file and implementing a class that inherits from **StaticSubscriberExtensionAbility**. Note that this subscribing mode has negative impact on system power consumption. Therefore, exercise caution when using this mode.
+A static subscriber is started once it receives a target event published by the system or application. At the same time, the [onReceiveEvent()](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent) callback is triggered.
+
+You can implement the service logic in the [onReceiveEvent()](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent) callback. For example, if an application needs to execute some initialization tasks during device power-on, the application can subscribe to the power-on event in static mode. After receiving the power-on event, the application is started to execute the initialization tasks.
+
+Subscribing to a common event in static mode is achieved by configuring a declaration file and implementing a class that inherits from [StaticSubscriberExtensionAbility](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md).
+
+> **NOTE**
+>
+> The static subscription mode has negative impact on system power consumption. Therefore, exercise caution when using this mode.
 
 ## How to Develop
 
-1. Declaring a Static Subscriber
+1. Declaring a static subscriber.
+
+   To declare a static subscriber, create an ExtensionAbility, which is derived from the **StaticSubscriberExtensionAbility** class, in the project.
 
-   To declare a static subscriber, create an ExtensionAbility, which is derived from the **StaticSubscriberExtensionAbility** class, in the project. The sample code is as follows:
+   You can implement service logic in the **onReceiveEvent()** callback.
 
    ```ts
    import StaticSubscriberExtensionAbility from '@ohos.application.StaticSubscriberExtensionAbility'
    
    export default class StaticSubscriber extends StaticSubscriberExtensionAbility {
      onReceiveEvent(event) {
-           console.log('onReceiveEvent, event:' + event.event);
+       console.info('onReceiveEvent, event: ' + event.event);
      }
    }
    ```
 
-   You can implement service logic in the **onReceiveEvent** callback.
+2. Configure static subscriber settings.
 
-   
-
-2. Project Configuration for a Static Subscriber
-
-   After writing the static subscriber code, configure the subscriber in the **module.json5** file. The configuration format is as follows:
+   After writing the static subscriber code, configure the subscriber in the [module.json5](../quick-start/module-configuration-file.md) file.
 
    ```ts
    {
      "module": {
-       ......
+       ...
        "extensionAbilities": [
          {
            "name": "StaticSubscriber",
-           "srcEntrance": "./ets/StaticSubscriber/StaticSubscriber.ts",
+           "srcEntry": "./ets/staticsubscriber/StaticSubscriber.ts",
            "description": "$string:StaticSubscriber_desc",
            "icon": "$media:icon",
            "label": "$string:StaticSubscriber_label",
            "type": "staticSubscriber",
-           "visible": true,
+           "exported": true,
            "metadata": [
              {
                "name": "ohos.extension.staticSubscriber",
@@ -49,14 +55,14 @@ A static subscriber is started once it receives a target event published by the
            ]
          }
        ]
-       ......
+       ...
      }
    }
    ```
 
-   Pay attention to the following fields in the JSON file:
+   Some fields in the file are described as follows:
 
-   - **srcEntrance**: entry file path of the ExtensionAbility, that is, the file path of the static subscriber declared in Step 2.
+   - **srcEntry **: entry file path of the ExtensionAbility, that is, the file path of the static subscriber declared in Step 2.
 
    - **type**: ExtensionAbility type. For a static subscriber, set this field to **staticSubscriber**.
 
@@ -64,9 +70,10 @@ A static subscriber is started once it receives a target event published by the
         - **name**: name of the ExtensionAbility. For a static subscriber, declare the name as **ohos.extension.staticSubscriber** for successful identification.
         - **resource**: path that stores the ExtensionAbility configuration, which is customizable. In this example, the path is **resources/base/profile/subscribe.json**.
 
-     A level-2 configuration file pointed to by **metadata** must be in the following format:
 
-     ```ts
+3. Configure the level-2 configuration file to which the metadata points.
+
+   ```json
    {
      "commonEvents": [
        {
@@ -80,23 +87,32 @@ A static subscriber is started once it receives a target event published by the
    }
    ```
 
-     If the level-2 configuration file is not declared in this format, the file cannot be identified. The fields are described as follows:
+   If the level-2 configuration file is not declared in this format, the file cannot be identified. Some fields in the file are described as follows:
 
    - **name**: name of the ExtensionAbility, which must be the same as the name of **extensionAbility** declared in **module.json5**.
-
    - **permission**: permission required for the publisher. If a publisher without the required permission attempts to publish an event, the event is regarded as invalid and will not be published.
-
    - **events**: list of target events to subscribe to.
 
-3. Device System Configuration
+4. Modify the [preset configuration file](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/preinstall-config/install_list_permissions.json) of the device, that is, the **/system/etc/app/install_list_permission.json** file on the device. When the device is started, this file is read. During application installation, the common event type specified by **allowCommonEvent** in the file is authorized. The **install_list_permission.json** file contains the following fields:
 
-    In the device system configuration file **/etc/static_subscriber_config.json**, add the bundle name of the static subscriber.
+   - **bundleName**: bundle name of the application.
+   - **app_signature**: fingerprint information of the application. For details, see [Application Privilege Configuration Guide](../../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-in-install_list_capabilityjson).
+   - **allowCommonEvent**: type of common event that can be started by static broadcast.
+
+   > **NOTE**
+   >
+   > The **install_list_permissions.json** file is available only for preinstalled applications.
 
    ```json
+   [
+     ...
      {
-        "xxx",
-        "ohos.extension.staticSubscriber",
-        "xxx"
+       "bundleName": "com.example.myapplication", // Bundle name of the application.
+       "app_signature": ["****"], // Fingerprint information of the application.
+       "allowCommonEvent": ["usual.event.A", "usual.event.B"], // Type of common event that can be started by static broadcast.
+       ]
      }
+   ]
    ```
 
+<!--no_check-->
\ No newline at end of file

en/application-dev/application-models/common-event-subscription-overview.md

 # Common Event Subscription Overview
 
-​The common event service provides two subscription modes: dynamic and static. The biggest difference between these two modes is that dynamic subscription requires the application to be running, while static subscription does not.
+The common event service provides two subscription modes: dynamic and static. The biggest difference between these two modes is that dynamic subscription requires the application to be running, while static subscription does not.
 
 - In dynamic subscription mode, a subscriber subscribes to common events by calling an API during the running period. For details, see [Subscribing to Common Events in Dynamic Mode](common-event-subscription.md).
 
-- In static subscription mode, a subscriber subscribes to common events by configuring a declaration file and implementing a class that inherits from StaticSubscriberExtensionAbility. For details, see [Subscribing to Common Events in Static Mode](common-event-static-subscription.md).
+- In static subscription mode, a subscriber subscribes to common events by configuring a declaration file and implementing a class that inherits from **StaticSubscriberExtensionAbility**. For details, see [Subscribing to Common Events in Static Mode](common-event-static-subscription.md).

en/application-dev/application-models/common-event-subscription.md

@@ -8,7 +8,7 @@ In dynamic subscription mode, an application subscribes to a common event when i
 
 ## Available APIs
 
-For details about the APIs, see [API Reference](../reference/apis/js-apis-commonEvent.md#commoneventcreatesubscriber).
+For details about the APIs, see [API Reference](../reference/apis/js-apis-commonEventManager.md#commoneventmanagersubscribe).
 
 | API| Description|
 | -------- | -------- |
@@ -19,10 +19,10 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
 
 ## How to Develop
 
-1. Import the **commonEvent** module.
+1. Import the **commonEventManager** module.
    
    ```ts
-   import commonEvent from '@ohos.commonEventManager';
+   import commonEventManager from '@ohos.commonEventManager';
    ```
 
 2. Create a **subscribeInfo** object. For details about the data types and parameters of the object, see [CommonEventSubscribeInfo](../reference/apis/js-apis-commonEventManager.md#commoneventsubscribeinfo).
@@ -40,14 +40,14 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
    
    ```ts
    // Callback for subscriber creation.
-   commonEvent.createSubscriber(subscribeInfo, (err, data) => {
+   commonEventManager.createSubscriber(subscribeInfo, (err, data) => {
      if (err) {
-           console.error(`[CommonEvent] CreateSubscriberCallBack err=${JSON.stringify(err)}`);
-       } else {
-           console.info(`[CommonEvent] CreateSubscriber success`);
+       console.error(`Failed to create subscriber. Code is ${err.code}, message is ${err.message}`);
+       return;
+     }
+     console.info('Succeeded in creating subscriber.');
      subscriber = data;
      // Callback for common event subscription.
-       }
    })
    ```
 
@@ -56,14 +56,13 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
    ```ts
    // Callback for common event subscription.
    if (subscriber !== null) {
-       commonEvent.subscribe(subscriber, (err, data) => {
+     commonEventManager.subscribe(subscriber, (err, data) => {
        if (err) {
-               console.error(`[CommonEvent] SubscribeCallBack err=${JSON.stringify(err)}`);
-           } else {
-               console.info(`[CommonEvent] SubscribeCallBack data=${JSON.stringify(data)}`);
+         console.error(`Failed to subscribe common event. Code is ${err.code}, message is ${err.message}`);
+         return;
        }
      })
    } else {
-       console.error(`[CommonEvent] Need create subscriber`);
+     console.error(`Need create subscriber`);
    }
    ```

en/application-dev/application-models/component-startup-rules.md

@@ -23,14 +23,14 @@ In view of this, OpenHarmony formulates a set of component startup rules, as fol
 
 
 - **Before starting a component of another application, verify the visible field of the target component.**
-  - If the **visible** field of the target component is **false**, verify the **ohos.permission.START_INVISIBLE_ABILITY** permission.
-  - For details, see [Component Visible Configuration](../quick-start/module-configuration-file.md#abilities).
+  - If the **exported** field of the target component is **false**, verify the **ohos.permission.START_INVISIBLE_ABILITY** permission.
+  - For details, see [Component exported Configuration](../quick-start/module-configuration-file.md#abilities).
 
 - **Before starting a component of a background application, verify the BACKGROUND permission.**
   - An application is considered as a foreground application only when the application process gains focus or its UIAbility component is running in the foreground.
   - Verify the **ohos.permission.START_ABILITIES_FROM_BACKGROUND** permission.
 
-- **When the startAbilityByCall() method is used, verify the call permission.** For details, see [Using Ability Call to Implement UIAbility Interaction](uiability-intra-device-interaction.md#using-ability-call-to-implement-uiability-interaction) and [Using Cross-Device Ability Call](hop-multi-device-collaboration.md#using-cross-device-ability-call).
+- **When the startAbilityByCall() method is used, verify the call permission.** For details, see [Using Call to Implement UIAbility Interaction](uiability-intra-device-interaction.md#using-call-to-implement-uiability-interaction) and [Using Cross-Device Call](hop-multi-device-collaboration.md#using-cross-device-call).
   - Verify the **ohos.permission.ABILITY_BACKGROUND_COMMUNICATION** permission.
 
 

en/application-dev/application-models/config-file-stage.md

+# Application Configuration File (Stage Model)
+
+The application configuration file contains information about the application configuration, application components, and permissions, as well as custom information. The information will be provided for the compiler, application market, and operating system in the build, distribution, and running phases.
+
+The application project code developed based on the stage model contains one **app.json5** file and one or more **module.json5** files. For details about common configuration items, see [Application- or Component-Level Configuration (Stage Model)](application-component-configuration-stage.md). For details about the two files, see [Application Configuration File Overview (Stage Model)](../quick-start/application-configuration-file-overview-stage.md).
+

en/application-dev/application-models/context-switch.md

@@ -5,7 +5,7 @@
 | -------- | -------- | -------- |
 | [getOrCreateLocalDir(callback:AsyncCallback&lt;string&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextgetorcreatelocaldir7)<br>[getOrCreateLocalDir():Promise&lt;string&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetorcreatelocaldir7-1) | There is no corresponding API in the stage model.| Applications developed on the stage model do not have the operation permission in the application root directory. Therefore, no corresponding API is provided.|
 | [verifyPermission(permission:string,options:PermissionOptions,callback:AsyncCallback&lt;number&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7)<br>[verifyPermission(permission:string,callback:AsyncCallback&lt;number&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7-1)<br>[verifyPermission(permission:string,options?:PermissionOptions):Promise&lt;number&gt;;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7-2) | \@ohos.abilityAccessCtrl.d.ts | [verifyAccessTokenSync(tokenID: number, permissionName: Permissions): GrantStatus;](../reference/apis/js-apis-abilityAccessCtrl.md#verifyaccesstokensync9)<br>[verifyAccessToken(tokenID: number, permissionName: Permissions): Promise&lt;GrantStatus&gt;;](../reference/apis/js-apis-abilityAccessCtrl.md#verifyaccesstoken9) |
-| [requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number,resultCallback:AsyncCallback&lt;PermissionRequestResult&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7)<br>[requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number):Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7-1) | application\UIAbilityContext.d.ts | [requestPermissionsFromUser(permissions: Array&lt;string&gt;, requestCallback: AsyncCallback&lt;PermissionRequestResult&gt;) : void;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextrequestpermissionsfromuser)<br>[requestPermissionsFromUser(permissions: Array&lt;string&gt;) : Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextrequestpermissionsfromuser-1) |
+| [requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number,resultCallback:AsyncCallback&lt;PermissionRequestResult&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7)<br/>[requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number):Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7-1) | \@ohos.abilityAccessCtrl.d.ts | [requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;, requestCallback: AsyncCallback&lt;PermissionRequestResult&gt;) : void;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9)<br/>[requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;) : Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9-1) |
 | [getApplicationInfo(callback:AsyncCallback&lt;ApplicationInfo&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextgetapplicationinfo7)<br>[getApplicationInfo():Promise&lt;ApplicationInfo&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetapplicationinfo7-1) | application\Context.d.ts | [applicationInfo: ApplicationInfo;](../reference/apis/js-apis-inner-application-context.md#attributes)|
 | [getBundleName(callback : AsyncCallback&lt;string&gt;): void;](../reference/apis/js-apis-inner-app-context.md#contextgetbundlename7)<br>[getBundleName(): Promise&lt;string&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetbundlename7-1) | application\UIAbilityContext.d.ts | [abilityInfo.bundleName: string;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#attributes)|
 | [getDisplayOrientation(callback : AsyncCallback&lt;bundle.DisplayOrientation&gt;): void;](../reference/apis/js-apis-inner-app-context.md#contextgetdisplayorientation7)<br>[getDisplayOrientation(): Promise&lt;bundle.DisplayOrientation&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetdisplayorientation7-1) | \@ohos.screen.d.ts | [readonly orientation: Orientation;](../reference/apis/js-apis-screen.md#orientation) |

en/application-dev/application-models/create-pageability.md

@@ -76,22 +76,22 @@ In the FA model, you can call **getContext** of **featureAbility** to obtain the
 The following code snippet shows how to use **getContext()** to obtain the application context and distributed directory:
 
 ```ts
-import featureAbility from '@ohos.ability.featureAbility'
-import fileIo from '@ohos.fileio'
+import featureAbility from '@ohos.ability.featureAbility';
+import fs from '@ohos.file.fs';
 
 (async () => {
-  let dir: string
+  let dir: string;
   try {
-    console.info('Begin to getOrCreateDistributedDir')
-    dir = await featureAbility.getContext().getOrCreateDistributedDir()
+    console.info('Begin to getOrCreateDistributedDir');
+    dir = await featureAbility.getContext().getOrCreateDistributedDir();
     console.info('distribute dir is ' + dir)
   } catch (error) {
-    console.error('getOrCreateDistributedDir failed with ' + error)
+    console.error('getOrCreateDistributedDir failed with ' + error);
   }
 
   let fd: number;
   let path = dir + "/a.txt";
-  fd = fileIo.openSync(path, 0o2 | 0o100, 0o666);
-  fileIo.close(fd);
+  fd = fs.openSync(path, fs.OpenMode.READ_WRITE).fd;
+  fs.close(fd);
 })()
 ```

en/application-dev/application-models/data-share-via-want.md

 # Using Want to Share Data Between Applications
 
-
 Users often need to share data (such as a text or an image) from one application to another. The following uses PDF file sharing as an example to describe how to use Want to share data between applications.
 
+Data sharing requires two UIAbility components (one for the sharing party and the other for the shared party) and one system component (used as the application sharing box). When the sharing party initiates data sharing by calling **startAbility()**, the system implicitly matches and displays all applications that support the type of data to share. After the user selects an application, the system starts the application to complete data sharing.
 
-## Prerequisites
-
-1. There are two UIAbility components (one for the sharing party and the other for the shared party) and one system component (used as the application selector). When the sharing party initiates data sharing through **startAbility()**, the application selector is started. The system implicitly matches and displays all applications that support the type of data to share. After the user selects an application, the system starts that application to complete data sharing.
-
-2. In this section, data sharing is triggered by touching a button. You can use other ways to trigger data sharing during application development. This section focuses on the Want configuration used for data sharing.
+In this section, data sharing is triggered by touching a button. You can use other ways to trigger data sharing during application development. This section focuses on how to configure Want to implement data sharing.
 
-3. The following actions are involved in this section:
-   - **ACTION_SELECT (ohos.want.action.select)**: action of displaying the application selector.  
-   - **ACTION_SEND_DATA (ohos.want.action.sendData)**: action of launching the UI for sending a single data record. It is used to transfer data to the shared party.
+The following actions are involved for data sharing:
 
+- **ohos.want.action.select**: action of starting the application sharing box.
+- **ohos.want.action.sendData**: action of sending a single data record, that is, transferring data to the shared party.
 
-## How to Develop
+## Sharing Party
 
-- Sharing party
-  1. In the stage mode, the [File Descriptor (FD)](../reference/apis/js-apis-fileio.md#fileioopensync) is used for file transfer. This example assumes that the path of the file to share is obtained.
+The sharing party starts an application sharing box and transfers the data to the shared party. Therefore, Want of the sharing party must be nested at two layers. In the first layer, implicit Want is used together with the **ohos.want.action.select** action to display the application sharing box. In the second layer, the data to share is declared
 
-      ```ts
-      import fileIO from '@ohos.fileio';
+in the custom field **parameters**, and then the Want that includes the **ohos.want.action.sendData** action and the **parameters** field is transferred to the application sharing box. The shared party obtains the shared data from **parameters**.
 
-      // let path = ...
-      // Open the file whose path is a variable.
-      let fileFd = fileIO.openSync(path, 0o102, 0o666);
-      ```
+```ts
+import common from '@ohos.app.ability.common';
 
-  2. As described in the prerequisites, the sharing party starts an application selector and shares the data to the selector, and the selector transfers the data to the shared party. Want of the sharing party must be nested at two layers. At the first layer, implicit Want is used together with the **ohos.want.action.select** action to display the application selector. At the second layer, complete Want is declared in the custom field **parameters** to transfer the data to share.
+let fileType = 'application/pdf';
+let fileName = 'TestFile.pdf';
+let fileFd = -1; // Obtain the file descriptor (FD) of the file to share.
+let fileSize; // Obtain the size of the file to share.
 
-      ```ts
-      import wantConstant from '@ohos.app.ability.wantConstant';
-      
-      // let path = ...
-      // let fileFd = ...
-      // let fileSize = ...
-      let want = {
-          / This action is used to implicitly match the application selector.
-          action: wantConstant.Action.ACTION_SELECT,
+function implicitStartAbility() {
+  let context = getContext(this) as common.UIAbilityContext;
+  let wantInfo = {
+    / This action is used to implicitly match the application sharing box.
+    action: 'ohos.want.action.select',
     // This is the custom parameter in the first layer of Want,
-          / which is intended to add information to the application selector.
+    / which is intended to add information to the application sharing box.
     parameters: {
       // MIME type of PDF.
-              "ability.picker.type": "application/pdf",
-              "ability.picker.fileNames": [path],
-              "ability.picker.fileSizes": [fileSize],
-              // This nested Want ,which will be directly sent to the selected application.        
-              "ability.want.params.INTENT": {
-                  "action": "ohos.want.action.sendData",
-                  "type": "application/pdf",
-                  "parameters": {
-                     "keyFd": {"type": "FD", "value": fileFd}
+      'ability.picker.type': fileType,
+      'ability.picker.fileNames': [fileName],
+      'ability.picker.fileSizes': [fileSize],
+      // This is nested Want ,which will be directly sent to the selected application.
+      'ability.want.params.INTENT': {
+        'action': 'ohos.want.action.sendData',
+        'type': 'application/pdf',
+        'parameters': {
+          'keyFd': { 'type': 'FD', 'value': fileFd }
         }
       }
     }
   }
-      ```
+  context.startAbility(wantInfo).then(() => {
+    ...
+  }).catch((err) => {
+    ...
+  })
+}
+```
 
-      In the preceding code, the custom field **parameters** is used. The **ability.picker.\*** fields in the first-layer **parameters** are used to pass the information to be displayed on the application selector. The following fields are involved:
+> **NOTE**
+>
+> Data sharing can be implemented only in FD format. For details about how to obtain the FD and file name, see [File Management](../reference/apis/js-apis-file-fs.md).
 
-      - **"ability.picker.type"**: The application selector renders the file type icon based on this field.
-      - **"ability.picker.fileNames"**: The application selector displays the file name based on this field.
-      - **"ability.picker.fileSizes"**: The application selector displays the file size based on this field. The unit is byte.
-      - **"ability.picker.fileNames"** and **"ability.picker.fileSizes"** are arrays and have a one-to-one mapping.
+In the preceding code, under the custom field **parameters**, the following **ability.picker.*** fields are used to pass the information to be displayed on the application sharing box:
 
-      For example, when **"ability.picker.type"** is **"application/pdf"**, **"ability.picker.fileNames"** is **"["APIs.pdf"]"**, and **"ability.picker.fileSizes"** is **"[350 \* 1024]"**, the application selector is displayed as follows:
+- **ability.picker.type**: file type icon.
+- **ability.picker.fileNames**: file name.
+- **ability.picker.fileSizes**: file size, in bytes.
+- **ability.picker.fileNames** and **ability.picker.fileSizes** are arrays and have a one-to-one mapping.
 
-      ![stage-want2](figures/stage-want2.png)
+The following figure shows an example.  
+![](figures/ability-startup-with-implicit-want2.png)
 
-      In the preceding code, the **ability.want.params.INTENT** field is nested Want. In this field, **action** and **type** are used for implicit matching by the application selector. For details about implicit matching, see [Matching Rules of Implicit Want](explicit-implicit-want-mappings.md#matching-rules-of-implicit-want). After the user selects an application, the nested Want of the **ability.want.params.INTENT** field is passed to that application.
+## Shared Party
 
-- Shared party
-  1. As mentioned above, the application selector performs implicit matching based on the **ability.want.params.INTENT** field. Therefore, you must set **skills** in the ability configuration file (**module.json5** file in the stage model) of the shared party as follows:
+To enable the shared party to identify the shared content, configure **skills** in the [module.json5 file](../quick-start/module-configuration-file.md) of the UIAbility of the shared party. The **actions** and **type** fields in **uris** match the **action** and **type** fields in **ability.want.params.INTENT** of the sharing party, respectively.
 
-      ```ts
+```json
+{
+  "module": {
+    ...
+    "abilities": [
+      {
+        ...
         "skills": [
           {
-          "entities": [
-            // ...
-          ],
+            ...
             "actions": [
+              "action.system.home",
               "ohos.want.action.sendData"
-              // ...
+              ...
             ],
             "uris": [
               {
                 "type": "application/pdf"
               },
-            // ...
             ]
-        },
+          }
         ]
-      ```
+      }
+    ]
+  }
+}
+```
 
-      The **actions** and **type** fields in **uris** match the **action** and **type** fields in **ability.want.params.INTENT**, respectively.
+After the user selects an application, the Want nested in the **ability.want.params.INTENT** field is passed to that application. After the UIAbility of the application starts, the application obtains **want** information from [**onCreate()**](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityoncreate) or [**onNewWant()**](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityonnewwant).
 
-      Files can be transferred in FD mode, but not URI mode. In implicit matching, the **type** field in Want must match the **type** field in **uris** under **skills** of the shared party. Therefore, specify only the **type** field in **uris**. If **host** and **port** are specified, the matching fails. The application selector initiates implicit matching based on **ability.want.params.INTENT**. Therefore, when the **uri** field added to **ability.want.params.INTENT** matches the **uris** field under **skills**, the matching is successful and additional data can be transferred.
-  2. After the application selector starts the shared party, the system calls **onCreate** and passes **ability.want.params.INTENT** to the **want** parameter.
+The following is an example of the Want obtained. You can use the FD of the shared file to perform required operations.
 
-      ```ts
-      onCreate(want, launchParam) {
-        // When keyFd is undefined, the application crashes.
-        if (want["parameters"]["keyFd"] !== undefined) {
-          // Receive the file descriptor.
-          let fd = want["parameters"]["keyFd"].value;
-          // ...
-        }
-      }
-      ```
+```json
+{
+    "deviceId": "",
+    "bundleName": "com.example.myapplication",
+    "abilityName": "EntryAbility",
+    "moduleName": "entry",
+    "uri": "",
+    "type": "application/pdf",
+    "flags": 0,
+    "action": "ohos.want.action.sendData",
+    "parameters": {
+        "component.startup.newRules": true,
+        "keyFd": {
+            "type": "FD",
+            "value": 36
+        },
+        "mime-type": "application/pdf",
+        "moduleName": "entry",
+        "ohos.aafwk.param.callerPid": 3488,
+        "ohos.aafwk.param.callerToken": 537379209,
+        "ohos.aafwk.param.callerUid": 20010014
+    },
+    "entities": []
+}
+```

en/application-dev/application-models/datashareextensionability.md

 # DataShareExtensionAbility (for System Applications Only)
 
 
-DataShareExtensionAbility provides the data sharing capability. System applications can implement a DataShareExtensionAbility or access an existing DataShareExtensionAbility in the system. Third-party applications can only access an existing DataShareExtensionAbility. For details, see [DataShare Development](../database/database-datashare-guidelines.md).
+DataShareExtensionAbility provides the data sharing capability. System applications can implement a DataShareExtensionAbility or access an existing DataShareExtensionAbility in the system. Third-party applications can only access an existing DataShareExtensionAbility. For details, see [Cross-Application Data Sharing Overview](../database/share-device-data-across-apps-overview.md).

en/application-dev/application-models/enterprise-extensionAbility.md

@@ -2,12 +2,11 @@
 
 ## Introduction to EnterpriseAdminExtensionAbility
 
-EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Management (MDM) applications. When developing MDM applications for enterprises, you need to inherit EnterpriseAdminExtensionAbility and implement MDM service logic in the EnterpriseAdminExtensionAbility instance. EnterpriseAdminExtensionAbility implements notifications of system management status changes and defines the callbacks when a device administrator application is enabled or disabled or an application is installed or uninstalled.
+EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Management (MDM) applications. When developing MDM applications for enterprises, you need to inherit EnterpriseAdminExtensionAbility and implement MDM service logic in the EnterpriseAdminExtensionAbility instance. EnterpriseAdminExtensionAbility implements notifications of system management status changes and defines the callbacks for when a device administrator application is enabled or disabled or an application is installed or uninstalled.
 
 ## Constraints
 
-  EnterpriseAdminExtensionAbility is applicable only to enterprise administrator applications.
-  
+EnterpriseAdminExtensionAbility is applicable only to enterprise administrator applications.
 
 ## Observing Activation/Deactivation of a Device Administrator Application and Installation/Removal of an Application
 
@@ -24,24 +23,24 @@ EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Manag
 ### Available APIs
 
 | Class                           | API                                 | Description                        |
-| :------------------------------ | ----------------------------------------- | ---------------------------- |
+| ------------------------------ | ----------------------------------------- | ---------------------------- |
+| EnterpriseAdminExtensionAbility | onAdminEnabled(): void                    | Called when a device administrator application is activated.  |
 | EnterpriseAdminExtensionAbility | onAdminDisabled(): void                   | Called when a device administrator application is deactivated.|
 | EnterpriseAdminExtensionAbility | onBundleAdded(bundleName: string): void   | Called when an application is installed on a device.            |
-| EnterpriseAdminExtensionAbility | onAdminEnabled(): void                    | Called when a device administrator application is activated.  |
 | EnterpriseAdminExtensionAbility | onBundleRemoved(bundleName: string): void | Called when an application is removed from a device.            |
 
 ### How to Develop
 
 To implement EnterpriseAdminExtensionAbility, you need to activate the device administrator application and create **ExtensionAbility** in the code directory of the device administrator application. The procedure is as follows:
 
-1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **EnterpriseExtAbility**.
+1. In the **ets** directory of the target module, right-click and choose **New > Directory** to create a directory named **EnterpriseExtAbility**.
 2. Right-click the **EnterpriseExtAbility** directory, and choose **New > TypeScript File** to create a file named **EnterpriseExtAbility.ts**.
 3. Open the **EnterpriseExtAbility.ts** file and import the **EnterpriseAdminExtensionAbility** module. Inherit the **EnterpriseAdminExtensionAbility** module to the custom class and add application notification callbacks, such as **onAdminEnabled()** and **onAdminDisabled()**. When the device administrator application is activated or deactivated, the device administrator can receive notifications.
 
-```ts
-import EnterpriseAdminExtensionAbility from '@ohos.enterprise.EnterpriseAdminExtensionAbility';
+   ```ts
+   import EnterpriseAdminExtensionAbility from '@ohos.enterprise.EnterpriseAdminExtensionAbility';
 
-export default class EnterpriseAdminAbility extends EnterpriseAdminExtensionAbility {
+   export default class EnterpriseAdminAbility extends EnterpriseAdminExtensionAbility {
 
        onAdminEnabled() {
            console.info("onAdminEnabled");
@@ -58,25 +57,25 @@ export default class EnterpriseAdminAbility extends EnterpriseAdminExtensionAbil
        onBundleRemoved(bundleName: string) {
            console.info("EnterpriseAdminAbility onBundleRemoved bundleName" + bundleName)
        }
-};
-```
+   };
+   ```
 
-​	4. Register **ServiceExtensionAbility** in the [**module.json5**](../quick-start/module-configuration-file.md) file corresponding to the project module. Set **type** to **enterpriseAdmin** and **srcEntrance** to the path of the ExtensionAbility code.
+4. Register **ServiceExtensionAbility** in the [**module.json5**](../quick-start/module-configuration-file.md) file corresponding to the project module. Set **type** to **enterpriseAdmin** and **srcEntry** to the path of the ExtensionAbility code.
 
-```ts
-"extensionAbilities": [
+   ```ts
+   "extensionAbilities": [
          {
            "name": "ohos.samples.enterprise_admin_ext_ability",
            "type": "enterpriseAdmin",
-        "visible": true,
-        "srcEntrance": "./ets/enterpriseextability/EnterpriseAdminAbility.ts"
+           "exported": true,
+           "srcEntry": "./ets/enterpriseextability/EnterpriseAdminAbility.ts"
          }
        ]
-```
+   ```
 
 ## Example
 
-Use **subscribeManagedEvent()** and **unsubscribeManagedEvent()** in the @ohos.enterprise.adminManager module to subscribe to application installation and removal events. When an application is installed or removed, the MDM application is notified of the event. Then, the MDM application reports the event in the callback to notify the enterprise administrator.
+Use **subscribeManagedEvent** in the **@ohos.enterprise.adminManager** module to subscribe to application installation and removal events. When an application is installed or removed, the MDM application is notified of the event. Then, the MDM application reports the event in the callback to notify the enterprise administrator. To unsubscribe from events, use **unsubscribeManagedEvent**.
 
 ```ts
   @State managedEvents: Array<adminManager.ManagedEvent> = [0,1]
@@ -105,3 +104,4 @@ Use **subscribeManagedEvent()** and **unsubscribeManagedEvent()** in the @ohos.e
     })
   }
 ```
+

en/application-dev/application-models/explicit-implicit-want-mappings.md

 # Matching Rules of Explicit Want and Implicit Want
 
-Both explicit Want and implicit Want can be used to match an ability to start based on certain rules. These rules determine how the parameters set in Want match the configuration file declared by the target ability.
+Both explicit [Want](../reference/apis/js-apis-app-ability-want.md) and implicit [Want](../reference/apis/js-apis-app-ability-want.md) can be used to match an application component to start based on certain rules. These rules determine how the parameters set in [want](../reference/apis/js-apis-app-ability-want.md) match the configuration file declared by the target application component.
 
 ## Matching Rules of Explicit Want
 
 
-The table below describes the matching rules of explicit Want.
+The table below describes the matching rules of explicit [Want](../reference/apis/js-apis-app-ability-want.md).
 
 | Name| Type| Matching Item| Mandatory| Rule Description|
 | -------- | -------- | -------- | -------- | -------- |
-| deviceId | string | Yes| No| If this field is unspecified, only abilities on the local device are matched.|
+| deviceId | string | Yes| No| If this field is unspecified, only application components on the local device are matched.|
 | bundleName | string | Yes| Yes| If **abilityName** is specified but **bundleName** is unspecified, the matching fails.|
-| moduleName | string | Yes| No| If this field is unspecified and multiple modules with the same ability name exist in the application, the first ability is matched by default.|
+| moduleName | string | Yes| No| If this field is unspecified and multiple modules with the same ability name exist in the application, the first application component is matched by default.|
 | abilityName | string | Yes| Yes| To use explicit Want, this field must be specified.|
-| uri | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| type | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| action | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| entities | Array<string> | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
+| uri | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| type | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| action | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| entities | Array<string> | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
 | flags | number | No| No| This field is not used for matching and is directly transferred to the system for processing. It is generally used to set runtime information, such as URI data authorization.|
-| parameters | {[key: string]: any} | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
+| parameters | {[key: string]: any} | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
 
 ## Matching Rules for Implicit Want
 
-The table below describes the matching rules of implicit Want.
+The table below describes the matching rules of implicit [Want](../reference/apis/js-apis-app-ability-want.md).
 
 | Name       | Type                          | Matching Item| Mandatory| Rule Description                                                        |
 | ----------- | ------------------------------ | ------ | ---- | ------------------------------------------------------------ |
@@ -35,30 +35,32 @@ The table below describes the matching rules of implicit Want.
 | action      | string                         | Yes    | No  |                                                              |
 | entities    | Array<string>            | Yes    | No  |                                                              |
 | flags       | number                         | No    | No  | This field is not used for matching and is directly transferred to the system for processing. It is generally used to set runtime information, such as URI data authorization.|
-| parameters  | {[key: string]: any} | No    | No  | This field is not used for matching. It is passed to the target ability as a parameter.         |
+| parameters  | {[key: string]: any} | No    | No  | This field is not used for matching. It is passed to the target application component as a parameter.        |
 
 Get familiar with the following about implicit Want:
 
 
 - The **want** parameter passed by the caller indicates the operation to be performed by the caller. It also provides data and application type restrictions.
 
-- The **skills** field declares the capabilities of the target ability. For details, see [the skills tag](../quick-start/module-configuration-file.md#skills) in the [module.json5 file](../quick-start/module-configuration-file.md).
+- The **skills** field declares the capabilities of the target application component. For details, see [the skills tag](../quick-start/module-configuration-file.md#skills) in the [module.json5 file](../quick-start/module-configuration-file.md).
 
 
-The system matches the **want** parameter (including the **action**, **entities**, **uri**, and **type** attributes) passed by the caller against the **skills** configuration (including the **actions**, **entities**, **uris**, and **type** attributes) of the abilities one by one. When all the four attributes are matched, a dialog box is displayed for users to select a matched application.
+The system matches the **want** parameter (including the **action**, **entities**, **uri**, and **type** attributes) passed by the caller against the **skills** configuration (including the **actions**, **entities**, **uris**, and **type** attributes) of the application components one by one. When all the four attributes are matched, a dialog box is displayed for users to select a matched application.
 
 
 ### Matching Rules of action in the want Parameter
 
-The system matches the [action](../reference/apis/js-apis-ability-wantConstant.md#wantconstantaction) attribute in the **want** parameter passed by the caller against **actions** under **skills** of the abilities.
+The system matches the **action** attribute in the **want** parameter passed by the caller against **actions** under **skills** of the application components.
 
-- If **action** in the passed **want** parameter is specified but **actions** under **skills** of an ability is unspecified, the matching fails.
+- If **action** in the passed **want** parameter is unspecified and **actions** under **skills** of an application component is unspecified, the matching fails.
 
-- If **action** in the passed **want** parameter is unspecified but **actions** under **skills** of an ability is specified, the matching is successful.
+- If **action** in the passed **want** parameter is specified but **actions** under **skills** of an application component is unspecified, the matching fails.
 
-- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an ability is specified and contains **action** in the passed **want** parameter, the matching is successful.
+- If **action** in the passed **want** parameter is unspecified but **actions** under **skills** of an application component is specified, the matching is successful.
 
-- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an ability is specified but does not contain **action** in the passed **want** parameter, the matching fails.
+- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an application component is specified and contains **action** in the passed **want** parameter, the matching is successful.
+
+- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an application component is specified but does not contain **action** in the passed **want** parameter, the matching fails.
 
   **Figure 1** Matching rules of action in the want parameter
 
@@ -67,68 +69,73 @@ The system matches the [action](../reference/apis/js-apis-ability-wantConstant.m
 
 ### Matching Rules of entities in the want Parameter
 
-The system matches the [entities](../reference/apis/js-apis-ability-wantConstant.md#wantconstantentity) attribute in the **want** parameter passed by the caller against **entities** under **skills** of the abilities.
+The system matches the **entities** attribute in the **want** parameter passed by the caller against **entities** under **skills** of the application components.
 
-- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an ability is specified, the matching is successful.
+- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an application component is specified, the matching is successful.
 
-- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an ability is unspecified, the matching is successful.
+- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an application component is unspecified, the matching is successful.
 
-- If **entities** in the passed **want** parameter is specified but **entities** under **skills** of an ability is unspecified, the matching fails.
+- If **entities** in the passed **want** parameter is specified but **entities** under **skills** of an application component is unspecified, the matching fails.
 
-- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an ability is specified and contains **entities** in the passed **want** parameter, the matching is successful.
+- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an application component is specified and contains **entities** in the passed **want** parameter, the matching is successful.
 
-- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an ability is specified but does not contain **entities** in the passed **want** parameter, the matching fails.
+- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an application component is specified but does not contain **entities** in the passed **want** parameter, the matching fails.
 
-  Figure 2 Matching rule of entities in the want parameter
+  **Figure 2** Matching rules of entities in the want parameter
 
   ![want-entities](figures/want-entities.png)  
 
 
 ### Matching Rules of uri and type in the want Parameter
 
-When the **uri** and **type** parameters are specified in the **want** parameter to initiate a component startup request, the system traverses the list of installed components and matches the **uris** array under **skills** of the abilities one by one. If one of the **uris** arrays under **skills** matches the **uri** and **type** in the passed **want**, the matching is successful.
-
-Figure 3 Matching rules when uri and type are specified in the want parameter 
-
-![want-uri-type1](figures/want-uri-type1.png)
+When the **uri** and **type** parameters are specified in the **want** parameter to initiate an application component startup request, the system traverses the list of installed components and matches the **uris** array under **skills** of the application components one by one. If one of the **uris** arrays under **skills** matches the **uri** and **type** in the passed **want**, the matching is successful.
 
 There are four combinations of **uri** and **type** settings. The matching rules are as follows:
 
 - Neither **uri** or **type** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching is successful.
-  - If the **uris** array under **skills** of an ability contains an URI element whose **scheme** and **type** are unspecified, the matching is successful.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching is successful.
+  - If the **uris** array under **skills** of an application component contains an URI element whose **scheme** and **type** are unspecified, the matching is successful.
   - In other cases, the matching fails.
 
 - Only **uri** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an element whose [uri is matched](#matching-rules-of-uri) and **type** is unspecified, the matching is successful. Otherwise, the matching fails.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an element whose [uri is matched](#matching-rules-of-uri) and **type** is unspecified, the matching is successful. Otherwise, the matching fails.
 
 - Only **type** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an URI element whose **scheme** is unspecified and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an URI element whose **scheme** is unspecified and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
+
+- Both **uri** and **type** are specified in the **want** parameter, as shown below.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an element whose [uri is matched](#matching-rules-of-uri) and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
 
-- Both **uri** and **type** are specified in the **want** parameter, as shown in Figure 3.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an element whose [uri is matched](#matching-rules-of-uri) and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
+Leftmost URI matching: When only **scheme**, a combination of **scheme** and **host**, or a combination of **scheme**, **host**, and **port** is configured in the **uris** array under **skills** of the application component, the matching is successful only if the leftmost URI in the passed **want** parameter matches **scheme**, the combination of **scheme** and **host**, or the combination of **scheme**, **host**, and **port**.
 
+**Figure 3** Matching rules when uri and type are specified in the want parameter
 
-To simplify the description, **uri** and **type** passed in the **want** parameter are called **w_uri** and **w_type**, respectively; the **uris** array under **skills** of an ability to match is called **s_uris**; each element in the array is called **s_uri**. Matching is performed from top to bottom.
+![want-uri-type1](figures/want-uri-type1.png)  
+
+To simplify the description:
 
+- **uri** in the **want** parameter passed in by the caller is called **w_uri**; each element in the **uris** array under **skills** of the application component to match is called **s_uri**.
+- **type** in the **want** parameter passed in by the caller is called **w_type**; the type in the **uris** array under **skills** of the application component to match is called **s_type**.
 
-Figure 4 Matching rules of uri and type in the want parameter
+**Figure 4** Matching rules of uri and type in the want parameter
 
 ![want-uri-type2](figures/want-uri-type2.png)  
 
 
 ### Matching Rules of uri
 
-To simplify the description, **uri** in the passed **want** parameter is called **w_uri**; **uri** under **skills** of an ability to match is called **s_uri**. The matching rules are as follows:
+The rules are as follows:
 
 - If **scheme** of **s_uri** is unspecified and **w_uri** is unspecified, the matching is successful. Otherwise, the matching fails.
 
 - If **host** of **s_uri** is unspecified and **scheme** of **w_uri** and **scheme** of **s_uri** are the same, the matching is successful. Otherwise, the matching fails.
 
-- If **path**, **pathStartWith**, and **pathRegex** of **s_uri** are unspecified and **w_uri** and **s_uri** are the same, the matching is successful. Otherwise, the matching fails.
+- If **port** of **s_uri** is unspecified and the combination of **scheme** and **host** of **w_uri** is the same as the combination of **scheme** and **host** of **s_uri**, the matching is successful. Otherwise, the matching fails.
+
+- If **path**, **pathStartWith**, and **pathRegex** of **s_uri** are unspecified and the combination of **scheme**, **host**, and **port** of **w_uri** is the same as the combination of **scheme**, **host**, and **port** of **s_uri**, the matching is successful. Otherwise, the matching fails.
 
 - If **path** of **s_uri** is specified and the **full path expressions** of **w_uri** and **s_uri** are the same, the matching is successful. Otherwise, the matching of **pathStartWith** continues.
 
@@ -138,12 +145,14 @@ To simplify the description, **uri** in the passed **want** parameter is called
 
 > **NOTE**
 >
-> The **scheme**, **host**, **port**, **path**, **pathStartWith**, and **pathRegex** attributes of **uris** under **skills** of an ability are concatenated. If **path**, **pathStartWith**, and **pathRegex** are declared in sequence, **uris** can be concatenated into the following expressions:
+> The **scheme**, **host**, **port**, **path**, **pathStartWith**, and **pathRegex** attributes of **uris** under **skills** of an application component are concatenated. If **path**, **pathStartWith**, and **pathRegex** are declared in sequence, **uris** can be concatenated into the following expressions:
 >
+> - **Prefix URI expression**: When only **scheme**, a combination of **scheme** and **host**, or a combination of **scheme**, **host**, and **port** is configured in the configuration file, the matching is successful if a URI prefixed with the configuration file is passed in.
+>     * `scheme://`
+>     * `scheme://host`
+>     * `scheme://host:port`
 > - **Full path expression**: `scheme://host:port/path`
->
 > - **Prefix expression**: `scheme://host:port/pathStartWith`
->
 > - **Regular expression**: `scheme://host:port/pathRegex`
 
 
@@ -153,7 +162,7 @@ To simplify the description, **uri** in the passed **want** parameter is called
 >
 > The matching rules of **type** described in this section are based on the fact that **type** in the **want** parameter is specified. If **type** is unspecified, follow the [matching rules of uri and type in the want parameter](#matching-rules-of-uri-and-type-in-the-want-parameter).
 
-To simplify the description, **uri** in the passed **want** parameter is called **w_type**, and **type** of **uris** under **skills** of an ability to match is called **s_type**. The matching rules are as follows:
+The matching rules are as follows:
 
 - If **s_type** is unspecified, the matching fails.
 

en/application-dev/application-models/extensionability-overview.md

@@ -9,9 +9,9 @@ An [ExtensionAbilityType](../reference/apis/js-apis-bundleManager.md#extensionab
 
 - [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md): ExtensionAbility component of the form type, which provides APIs related to widgets.
 
-- [WorkSchedulerExtensionAbility](../reference/apis/js-apis-WorkSchedulerExtensionAbility.md): ExtensionAbility component of the work_scheduler type, which provides APIs for registering, canceling, and querying Work Scheduler tasks.
+- [WorkSchedulerExtensionAbility](../reference/apis/js-apis-WorkSchedulerExtensionAbility.md): ExtensionAbility component of the work_scheduler type, which provides callbacks for Work Scheduler tasks.
 
-- [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod.md): ExtensionAbility component of the input_method type, which provides an input method framework that can be used to hide the keyboard, obtain the list of installed input methods, display the dialog box for input method selection, and more.
+- [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod.md): ExtensionAbility component of the input_method type, which is used to develop input method applications.
 
 - [ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md): ExtensionAbility component of the service type, which provides APIs related to background service scenarios.
 
@@ -25,6 +25,14 @@ An [ExtensionAbilityType](../reference/apis/js-apis-bundleManager.md#extensionab
 
 - [EnterpriseAdminExtensionAbility](../reference/apis/js-apis-EnterpriseAdminExtensionAbility.md): ExtensionAbility component of the enterprise_admin type, which provides APIs for processing enterprise management events, such as application installation events on devices and events indicating too many incorrect screen-lock password attempts.
 
+> **NOTE**
+>
+> 1. Third-party applications cannot implement ServiceExtensionAbility, DataShareExtensionAbility, StaticSubscriberExtensionAbility, or WindowExtensionAbility.
+>
+> 2. To implement transaction processing in the background for a third-party application, use background tasks rather than ServiceExtensionAbility. For details, see [Background Task](../task-management/background-task-overview.md).
+>
+> 3. Third-party applications can use other types of ExtensionAbility components that have been defined.
+
 
 ## Using ExtensionAbility of the Specified Type
 
@@ -39,10 +47,9 @@ The following uses [InputMethodExtensionAbility](../reference/apis/js-apis-input
 
 ## Implementing ExtensionAbility of the Specified Type
 
-The following uses [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) as an example. The widget framework provides the base class [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md). You derive this base class to create your own class (such as **MyFormExtensionAbility**), implement the callbacks, such as **onCreate()** and **onUpdateForm()**, to provide specific widget functionalities. For details, see [FormExtensionAbility](Widget-development-stage.md).
+The following uses [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) as an example. The widget framework provides the base class [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md). You derive this base class to create your own class (such as **MyFormExtensionAbility**), implement the callbacks, such as **onCreate()** and **onUpdateForm()**, to provide specific widget functionalities. For details, see [FormExtensionAbility](service-widget-overview.md).
 
 You do not need to care when to add or delete a widget. The lifecycle of the FormExtensionAbility instance and the lifecycle of the ExtensionAbility process where the FormExtensionAbility instance is located are scheduled and managed by FormManagerService.
-
 ![form_extension](figures/form_extension.png)
 
 

en/application-dev/application-models/fa-model-development-overview.md

@@ -3,12 +3,13 @@
 
 During application development based on the Feature Ability (FA) model, the following tasks are involved in the application model.
 
-**Table 1** FA model development process
+
+  **Table 1** FA model development process
 
 | Task| Introduction| Guide|
 | -------- | -------- | -------- |
-| Application component development| Use the PageAbility, ServiceAbility, DataAbility, and widgets of the FA model to develop applications.| - [Application- or Component-Level Configuration](application-component-configuration-fa.md)<br>- [PageAbility Component](pageability-overview.md)<br>- [ServiceAbility Component](serviceability-overview.md)<br>- [DataAbility Component](dataability-overview.md)<br>- [Widget Development](Widget-development-fa.md)<br>- [Context](application-context-fa.md)<br>- [Want](want-fa.md) |
-| Inter-process communication (IPC)| Learn the process model and common IPC modes of the FA model.| [Common Events](common-event-fa.md)<br>[Background Services](rpc.md) |
-| Inter-thread communication| Learn the thread model and common inter-thread communication modes of the FA model.| [Inter-Thread Communication](itc-fa-overview.md)|
+| Application component development| Use the PageAbility, ServiceAbility, DataAbility, and widgets of the FA model to develop applications.| - [Application- or Component-Level Configuration](application-component-configuration-fa.md)<br>- [PageAbility Component](pageability-overview.md)<br>- [ServiceAbility Component](serviceability-overview.md)<br>- [DataAbility Component](dataability-overview.md)<br>- [Widget Development](widget-development-fa.md)<br>- [Context](application-context-fa.md)<br>- [Want](want-fa.md)|
+| Process model| Learn the process model and common IPC modes of the FA model.| [Common Events](common-event-fa.md)<br>[Background Services](rpc.md)|
+| Thread model| Learn the thread model and common inter-thread communication modes of the FA model.| [Inter-Thread Communication](itc-fa-overview.md)|
 | Mission management| Learn the basic concepts and typical scenarios of mission management in the FA model.| [Mission Management](mission-management-fa.md)|
-| Application configuration file| Learn the requirements for developing application configuration files in the FA model.| [Application Configuration File](../quick-start/application-configuration-file-overview-fa.md) |
+| Application configuration file| Learn the requirements for developing application configuration files in the FA model.| [Application Configuration File](../quick-start/application-configuration-file-overview-fa.md)|

en/application-dev/application-models/hop-cross-device-migration.md

-# Cross-Device Migration (for System Applications Only)]
+# Cross-Device Migration (for System Applications Only)
 
 
 ## When to Use
@@ -47,32 +47,23 @@ The table below describes the main APIs used for cross-device migration. For det
 
 ## How to Develop
 
-1. Configure the data synchronization permission in the **module.json5** file. The sample code is as follows:
+1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-   ```json
-   {
-     "module": {
-       "requestPermissions":[  
-         {  
-           "name" : "ohos.permission.DISTRIBUTED_DATASYNC",
-         }
-       ]
-     }
-   }
-   ```
-
-2. Configure the fields related to cross-device migration in the configuration file.
-   - Configure the application to support migration.
+2. Display a dialog box to ask authorization from the user when the application is started for the first time. For details, see [Requesting User Authorization](../security/accesstoken-guidelines.md#requesting-user-authorization).
 
+3. Configure the fields related to cross-device migration in the configuration file.
 
+   Configure the application to support migration.
    Set the **continuable** field in the **module.json5** file to **true**. The default value is **false**. If this parameter is set to **false**, the application cannot be continued on the target device.
+
+
    ```json
    {
      "module": {
-          // ...
+       ...
        "abilities": [
          {
-              // ...
+           ...
            "continuable": true,
          }
        ]
@@ -80,26 +71,10 @@ The table below describes the main APIs used for cross-device migration. For det
    }
    ```
 
-   - Configure the application launch type. For details, see [UIAbility Component Launch Type](uiability-launch-type.md).
-
-3. Request the data synchronization permission. The sample code for displaying a dialog box to request the permission is as follows:
-   
-   ```ts
-   requestPermission() {   
-       let context = this.context
-       let permissions: Array<string> = ['ohos.permission.DISTRIBUTED_DATASYNC']   
-       context.requestPermissionsFromUser(permissions).then((data) => {   
-           console.info("Succeed to request permission from user with data: "+ JSON.stringify(data))
-       }).catch((error) => {       
-           console.info("Failed to request permission from user with error: "+ JSON.stringify(error))   
-       }) 
-   }
-   ```
+   Configure the application launch type. For details, see [UIAbility Component Launch Type](uiability-launch-type.md).
 
 4. Implement [onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) in the UIAbility of the initiator.
-
    [onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) is called on the initiator. You can save the  data in this method to implement application compatibility check and migration decision.
-
    - Saving migrated data: You can save the data to be migrated in key-value pairs in **wantParam**.
 
    - Checking application compatibility: You can obtain the version number of the target application from **wantParam** and check the compatibility between the target application and the current application.