Offline View Controller Graph for Mobile CRM
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile CRM users face challenges in accessing CRM services when their devices are offline due to the lack of data communication with the CRM server, as existing technologies do not effectively enable offline rendering and navigation of views and view components.
Innovation Solution
A method and system for defining an offlinable view/controller graph, where view definitions are received from a server, stored in memory, and mapped to universal resource locators (URLs), allowing mobile devices to render and navigate views even without internet connection by using Uniform Resource Identifiers (URIs) and a view table to store and retrieve view definitions locally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If view definitions are stored and accessed from a remote server, then data centralization and synchronization are improved, but offline access capability deteriorates
Solution Approach 1:
The system performs preliminary actions by caching view definitions and their associated resources (images, stylesheets, scripts) in the mobile device's memory before offline access is needed. This pre-caching mechanism enables the device to render views locally without real-time server connection, resolving the contradiction between centralized data management and offline accessibility
Solution Approach 2:
The patent introduces an intermediary caching layer between the remote server and the mobile device UI. This intermediary stores view definitions and resources locally, mediating between the need for centralized data synchronization and the requirement for offline access. The caching mechanism acts as a buffer that allows the system to maintain data centralization while providing offline capability
2Adaptability or versatility
If view definitions are cached locally in memory, then offline rendering capability is improved, but device memory consumption increases
Solution Approach 1:
The system extracts and caches only the essential view definition data and associated resources needed for offline rendering, separating critical information from non-essential data. By selectively caching only what is necessary for view rendering (HTML structures, critical styles, essential scripts), the system improves offline capability while minimizing memory consumption
Solution Approach 2:
The patent implements local quality by differentiating between various types of data and applying different caching strategies. Critical view definitions and resources are cached locally with high priority, while less essential data is either not cached or cached with lower priority. This selective local caching optimizes the balance between offline rendering capability and memory usage
3Ease of operation
If a view table mapping identifiers to URLs is maintained, then view navigation and retrieval are improved, but system complexity increases
Solution Approach 1:
The system creates simplified copies of view reference information in the form of a mapping table that stores only essential identifier-to-URL relationships. Instead of maintaining complex view definition structures, the system uses lightweight copy entries that map view identifiers to their corresponding cached URLs, simplifying navigation while improving retrieval efficiency
Data Source
AI summary
A method and system for defining an offlinable view/controller graph. In one embodiment of the method a first view definition is received from a server via data communication link, wherein the first view definition comprises a first identifier. The first view definition is stored in memory at a location identified by a first universal resource locator (URL). The first URL is mapped to the first identifier in a table.