Navigation Service Parameter Mapping for Web UI Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interfaces struggle with dynamic updates and navigation, particularly in web-based applications, where deep linking and user interaction lead to usability issues such as broken bookmarks, non-functional browser buttons, and inefficient data retrieval.
Innovation Solution
A method involving a navigation service that processes events by identifying target code to update the user interface, mapping source parameters to target parameters using metadata, and transferring control to dynamically modify the document object model, enabling seamless navigation and data retrieval without full page reloads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing user interface applications control UI elements by setting properties within application code, then the application can maintain control over visual aspects, but the system lacks flexibility for dynamic updates and navigation without full page reloads
Solution Approach 1:
The patent segments the user interface into modular components (UI elements, content views, navigation points) that can be independently updated. The navigation service separates concerns by handling navigation logic separately from the application code, allowing dynamic updates without reloading entire pages. This segmentation enables partial page updates and maintains state across navigation events.
Solution Approach 2:
The navigation service acts as an intermediary layer between the application code and the user interface. It receives navigation events, maps parameters, identifies target code, and coordinates updates to UI elements and content views. This mediator pattern allows the system to handle dynamic navigation and updates without requiring changes to the core application code, resolving the contradiction between adaptability and complexity.
2Ease of operation
If the system performs full page reloads for navigation, then data retrieval is simplified, but user experience deteriorates due to lost deep linking functionality and inefficient data retrieval
Solution Approach 1:
The system performs preliminary actions by pre-defining navigation points and associated content views in the application code. When a navigation event occurs, the navigation service quickly identifies the target content view and updates only the necessary portions of the page. This preliminary structuring enables fast navigation without full page reloads, maintaining both user experience and data retrieval efficiency.
Solution Approach 2:
The patent implements dynamic navigation where the system can transition between different content views by updating specific UI elements and data models without reloading the entire page. The navigation service dynamically identifies which content views to update based on navigation events, allowing efficient data retrieval while maintaining excellent user experience with persistent deep linking functionality.
3Adaptability or versatility
If the application uses fixed parameter structures, then code simplicity is maintained, but the system cannot handle varied navigation contexts and parameter mappings
Solution Approach 1:
The patent employs parameter changes by using metadata to define the structure and mapping of parameters for different navigation points. The navigation service reads this metadata to dynamically map source parameters to target parameters based on the specific navigation context. This allows the system to handle varied navigation contexts with different parameter structures without requiring complex conditional logic, resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The system uses metadata files that contain copies or templates of parameter structures for different navigation points. Instead of hardcoding parameter mappings in the application code, the navigation service loads and applies these pre-defined parameter structures from metadata. This copying approach provides flexibility for handling varied navigation contexts while keeping the application code simple and maintainable.
Data Source
AI summary
Described are techniques for event processing. Notification may be received at a navigation service of a first event regarding an interaction with a user interface element of a user interface of an application. The notification may include a set of one or more source parameters describing context information about the notification and information identifying a navigation point in the application. Responsive to receiving the notification, the navigation service may perform first processing that includes identifying first target code of the application to be invoked to update the user interface to include a content view associated with the navigation point, mapping the set of one or more source parameters to a set of one or more target parameters in accordance with first metadata, and transferring control to the first target code. The set of one or more target parameters may be provided as input parameters to the first target code.