Discrete Embedded Barcode for Application Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Debugging issues on user devices, such as smartphones and tablets, is challenging due to the lack of context and inability to track errors, leading to increased user frustration and time loss during transactions or interactions, as conventional debugging methods like tokens or cookies are not effective in these scenarios.
Innovation Solution
A system and method that generate an unobtrusive and discrete embedded barcode on the user interface to track application interactions, allowing for easy debugging by converting a debug ID and token into a barcode that can be captured and used to identify and resolve application malfunctions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional debugging methods like tokens or cookies are used, then debugging capability is provided, but user device malfunctions cannot be effectively tracked or debugged due to lack of context
Solution Approach 1:
The patent creates a visual copy (screenshot) of the user device screen at the moment of malfunction, which captures the contextual state including the embedded barcode. This visual copy preserves the application state, UI elements, and debugging information that would otherwise be lost, enabling effective debugging without requiring the original device state to be maintained.
Solution Approach 2:
The patent embeds a barcode containing debugging information and session context into the user interface before malfunction occurs. This preliminary embedding ensures that when a malfunction happens, the debugging information is already present and captured in the screenshot, eliminating the need to collect context information after the error occurs.
2Loss of information
If debugging information is displayed prominently on the user interface, then debugging context is provided, but user experience is degraded due to obtrusive elements
Solution Approach 1:
The patent places the debugging barcode in a specific, localized region of the user interface (such as a corner or designated area) rather than distributing debugging information throughout the screen. This localized placement provides the necessary debugging context while minimizing interference with the overall user experience, as the barcode occupies a small, discrete portion of the interface.
Solution Approach 2:
Instead of displaying debugging information directly in a prominent manner, the patent encodes it in a barcode format that can be captured as part of a regular screenshot. The debugging information is thus available when needed (in the screenshot) but remains unobtrusive during normal operation, as users can ignore the barcode in the corner without affecting their interaction with the application.
Data Source
AI summary
Aspects of the present disclosure involve systems, methods, devices, and the like for generating an unobtrusive and discrete barcode used for debugging. In one embodiment, a system is introduced that enables the tracking of application interactions on a user device. The tracking can include the generation of a debug id which can include a discrete string used to describe locations, preferences, and interactions with a user device application. The string may then be converted into a corresponding barcode which can be discretely displayed on the user interface of the application. In another embodiment, the barcode may be captured and/or retrieved for use in debugging the application, in an instance where an application malfunction is encountered.