Native App Web Component Preloading and Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing native applications that provide web functionality is costly and often results in decreased performance due to the overhead of embedded browser engines, particularly when user authentication and data retrieval are involved, leading to slow response times and poor user experience.
Innovation Solution
Implementing a loader manager that preloads web components and authenticates users in advance, allowing for faster access to web-dependent features by caching static and dynamic components, thereby reducing load and response times without the need for continuous browser interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an embedded browser engine is used within the native app, then web functionality is provided, but performance decreases due to authentication overhead and browser overhead
Solution Approach 1:
The patent segments the web functionality into two parts: a lightweight embedded browser engine for rendering and a separate authentication module that handles user verification. This segmentation allows the authentication overhead to be isolated and managed separately from the browser rendering process, reducing the performance impact on web functionality.
Solution Approach 2:
The patent implements preliminary authentication where user credentials are verified before the embedded browser engine is activated. By performing authentication in advance, the system eliminates repeated authentication overhead during browser operations, thereby improving overall performance while maintaining web functionality.
2Adaptability or versatility
If a browser-based application is used, then web functionality is provided, but development cost increases when creating native applications with the same functionality
Solution Approach 1:
The patent creates a universal embedded browser engine that can be integrated into multiple native applications with different functionalities. This single browser engine component serves multiple purposes across different apps, reducing the need to develop separate browser implementations for each native application and thereby lowering overall development costs.
Solution Approach 2:
The patent introduces an intermediary layer that bridges native application code and web content rendering. This intermediary provides standardized interfaces and protocols that simplify the integration process, making it easier to add web functionality to native applications without requiring extensive custom development work.
3Quantity of substance
If web components are loaded on demand, then memory usage is optimized, but loading time increases
Solution Approach 1:
The patent implements preliminary loading of critical web components into memory before they are actually needed by the user. By pre-loading authentication modules, configuration files, and frequently used web resources, the system reduces loading time when these components are accessed, while still maintaining optimized memory usage through selective pre-loading based on usage patterns.
Solution Approach 2:
The patent employs periodic memory management where pre-loaded web components are periodically reviewed and unloaded from memory when not in use. This periodic action allows the system to maintain a balance between having components readily available (reducing load time) and freeing up memory resources when they are no longer needed.
Data Source
AI summary
Methods, systems, and computer programs are presented for presenting web components in a native application. One method includes operations for monitoring a first user interface (UI) presented on a native app, and based on the monitoring, determining a second UI that may be selected by a user when accessing the first UI. The second UI is based on web components downloaded from a web server. The method further includes operations for authenticating the user for accessing the web server, selecting web components associated with the UI for preloading, and preloading the selected web components. Further yet, the method includes operations for detecting that the user has selected the second UI, and causing presentation of the second UI, which includes presenting the preloaded components on the second UI and downloading and presenting in the second UI the components not preloaded.