We use essential cookies for the website to function, as well as analytics cookies for analyzing and creating statistics of the website performance. To agree to the use of analytics cookies, click "Accept All". You can manage your preferences at any time by clicking "Cookie Settings" on the footer. More Information.

Only Essential Cookies
Accept All
GuidesWear EngineAndroid Phone App DevelopmentGetting StartedApplying for the Wear Engine Service

Applying for the Wear Engine Service

Before applying for the Wear Engine service, make sure that you have completed the task of Registering a HUAWEI ID and Applying for the HUAWEI ID Service.

  1. Go to App services > Development > Wear Engine.

    Figure 1 Wear Engine card

    NOTE

    If you can't find the Wear Engine card, click on the right of Development to add a card.

  1. Click Apply for Wear Engine and agree to the agreement. The screen for data permission application will then be displayed.

    Figure 2 Applying for the Wear Engine Service

  2. Select Android app and select a product and the required permissions. (Individual developers can only apply for basic device information and message notification permissions.)

    NOTE
    • You need to apply for the permissions for the app on the phone. By default, you do not need to apply for permissions for the wearable app.
    • If no selectable apps are shown in the drop-down list box, apply for the HUAWEI ID service as instructed in Registering a HUAWEI ID and Applying for the HUAWEI ID Service.

    Table 1 Permission description
    Expand

    Permission

    Open Capability

    Function

    Basic device information

    DEVICE_MANAGER

    Wearable device status management

    Querying basic wearable device information

    Obtains a list of paired wearable devices and selects a device; queries the available space of the wearable device.

    Querying or subscribing to the wearable device status

    Queries the battery level; subscribes to low battery level alerts; queries or subscribes to the connection status, available space, and charging status of wearable devices.

    Communications management

    Sending P2P messages or files

    xxx (your app name) on the phone sends a message or file to xxx (your app name) on the wearable device.

    Receiving P2P messages or files

    xxx (your app name) on the phone receives a message or file from xxx (your app name) on the wearable device.

    Message notification

    NOTIFY

    Message notification management

    Sending notifications to the wearable device

    Your phone app sends a notification to the wearable device and the notification is displayed on the wearable device according to the template. The message title, content, and button can be configured.

    Wearable user status

    WEAR_USER_STATUS

    Wearable device users' status management

    Querying or subscribing to the wearable user status

    Queries and subscribes to users' wearing status; subscribes to users' heart rate alerts.

    Device identifier

    DEVICE_SN

    Device identifier

    Obtaining the device SN

    Obtains the SN of paired wearable devices.

  3. Upload the data permission, data usage description, and the user authorization path description, select whether to show the HUAWEI logo on the authorization screen, and submit the application.

    • Requirements on describing requested data permissions and their usage
      • Data permission: Provide data permissions to be applied for. Each permission occupies a row.
      • Data usage: Describe the requirements, scenarios, and purposes of data usage, and the way you will use the data.
      • Data display path: Provide the screenshots of the application scenarios of the permissions to be applied for. (Optional)
    • Requirements for filling in the user authorization path description:
      • Provide screenshots of the user authorization screens and the text description of the operation paths.
      • If the modification permission comes with your app, provide screenshots of the user authorization modification screens and the text description of the operation paths. (Optional)

  4. Wait for the approval result.

    Generally, the approval process may take one to two weeks, depending on the requested permission types and the app release regions.

    An application won't be approved if the submitted materials do not meet the requirements. Once the application is approved, the development and test phases can start and the app can be released once the related procedures are completed.

    If your business scope changes and you need to modify the corresponding data permissions, click Modify and submit the application again.

    Figure 3 Application approved

Search
Enter a keyword.