Help Center> > User Guide > Mobile >App Management

App Management

App management refers to creating a mobile app.

  1. Permissions required by mobile probes:



  2. Ensure that the Java 1.8 or a later version is installed and the JAVA_HOME environment variable is correct.

Creating a Mobile App

  1. In the navigation pane, choose Mobile > App Management.
  2. Click Download Instrument Tool to download the tool package to the local host, and decompress it.



  3. Create an app. Click Create Mobile App, enter an app name, and click Generate. The system generates a dedicated command for your app.

    The following figure shows the Windows and Linux instrument commands.

  4. Click Finish and Copy. The app is created and the instrument command is automatically copied to the clipboard.
  5. Copy the generated command to a TXT file, and replace {APK_PATH} with the actual APK address.


    1. Access the apk_instrumenter directory.
    2. Open the cmd in the current file.

    3. Replace {APK_PATH} in the generated Windows command with the full APK path to be tracked.


    1. Access the apk_instrumenter directory.
    2. Replace {APK_PATH} in the generated Linux command with the full APK path to be tracked.

  6. Copy and run the command based on your Operating System (OS).

    1. Run the replaced command in the cmd.

    2. After the tracking is complete, both the original and tracked APKs are displayed in the file.


    Run the instrument command in the apk_instrumenter directory. After the command is executed, the generated APK is displayed.

  7. Sign the APK and install it.


    After the tracking is complete, the APK is not signed. You need to sign the generated APK.

Instrument Command

  1. After the app is created, the instrument command exists in the clipboard. If the command is lost or you need to track an upgraded app, click View Instrument Command in the Operation column.

  2. In the View Instrument Command dialog box, click Finish and Copy to obtain the command again.

  3. Implement tracking again to generate a new APK file.

    About 3 minutes later, the performance statistics of the mobile app will be sent to the mobile server. Then, you can view the app performance data on the App Summary page. You can also view the topology of the backend service on the Topology page, or expand the frontend to view Android statistics.

Tracking Tool Package Readme


  • The APK that undergoes security hardening is not supported.
  • The APK needs to be signed after tracking is complete.

Tracking Technology Overview

As shown in Figure 1, the tracking tool uses the open-source tool ( to parse the compiled APK and integrates codes into customers' apps based on the configuration file in the tool package, reducing customers' development costs. This configuration file is decompressed to the C:\Windows\Temp\huaweiapmmobile\plugins directory after the tracking is complete. This tool does not collect data or analyze codes from customers' apps without permissions. All integrated codes are transparent. Customers can use the APKTool provided in the tool package to decompress APKs and compare codes before and after the tracking.

Figure 1 Principle of the tracking technology

Instrument Command Parameters

Table 1 describes the instrument command parameters. For example, in the Windows environment, the instrument command contains instrument.bat @Param_APKFile @Param_AppID @Param_Gateway.

Table 1 Instrument command parameters




Path of the APK file

Full path of the APK file


App ID

AppID generated on the page.


Gateway address

Gateway address of the backend data generated on the page.


Whether to sign the APK file

Whether to sign the default signature file (manually generated) of Android Studio. If the value of this parameter is 1, sign the file. Otherwise, do not sign the file.


If the signature file is abnormal, the signature fails, but the file that is not signed will not be affected.


For more information, see the instrument command parameters in Creating a Mobile App.

Performance and Data Traffic

Table 2 describes the performance and data traffic of the tracking tool.

Table 2 Performance and data traffic

Metric Dimension



Increase of less than 2%.


Increase of less than 3 MB (depending on the service load). The deviation is less than 5%.

Data traffic

Crash or ANR scenario: About 200 KB for each piece of crash or Application Not Responding (ANR) analysis data. Other scenarios: 1 KB/minute. The deviation is less than 5%.

More Operations

On the App Management page, you can also perform the operations in Table 3:

Table 3 Related operations



Select or clear all

Click to select all apps or click to clear them.

Go to the Topology page

Click View Topology in the Operation column to go to the Topology page and view call details.

Go to the App Summary page

Click View Summary in the Operation column to go to the App Summary page and view user experience details.