Mobile App Error Handling for Intermittent Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile processing environments, intermittently connected devices face challenges in error handling due to asynchronous communication, leading to inconsistent data states and delayed error notifications, which can result in erroneous data being used by users until synchronization occurs, potentially causing issues with inventory validation and transaction accuracy.
Innovation Solution
A system where data objects on mobile devices are managed through a middleware component, allowing them to be set to an inconsistent state initially, with error resolution processes enabled when errors are detected, enabling users to selectively manage and update data objects, ensuring consistency with the back-end system upon reconnection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If asynchronous communication is used between mobile device and back-end system, then device autonomy and intermittent connectivity are improved, but data consistency and error handling timeliness deteriorate
Solution Approach 1:
The system performs preliminary actions by setting data objects to an inconsistent state before actual synchronization occurs. This allows the mobile device to continue operating autonomously during intermittent connectivity, preparing the data structure in advance for future synchronization without blocking user operations.
Solution Approach 2:
The system implements feedback mechanisms where error information is sent back to the mobile device from the back-end system. This feedback loop enables the device to detect and respond to data consistency issues, allowing users to review and correct erroneous data objects while maintaining autonomous operation during connectivity interruptions.
2Productivity
If error information is sent back asynchronously, then device operation continuity is improved, but error notification timeliness deteriorates
Solution Approach 1:
Error handling structures are prepared in advance on the mobile device, including pre-configured error states and resolution interfaces. This preliminary preparation ensures that when error information arrives asynchronously, the device can immediately process and present it to users without operational interruption or noticeable delay.
3Measurement precision
If users can selectively manage erroneous data objects, then data accuracy is improved, but system complexity increases
Solution Approach 1:
The system enables users to self-manage erroneous data objects through intuitive interfaces that present error information and resolution options. Users can independently review, select, and correct data objects without requiring complex system interventions or administrative overhead, thereby improving data accuracy while keeping the system relatively simple.
Data Source
AI summary
An intermittently connected mobile device asynchronously communicates with a middleware system for subsequent communication with a back-end system. Local data objects are given an inconsistent state when charged on the mobile device and the back-end system is not available for data validation. Due to the intermittent communication, a waiting period for possible validation may be hours, days, weeks, etc. If an error occurs, the mobile device then receives and maintains a list of the error notifications. Upon selection of an error notification, an error resolution process is executed on the mobile device so that the user can select between the local data object and the remote data object. If the back-end object is selected, the process terminates otherwise if the local is selected, the user is presented the interface to update the data object, which is again verified by the back-end system.