Switchboard Component for Mobile Event Delegation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile device applications face inefficiencies in handling computing events, leading to increased processing overhead due to the traditional reliance on native containers for web content and limited integration between web browser and native components.
Innovation Solution
The implementation of a 'switchboard' component in hybrid mobile apps that enables seamless event bridging between native and web browser components, using metadata-driven rules for customizable event delegation, reducing processing overhead and enhancing user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native containers are used for web content handling, then integration with native components is achieved, but processing overhead increases
Solution Approach 1:
The patent segments the event handling system into distinct components: a switchboard component that receives events, metadata that defines handling rules, and separate handling paths for native and web browser components. This segmentation allows efficient routing of events to the most appropriate handler without requiring full integration overhead.
Solution Approach 2:
The switchboard component acts as an intermediary between event sources and handlers. It receives computing events, consults metadata to determine the appropriate handling component, and delegates events accordingly. This intermediary layer reduces processing overhead by avoiding direct, complex interactions between native and web browser components while maintaining reliable integration.
2Adaptability or versatility
If traditional native container architecture is used, then web content can be displayed, but event handling efficiency decreases
Solution Approach 1:
The patent implements dynamic event handling where the system can adaptively route events based on metadata definitions. The switchboard dynamically determines whether to handle events natively or delegate to web browser components based on configurable rules stored in metadata, optimizing event handling efficiency while maintaining web content display capability.
Solution Approach 2:
The system changes the parameter of event routing from static (always native or always web) to dynamic based on metadata configurations. Metadata contains parameters that define which components should handle specific event types, allowing the system to optimize handling efficiency for different event scenarios while preserving web content capabilities.
3Ease of operation
If seamless event bridging is implemented, then user experience improves, but system complexity increases
Solution Approach 1:
The switchboard component serves multiple functions: receiving events from various sources, consulting metadata to determine routing decisions, delegating events to appropriate handlers, and managing the interaction between native and web browser components. This universal component simplifies the overall system architecture while enabling seamless event bridging and improved user experience.
Data Source
AI summary
Disclosed are examples of systems, apparatus, methods and computer program products for delegating handling of computing events of a mobile device application. For example, an identification of a computing event can be received. The computing event can have associated metadata. The computing event can be associated with a first component of a plurality of components of a first application executable on a mobile device. The plurality of components can comprise at least a native component and a web browser component. One or more rules can be applied to the metadata. Based on the application of the one or more rules to the metadata, a second component can be identified for handling the event. Handling of the event can be delegated to the second component.