Cross-App Service Interface Using a Vertical Domain Independent Process
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The interaction path between applications is long, and power consumption is increased due to the need to start a secondary application when using its service in a primary application, compromising user experience and efficiency.
Innovation Solution
A cross-application interface display method that utilizes a vertical domain service independent process to display an interface without starting the main process of the secondary application, allowing quick access to services like preview, sharing, or editing by running a vertical domain service independent process of the secondary application within the primary application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the main process of application B is started to provide service in application A, then the service can be fully functional, but the interaction path becomes long and power consumption increases
Solution Approach 1:
The patent segments the application process into a main process and a vertical domain service independent process. The vertical domain service independent process can be launched separately without starting the entire main process of application B, allowing users to access specific services (like preview, sharing, editing) directly within application A. This segmentation resolves the contradiction by enabling service functionality while avoiding the need to start the complete application B main process, thus shortening the interaction path and reducing power consumption.
Solution Approach 2:
The patent introduces a vertical domain service independent process as an intermediary between application A and application B's main process. This intermediary can be launched independently and provides the necessary service functionality without requiring the main process of application B to start. The vertical domain service independent process acts as a mediator that enables service access while avoiding the long interaction path and power consumption associated with starting the complete application B.
2Reliability
If the main process of application B is started to provide service in application A, then the service can be fully functional, but power consumption of the electronic device increases
Solution Approach 1:
The patent segments the application process into a main process and a vertical domain service independent process. The vertical domain service independent process can be launched separately without starting the entire main process of application B, allowing users to access specific services (like preview, sharing, editing) directly within application A. This segmentation resolves the contradiction by enabling service functionality while avoiding the need to start the complete application B main process, thus shortening the interaction path and reducing power consumption.
Solution Approach 2:
Instead of starting the complete main process of application B (excessive action), the patent enables starting only the necessary vertical domain service independent process (partial action). This partial action approach allows users to access specific services without the overhead of launching the entire application B main process, thereby reducing power consumption while maintaining the required service functionality.
3Ease of operation
If multiple redirections are used to access service in application B from application A, then the service can be accessed, but the interaction path becomes long and user experience deteriorates
Solution Approach 1:
The patent introduces a vertical domain service independent process as an intermediary between application A and application B's main process. This intermediary can be launched independently and provides the necessary service functionality without requiring the main process of application B to start. The vertical domain service independent process acts as a mediator that enables service access while avoiding the long interaction path and power consumption associated with starting the complete application B.
Solution Approach 2:
The patent enables preliminary action by allowing the vertical domain service independent process to be launched in advance or directly when needed, without requiring users to go through multiple redirections. The service interface can be prepared and made accessible within application A before the user completes their workflow, eliminating the need for lengthy interaction paths and improving user experience.
Data Source
Figure 1(a)
Figure 1(b)
Figure 1(c)
AI summary
This application provides a cross-application interface display method and an electronic device. The method includes: displaying a user interface of a first application, where the user interface includes first shared content of a second application; receiving a first operation performed by a user on the first shared content; and in response to the first operation, running a vertical domain service independent process of the second application and displaying a first interface of a vertical domain service of the second application; and when a main process of the second application is running, displaying a second interface of the main process of the second application, where the vertical domain service independent process is different from the main process. The method provided in this application enables the user to quickly use, in the first application, a service provided by the second application, to resolve problems of a long interaction path, cumbersome operations, and poor user experience that are caused by a need of starting the main process of the second application when the service provided by the second application is used in the first application.