A method for waking up an APP and directly accessing an H5 page without any sense of login

Abstract

The present invention relates to the field of smart terminal APP application technology, and is a method for waking up an APP and directly accessing an H5 page without perceiving a login, comprising the following steps: S1, a user clicks on a notification bar to receive a push message, and after a delay of a period of time, the message is transmitted through broadcast; S2, when the App has been opened or the main application process is still running in the background, the main application interface parses the message transmitted by intent or broadcast, and then transmits it to the web page view through the H5JS bridge mode, and the H5 page jumps to the specified page. A combination of multiple methods is used to improve the arrival rate of third-party Android push, and under the premise that the message is reachable, the notification bar message is clicked and the login is not perceived to directly access the corresponding page. By waking up the APP based on the third-party Android message push and logging in without perceiving to directly access the H5 page, the third-party Android message push service is used as a basis, so that users can log in without perceiving and directly access the specified H5 scene interface, directly access the authorized H5 page with one click, reduce user operations, and improve user experience.

Description

Technical Field

[0001] The present invention relates to the technical field of smart terminal APP applications, and in particular to a method for waking up an APP and directly accessing an H5 page without any perception of login. Background Art

[0002] In the era of mobile Internet, in order to solve the problem of cross-platform App, more and more mobile applications adopt front-end web technology (HTML5+CSS+JS) for hybrid development. When we use mobile App developed in hybrid mode, when using other applications at the same time, the original App may stay in the memory, and the interface may be covered by other applications. It is also possible that the original application interface will be cleared by the system due to memory and power consumption reasons, or the original application may be forcibly cleared; in order to improve the user experience, when the app has a push notification message, it is necessary to guide the user to enter the mobile APP and go directly to the H5 page. When the user exits the application and the App application is cleared by the system due to memory and power consumption reasons, the third-party Android-based message push service (pushservice) still survives as an independent process, so the user can still see the push message notification on the mobile device lock screen and notification bar. However, if the user forcibly clears the App, the push process will also be cleared, so it is difficult to wake up the application through the push message. At the same time, after Android integrates third-party push, the default way to handle push is to open the application itself, and it is difficult to view the relevant permission page information beyond the login interface. The purpose of the present invention is to improve the arrival rate of third-party Android push by combining multiple methods. Under the premise that the message is reachable, click the notification bar message and log in without perception to directly reach the corresponding page.

[0003] It can be seen that the prior art has the following problems:

[0004] (1) How to improve the arrival rate of third-party Android push notifications when the user exits the app, the app activity is cleared by the system due to memory and power consumption reasons, or the user forcibly clears the app;

[0005] (2) How to prevent users from re-starting the entry point when they click a push message to open the Activity when the mobile app is already open or the main application process is still running in the background?

[0006] (3) Solve the problem of how to jump to a page when the mobile app is already open or the main application process is still running in the background and has stopped at a non-direct target page;

[0007] (4) When the page that directly receives a notification message requires login permission, how can the application be logged in without being aware of the page being accessed?

[0008] (5) Solve the problem of how users can directly access different H5 pages by clicking on different notification bar messages. Summary of the invention

[0009] The present invention provides a method for waking up an APP and directly accessing an H5 page without perceiving a login, which solves the technical problem of low arrival rate of third-party Android push mentioned above.

[0010] In order to solve the above technical problems, the present invention provides a method for waking up an APP and directly accessing an H5 page without perceiving a login, comprising the following steps:

[0011] S1, the user clicks the notification bar to receive the push message, and after a delay, the message is sent out through broadcast;

[0012] S2: When the App is already opened or the main application process is still running in the background, if the main application login interface receives a broadcast message, the main application interface is started through intent to pass the message parameters and terminate itself;

[0013] If the main application interface receives a broadcast message, the main application interface parses the message passed in by intent or broadcast, and then passes it to the web page view through H5 JS bridging. The H5 page jumps to the specified page.

[0014] S3, when the App or main application process is killed, the user clicks the push message to open the login interface and re-executes the entry startup. After waiting for the startup to complete, it receives the broadcast message and jumps to S2.

[0015] Optionally, before S1, it also includes: for users who successfully log in for the first time, the App locally retains the account information and authorization token information, and subsequently forms virtual login information through calling and private protocols, and enters the corresponding page without logging in when clicking the notification message.

[0016] Optionally, after the user successfully logs in for the first time, the app stores the user account information and Token information locally.

[0017] Optionally, before S1, it also includes: placing the third-party Android message push process in the background by means of multiple processes, process startup self-start and process mutual protection; registering to the third-party message push service through a service when the App is started for the first time, and at the same time, the service monitors the system startup broadcast, and when the mobile phone restarts and monitors the startup broadcast, the message push process is started; at the same time, the message push process survival rate and message arrival rate are improved through the mutual protection of inter-process communication of high-frequency applications.

[0018] Optionally, a native service is used to register the pigeon message service. The service is started when the login interface starts. After the pigeon is successfully registered, the Push process is used as an independent process in the background.

[0019] Optionally, S3 specifically includes: each time the entry startup is re-executed, judging in the entry Activity through AppManager whether there is an Activity in the current stack in the startup state at the time of startup.

[0020] Optionally, the login interface of the App entrance is developed natively, and all other contents of the main application are developed using H5 pages.

[0021] Optionally, a native message receiver is used to receive messages and result feedback, while accepting message transparent transmission and listening for notification bar messages being clicked.

[0022] Optionally, S1 specifically includes: ensuring that after receiving the push message, the user clicks the push message to open the main application login interface and re-execute the entry startup, passing parameters to the main application and service through the intent message, and the login interface and the main application process are registered at the same time so that they can receive and process Push message broadcasts and service broadcasts.

[0023] Optionally, in order to achieve login-free operation on the login interface, the account information and Token information are transparently transmitted from the local storage.

[0024] Beneficial effect: The present invention provides a method for waking up an APP and logging in directly to an H5 page without perception, comprising the following steps: S1, the user clicks on the notification bar to receive a push message, and after a delay of a period of time, the message is transmitted through broadcast; S2, when the App is already opened or the main application process is still running in the background, if the main application login interface receives a broadcast message, the main application interface is started through intent to pass in the message parameters and terminate itself; if the main application interface receives a broadcast message, the main application interface parses the message passed in by intent or broadcast, and then passes it to the web page view through H5 JS bridging, and the H5 page jumps to the specified page; S3, when the App or the main application process is killed, the user clicks on the push message to open the login interface and re-execute the entry startup, waits for the startup to complete, and then receives the broadcast message and jumps to S2. A combination of methods is used to improve the arrival rate of third-party Android push, and under the premise that the message is reachable, click on the notification bar message and log in directly to the corresponding page without perception. Through the APP based on third-party Android message push, users can wake up and go directly to the H5 page without logging in. The third-party Android message push service is used as the basis to allow users to log in without perception and go directly to the designated H5 scene interface, and directly access the authorized H5 page with one click, reducing user operations and improving user experience.

[0025] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention and implement it according to the contents of the specification, the following is a detailed description of the preferred embodiments of the present invention in conjunction with the accompanying drawings. The specific implementation of the present invention is given in detail by the following embodiments and their accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0027] Figure 1 This is a flow chart of the method for waking up the APP and logging in directly to the H5 page without perception of the present invention. DETAILED DESCRIPTION

[0028] The principles and features of the present invention are described below in conjunction with the accompanying drawings. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention. The present invention is described in more detail by way of example with reference to the accompanying drawings in the following paragraphs. The advantages and features of the present invention will become clearer according to the following description and claims. It should be noted that the drawings are all in a very simplified form and are not in precise proportions, and are only used to conveniently and clearly assist in explaining the purpose of the embodiments of the present invention.

[0029] It should be noted that when a component is referred to as being "fixed to" another component, it may be directly on the other component or there may also be a component centered. When a component is considered to be "connected to" another component, it may be directly connected to the other component or there may also be a component centered. When a component is considered to be "set on" another component, it may be directly set on the other component or there may also be a component centered. The terms "vertical", "horizontal", "left", "right" and similar expressions used herein are for illustrative purposes only.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used herein in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The term "and / or" used herein includes any and all combinations of one or more related listed items.

[0031] like Figure 1 As shown, the present invention provides a method for waking up an APP and directly accessing an H5 page without perceiving a login, including the following steps: S1, the user clicks on the notification bar to receive a push message, and after a delay of a period of time, the message is transmitted through broadcast; S2, when the App is already opened or the main application process is still running in the background, if the main application login interface receives a broadcast message, the main application interface is started through intent to pass in the message parameters and terminate itself; if the main application interface receives a broadcast message, the main application interface parses the message passed in by intent or broadcast, and then passes it into the web page view through H5 JS bridging, and the H5 page jumps to the specified page; S3, when the App or the main application process is killed, the user clicks on the push message to open the login interface and re-execute the entry startup, waits for the startup to complete, and then receives the broadcast message and jumps to S2. A combination of methods is used to improve the arrival rate of third-party Android push, and under the premise that the message is reachable, click on the notification bar message and log in without perceiving to reach the corresponding page. Through the APP based on third-party Android message push, users can wake up and go directly to the H5 page without logging in. The third-party Android message push service is used as the basis to allow users to log in without perception and go directly to the designated H5 scene interface, and directly access the authorized H5 page with one click, reducing user operations and improving user experience.

[0032] It is universally applicable to various Android application status scenarios such as user exiting the application, App being cleaned up by the system due to memory and power consumption reasons, and application being forced to be cleaned up. Under the premise that the push message is reachable, this method can directly reach the specified page, avoiding the situation where users can only open the application itself after receiving the push message, and cannot directly see the push-related pages, especially the pages that require login authorization. This method improves the user experience of the App and can increase user application stickiness.

[0033] Specifically, the login interface LoginActivity of the Android App entrance is developed natively, and all other contents of the main interface MainActivity are developed using H5 pages. The specific method flow is as follows:

[0034] The user clicks the notification bar to receive a push message, and after a delay of 3 seconds, the message is sent out through broadcast; when the main application process of the App is not cleaned up, that is, there is still an Activity alive in the AppMananger (application management), that is, the AppActivity still exists.

[0035] If the main application login interface LoginActivity receives a broadcast message, it starts MainActivity through intent, passes the message parameters and finishes itself; if the main application interface MainActivity receives a broadcast message, MainActivity parses the message passed in by Intent or broadcast and passes it to webview (web view) through H5 JS bridging, and the H5 page jumps to the specified page.

[0036] When the App or main application process is killed, the user clicks the push message to open the LoginActivity to re-execute the entry startup, and waits for the startup to complete before receiving the broadcast message.

[0037] An optional solution is to place the third-party Android message push process in the background through multiple processes, process startup self-start, and process mutual protection. When the App is started for the first time, register with the third-party message push service through the service. At the same time, the service listens to the system startup broadcast. When the phone is restarted and the startup broadcast is listened, the message push process is started. At the same time, the inter-process communication and mutual protection of high-frequency applications are used to improve the survival rate of the message push process and the message arrival rate.

[0038] As an optional solution, each time the entry is restarted, the AppManager is used in the entry Activity to determine whether there is an interface Activity in the startup state in the current stack at the time of startup; an App may have multiple Activities (active windows or interfaces or processes or threads).

[0039] As an optional solution, the login interface LoginActivity of the Android App entrance is developed natively, and all other contents of the main application (MainActivity) are developed using H5 pages.

[0040] As an optional solution, for users who successfully log in for the first time, the App locally retains the account information and authorization token information, and subsequently forms a virtual login information through calling and private protocols. When the notification message is clicked, the user can enter the corresponding page without logging in.

[0041] An optional solution is that third-party message push carries message ID, message content and page logo; click on the message in the notification bar to broadcast the message ID, message content and page logo. Finally, MainActivity calls different JS bridge methods according to different messages, so different H5 pages can be jumped according to different notification bar messages.

[0042] In a specific implementation scenario:

[0043] The multi-view hybrid app is developed using JAVA language and implemented in the Android Studio development environment. Tencent Xinge 3.2.7 version is used as the third-party messaging service, and Android 4.1 is used as the test environment. The program is compatible with Android 4.1 and above. The specific implementation process is as follows:

[0044] (1) Hybrid App is a scene where Native View and WebView appear alternately. The entry login interface (LoginActivity) is developed natively, and all other contents of the main application (MainActivity) are developed using H5 pages;

[0045] (2) Use native implementation of the message receiver (Receiver) to receive messages and result feedback, accept message transparent transmission, and listen for notification bar messages being clicked;

[0046] (3) Use native service to register the pigeon messaging service. Start the service when LoginActivity starts. After the pigeon is successfully registered, the Push process is used as an independent background process.

[0047] (4) The service monitors the boot broadcast, and when the phone restarts, it registers the pigeon messaging service and starts the Push process;

[0048] (5) After the user successfully logs in for the first time, the app stores the user account information and token information locally;

[0049] (6) When the APP is running in the foreground or the background, after the APP is forcibly cleaned up, it corresponds to the following three situations: the main application process and the push process survive, the main application process stops the push process and the main application process and the push process stops.

[0050] Corresponding to the two forms of push, when the APP is running in the foreground or the background, the long connection between the Push process and the third-party messaging service is not terminated, so both can receive pushes; all apps using the same push service will share the push link, and after the main application process and the Push process are stopped, the user can automatically open the high-frequency application to make the push link of other apps unblocked. This realizes the mutual care between various applications and effectively ensures the survival of the Push process;

[0051] (7) Ensure that after receiving a push message, the user clicks on the push message to open the main application login interface LoginActivity and re-execute the entry startup, pass parameters to the main application and service through the intent message transparent transmission, and register LoginActivity and MainActivity at the same time so that they can receive and process Push message broadcasts and service broadcasts. In order to achieve login-free, the account information and Token information are transparently transmitted from the local storage in LoginActivity;

[0052] (8) When a third-party message is pushed, it carries the message ID, message content, and page ID. The incoming message ID, message content, page ID, and identity information are passed to the webview through the H5 JS bridge, and the H5 page jumps to the specified page.

[0053] Beneficial effects: This method is universally applicable to the wake-up of various Android application status scenarios, such as users exiting the application, the App being cleaned up by the system due to memory and power consumption reasons, and the application being forced to be cleaned up. Under the premise that the push message is reachable, this method can be used to directly reach the specified page, avoiding the situation where users can only open the application itself after receiving the push message, and cannot directly see the pages related to the push, especially the pages that require login authorization. This method improves the user experience of the App and can increase user application stickiness.

[0054] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any ordinary technician in the industry can smoothly implement the present invention as shown in the drawings and described above. However, any equivalent changes, modifications and evolutions made by technicians familiar with the profession without departing from the scope of the technical solution of the present invention using the technical content disclosed above are all equivalent embodiments of the present invention. At the same time, any equivalent changes, modifications and evolutions made to the above embodiments based on the essential technology of the present invention are still within the protection scope of the technical solution of the present invention.

Claims

1. A method for waking up an APP and logging in directly to an H5 page without any perception, characterized in that: The following steps are involved: The third-party Android message push process is placed in the background through multiple processes, process startup and process mutual protection. When the App is first started, the service is registered with the third-party message push service, and the service monitors the system startup broadcast. When the phone is restarted, the message push process is started after the startup broadcast is monitored. At the same time, the inter-process communication and mutual protection of high-frequency applications are used to improve the survival rate of the message push process and the message arrival rate. S1, the user clicks the notification bar to receive the push message, and after a delay, the message is sent out through broadcast; S2: When the App is already opened or the main application process is still running in the background, if the main application login interface receives a broadcast message, the main application interface is started through intent to pass the message parameters and terminate itself; If the main application interface receives a broadcast message, the main application interface parses the message passed in by intent or broadcast, and then passes it to the web page view through H5 JS bridging. The H5 page jumps to the specified page. S3, when the App or main application process is killed, the user clicks the push message to open the login interface and re-executes the entry startup. After waiting for the startup to complete, it receives the broadcast message and jumps to S2.

2. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The S1 also includes: for users who successfully log in for the first time, the App locally retains the account information and authorization token information, and subsequently forms virtual login information through calling and private protocols, and enters the corresponding page without logging in when clicking on the notification message.

3. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 2 is characterized in that: After the user successfully logs in for the first time, the app stores the user account information and Token information locally.

4. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The native service is used to register the pigeon message service. The service is started when the login interface starts. After the pigeon registration is successful, the Push process is used as an independent process in the background.

5. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The S3 specifically includes: each time the entry startup is re-executed, in the entry Activity, judging through the AppManager whether there is an Activity in the current stack in the startup state at the time of startup.

6. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The login interface of the App entrance is developed natively, and all other contents of the main application interface are developed using H5 pages.

7. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The native implementation of the message receiver is used to receive messages and result feedback, while accepting message transparent transmission and listening to notification bar messages being clicked.

8. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 1 is characterized in that: The S1 specifically includes: ensuring that after receiving the push message, the user clicks the push message to open the main application login interface and re-executes the entry startup, passing parameters to the main application and service through the intent message transparent transmission, and the login interface and the main application interface are registered at the same time so that they can receive and process Push message broadcasts and service broadcasts.

9. The method for waking up the APP and logging in directly to the H5 page without perception according to claim 8 is characterized in that: In order to achieve login-free operation on the login interface, the account information and Token information are transparently transmitted from the local storage.

Images