Mobile Device Shake Gesture Error Reporting System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for reporting software errors on mobile devices are inconvenient and time-consuming, providing little incentive for users to report issues and often leaving them unaware of existing or pending solutions.
Innovation Solution
A computer-implemented method and system that captures error diagnostic information upon detecting a shaking motion, generates an error report, and submits it to a server for tracking, allowing users to authorize submission and receive periodic updates on the status of the error, including whether it has been previously reported, is pending, or has a solution found.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional error reporting methods are used, then error reports can be submitted, but the process is inconvenient and time-consuming
Solution Approach 1:
The system performs preliminary actions by automatically capturing error diagnostic information (screenshots, logs, device state) in the background before the user needs to report an error. This pre-capture of data eliminates the time-consuming manual information gathering step, allowing users to simply trigger the report with a shake gesture.
Solution Approach 2:
The system enables self-service by automatically collecting and organizing all necessary error diagnostic information without requiring user intervention. The mobile device autonomously captures screens, logs, and system state, then prepares the complete error report package, freeing the user from the tedious data collection process.
2Productivity
If conventional error reporting methods are used, then errors can be reported, but users receive no incentive to report and remain unaware of solutions
Solution Approach 1:
The system implements feedback by notifying users when their error reports have been received and providing updates on the resolution status. This closed-loop communication informs users about the outcome of their error reports and whether solutions have been found, creating awareness and encouraging continued reporting of issues.
Solution Approach 2:
The system allows users to opt-in to receive automatic notifications about their error report status without requiring manual follow-up. This self-service notification system proactively provides updates to users, eliminating the need for them to actively track their reports and keeping them informed about solutions.
3Ease of operation
If manual error reporting is used, then users can submit reports, but the process requires significant user effort and time
Solution Approach 1:
The system performs self-service by automatically capturing all necessary error diagnostic information including screenshots, application logs, system state, and device configuration. This autonomous data collection eliminates the need for users to manually gather information, significantly reducing user effort while maintaining high reporting efficiency.
Solution Approach 2:
The system performs preliminary actions by pre-capturing and storing error diagnostic data in the background. When a user decides to report an error, the information is already collected and organized, requiring only a simple trigger action from the user to submit the complete report package.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
Facilitates efficient and user-friendly error reporting, enabling users to track the progress of their error reports and receive solutions promptly, thereby improving the debugging process and user engagement.
Implementation Method 1
a sensor configured to detect a motion of the mobile device indicating shaking
Data Source
AI summary
Systems and methods for tracking mobile device software errors are disclosed. A mobile device, in response to receiving an indication of shaking, may capture error diagnostic information including, for instance, a screen shot, user information, and/or a session log. The mobile device may generate an error report including the error diagnostic information, and may submit the error report to a server after a user authorizes the submission. The mobile device may further subscribe the user to error report tracking, which may include periodically receiving and displaying progress status updates for a software error indicated by the error report. The progress status update may indicate that, for instance, the software error has previously been reported by a second user, that a solution for the software error is pending, or that a solution for the software error has been found.