Method and system for starting application

1. A computer-implemented method, comprising:

starting, by a first local application, a websocket;

attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application;

if the first local application connects, with the websocket, to the local socket, stopping a jump to a boot page for downloading the second local application; and wherein

if a port used by the second local application to start the local socket is occupied, using another port in a predetermined port group;

if the websocket started by the first local application fails to connect to the local socket in a predetermined duration of time, using another port in the predetermined port group to connect to the local socket; and

if the websocket started by the first local application fails to connect to the local socket in the predetermined duration of time after using all ports in the predetermined port group, jumping, by the first local application, to a boot page for downloading the second local application.

2. The computer-implemented method of claim 1 , wherein the first local application comprises a browser application or a local application integrated with a WebView component.

3. The computer-implemented method of claim 1 , wherein, when a link to a web page is triggered and opened:

assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and

invoking, by the first local application, the second local application corresponding to the URI.

4. The computer-implemented method of claim 3 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.

5. The computer-implemented method of claim 1 , further comprising:

if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or

if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.

6. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

starting, by a first local application, a websocket;

attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application;

if the first local application connects, with the websocket, to the local socket, stopping a jump to a boot page for downloading the second local application; and wherein

if a port used by the second local application to start the local socket is occupied, using another port in a predetermined port group;

if the websocket started by the first local application fails to connect to the local socket in a predetermined duration of time, using another port in the predetermined port group to connect to the local socket; and

if the websocket started by the first local application fails to connect to the local socket in the predetermined duration of time after using all ports in the predetermined port group, jumping, by the first local application, to a boot page for downloading the second local application.

7. The non-transitory, computer-readable medium of claim 6 , wherein the first local application comprises a browser application or a local application integrated with a Web View component.

8. The non-transitory, computer-readable medium of claim 6 , wherein, when a link to a web page is triggered and opened:

assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and

invoking, by the first local application, the second local application corresponding to the URI.

9. The non-transitory, computer-readable medium of claim 8 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.

10. The non-transitory, computer-readable medium of claim 6 , further comprising:

if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or

if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.

11. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executable by the one or more computers, perform one or more operations comprising:

starting, by a first local application, a websocket;

attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application;

if the first local application connects, with the websocket, to the local socket, stopping a jump to a boot page for downloading the second local application; and wherein

if a port used by the second local application to start the local socket is occupied, using another port in a predetermined port group;

if the websocket started by the first local application fails to connect to the local socket in a predetermined duration of time, using another port in the predetermined port group to connect to the local socket; and

if the websocket started by the first local application fails to connect to the local socket in the predetermined duration of time after using all ports in the predetermined port group, jumping, by the first local application, to a boot page for downloading the second local application.

12. The computer-implemented system of claim 11 , wherein the first local application comprises a browser application or a local application integrated with a WebView component.

13. The computer-implemented system of claim 11 , wherein, when a link to a web page is triggered and opened:

assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and

invoking, by the first local application, the second local application corresponding to the URI.

14. The computer-implemented system of claim 13 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.

15. The computer-implemented system of claim 11 , further comprising:

if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or

if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.