Mobile App Event Detection Without Code Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile application development requires frequent code updates to detect and correlate user-initiated events, which is computationally expensive and burdens mobile devices, often leading to performance issues and increased development and testing time.
Innovation Solution
A system that detects user-initiated events within mobile applications without modifying the application's code, using front-end and back-end servers to correlate events by linking user interaction identifiers with interactive item identifiers, allowing for event detection and correlation without installing or modifying SDKs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If code updates are performed frequently to detect and correlate user-initiated events, then event detection capability is improved, but computing resources are consumed and battery life is reduced
Solution Approach 1:
The patent introduces a server as an intermediary that performs event detection and correlation externally, eliminating the need for the mobile device to run detection code locally. The server receives interaction data from the device, correlates events using stored data entries, and sends results back, thus preserving battery life while maintaining event detection capability.
Solution Approach 2:
The patent extracts the event detection and correlation functionality from the mobile application code and relocates it to a separate server system. This allows the mobile device to operate without the computationally expensive detection code, while the server handles all event analysis externally.
2Adaptability or versatility
If code updates are performed frequently to detect and correlate user-initiated events, then event detection capability is improved, but development and testing time is increased
Solution Approach 1:
The server acts as an intermediary that can be updated independently of mobile applications. Event detection logic, correlation rules, and data entry structures are modified on the server side only, eliminating the need to recompile, redistribute, and test mobile application code for every event detection enhancement.
Solution Approach 2:
The patent shifts event detection from the application code dimension to the server infrastructure dimension. This allows detection capabilities to be enhanced by modifying server-side data structures and correlation logic without touching the mobile application layer, thus avoiding development and testing cycles for the device side.
3Adaptability or versatility
If SDKs are installed or modified to detect events, then event detection functionality is improved, but device complexity is increased
Solution Approach 1:
The server serves as an intermediary that handles all complex event detection and correlation logic externally. The mobile device only needs to send simple interaction data to the server and receive results, eliminating the need for complex SDK installations, modifications, or local detection mechanisms on the device.
Data Source
AI summary
The subject matter of this specification generally relates to detecting events that occur within mobile applications without modifying code of the mobile application. In some implementations, a front-end server receives, from a mobile application management application installed on a client device, interaction data specifying (i) a user interaction identifier for a user interaction with an interactive item that presents, at a first mobile application, content for a second mobile application and (ii) an interactive item identifier. The front-end server receives event data specifying an occurrence of a specified user action within the second mobile application and the interactive identifier for the interactive item. A back-end server determines that the specified user action resulted from the user interaction based on a match between the interactive item identifier specified by the event data and the interactive item identifier that links to the user interaction identifier for the user interaction.