Interactive Subsidiary Application Rendering in Search Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer applications and webpages require installation and launch to access specific functions, leading to unnecessary network and computer resource usage due to irrelevant content being retrieved and rendered.
Innovation Solution
Implementing interactive subsidiary applications that are rendered directly within a search results interface, allowing users to access specific functionalities without launching the full application, and optimizing content delivery by only rendering relevant interface elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a standard computer application is installed and launched to access specific functions, then the user can access the desired functionality, but network and storage resources are consumed to download and store the entire application, and irrelevant content is rendered along with the relevant interface elements
Solution Approach 1:
The application interface is segmented into relevant and irrelevant portions. Only the relevant interface elements and content necessary for the user's specific task are retrieved and rendered, while the rest of the application remains unloaded. This allows users to access specific functionality without downloading or storing the entire application.
Solution Approach 2:
The relevant interface elements and content are extracted from the full application and delivered separately to the user's device. This extraction enables the user to access only the necessary portion of the application without consuming resources to obtain the complete application package.
2Ease of operation
If a standard computer application is installed and launched to access specific functions, then the user can access the desired functionality, but time is consumed to launch the application and navigate through irrelevant states and interface elements
Solution Approach 1:
The relevant interface elements and content are prepared and delivered in advance based on the user's expressed intent or search query. This preliminary action eliminates the need for users to launch the full application and manually navigate through irrelevant states, as only the necessary interface is made available immediately.
3Ease of operation
If a webpage is accessed to provide functions, then the user can access information and services, but navigation through the webpage is required and irrelevant content is loaded and rendered
Solution Approach 1:
The webpage content is segmented into relevant and irrelevant portions based on the user's search query or intent. Only the relevant sections are retrieved and rendered, eliminating the need to load and process the entire webpage. This segmentation reduces network resource consumption while maintaining access to desired functionality.
4Loss of time
If deeplinks are used to launch applications in particular states, then direct access to specific functions is enabled, but the application must still be installed and executed, and irrelevant interface elements are still rendered
Solution Approach 1:
Instead of launching the full application even with deeplinks, only the relevant interface elements and content are extracted and delivered to the user's device. This extraction approach maintains the direct access benefit of deeplinks while eliminating the resource overhead of running the complete application.
Solution Approach 2:
The application is segmented such that only the specific state or function accessed via the deeplink is delivered and executed, rather than the entire application. This allows direct access to specific functions without the penalty of loading and running the full application package.
Data Source
AI summary
Implementations set forth herein relate to providing a subsidiary application GUI via a client interface. The GUI can be rendered when a user is accessing a first party system via an application that is provided by the first party or a separate entity. The subsidiary application GUI can be rendered in response to the user providing a search query to the first party server-such as a search query that is in furtherance of initializing receiving certain search results. The server can identify, based on the search query, one or more entities that offer primary and/or subsidiary applications, and request subsidiary data for visibly rendering corresponding subsidiary applications for each entity. The subsidiary applications can optionally provide access to application functions that would not otherwise be available at the client without a corresponding application being installed.