Mobile Application State Identifier Framework for Cross-Device Context Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges in sharing and recreating the state of mobile devices across different devices due to the closed environment of mobile computing, where most tasks cannot be easily shared or transferred like in browser-based computing environments.
Innovation Solution
A mobile application state identifier framework that captures and shares the state of a mobile device by including a target task, sub-task, user input, and device-specific components, allowing devices without the specific application to recreate the state, and enabling hierarchical organization and deep linking into mobile applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a mobile application state identifier is generated using application-specific identifiers, then the state can be precisely identified within that application, but the state cannot be shared with devices that do not have the specific application installed
Solution Approach 1:
The application state identifier is segmented into multiple components: a task component that identifies the general task type (accessible without the application) and a sub-task component that identifies the specific state within the application. This segmentation allows the identifier to function both as a general task reference and a precise application state reference, resolving the contradiction between shareability and information preservation.
Solution Approach 2:
The identifier system is designed to serve multiple functions: it can be used by devices with the application to access precise states, and by devices without the application to understand the general task context. The hierarchical structure enables the same identifier to provide different levels of information depending on the recipient's capabilities, achieving both universality and specificity.
2Manufacturing precision
If detailed application-specific information is included in the state identifier, then the state can be accurately recreated, but the identifier becomes more complex and harder to share across different applications
Solution Approach 1:
The identifier is divided into a task component and a sub-task component, where the task component contains general information applicable across applications and the sub-task component contains application-specific details. This hierarchical segmentation organizes complexity in a structured way that maintains precision while improving shareability and interpretability.
3Reliability
If the state identifier includes user-specific input data, then the exact user experience can be replicated, but the identifier becomes less adaptable to different users and contexts
Solution Approach 1:
The identifier structure applies different levels of specificity to different components: the task component uses general, adaptable information that works across users and contexts, while the sub-task component uses specific information tailored to the particular user experience. This local differentiation of quality allows the identifier to be both reliable for replication and adaptable to different contexts.
Data Source
AI summary
Systems and methods are provided for sharing or recreating a state from a mobile device. For example, a mobile application state identifier can include a protocol identifier, a target task component associated with a mobile application executing when the application state identifier is generated and a sub-task component related to a user-interface active in the mobile application when the application state identifier is generated. The application state identifier can also include a user input component reflecting actions taken by a user during execution of the mobile application. A method can include generating, on a first mobile device, an application state identifier and transmitting the application state identifier to a second mobile device, wherein the second mobile device opens a mobile application associated with the target task to a user-interface corresponding to the sub-task component in response to receiving the application state identifier.