In-Browser Application Event Annotation Via Experience Simulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for annotating events in applications require multi-party communication and coordination, leading to high communication costs and delayed data collection, as they rely on embedded codes that only take effect after application changes are launched.
Innovation Solution
A method and apparatus using an event annotating tool that allows analysts to visually annotate events through an application experience simulator, reducing the need for communication with developers and testers by displaying event information related to selected elements and confirming operation events directly in the tool.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If embedded code is used for event annotation, then data collection can be automated, but communication cost increases and data cannot be obtained instantly
Solution Approach 1:
The system performs preliminary action by pre-instrumenting the application with annotation capabilities during the development phase. Event annotation configurations are prepared and stored in advance, allowing immediate data collection once the application runs, eliminating the need for post-deployment code modifications and relaunches.
Solution Approach 2:
An intermediary annotation system is introduced between the application and the data collection mechanism. This intermediary layer captures events in real-time without requiring direct code embedding at event locations, enabling automated data collection while providing immediate access to event data through a separate annotation interface.
2Measurement precision
If embedded code is used for event annotation, then event data can be collected, but communication and coordination among multiple parties is required
Solution Approach 1:
The annotation system provides self-service capabilities where developers can independently configure and annotate events without requiring coordination with analysts or testers. The system includes built-in tools for event identification, configuration, and validation, allowing a single person to complete the entire annotation process.
Solution Approach 2:
The annotation system is designed as a universal platform that combines multiple functions previously requiring separate roles: event identification, data collection configuration, validation, and analysis. This multi-functional system eliminates the need for multiple parties by consolidating all annotation tasks into a single integrated tool.
3Measurement precision
If embedded code is used for event annotation, then code-level event tracking is achieved, but annotation difficulty and cost increase
Solution Approach 1:
The system replaces the mechanical process of manual code embedding with an automated annotation mechanism. Instead of requiring analysts to locate and insert code at specific event points, the system uses automated event detection and annotation technologies that capture events through non-invasive means, significantly reducing annotation difficulty.
Solution Approach 2:
The system creates a virtual copy or model of the application's event structure that mirrors the actual application behavior. This copied event model allows for precise event tracking without modifying the original application code, enabling code-level tracking while eliminating the complexity of direct code embedding.
Data Source
AI summary
A user interface of an event annotating tool is displayed in a browser. In response to a start operation, a user interface of an application experience simulator of the application is displayed in the user interface of the event annotating tool. When the application experience simulator enters an element selection mode, in response to a selection operation of a first element in the user interface of the application experience simulator, event annotating information related to the first element is displayed in the user interface of the event annotating tool. The event annotating information includes at least an interaction type and/or a display feature of an element related to the first element. In response to a confirmation operation on the event annotating information, one or more operation events that occur in the application corresponding to the application experience simulator and match the event annotating information are annotated.