Skip to main content

Operation experience analysis

User operation is an important part of the user experience module. Operation experience analysis can monitor the usability and performance of the "operation" in the process of real user use, which plays an important role in analyzing the user experience and performance of real end users. Operation experience analysis can provide customers with operation availability and performance trend data display in the process of real user operation (including operation time consumption, blocking time consumption, providing multi-dimensional distribution charts of system version, equipment and region). It provides abnormal data analysis and tracking in the operation process (including slow operation, stuttering operation, error operation, crash, HTTP error, network error, and single sample details of all kinds of abnormalities), which completely subverts and changes the standards and methods of user experienc e measurement of APM manufacturers on the market at present, and makes our products. Upgrade to the business success value-oriented "user experience management platform". At the same time, the value also helps R & D, operation and maintenance to prevent risks, find positioning and solve performance problems, promote internal cooperation, increase business initiative and optimize user experience, so as to enhance brand goodwill, customer retention, business conversion rate, business achievement and business amount.

Description of indicators​

  • Operation name: the specific method name of the operation (Android: class name + control ID; iOS: class name + method name).

  • Page: the name of the page to which the operation belongs (Android: Activity or Fragment name; iOS: VC name).

  • Number of operations: The total number of times the operation was performed.

  • Operation time consumed: The total time consumed by the operation (including the execution time of the asynchronous method).

  • Blocking time: The execution time of the entry function during the operation (the user cannot do anything during the blocking process).

  • Failed operation: an operation with a request error rate of 100% during the operation (three requests are issued during the operation, and if all three requests have errors, this operation is an error operation).

  • Crash operation: The operation that the application crashes/backs down during the operation.

  • Smooth operation: operation that takes less time than the set threshold (default threshold of 3s).

  • Slow operation: operation that takes more time than the set threshold (default threshold of 3s).

  • Stuck operation: the blocking time exceeds the set threshold (default threshold of 3s).

  • Number of available operations: total number of operations-number of failed operations-number of crash operations.

  • Availability = number of operations available/total number of operations

  • Proportion of smooth operation = number of smooth operations/total number of operations

  • Proportion of slow operations = number of slow operations/total number of operations

  • Percentage of stuttering operations = number of stuttering operations/total number of operations

  • Percentage of crash operations = number of crash operations/total number of operations

  • Proportion of failed operations = number of failed operations/total number of operations

Type of operation​

Android​

Click event:

  • onClick

  • onItemClick

  • ItemSelected

  • PageSelected

iOS​

Operational events other than the system:

  • UI TapGestureRecognizer (click)

  • UIPinchGestureRecognizer (two-finger kneading)

  • UIS wipeGestureRecognizer (Swipe)

  • UIPanGestureRecognizer (drag)

  • UI ScreenEdgePanGe stureRecognizer (swipe left from the right edge of the screen)

  • UILongPressGe stureRecognizer (long press)

Controls:

  • UITableView-didSelectRowAtIndexPath

  • UICollectionView-didSelectItemAtIndexPath

  • UIPickerView-didSelectRow