Mobile Browser App Invocation with Automatic Return
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
On Android platforms, when a mobile browser initiates a service call to a third-party app, users are unable to automatically return to the original mobile browser after completing the service process, leading to poor user experience due to manual browser selection and potential loss of user session states.
Innovation Solution
The method involves using the package name information of the mobile browser, obtained through user agent information or system queries, to construct an intent that allows the Android system to accurately return to the original mobile browser after the service call, eliminating the need for manual browser selection and preserving user session states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the mobile browser uses the Android system's app jump mechanism to invoke a third-party app, then the app can be returned to automatically, but the mobile browser cannot be returned to automatically after the service is completed
Solution Approach 1:
The mobile browser performs preliminary actions by storing its identification information (package name) and the invoked URL in the Android system's clipboard before invoking the third-party app. This allows the browser to be automatically returned to after the service is completed, resolving the contradiction between automatic return capability and session state preservation.
Solution Approach 2:
The Android system's clipboard serves as an intermediary between the mobile browser and the third-party app. The browser writes its identification information to the clipboard, and the target app reads this information to construct an intent for returning to the browser, enabling automatic return without losing session state.
2Reliability
If the user manually selects the mobile browser to return to after completing the service process, then the browser can be returned to, but the user experience deteriorates due to manual selection and potential loss of session states
Solution Approach 1:
The system enables self-service by automatically returning the user to the original mobile browser using the identification information stored in the clipboard. The target app automatically constructs and sends an intent to the browser's activity component, eliminating the need for manual browser selection and preserving session state automatically.
3Extent of automation
If the mobile browser stores identification information in the Android system clipboard, then automatic return is enabled, but the system clipboard is used for a purpose it was not originally designed for
Solution Approach 1:
The solution enhances the universality of the Android system clipboard by making it serve dual purposes: its original function for copy-paste operations and the new function of storing mobile browser identification information for automatic return. This multi-functionality enables automatic return while maintaining compatibility with the existing clipboard system.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present application provides a method and an apparatus for invoking an app by means of a mobile browser. The method includes: obtaining identification information of a mobile browser when the mobile browser initiates a service call for a target app, where the identification information includes package name information of the mobile browser; submitting first call data for the target app to a system, where the first call data includes a custom parameter used to invoke the target app and the identification information of the mobile browser; receiving, by the system, the first call data submitted by the mobile browser when the service call for the target app is initiated; invoking the target app based on the custom parameter to execute a corresponding target service, and transferring the identification information of the mobile browser to the target app; and after the target service is executed, responding to second call data carrying the package name information of the mobile browser and submitted by the target app, and returning to the mobile browser. User experience can be improved based on the present application.