WO2019001138A1 - 应用程序处理方法、装置和存储介质 - Google Patents
应用程序处理方法、装置和存储介质 Download PDFInfo
- Publication number
- WO2019001138A1 WO2019001138A1 PCT/CN2018/085527 CN2018085527W WO2019001138A1 WO 2019001138 A1 WO2019001138 A1 WO 2019001138A1 CN 2018085527 W CN2018085527 W CN 2018085527W WO 2019001138 A1 WO2019001138 A1 WO 2019001138A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- sub
- page
- identifier
- parent
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
Definitions
- the present application relates to the field of computer technologies, and in particular, to an application processing method, apparatus, and storage medium.
- An application is a sequence of coded instructions that can be executed by a terminal having information processing capabilities, such as a computer, to obtain a result, or a sequence of symbolized instructions or symbolic statements that can be automatically converted into a sequence of coded instructions.
- a terminal having information processing capabilities, such as a computer, to obtain a result, or a sequence of symbolized instructions or symbolic statements that can be automatically converted into a sequence of coded instructions.
- users can install various applications on the terminal, such as a photo application, a social application, or a mail application, so that various functions such as a photographing function, a social function, or an email can be implemented through the applications installed on the terminal. Management functions, etc.
- An embodiment of the present application provides an application processing method, apparatus, and storage medium.
- An application processing method is applied to a terminal, the method comprising:
- An application processing apparatus includes a processor and a memory, the memory storing computer readable instructions, the instructions causing the processor to:
- a computer readable storage medium having stored thereon computer readable instructions, the computer readable instructions being executed by a processor such that the processor performs the following steps:
- FIG 1 is an application environment diagram of an application processing system in an embodiment of the present application
- FIG. 2 is a schematic flowchart of an application processing method in an embodiment of the present application
- FIG. 3 is a schematic diagram of relationships between pages of an operating system, a parent application, a sub-application, and a sub-application in an embodiment of the present application;
- FIG. 4 is a schematic diagram of a sub-application return in an embodiment of the present application.
- FIG. 5 is a schematic diagram of a sub-application closing in an embodiment of the present application.
- FIG. 6 is a schematic diagram of a sub-application jump in an embodiment of the present application.
- FIG. 7 is a schematic flowchart of an application processing method in another embodiment of the present application.
- FIG. 8 is a structural block diagram of an application processing apparatus according to an embodiment of the present application.
- FIG. 9 is a block diagram of a parent application in an embodiment of the present application.
- FIG. 10 is a block diagram of a parent application in another embodiment of the present application.
- Figure 11 is a diagram showing the internal structure of a computer device in an embodiment of the present application.
- FIG. 1 is an application environment diagram of an application processing system in an embodiment of the present application.
- the application processing system includes a terminal 110 and a server 120.
- the terminal 110 and the server 120 are connected through a network.
- the operating system runs on the terminal 110, and the parent application is run on the operating system.
- the terminal 110 implements an application processing method through the parent application to implement the sub-application jump through the parent application.
- the terminal 110 may specifically create a sub-application logic layer unit and a corresponding sub-application view layer unit through the parent application.
- the sub-application view layer processing unit can be used to generate sub-application pages.
- the server 120 may store data required for generating a sub-application page, such as page data corresponding to the sub-application identifier.
- FIG. 2 is a schematic flowchart diagram of an application processing method in an embodiment of the present application. This embodiment is mainly illustrated by the method being applied to the terminal 110 in FIG. 1 described above. Referring to FIG. 2, the application processing method specifically includes the following steps:
- the operating system is run on the terminal and the parent application is run on the operating system.
- the operating system is a computer program that manages and controls the hardware and software resources of the terminal. It is the most basic system software that runs directly on the bare metal of the terminal.
- the application needs to run under the support of the operating system.
- the operating system can be a desktop operating system such as Windows (Windows) operating system or Linux operating system or Mac OS (Apple desktop operating system), or a mobile operating system such as iOS (Apple mobile terminal operating system) or Android (Android) operating system. .
- the parent application is a native application.
- Native applications are applications that run directly on the operating system.
- the parent application can be a social application, a mail application, or a game application.
- Social applications include instant messaging applications, SNS (Social Network Service) applications, or live applications.
- the parent application can specifically be a WeChat program (WeChat).
- FIG. 3 is a schematic diagram showing the relationship between pages of an operating system, a parent application, a sub-application, and a sub-application in one embodiment of the present application.
- the operating system 301 is run on the terminal
- the parent application 302 is run on the operating system 301
- the parent application 302 provides an environment for the operation of the child application.
- the terminal may create a sub-application logic layer unit 304 and a corresponding sub-application view layer unit 305 for implementing the sub-application according to the package of the sub-application.
- the sub-application logic layer unit 304 can be used to execute page logic code in a package
- the sub-application view layer unit 305 can be used to execute page structure code in the package, and can also execute page style code in the package.
- the page logic code, page structure code, and page style code in the package can be collectively referred to as page code.
- the terminal may create a sub-application logic layer unit 304 and a corresponding sub-application view layer unit 305 through the parent application when there is a sub-application to be run in the environment provided by the parent application.
- the terminal may further obtain the program package corresponding to the sub-application and the page data corresponding to the sub-application through the parent application 302, and obtain the page code from the package.
- the page code can include page logic code, page structure code, and page style code.
- the terminal may further execute the page structure code through the sub-application view layer unit 305, select a common component corresponding to the identifier from the common component library according to the identifier of the common component defined in the execution page structure code, and obtain the common component.
- the default component style data which organizes the common components according to the default component style data, and applies the page data to the common component and renders it to form a sub-application page and display it to display the child of the sub-application run by the parent application.
- Application page is
- the page structure code is the code that defines the composition of the page.
- the page structure code can include an identification of the common components included in the page.
- the page style code is the code that defines the page style.
- the page logic code is the code that defines the processing logic of the corresponding sub-application page.
- a common component is a component shared by pages of different sub-applications, has a visual form, and is a component of a sub-application page.
- a public component has a unique identifier and can be the name of a public component.
- the sub-application ID is used to uniquely identify a sub-application.
- the parent application may assign each sub-application a sub-application identifier (such as an APP ID) that uniquely identifies each sub-application, through each sub-application identifier. , you can open each sub-application.
- a sub-application identifier such as an APP ID
- WeChat will assign an APP ID to the shared bicycle, card coupon, etc., to uniquely identify sub-applications such as shared bicycles and card coupons.
- the shared bicycle sub-application jumps to the card coupon sub-application, the shared bicycle sub-application obtains the APP ID of the card sub-application to open the card coupon sub-application.
- the sub-application identifier may be a string including at least one of a number, a letter, and a symbol, such as X123456789.
- the terminal may detect or monitor the triggered in the currently displayed sub-application page by using the sub-application (ie, the first sub-application) to which the currently displayed sub-application page (ie, the first sub-application page) belongs.
- event This event is used to trigger a jump to another sub-application (ie the second sub-application) from the sub-application to which the currently displayed sub-application page belongs.
- This event can be a trigger action for a jump entry.
- the jump entry may specifically be an icon, a link, a virtual button, or the like.
- This event can also be an event that is triggered after the specified event occurs. For example, when the payment is made, after the payment method is selected, the triggered event that jumps to the sub-application corresponding to the selected payment method is triggered.
- the terminal When the terminal detects or listens to the sub-application to which the currently displayed sub-application page belongs from the sub-application to which the currently displayed sub-application page belongs, after the event jumps to another sub-application, the terminal acquires The corresponding sub-application ID (ie the second sub-application ID) of the sub-application that jumps to.
- the corresponding sub-application identifier of the sub-application to be jumped to may be carried in the jump entry, and the sub-application to which the currently displayed sub-application page belongs may detect the trigger for the jump entry. After the operation, the sub-application ID encapsulated in the jump entry is extracted.
- the corresponding sub-application ID of the sub-application to be jumped to may also be the sub-application ID to which the currently displayed sub-application page belongs, and the sub-application ID found according to the detected or monitored time.
- the page data is data for presentation in a sub-application page.
- the page data may be text data, voice data, video data, or picture data.
- the page data can be dynamic data or static data. Dynamic data can be either continuously changing data or periodically changing data.
- the page data corresponding to the sub-application identifier may be a sub-application corresponding to the sub-application identifier, and the page data included in the selected page is unified.
- the selected page is unified, such as the home page of the sub-application, and the home page of the sub-application is the page directly displayed after the sub-application is loaded.
- the page data corresponding to the sub-application identifier may also be page data of a specific page belonging to the sub-application corresponding to the sub-application identifier. For example, the page data of the page where the mail content is located in the mail application, or the page data of the page where the weather information is located in the weather application.
- the terminal may obtain a sub-application global logic file corresponding to the sub-application to be jumped by the parent application, create a sub-application logic layer unit according to the sub-application global logic file, and obtain the sub-application identifier.
- the corresponding sub-application global configuration file obtains the sub-application page configuration file specified by the sub-application global configuration file, and creates the sub-application view layer unit according to the sub-application page configuration file.
- the sub-application logic layer unit initiates a page data acquisition request for acquiring page data corresponding to the sub-application to be jumped to.
- the parent application obtains the page data corresponding to the sub-application to be jumped to, according to the page data acquisition request, from the server corresponding to the parent application, or from the server corresponding to the sub-application. After the parent application obtains the page data, the obtained page data is transferred to the sub-application view layer unit.
- the terminal may activate the sub-application logic layer unit and the sub-application view layer unit corresponding to the sub-application to be jumped by calling the sub-application startup interface provided by the parent application, or may switch to the trigger sub-application.
- the sub-application startup interface may specifically be a launch JSAPI or the like.
- the terminal may also send the page data acquisition request to the server corresponding to the parent application through the parent application, so that the server corresponding to the parent application is from the server corresponding to the child application to be redirected to. Get the page data corresponding to the sub-application to be jumped to.
- the terminal obtains the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and obtains the sub-application identifier corresponding to the currently displayed sub-application page.
- the terminal then sends the two sub-application IDs and the jump relationship between the sub-applications to the server.
- the server detects whether the jump relationship between the received sub-applications is allowed. If the jump relationship between the received sub-applications is blocked, the default page data is returned.
- sub-application A needs to jump to sub-application B (ie, the jump relationship is A ⁇ B)
- the parent application such as WeChat
- its corresponding server such as WeChat server
- sub-application A a list of sub-applications that can be jumped to (the list lists sub-applications to which sub-application A has permission to jump to), and a list of sub-applications that sub-application B can jump to (lists in the list)
- sub-application that sub-application B has permission to jump to if sub-application A has permission to jump to sub-application B, and sub-application B has permission to jump to sub-application A, then jump The relationship A ⁇ B is established. Otherwise, the jump relationship A ⁇ B is blocked, that is, the sub-application A is not allowed to jump to the sub-application B.
- the jump relationship between the received sub-applications is allowed, it continues to detect whether the sub-application to be jumped to is valid. If the sub-application to be jumped to is valid, the corresponding page data of the sub-application to which the jump is made is returned, and if the sub-application to be jumped to is invalid, the default page data is returned.
- the parent application will send a jump relationship from A to B, and the sub-application IDs of A and B are sent to the server. .
- the server detects whether it is allowed to jump from A to B. If it is not allowed, it returns the default page data; if it is allowed, it continues to detect whether B is valid. If it is valid, it returns the page data corresponding to B. If it is invalid, it returns the default. Page data.
- the sub-application identifies the corresponding page data, including the data delivered by the sub-application corresponding to the currently displayed sub-application page.
- the data passed by the sub-application corresponding to the currently displayed sub-application page may be a page path and a page parameter of the sub-application to be jumped to, or may be a sub-application that can be populated to the sub-application to be jumped to.
- the data of the program page may be a page path and a page parameter of the sub-application to be jumped to, or may be a sub-application that can be populated to the sub-application to be jumped to.
- the terminal may detect whether the corresponding code package of the sub-application identifier is stored locally. If it is not detected that the corresponding code package of the sub-application identifier is stored locally, the page data of the default loading page is obtained, and the default loading page is generated to be overlaid on the displayed sub-application page for display, and the sub-application identifier is displayed from the sub-application.
- the corresponding server downloads the code package and executes the code in the code package to run the corresponding sub-application.
- the terminal may execute, by using a sub-application view layer unit corresponding to the sub-application identifier, a page structure code corresponding to the sub-application identifier, according to the identifier of the common component defined in the execution page structure code, from the common component library. Select the common component corresponding to the identifier, obtain the default component style data that comes with the common component, and then organize the common component according to the default component style data, and apply the page data to the common component and render, and generate the overlay to be displayed.
- the sub-application page that is displayed on the child application page.
- the terminal may overwrite the displayed sub-application page by the sub-application view layer unit corresponding to the sub-application identifier according to the sub-application page by the parent application.
- the sub-application view layer unit corresponding to the sub-application identifier, the sub-application page generated according to the page data may also be automatically overlaid on the displayed sub-application page for display.
- the parent application is run on the operating system, and the child application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- each sub-application can realize mutual help of functions, that is, an environment in which division of labor can be formed between sub-applications, for example, a part of sub-applications are focused on platform classes (such as job search platforms) and professional classes (such as coupons). ), serving other sub-applications; while another sub-application focuses on business functions (such as shared bicycles), reducing the development cost of each sub-application and shortening its development time, while the depth and breadth of each sub-application (For example, through the mutual help between the sub-applications, the functions of each sub-application become more and more powerful, so that the depth is expanded; and through the above jump function, one sub-application can jump to other sub-applications. The application, thus making its breadth expanded, has been extended.
- WeChat parent application
- Other sub-applications that need to use the loyalty card function can jump through the above sub-applications. Jump to the card coupon (sub-application) to realize the management of the membership card, such as member registration, point management, etc., so that other sub-applications can easily integrate the membership card function without consuming the corresponding manpower and resources.
- the application processing method further includes: acquiring a jump path for recording a sub-application jump relationship; and acquiring the obtained sub-application identifier when the obtained sub-application identifier exists in the jump path The sub-application ID is moved to the end of the jump path; when the obtained sub-application ID does not exist in the jump path, the obtained sub-application ID is added to the end of the jump path.
- the jump path includes the sub-application identifiers arranged according to the sub-application jump order, and the sub-application jump relationship is recorded.
- the jump path of the sub-application jump relationship that records "jump from sub-application A to sub-application B and then jump to sub-application C" is: A ⁇ B ⁇ C.
- the terminal may obtain a jump path for recording a sub-application jump relationship through the parent application, traverse the sub-application identifier in the obtained jump path, and traverse the sub-application identifier and the acquired sub-application.
- the program identification is compared.
- the parent application determines that the sub-application ID traversed to is the same as the obtained sub-application ID
- the parent application ID traversed to the end of the jump path is moved.
- the parent application determines that the sub-application ID traversed to is different from the obtained sub-application ID, the obtained sub-application ID is directly added to the end of the jump path.
- the terminal may detect, by the parent application, whether the obtained sub-application identified by the sub-application is currently running in an environment provided by the parent application. If yes, query the page path of the sub-application identified by the sub-application at runtime. If the page path of the sub-application at runtime is inconsistent with the page path of the sub-application page to which the current intent jumps, it is not necessary to close the sub-application first, and the re-loading interface is called to generate the current intent jump. To the sub-application page.
- the reload interface may specifically be Relaunch JSAPI or the like.
- the sub-application jump relationship is recorded, so that each of the accessed sub-applications can be returned layer by layer.
- the application processing method further includes: obtaining, by the sub-application to which the currently displayed sub-application page belongs, a return instruction; determining, in response to the return instruction, the corresponding sub-application of the currently displayed sub-application page In the jump path, the sub-application ID adjacent to the determined sub-application identifier and located before the determined sub-application identifier is searched; and the sub-application page corresponding to the found sub-application identifier is returned.
- the return instruction is an instruction for returning to the previous sub-application (ie, the third sub-application, which may be the same as the first sub-application or different from the first sub-application).
- the return instruction can be either a passively triggered instruction or an actively triggered instruction.
- Passive trigger is the return instruction that is triggered by the sub-application to which the currently displayed sub-application page belongs, after the trigger event is detected.
- the active trigger is a return instruction that is actively triggered by the sub-application to which the currently displayed sub-application page belongs.
- the terminal may detect or listen to an event triggered in the currently displayed sub-application page by the sub-application to which the currently displayed sub-application page belongs. This event is used to trigger the sub-application to which the currently displayed sub-application page belongs, and return to the previously launched sub-application (ie the third sub-application).
- the event may be a triggering operation for an operation portal such as an icon or a virtual button.
- the triggering operation may be a touch operation, a click operation (for example, clicking on the control 400 in FIG. 4) or a sliding operation (such as a right sliding operation in the page shown in FIG. 4).
- the terminal may automatically trigger a return instruction after performing a specific operation through the sub-application to which the currently displayed sub-application page belongs. For example, if the sub-application to which the currently displayed sub-application page belongs is a payment sub-application, the payment sub-application automatically triggers a return instruction to return to the previous sub-application after the payment is completed.
- the automatic trigger return instruction may be triggered by calling a return interface provided by the parent application.
- the return interface can be an interface such as Back JSAPI.
- the terminal when the terminal returns the sub-application according to the return instruction, the terminal may acquire the data that the sub-application that is currently returning needs to be delivered to the sub-application to be returned, and then transfer the acquired data to the to-be-returned. Sub-application.
- data transfer occurs when a return is triggered by a call to the return interface provided by the parent application.
- the terminal determines the corresponding sub-application identifier of the currently displayed sub-application page in response to the return instruction.
- the sub-application identifier adjacent to the determined sub-application identifier and located before the determined sub-application identifier is searched, and the sub-application page corresponding to the found sub-application identifier is returned.
- returning the sub-application page corresponding to the found sub-application identifier including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-
- the parent application runs in the background state, is run by the parent application, but does not display the page through the view layer.
- the foreground state is a concept corresponding to the background state. Runn by the parent application in the foreground state, is run by the parent application, and the page is displayed through the view layer. After jumping from one sub-application to another sub-application, the sub-application that was jumped is not closed, but continues to run in the background state by the parent application until the sub-application running in the background state is artificial Shut down, or shut down by the parent application due to a running timeout. For example, it will be closed if it runs in the background for more than ten minutes.
- the terminal may query the sub-application identifier corresponding to the sub-application to be returned in the sub-application running management list. If the sub-application ID corresponding to the sub-application to be returned is found in the sub-application running management list, the sub-application to be returned is indicated, and the parent application runs in the background state.
- the terminal can switch the sub-application to be returned to the foreground state through the parent application, and display the sub-application page displayed by the sub-application to be returned when the jump occurs.
- the terminal may obtain, by the parent application, page data of the default sub-application page corresponding to the sub-application to be returned to display the default sub-application page corresponding to the sub-application to be returned, for example, the parent application Re-push (or open) the sub-application, display the home page of the sub-application, and the like.
- the sub-application to be returned when the sub-application to be returned is still running in the background, the sub-application can be switched to the foreground to quickly return to the page displayed by the sub-application to be returned when the jump is performed. This allows the user to continue on the page, improving the convenience of the application. Moreover, when the sub-application to be returned has finished running, the default sub-application page of the sub-application to be returned is directly returned in the parent application, and the time consuming to avoid manual switching improves the application efficiency.
- the processing method that the sub-application returns after the jump is provided, so that when the intent is returned to the used sub-application, the return can be directly performed in the parent application, and the current use is required without exiting.
- the application re-starting the application's time-consuming return to the application, increases the efficiency of the application.
- Figure 4 shows a schematic diagram of a sub-application return in one embodiment.
- the schematic diagram includes a return operation portal 400, a currently displayed sub-application page 401, a sub-application page 402 displayed by the sub-application to be returned when the jump occurs, and a sub-application to be returned to.
- the terminal determines the sub-application to be returned by the parent application, and when the parent application runs in the background state, the sub-application to be returned to the jump occurs.
- the sub-application page 402 displayed at the time is overlaid on the currently displayed sub-application page 401.
- the terminal when it is determined by the parent application that the sub-application to be returned has finished running, is overlaid on the currently displayed sub-application page 401 with the default sub-application page 403 of the sub-application to be returned.
- the sub-application includes a native plug-in sub-application.
- the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier is moved to the end of the jump path, and includes: when the obtained sub-application identifier exists in the jump path, determining the jump a continuous native plug-in sub-application ID in the transfer path that is adjacent to the obtained sub-application ID and located after the obtained sub-application ID; moves the obtained sub-application ID to the end of the jump path, and jumps The continuous native plug-in sub-application ID is removed from the transfer path.
- the native plug-in sub-application is a sub-application developed by the developer of the parent application to implement the plug-in function of the parent application. For example, a nearby sub-application or a swipe sub-application.
- you run the native plug-in sub-application in the parent application you can treat the native plug-in sub-application as a whole with the parent application.
- you jump from a sub-application to a native plug-in sub-application you can also treat the native plug-in sub-application as a whole with the sub-application that intends to jump.
- the terminal may obtain a jump path for recording a sub-application jump relationship through the parent application, traverse the sub-application identifier in the obtained jump path, and traverse the sub-application identifier and the acquired sub-application.
- the program identification is compared.
- the parent application determines that the sub-application ID traversed to is the same as the obtained sub-application ID, it detects whether the next sub-application ID of the sub-application ID traversed to is the native plug-in sub-application ID.
- the parent application determines in the jump path that the next sub-application ID traversed to the sub-application ID is the native plug-in sub-application ID, then the continuous native plug-in application is determined from the native plug-in sub-application identifier.
- the program identifier moves the obtained sub-application ID to the end of the jump path and deletes the continuous native plug-in sub-application ID in the jump path. If the parent application determines in the jump path that the next sub-application ID of the sub-application ID traversed to is not the native plug-in sub-application ID, the obtained sub-application ID is directly moved to the end of the jump path.
- the native plug-in sub-application is used to provide a functional implementation of the parent application or the sub-application, and when the location of the sub-application identification needs to be moved, the sub-application is simultaneously identified by the adjacent, continuous native plug-in.
- the sub-application ID is deleted.
- the jump path obtained by the terminal through the parent application is “A ⁇ B ⁇ K1 ⁇ K2 ⁇ C”, where K1 and K2 are the native plug-in sub-application identifiers. If the current intent jumps from the sub-application corresponding to C to the sub-application corresponding to B, at this time, B exists in "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C", and the next sub-application ID of B is K1. , that is, the native plug-in application identifier, then determine the continuous native plug-in application identifier "K1 ⁇ K2" after B, move B to the end of "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C", and delete "K1 ⁇ K2", get "A ⁇ C ⁇ B”.
- K1 exists in "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C", and the next sub-application ID of K1
- the native plug-in application identifier determine the continuous native plug-in application identifier "K2" after K1, move K1 to the end of "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C", and delete "K2" , get "A ⁇ B ⁇ C ⁇ K1".
- K2 exists in "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C", and the next sub-application ID of K2 For C, instead of the native plug-in application identifier, move K2 directly to the end of "A ⁇ B ⁇ K1 ⁇ K2 ⁇ C" and get "A ⁇ B ⁇ K1 ⁇ C ⁇ K2".
- a native plug-in sub-application that can be used as a component of a sub-application can be provided, which can be substantially consistent with the direct use of the sub-application when jumping from the sub-application to the native plug-in sub-application.
- the use experience avoids the process of developing sub-applications and improves the efficiency of sub-application implementation.
- the sub-application also includes a third party sub-application.
- the application processing method further includes: detecting, by the sub-application to which the currently displayed sub-application page belongs, a shutdown instruction; and when the shutdown instruction is detected, and the first third-party sub-application identifier in the jump path exists, the native plug-in exists
- the application identifier ie, the first native plug-in sub-application ID
- the close command is detected and the first third-party sub-application in the jump path is detected
- the program ID does not exist before the native plug-in sub-application ID, it returns to the parent application.
- the third-party sub-application is a sub-application developed by a third-party service provider registered with the open service platform corresponding to the parent application.
- the close instruction is an instruction to close the sub-application and return the parent application or the native plug-in sub-application.
- the parent application is WeChat
- the third party sub-application is a shared bicycle, XXXX shopping, etc.
- the user can scan the QR code to search for the name of the third-party sub-application (such as Mobike, etc.)
- the third party sub-application can be downloaded and run by clicking on a message or business card shared by other users, and then using the service provided by the third-party sub-application.
- the third party sub-application seamlessly accesses the parent application, referred to as part of the parent application, such that the user has a native experience, and the third party sub-application substantially extends the parent application
- the functions of the program for example, WeChat can use shared bicycles through meditation, shopping with XXXX, etc.
- the terminal may detect or listen to an event triggered in the currently displayed sub-application page by the sub-application to which the currently displayed sub-application page belongs. This event is used to trigger the close of the sub-application, returning to the parent application or the native plug-in sub-application.
- the event may be a triggering operation for an icon (eg, operating the control 500 in FIG. 5) or an operational portal such as a virtual button.
- the jump path is invalid, for example, the jump path is A ⁇ B ⁇ C, and the sub-application C is currently displayed, when the user operation is detected in FIG. 5 Control 500 (ie, closing sub-application C), then the jump path A ⁇ B ⁇ C is invalidated and returned to the parent application.
- the terminal detects or listens to the shutdown instruction through the sub-application to which the currently displayed sub-application page belongs, whether the native plug-in is existed before the first third-party sub-application identifier is queried in the jump path by the parent application.
- Application ID If the native plug-in sub-application ID exists before the first third-party sub-application ID in the jump path, the native plug-in sub-application corresponding to the native plug-in sub-application identifier is returned, if the first third party in the jump path If the child application ID does not exist before the native plug-in sub-application ID, it returns to the parent application.
- returning the native plug-in sub-application corresponding to the native plug-in sub-application identifier includes: the number of native plug-in sub-application IDs existing before the first third-party sub-application identifier in the jump path is more than At one time, obtain the native plug-in sub-application ID (ie, the second native plug-in sub-application ID) adjacent to the first third-party sub-application ID and located before the first third-party sub-application ID; The native plug-in sub-application corresponding to the native plug-in application identifies the native plug-in sub-application page that is displayed when the jump is displayed; the determined native plug-in sub-application page is displayed.
- the native plug-in sub-application ID ie, the second native plug-in sub-application ID
- the terminal determines the existence of the first third-party sub-application identifier in the jump path. Whether the number of native plug-in sub-application IDs is more than one. If the terminal determines that the number of the native plug-in application identifiers is only one by the parent application, the native plug-in application displayed by the native plug-in application corresponding to the unique native plug-in application identifier is displayed. Program page.
- the terminal determines, by the parent application, that the number of the native plug-in sub-application identifiers is more than one, the native plug-in sub-application adjacent to the first third-party sub-application identifier and located before the first third-party sub-application identifier is obtained.
- the native plug-in sub-application since the native plug-in sub-application is used to provide the functional implementation of the parent application, it is considered as a whole with the parent application, and directly returns to the parent application or the native when the third-party sub-application is intended to be closed. Plug-in sub-applications do not require indirect control through third-party sub-applications, improving application efficiency.
- the parent application or the native plug-in sub-application can be directly returned by triggering the shutdown instruction, thereby avoiding Increasing the time-consumingness of closing third-party sub-applications one by one increases the efficiency of application usage.
- Figure 5 shows a schematic diagram of a sub-application shutdown in one embodiment.
- the schematic diagram includes a close trigger entry 500, a currently displayed sub-application page 501, a neighbor adjacent to the first third-party sub-application identifier in the jump path, and located before the first third-party sub-application identifier.
- the sub-application page 501 currently displayed by the terminal after detecting the triggering operation for the shutdown trigger entry 500, detects that the native plug-in sub-application identifier exists before the first third-party sub-application identifier in the jump path by the parent application. Returning the native plug-in application identifier adjacent to the first third-party sub-application ID in the jump path and before the first third-party sub-application ID according to the shutdown command, corresponding to the native plug-in sub-application At the time of the jump, the native plug-in sub-application page 502 is displayed.
- the parent application detects that the native plug-in sub-application ID is not present before the first third-party sub-application ID in the jump path, it returns the parent application page that is displayed when the parent application runs the sub-application. 503.
- the page data corresponding to the sub-application identifier is passed to the sub-application corresponding to the sub-application identifier and run by the parent application, including: switching to triggering the sub-application jump a parent application page, wherein the parent application page is a page displayed by the parent application; the parent application page triggers acquiring page data corresponding to the child application identifier; and the page data is transmitted to the child application
- the program identifies the sub-application that corresponds to and is run by the parent application.
- the parent application page is used to trigger a jump of the child application. That is to say, when jumping from one sub-application to another, it is necessary to switch to the parent application page, and then trigger the page data corresponding to the sub-application identifier through the parent application page. The page data is then passed to the sub-application that corresponds to the sub-application ID and is run by the parent application.
- the parent application page for triggering the sub-application jump may be a unified parent application page. Jumping to any sub-application can be triggered by a unified parent application page.
- Each sub-application has a corresponding parent application page for launching the sub-application.
- a new sub-application jump is provided by switching to the parent application page that triggers the sub-application jump to implement the sub-application jump.
- Figure 6 shows a schematic diagram of a sub-application jump in one embodiment.
- the schematic diagram includes a currently displayed sub-application page 601, a parent application page 602 for triggering a sub-application jump, and a sub-application page 603 corresponding to the sub-application to be jumped to.
- the terminal switches from the sub-application page 601 currently displayed in the current sub-application to the parent application page 602 for triggering the sub-application jump, and then triggers the jump to the sub-application corresponding to the sub-application to be jumped to.
- Program page 603, implements sub-application jumps.
- the application processing method further includes: obtaining a parent application page identifier (ie, a first parent application page identifier) of the parent application page (ie, the first parent application page) to which the switch is made. And a jump path for recording the sub-application jump relationship; when the obtained sub-application identifier exists in the jump path, the jump path is adjacent to the obtained sub-application identifier and located
- the parent application page identifier ie, the second parent application page identifier
- the obtained sub-application ID is deleted; the obtained parent application page identifier is added to the end of the jump path; the sub-application obtained in the jump path is obtained
- the program ID moves after the added parent application page ID.
- the jump path includes a sub-application identifier and/or a parent application page identifier arranged according to a sub-application jump order, and records a sub-application jump relationship and reflects a sub-application jump manner.
- the jump path of the sub-application jump relationship that records "from the sub-application A by switching to the parent application page M to the sub-application C" is: A ⁇ M ⁇ C.
- the terminal may obtain a jump path for recording a sub-application jump relationship through the parent application, traverse the sub-application identifier in the obtained jump path, and traverse the sub-application identifier and the acquired sub-application.
- the program identification is compared.
- the parent application determines that the sub-application ID traversed to is the same as the obtained sub-application ID, it will traverse to the sub-application ID, and the adjacent parent application page identifier is deleted, and will be switched to After the parent application page identifier of the parent application page is added to the end of the jump path, the child application ID traversed to is moved to the parent application page identifier after the addition.
- the parent application determines that the child application identifier traversed to is different from the obtained child application identifier, the parent application page identifier corresponding to the parent application page that is switched to directly, and the obtained child application identifier are directly obtained. Add to the end of the jump path in turn.
- the jump path obtained by the terminal through the parent application is “A ⁇ M1 ⁇ B ⁇ C”. If the current intent is to jump from the sub-application corresponding to C through the parent application page M2 to the sub-application corresponding to A, at this time, A exists in "A ⁇ M1 ⁇ B ⁇ C", then A will be followed by The neighboring parent application page M1 is deleted, and after M2 is added to the end of "A ⁇ B ⁇ C", A is moved to M2, and "B ⁇ C ⁇ M2 ⁇ A" is obtained.
- the sub-application jump relationship reflecting the sub-application jump mode is recorded, so that each accessed layer can be returned layer by layer.
- the child application identifies the parent application page of the parent application page and the child application of the child application that is jumped to by jumping to the parent application page and then triggering a jump to another child application.
- the program identification is recorded in the jump path. No data transfer is made when the sub-application returns by triggering the return interface provided by the parent application. If the sub-application that needs to be returned currently needs to be returned to the sub-application determined according to the jump path, instead of jumping to the source sub-application of the sub-application that needs to be returned, then the return provided by calling the parent application When the interface triggers the sub-application to return, no data is passed.
- FIG. 7 is a schematic flow chart of an application processing method in a specific embodiment. Referring to FIG. 7, the application processing method specifically includes the following steps:
- step S706 detecting a sub-application jump mode; if the sub-application jump mode is to jump to an interface (such as launch JSAPI) provided by the calling parent application, then the process goes to step S708; if the sub-application jump mode is through the parent application If the page triggers a jump, the process jumps to step S722.
- an interface such as launch JSAPI
- S708 Pass the page data corresponding to the sub-application identifier to the sub-application corresponding to the sub-application identifier and run by the parent application.
- step S712 Detect whether the acquired sub-application identifier exists in the jump path; if yes, go to step S714; if no, go to step S720.
- step S714. Detect whether there is an adjacent native plug-in application after the acquired sub-application identifier; if yes, go to step S716; if no, go to step S718.
- S716 Determine a continuous native plug-in application identifier that is adjacent to the obtained sub-application identifier and that is located after the obtained sub-application identifier in the jump path; and move the obtained sub-application identifier to the end of the jump path. And delete the continuous native plug-in sub-application ID in the jump path.
- step S726 Detect whether the acquired sub-application identifier exists in the jump path; if yes, go to step S728; if no, go to step S730.
- S732 Generate, by the sub-application corresponding to the sub-application identifier, a sub-application page that is displayed on the displayed sub-application page according to the page data.
- S734 obtaining a return instruction by using a sub-application to which the currently displayed sub-application page belongs; determining, according to the return instruction, a corresponding sub-application identifier of the currently displayed sub-application page; searching and determining in the jump path
- the child application identifies the child application ID that is adjacent and that precedes the determined child application ID.
- step S736 detecting the running status of the sub-application corresponding to the found sub-application identifier; if the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then the process proceeds to step S738; If the sub-application corresponding to the found sub-application ID has finished running, then the process goes to step S740.
- S742 Detect a shutdown instruction by using a sub-application to which the currently displayed sub-application page belongs.
- step S744 when detecting the close instruction, detecting whether the native plug-in application identifier exists before the first third-party sub-application identifier in the jump path; if yes, jumping to step S746; if not, jumping to step S752 .
- step S746 Detect whether there is more than one number of native plug-in application identifiers existing before the first third-party sub-application identifier in the jump path; if yes, go to step S748; if no, go to step S750.
- S748 obtaining a native plug-in sub-application identifier adjacent to the first third-party sub-application identifier and located before the first third-party sub-application identifier; determining the native plug-in sub-application corresponding to the obtained native plug-in sub-application identifier The native plug-in sub-application page that is displayed when the program jumps; displays the determined native plug-in sub-application page.
- the parent application is run on the operating system, and the child application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- the sub-application provides a way for the sub-application to return after the jump, so that when the intent is returned to the used sub-application, the return can be directly made in the parent application without exiting the application that needs to be quit.
- the parent application or the native plug-in sub-application can be directly returned by triggering the close instruction, thereby avoiding closing the third-party sub-application one by one.
- the time-consuming process leads to increased application efficiency.
- an application processing device 800 is provided.
- the application processing apparatus 800 includes a parent application 810.
- a parent application 810 configured to display a sub-application page of the running sub-application; obtain, by the sub-application, a corresponding sub-application identifier of the sub-application to be jumped; and the page data corresponding to the sub-application identifier, Passed to the sub-application corresponding to the sub-application identifier and run by the parent application; through the sub-application corresponding to the sub-application identifier, generating an overlay on the displayed sub-application page for display according to the page data Sub-application page.
- the application processing device 800 described above runs the parent application on the operating system, and the child application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- the parent application 810 is further configured to obtain a jump path for recording a sub-application jump relationship; and when the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier Move to the end of the jump path; when the obtained sub-application ID does not exist in the jump path, add the obtained sub-application ID to the end of the jump path.
- the sub-application jump relationship is recorded, so that each of the accessed sub-applications can be returned layer by layer.
- the parent application 810 is further configured to: obtain, by the sub-application to which the currently displayed sub-application page belongs, a return instruction; and in response to the return instruction, determine a corresponding sub-application identifier of the currently displayed sub-application page. In the jump path, find the sub-application ID adjacent to the determined sub-application identifier and located before the determined sub-application ID; return the sub-application page corresponding to the found sub-application ID.
- the processing method that the sub-application returns after the jump is provided, so that when the intent to return the used sub-application is returned, the return can be directly performed in the parent application, and the current use is required without exiting.
- the application re-starting the application's time-consuming return to the application, increases the efficiency of the application.
- the parent application 810 is further configured to: when the sub-application corresponding to the found sub-application identifier is run by the parent application in a background state, return the sub-application corresponding to the found sub-application identifier.
- the sub-application page displayed when the program jumps; when the sub-application corresponding to the found sub-application ID has finished running, the default sub-application page corresponding to the found sub-application identifier is returned. .
- the sub-application to be returned when the sub-application to be returned is still running in the background, the sub-application can be switched to the foreground to quickly return to the page displayed by the sub-application to be returned when the jump is performed. This allows the user to continue on the page, improving the convenience of the application. Moreover, when the sub-application to be returned has finished running, the default sub-application page of the sub-application to be returned is directly returned in the parent application, and the time consuming to avoid manual switching improves the application efficiency.
- the sub-application includes a native plug-in sub-application.
- the parent application 810 is further configured to: when the obtained sub-application identifier exists in the jump path, determine a consecutive one of the jump path adjacent to the acquired sub-application identifier and located after the acquired sub-application identifier Native plug-in application ID; moves the obtained sub-application ID to the end of the jump path and deletes the consecutive native plug-in sub-application IDs in the jump path.
- a native plug-in sub-application that can be used as a component of a sub-application can be provided, which can be substantially consistent with the direct use of the sub-application when jumping from the sub-application to the native plug-in sub-application.
- the use experience avoids the process of developing sub-applications and improves the efficiency of sub-application implementation.
- the sub-application also includes a third party sub-application.
- the parent application 810 is further configured to detect a close instruction by using a sub-application to which the currently displayed sub-application page belongs; and a native plug-in sub-application exists before the closing instruction is detected and the first third-party sub-application identifier in the jump path exists
- the native plug-in sub-application corresponding to the native plug-in application identifier is returned; when the close directive is detected and the first plug-in sub-application identifier is not in the jump path, the native plug-in sub-application identifier does not exist. , then return to the parent application.
- the parent application or the native plug-in sub-application can be directly returned by triggering the close instruction, thereby avoiding Increasing the time-consumingness of closing third-party sub-applications one by one increases the efficiency of application usage.
- the parent application 810 is further configured to acquire the first third party when the number of the native plug-in application identifiers existing before the first third-party sub-application identifier in the jump path is more than one.
- the application identifies the native plug-in sub-application ID that is adjacent to and located before the first third-party sub-application ID; determines that the native plug-in sub-application corresponding to the obtained native plug-in application identifier is displayed when the jump is Native plugin sub-application page; displays the determined native plug-in sub-application page.
- the native plug-in sub-application since the native plug-in sub-application is used to provide the functional implementation of the parent application, it is considered as a whole with the parent application, and directly returns to the parent application or the native when the third-party sub-application is intended to be closed. Plug-in sub-applications do not require indirect control through third-party sub-applications, improving application efficiency.
- the parent application 810 is further configured to switch to a parent application page for triggering a sub-application jump; by using the parent application page, triggering to acquire page data corresponding to the sub-application identifier; Passed to a sub-application that corresponds to the sub-application ID and is run by the parent application.
- a new sub-application jump is provided by switching to the parent application page that triggers the sub-application jump to implement the sub-application jump.
- the parent application 810 is further configured to obtain a parent application page identifier corresponding to the parent application page switched to, and a jump path for recording the sub-application jump relationship; when the obtained sub-application When the identifier exists in the jump path, the parent application page identifier adjacent to the obtained sub-application identifier in the jump path and located after the obtained sub-application identifier is deleted; the parent application page identifier to be obtained is deleted. Add to the end of the jump path; move the sub-application ID obtained in the jump path after the added parent application page ID.
- the sub-application jump relationship reflecting the sub-application jump mode is recorded, so that each accessed layer can be returned layer by layer.
- a block diagram of a parent application 810 is provided.
- the parent application 810 includes a display module 801, an acquisition module 802, a delivery module 803, and a jump module 804.
- the display module 801 is configured to display a sub-application page of the running sub-application.
- the obtaining module 802 is configured to obtain, by using the sub-application, a corresponding sub-application identifier of the sub-application to be jumped to.
- the delivery module 803 is configured to pass the page data corresponding to the sub-application identifier to the sub-application corresponding to the sub-application identifier and run by the parent application.
- the jump module 804 is configured to generate, by using the sub-application corresponding to the sub-application identifier, a sub-application page that is displayed on the displayed sub-application page for display according to the page data.
- the sub-application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- the obtaining module 902 is further configured to acquire a jump path for recording a sub-application jump relationship; and when the obtained sub-application identifier exists in the jump path, move the acquired sub-application identifier To the end of the jump path; when the obtained sub-application ID does not exist in the jump path, the obtained sub-application ID is added to the end of the jump path.
- the sub-application jump relationship is recorded, so that each of the accessed sub-applications can be returned layer by layer.
- the parent application 810 also includes an instruction processing module 805.
- the instruction processing module 805 is configured to obtain a return instruction by using a sub-application to which the currently displayed sub-application page belongs, and determine, according to the return instruction, a corresponding sub-application identifier of the currently displayed sub-application page; in the jump path Finding the sub-application ID adjacent to the determined sub-application ID and located before the determined sub-application ID; returning the sub-application page corresponding to the found sub-application ID.
- the processing method that the sub-application returns after the jump is provided, so that when the intent to return the used sub-application is returned, the return can be directly performed in the parent application, and the current use is required without exiting.
- the application re-starting the application's time-consuming return to the application, increases the efficiency of the application.
- the instruction processing module 805 is further configured to: when the sub-application corresponding to the found sub-application identifier is run by the parent application in a background state, return the sub-application corresponding to the found sub-application identifier.
- the sub-application page displayed when the program jumps; when the sub-application corresponding to the found sub-application ID has finished running, the default sub-application page corresponding to the found sub-application identifier is returned. .
- the sub-application to be returned when the sub-application to be returned is still running in the background, the sub-application can be switched to the foreground to quickly return to the page displayed by the sub-application to be returned when the jump is performed. This allows the user to continue on the page, improving the convenience of the application. Moreover, when the sub-application to be returned has finished running, the default sub-application page of the sub-application to be returned is directly returned in the parent application, and the time consuming to avoid manual switching improves the application efficiency.
- the sub-application includes a native plug-in sub-application.
- the obtaining module 802 is further configured to: when the obtained sub-application identifier exists in the jump path, determine a continuous native in the jump path adjacent to the acquired sub-application identifier and located after the acquired sub-application identifier The plug-in sub-application ID; moves the obtained sub-application ID to the end of the jump path, and deletes the consecutive native plug-in sub-application IDs in the jump path.
- a native plug-in sub-application that can be used as a component of a sub-application can be provided, which can be substantially consistent with the direct use of the sub-application when jumping from the sub-application to the native plug-in sub-application.
- the use experience avoids the process of developing sub-applications and improves the efficiency of sub-application implementation.
- the sub-application also includes a third party sub-application.
- the instruction processing module 805 is further configured to detect a shutdown instruction by using a sub-application to which the currently displayed sub-application page belongs; and a native plug-in sub-application exists before the closing instruction is detected and the first third-party sub-application identifier in the jump path exists
- the native plug-in sub-application corresponding to the native plug-in application identifier is returned; when the close directive is detected and the first plug-in sub-application identifier is not in the jump path, the native plug-in sub-application identifier does not exist. , then return to the parent application.
- the parent application or the native plug-in sub-application can be directly returned by triggering the close instruction, thereby avoiding Increasing the time-consumingness of closing third-party sub-applications one by one increases the efficiency of application usage.
- the instruction processing module 805 is further configured to: when the number of the native plug-in application identifiers existing before the first third-party sub-application identifier in the jump path is more than one, obtain the first third-party sub- The application identifies the native plug-in sub-application ID that is adjacent to and located before the first third-party sub-application ID; determines that the native plug-in sub-application corresponding to the obtained native plug-in application identifier is displayed when the jump is Native plugin sub-application page; displays the determined native plug-in sub-application page.
- the native plug-in sub-application since the native plug-in sub-application is used to provide the functional implementation of the parent application, it is considered as a whole with the parent application, and directly returns to the parent application or the native when the third-party sub-application is intended to be closed. Plug-in sub-applications do not require indirect control through third-party sub-applications, improving application efficiency.
- the delivery module 803 is further configured to switch to a parent application page for triggering a sub-application jump; triggering, by the parent application page, acquiring page data corresponding to the sub-application identifier; and transmitting the page data To the sub-application that corresponds to the sub-application ID and is run by the parent application.
- a new sub-application jump is provided by switching to the parent application page that triggers the sub-application jump to implement the sub-application jump.
- the obtaining module 802 is further configured to obtain a parent application page identifier corresponding to the parent application page that is switched to, and a jump path for recording the sub-application jump relationship; when the obtained sub-application identifier is obtained When it exists in the jump path, the parent application page identifier adjacent to the obtained sub-application identifier and located after the acquired sub-application identifier is deleted in the jump path; the obtained parent application page identifier is added. To the end of the jump path; move the sub-application ID obtained in the jump path after the added parent application page ID.
- the sub-application jump relationship reflecting the sub-application jump mode is recorded, so that each accessed layer can be returned layer by layer.
- Figure 11 is a diagram showing the internal structure of a computer device in one embodiment.
- the computer device may specifically be the terminal 110 in FIG.
- the computer device 1100 includes a processor 1101, a nonvolatile storage medium 1102, an internal memory 1103, a network interface 1104, and a display screen 1105 that are connected through a system bus.
- the non-volatile storage medium 1102 of the computer device 1100 can store an operating system 1106 and computer readable instructions 1107 that, when executed, can cause the processor 1101 to execute an application processing method.
- the processor 1101 is used to provide computing and control capabilities to support the operation of the entire computer device.
- Computer readable instructions 1107 can be stored in the internal memory 1103.
- the processor 1101 can be caused to execute an application processing method.
- the network interface 1104 is configured to perform network communication with the server, such as sending a collaborative operation authorization request to the server, receiving an authorization response returned by the server, and the like.
- the display screen of the computer device 1100 may be a liquid crystal display or an electronic ink display or the like, and the computer device 1100 may be a mobile phone, a tablet computer or a personal digital assistant or a wearable device or the like. It will be understood by those skilled in the art that the structure shown in FIG. 11 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
- the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
- the application processing apparatus may be implemented in the form of a computer program executable on a computer device 1100 as shown in FIG.
- the storage medium can store various program modules that make up the application processing device, such as the parent application 810 shown in FIG.
- Each of the program modules includes computer readable instructions for causing the computer device to perform the steps in the application processing method of various embodiments of the present application described in the specification, for example, the computer device may The child application page of the running sub-application is displayed by the parent application 810 in the application processing device 800 as shown in FIG.
- the corresponding sub-application identifier of the sub-application to be jumped to is obtained by the sub-application; Passing the page data corresponding to the sub-application identifier to the sub-application corresponding to the sub-application identifier and running by the parent application; generating the overlay according to the page data through the sub-application corresponding to the sub-application identifier The sub-application page that is displayed on the displayed sub-application page.
- a computer readable storage medium having stored thereon computer readable instructions that, when executed by a processor, cause the processor to perform the steps of: displaying The sub-application page of the sub-application running by the parent application; the sub-application obtains the corresponding sub-application ID of the sub-application to be jumped; and passes the page data corresponding to the sub-application identifier to The sub-application identifies a sub-application corresponding to and run by the parent application; and through the sub-application corresponding to the sub-application identifier, generates a sub-application that is displayed on the displayed sub-application page according to the page data. Program page.
- the computer readable instructions cause the processor to execute, after obtaining the corresponding sub-application identifier of the sub-application to be jumped through the sub-application, and further performing the following steps: acquiring the sub-application hop for recording The jump path of the transit relationship; when the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier is moved to the end of the jump path; when the obtained sub-application identifier does not exist in the jump path In the middle, add the obtained sub-application ID to the end of the jump path.
- the computer readable instructions further cause the processor to: obtain a return instruction by the sub-application to which the currently displayed sub-application page belongs; and determine the currently displayed sub-application page in response to the return instruction Corresponding sub-application identifier; in the jump path, searching for a sub-application identifier adjacent to the determined sub-application identifier and located before the determined sub-application identifier; returning the corresponding sub-application identifier corresponding to the search Sub-application page.
- returning the sub-application page corresponding to the found sub-application identifier including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-
- the sub-application includes a native plug-in sub-application.
- the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier is moved to the end of the jump path, and includes: when the obtained sub-application identifier exists in the jump path, determining the jump a continuous native plug-in sub-application ID in the transfer path that is adjacent to the obtained sub-application ID and located after the obtained sub-application ID; moves the obtained sub-application ID to the end of the jump path, and jumps The continuous native plug-in sub-application ID is removed from the transfer path.
- the sub-application also includes a third party sub-application.
- the computer readable instructions further cause the processor to: detect a close instruction by a sub-application to which the currently displayed sub-application page belongs; when the close instruction is detected, and the first third-party sub-application identifier in the jump path
- the native plug-in application identifier is present, the native plug-in sub-application corresponding to the native plug-in sub-application identifier is returned; when the close command is detected and the first third-party sub-application identifier in the jump path is not present, there is no native
- the plugin sub-application is identified, it returns to the parent application.
- returning the native plug-in sub-application corresponding to the native plug-in sub-application identifier includes: the number of native plug-in sub-application IDs existing before the first third-party sub-application identifier in the jump path is more than At one time, obtain the native plug-in sub-application identifier adjacent to the first third-party sub-application identifier and located before the first third-party sub-application identifier; determine the native plug-in corresponding to the obtained native plug-in sub-application identifier The native plug-in sub-application page that is displayed when the sub-application jumps; displays the determined native plug-in sub-application page.
- the page data corresponding to the sub-application identifier is passed to the sub-application corresponding to the sub-application identifier and run by the parent application, including: switching to triggering the sub-application jump The parent application page; triggers the page data corresponding to the child application identifier through the parent application page; and passes the page data to the child application corresponding to the child application identifier and run by the parent application.
- the computer readable instructions cause the processor to execute, after obtaining the corresponding sub-application identifier of the sub-application to be jumped through the sub-application, and further performing the step of: acquiring the parent application page switched to The corresponding parent application page identifier, and a jump path for recording the sub-application jump relationship; when the obtained sub-application identifier exists in the jump path, the jump path is obtained with the obtained sub-application Identifying the parent application page identifier deletion that is adjacent and located after the obtained sub-application ID; adding the obtained parent application page identifier to the end of the jump path; moving the sub-application identifier obtained in the jump path to After the parent application page ID is added.
- the parent application is run on the operating system, and the child application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- a computer apparatus comprising a memory and a processor, the memory storing computer readable instructions that, when executed by the processor, cause the processor to execute The following steps: display the sub-application page of the sub-application run by the parent application; through the sub-application, obtain the corresponding sub-application ID of the sub-application to be jumped; the page corresponding to the sub-application identifier The data is passed to the sub-application corresponding to the sub-application identifier and run by the parent application; and the sub-application corresponding to the sub-application identifier generates an overlay on the displayed sub-application page according to the page data.
- the sub-application page that is displayed.
- the computer readable instructions cause the processor to execute, after obtaining the corresponding sub-application identifier of the sub-application to be jumped through the sub-application, and further performing the following steps: acquiring the sub-application hop for recording The jump path of the transit relationship; when the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier is moved to the end of the jump path; when the obtained sub-application identifier does not exist in the jump path In the middle, add the obtained sub-application ID to the end of the jump path.
- the computer readable instructions further cause the processor to: obtain a return instruction by the sub-application to which the currently displayed sub-application page belongs; and determine the currently displayed sub-application page in response to the return instruction Corresponding sub-application identifier; in the jump path, searching for a sub-application identifier adjacent to the determined sub-application identifier and located before the determined sub-application identifier; returning the corresponding sub-application identifier corresponding to the search Sub-application page.
- returning the sub-application page corresponding to the found sub-application identifier including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-application ID when the jump occurs; when the sub-application corresponding to the found sub-application ID has finished running, the returned sub-application is returned.
- the default sub-application page for the application ID including: when the sub-application corresponding to the found sub-application identifier is run by the parent application in the background state, then returning The sub-application page displayed by the sub-application corresponding to the found sub-
- the sub-application includes a native plug-in sub-application.
- the obtained sub-application identifier exists in the jump path, the obtained sub-application identifier is moved to the end of the jump path, and includes: when the obtained sub-application identifier exists in the jump path, determining the jump a continuous native plug-in sub-application ID in the transfer path that is adjacent to the obtained sub-application ID and located after the obtained sub-application ID; moves the obtained sub-application ID to the end of the jump path, and jumps The continuous native plug-in sub-application ID is removed from the transfer path.
- the sub-application also includes a third party sub-application.
- the computer readable instructions further cause the processor to: detect a close instruction by a sub-application to which the currently displayed sub-application page belongs; when the close instruction is detected, and the first third-party sub-application identifier in the jump path
- the native plug-in application identifier is present, the native plug-in sub-application corresponding to the native plug-in sub-application identifier is returned; when the close command is detected and the first third-party sub-application identifier in the jump path is not present, there is no native
- the plugin sub-application is identified, it returns to the parent application.
- returning the native plug-in sub-application corresponding to the native plug-in sub-application identifier includes: the number of native plug-in sub-application IDs existing before the first third-party sub-application identifier in the jump path is more than At one time, obtain the native plug-in sub-application identifier adjacent to the first third-party sub-application identifier and located before the first third-party sub-application identifier; determine the native plug-in corresponding to the obtained native plug-in sub-application identifier The native plug-in sub-application page that is displayed when the sub-application jumps; displays the determined native plug-in sub-application page.
- the page data corresponding to the sub-application identifier is passed to the sub-application corresponding to the sub-application identifier and run by the parent application, including: switching to triggering the sub-application jump The parent application page; triggers the page data corresponding to the child application identifier through the parent application page; and passes the page data to the child application corresponding to the child application identifier and run by the parent application.
- the computer readable instructions cause the processor to execute, after obtaining the corresponding sub-application identifier of the sub-application to be jumped through the sub-application, and further performing the step of: acquiring the parent application page switched to The corresponding parent application page identifier, and a jump path for recording the sub-application jump relationship; when the obtained sub-application identifier exists in the jump path, the jump path is obtained with the obtained sub-application Identifying the parent application page identifier deletion that is adjacent and located after the obtained sub-application ID; adding the obtained parent application page identifier to the end of the jump path; moving the sub-application identifier obtained in the jump path to After the parent application page ID is added.
- the parent application is run on the operating system, and the child application can be run by the parent application to display the sub-application page belonging to the sub-application.
- the parent application only needs to obtain the corresponding sub-application identifier of the sub-application to be jumped to by the sub-application, and the page data corresponding to the sub-application identifier can be Passing to the sub-application corresponding to the sub-application identifier and running by the parent application, and then sub-application corresponding to the sub-application identifier, the sub-application can be generated according to the page data.
- the sub-application page displayed on the page automatically implements the jump of the sub-application. It avoids the time consuming to exit the currently used application and then launch the application that is intended to jump to, which improves the application efficiency.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Description
Claims (19)
- 一种应用程序处理方法,应用于终端,所述方法包括:显示由母应用程序所运行的第一子应用程序的第一子应用程序页面;通过所述第一子应用程序,获取待跳转至的第二子应用程序相应的第二子应用程序标识,其中,当所述第一子应用程序跳转至所述第二子应用程序时,母应用程序运行所述第二子应用程序;将所述第二子应用程序标识所对应的页面数据,传递至所述第二子应用程序;根据所述页面数据,生成覆盖于所述第一子应用程序页面上的第二子应用程序页面,并显示所述第二子应用程序页面。
- 根据权利要求1所述的方法,其中,所述通过所述第一子应用程序,获取待跳转至的第二子应用程序相应的第二子应用程序标识之后,所述方法还包括:获取用于记录子应用程序跳转关系的跳转路径;当所述第二子应用程序标识存在于所述跳转路径中时,将所述第二子应用程序标识移动至所述跳转路径的末尾;当所述第二子应用程序标识不存在于所述跳转路径中时,将所述第二子应用程序标识添加至所述跳转路径的末尾。
- 根据权利要求2所述的方法,其中,所述方法还包括:通过所述第二子应用程序,获取返回指令;响应于所述返回指令,确定所述第二子应用程序标识;在所述跳转路径中,查找与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之前的第三子应用程序标识;返回所述第三子应用程序标识所对应的第三子应用程序页面。
- 根据权利要求3所述的方法,其中,所述返回所述第三子应用程序标识所对应的第三子应用程序页面,包括:当所述第三子应用程序标识对应的第三子应用程序,由所述母应用程序以后台状态运行时,则返回所述第三子应用程序在发生跳转时,所对应的所述第三子应用程序页面;当所述第三子应用程序标识对应的第三子应用程序已结束运行时,则返回所述第三子应用程序标识所对应的默认子应用程序页面。
- 根据权利要求2所述的方法,其中,所述第二子应用程序包括原生插件子应用程序;所述当所述第二子应用程序标识存在于所述跳转路径中时,将所述第二子应用程序标识移动至所述跳转路径的末尾,包括:当所述第二子应用程序标识存在于所述跳转路径中时,则确定所述跳转路径中与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之后的连续的原生插件子应用程序标识;将所述第二子应用程序标识移动至所述跳转路径的末尾,并在所述跳转路径中删除所述连续的原生插件子应用程序标识。
- 根据权利要求2所述的方法,其中,所述第二子应用程序为原生插件子应用程序或第三方子应用程序;所述方法还包括:通过所述第二子应用程序,检测关闭指令;当检测到所述关闭指令、且所述跳转路径中首个第三方子应用程序标识之前存在第一原生插件子应用程序标识时,则返回所述第一原生插件子应用程序标识所对应的第一原生插件子应用程序;当检测到所述关闭指令、且所述跳转路径中首个第三方子应用程序 标识之前不存在所述第一原生插件子应用程序标识时,则返回所述母应用程序。
- 根据权利要求6所述的方法,其中,所述返回所述第一原生插件子应用程序标识所对应的第一原生插件子应用程序,包括:当所述跳转路径中首个第三方子应用程序标识之前存在的所述第一原生插件子应用程序标识的数量多于一个时,则获取第二原生插件子应用程序标识,其中,所述第二原生插件子应用程序标识与所述首个第三方子应用程序标识相邻、且位于所述首个第三方子应用程序标识之前;确定第二原生插件子应用程序页面;其中,所述第二原生插件子应用程序页面为所述第二原生插件子应用程序标识所对应的第二原生插件子应用程序在跳转时,所对应的页面;显示所述第二原生插件子应用程序页面。
- 根据权利要求1所述的方法,其中,所述将所述第二子应用程序标识所对应的页面数据,传递至所述第二子应用程序,包括:切换至用于触发子应用程序跳转的母应用程序页面,其中,所述母应用程序页面为所述母应用程序显示的页面;通过所述母应用程序页面,触发获取所述第二子应用程序标识对应的页面数据;将所述页面数据,传递至与所述第二子应用程序。
- 根据权利要求1所述的方法,其中,所述通过所述第一子应用程序,获取待跳转至的第二子应用程序相应的第二子应用程序标识之后,所述方法还包括:获取切换至的第一母应用程序页面相应的第一母应用程序页面标识,及用于记录子应用程序跳转关系的跳转路径;当获取的所述第二子应用程序标识存在于所述跳转路径中时,则将所述跳转路径中与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之后的第二母应用程序页面标识删除;将所述第一母应用程序页面标识添加至所述跳转路径的末尾;将所述第二子应用程序标识移动至所述第一母应用程序页面标识之后。
- 一种应用程序处理装置,包括处理器和存储器,所述存储器中存储有计算机可读指令,所述指令可以使所述处理器:显示由母应用程序所运行的第一子应用程序的第一子应用程序页面;通过所述第一子应用程序获取待跳转至的第二子应用程序相应的第二子应用程序标识,其中,当所述第一子应用程序跳转至所述第二子应用程序时,母应用程序运行所述第二子应用程序;将所述第二子应用程序标识所对应的页面数据,传递至与所述第二子应用程序;根据所述页面数据,生成覆盖于所述第一子应用程序页面上的第二子应用程序页面,并显示所述第二子应用程序页面。
- 根据权利要求10所述的装置,其中,所述计算机可读指令可以使所述处理器:获取用于记录子应用程序跳转关系的跳转路径;当所述第二子应用程序标识存在于所述跳转路径中时,将所述第二子应用程序标识移动至所述跳转路径的末尾;当所述第二子应用程序标识不存在于所述跳转路径中时,将所述第二子应用程序标识添加至所述跳转路径的末尾。
- 根据权利要求11所述的装置,其中,所述计算机可读指令可以使所述处理器:通过所述第二子应用程序,获取返回指令;响应于所述返回指令,确定所述第二子应用程序标识;在所述跳转路径中,查找与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之前的第三子应用程序标识;返回所述第三子应用程序标识所对应的第三子应用程序页面。
- 根据权利要求12所述的装置,其中,所述计算机可读指令可以使所述处理器:当所述第三子应用程序标识对应的第三子应用程序,由所述母应用程序以后台状态运行时,则返回所述第三子应用程序在发生跳转时,所对应的所述第三子应用程序页面;当所述第三子应用程序标识对应的第三子应用程序已结束运行时,则返回所述第三子应用程序标识所对应的默认子应用程序页面。
- 根据权利要求11所述的装置,其中,所述子应用程序包括原生插件子应用程序;所述计算机可读指令可以使所述处理器:当所述第二子应用程序标识存在于所述跳转路径中时,则确定所述跳转路径中与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之后的连续的原生插件子应用程序标识;将所述第二子应用程序标识移动至所述跳转路径的末尾,并在所述跳转路径中删除所述连续的原生插件子应用程序标识。
- 根据权利要求11所述的装置,其中,所述子应用程序为原生插件子应用程序或第三方子应用程序;所述计算机可读指令可以使所述处理器:通过所述第二子应用程序,检测关闭指令;当检测到所述关闭指令、且所述跳转路径中首个第三方子应用程序标识之前存在第一原生插件子应用程序标识时,则返回所述第一原生插件子应用程序标识所对应的第一原生插件子应用程序;当检测到所述关闭指令、且所述跳转路径中首个第三方子应用程序标识之前不存在所述第一原生插件子应用程序标识时,则返回所述母应用程序。
- 根据权利要求15所述的装置,其中,所述计算机可读指令可以使所述处理器:当所述跳转路径中首个第三方子应用程序标识之前存在的所述第一原生插件子应用程序标识的数量多于一个时,则获取第二原生插件子应用程序标识,其中,所述第二原生插件子应用程序标识与所述首个第三方子应用程序标识相邻、且位于所述首个第三方子应用程序标识之前;确定第二原生插件子应用程序页面;其中,所述第二原生插件子应用程序页面为所述第二原生插件子应用程序标识所对应的第二原生插件子应用程序在跳转时,所对应的页面;显示所述第二原生插件子应用程序页面。
- 根据权利要求10所述的装置,其中,所述计算机可读指令可以使所述处理器:切换至用于触发子应用程序跳转的母应用程序页面,其中,所述母应用程序页面为所述母应用程序显示的页面;通过所述母应用程序页面,触发获取所述第二子应用程序标识对应的页面数据;将所述页面数据,传递至与所述第二子应用程序。
- 根据权利要求10所述的装置,其中,所述计算机可读指令可以使所述处理器:获取切换至的第一母应用程序页面相应的第一母应用程序页面标识,及用于记录子应用程序跳转关系的跳转路径;当获取的所述第二子应用程序标识存在于所述跳转路径中时,则将 所述跳转路径中与所述第二子应用程序标识相邻、且位于所述第二子应用程序标识之后的第二母应用程序页面标识删除;将所述第一母应用程序页面标识添加至所述跳转路径的末尾;将所述第二子应用程序标识移动至所述第一母应用程序页面标识之后。
- 一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机可读指令,所述计算机可读指令被处理器执行时,使得所述处理器执行如权利要求1至9中任一项所述的方法的步骤。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019563361A JP6915091B2 (ja) | 2017-06-30 | 2018-05-04 | アプリケーション処理方法、装置および記憶媒体 |
EP18824354.7A EP3647949B1 (en) | 2017-06-30 | 2018-05-04 | Application program processing method, device and storage medium |
KR1020197027548A KR102255137B1 (ko) | 2017-06-30 | 2018-05-04 | 애플리케이션 프로그램 처리 방법, 장치 및 저장 매체 |
US16/532,089 US11132222B2 (en) | 2017-06-30 | 2019-08-05 | Application processing method and apparatus for jumping between child applications and storage medium |
US17/391,918 US11681548B2 (en) | 2017-06-30 | 2021-08-02 | Application processing method and apparatus for jumping between child applications and storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710524874.0A CN107357644B (zh) | 2017-06-30 | 2017-06-30 | 应用程序处理方法、装置、存储介质和计算机设备 |
CN201710524874.0 | 2017-06-30 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/532,089 Continuation US11132222B2 (en) | 2017-06-30 | 2019-08-05 | Application processing method and apparatus for jumping between child applications and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019001138A1 true WO2019001138A1 (zh) | 2019-01-03 |
Family
ID=60272536
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/085527 WO2019001138A1 (zh) | 2017-06-30 | 2018-05-04 | 应用程序处理方法、装置和存储介质 |
Country Status (6)
Country | Link |
---|---|
US (2) | US11132222B2 (zh) |
EP (1) | EP3647949B1 (zh) |
JP (1) | JP6915091B2 (zh) |
KR (1) | KR102255137B1 (zh) |
CN (1) | CN107357644B (zh) |
WO (1) | WO2019001138A1 (zh) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107357644B (zh) | 2017-06-30 | 2018-10-16 | 腾讯科技(深圳)有限公司 | 应用程序处理方法、装置、存储介质和计算机设备 |
CN108196930B (zh) * | 2018-01-18 | 2020-04-03 | 腾讯科技(深圳)有限公司 | 应用程序处理方法、装置、存储介质和计算机设备 |
CN108664304A (zh) * | 2018-05-03 | 2018-10-16 | 广州腾讯科技有限公司 | 应用程序处理方法、装置、存储介质和计算机设备 |
CN111294368A (zh) * | 2018-12-06 | 2020-06-16 | 上海博泰悦臻电子设备制造有限公司 | 云服务器、智能客户端及其车主服务方法 |
CN111475310B (zh) * | 2019-01-24 | 2023-03-21 | 腾讯科技(深圳)有限公司 | 消息分享方法、装置和用户数据获取方法、装置 |
CN110308958B (zh) * | 2019-05-08 | 2023-01-31 | 北京字节跳动网络技术有限公司 | 组件跳转方法、装置、电子设备和存储介质 |
CN110515610B (zh) * | 2019-06-27 | 2021-01-29 | 华为技术有限公司 | 页面绘制的控制方法、装置及设备 |
CN112394861B (zh) * | 2019-08-15 | 2023-08-29 | 腾讯科技(深圳)有限公司 | 页面跳转方法、装置、存储介质及电子装置 |
CN112734453B (zh) * | 2019-10-28 | 2024-02-02 | 腾讯科技(深圳)有限公司 | 电子券领取方法、发放方法、装置、设备和存储介质 |
CN111324397A (zh) * | 2020-03-26 | 2020-06-23 | 百度在线网络技术(北京)有限公司 | 小程序切换方法、装置、框架、设备和可读介质 |
CN113297518B (zh) * | 2020-07-24 | 2022-09-23 | 阿里巴巴集团控股有限公司 | 页面切换方法、装置、电子设备及可读存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140283012A1 (en) * | 2013-03-13 | 2014-09-18 | Research In Motion Limited | Method of locking an application on a computing device |
CN106775420A (zh) * | 2016-12-30 | 2017-05-31 | 华为机器有限公司 | 一种应用切换的方法、装置和图形用户界面 |
CN106802803A (zh) * | 2017-01-06 | 2017-06-06 | 腾讯科技(深圳)有限公司 | 应用数据处理的方法和装置 |
CN107357644A (zh) * | 2017-06-30 | 2017-11-17 | 腾讯科技(深圳)有限公司 | 应用程序处理方法、装置、存储介质和计算机设备 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU1940199A (en) * | 1997-12-24 | 1999-07-19 | America Online, Inc. | Asynchronous data protocol |
US8028023B2 (en) * | 2002-09-17 | 2011-09-27 | At&T Intellecutal Property I, L.P. | Extending functionality of instant messaging (IM) systems |
US7533121B2 (en) * | 2006-10-17 | 2009-05-12 | Microsoft Corporation | Executing pages of a guided process application in parallel |
JP5609269B2 (ja) * | 2010-05-27 | 2014-10-22 | 株式会社リコー | 画像処理装置、表示装置、画面制御システム、画面制御方法、画面制御プログラム、及びそのプログラムを記録した記録媒体 |
US9129259B2 (en) * | 2011-12-06 | 2015-09-08 | Facebook, Inc. | Pages: hub structure for related pages |
CN103955466B (zh) * | 2012-03-06 | 2017-11-14 | 北京奇虎科技有限公司 | 一种在浏览器中展示文档的方法及装置 |
US10282196B2 (en) * | 2012-04-06 | 2019-05-07 | Oracle International Corporation | System and method for moving enterprise software application components across environments |
CN103455234A (zh) * | 2012-06-01 | 2013-12-18 | 腾讯科技(深圳)有限公司 | 显示应用程序界面的方法及装置 |
KR20140040379A (ko) * | 2012-09-26 | 2014-04-03 | 삼성전자주식회사 | 휴대단말기의 어플리케이션 처리 장치 및 방법 |
US9880861B2 (en) * | 2013-06-05 | 2018-01-30 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for page view switching |
CN104424221B (zh) * | 2013-08-23 | 2019-02-05 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
US9244593B2 (en) * | 2013-10-28 | 2016-01-26 | Beijing Lenovo Software Ltd. | Information processing methods and electronic devices |
AU2015250982A1 (en) * | 2014-04-24 | 2016-11-03 | Barclays Bank Plc | Instant messaging systems and methods |
US20170269961A1 (en) | 2014-08-20 | 2017-09-21 | Huawei Technologies Co., Ltd. | Application program switching method and apparatus, and electronic terminal |
CN105573639B (zh) * | 2014-10-17 | 2018-11-20 | 国际商业机器公司 | 用于触发应用的显示的方法和系统 |
CN105160027B (zh) * | 2015-09-30 | 2019-03-12 | 百度在线网络技术(北京)有限公司 | 广告数据处理方法及装置 |
CN106020634B (zh) * | 2016-05-04 | 2019-04-16 | 北京小米移动软件有限公司 | 截屏方法及装置 |
CN106502736B (zh) * | 2016-10-18 | 2018-04-06 | 腾讯科技(深圳)有限公司 | 应用程序处理方法和装置 |
CN106569900B (zh) * | 2016-10-28 | 2019-08-23 | 腾讯科技(深圳)有限公司 | 应用程序处理方法和装置 |
CN106598655B (zh) * | 2016-12-05 | 2020-02-14 | 腾讯科技(深圳)有限公司 | 应用程序页面处理方法和装置 |
-
2017
- 2017-06-30 CN CN201710524874.0A patent/CN107357644B/zh active Active
-
2018
- 2018-05-04 EP EP18824354.7A patent/EP3647949B1/en active Active
- 2018-05-04 WO PCT/CN2018/085527 patent/WO2019001138A1/zh active Application Filing
- 2018-05-04 JP JP2019563361A patent/JP6915091B2/ja active Active
- 2018-05-04 KR KR1020197027548A patent/KR102255137B1/ko active IP Right Grant
-
2019
- 2019-08-05 US US16/532,089 patent/US11132222B2/en active Active
-
2021
- 2021-08-02 US US17/391,918 patent/US11681548B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140283012A1 (en) * | 2013-03-13 | 2014-09-18 | Research In Motion Limited | Method of locking an application on a computing device |
CN106775420A (zh) * | 2016-12-30 | 2017-05-31 | 华为机器有限公司 | 一种应用切换的方法、装置和图形用户界面 |
CN106802803A (zh) * | 2017-01-06 | 2017-06-06 | 腾讯科技(深圳)有限公司 | 应用数据处理的方法和装置 |
CN107357644A (zh) * | 2017-06-30 | 2017-11-17 | 腾讯科技(深圳)有限公司 | 应用程序处理方法、装置、存储介质和计算机设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3647949A4 * |
Also Published As
Publication number | Publication date |
---|---|
KR20190116479A (ko) | 2019-10-14 |
KR102255137B1 (ko) | 2021-05-21 |
EP3647949A1 (en) | 2020-05-06 |
EP3647949C0 (en) | 2024-04-17 |
CN107357644B (zh) | 2018-10-16 |
US20190361737A1 (en) | 2019-11-28 |
US11681548B2 (en) | 2023-06-20 |
JP2020525881A (ja) | 2020-08-27 |
CN107357644A (zh) | 2017-11-17 |
US11132222B2 (en) | 2021-09-28 |
EP3647949B1 (en) | 2024-04-17 |
US20210365287A1 (en) | 2021-11-25 |
JP6915091B2 (ja) | 2021-08-04 |
EP3647949A4 (en) | 2021-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019001138A1 (zh) | 应用程序处理方法、装置和存储介质 | |
US11606414B2 (en) | System and method for transferring states between electronic devices | |
US11868785B2 (en) | Application program page processing method and device | |
US10831567B2 (en) | Application processing method and apparatus | |
WO2019000933A1 (zh) | 信息显示方法、装置及计算机可读存储介质 | |
US10678413B2 (en) | Application for auto deletion of images | |
CN109117153A (zh) | 应用程序的处理方法、装置、终端和存储介质 | |
US9244668B1 (en) | Systems and methods for synchronizing mobile computing platforms | |
US11876814B2 (en) | Proxy services for the secure upload of file system tree structures | |
US11809550B2 (en) | Electronic device and control method therefor | |
CN118312273A (zh) | 一种依赖库共享方法、装置和可读存储介质 | |
CN115062012A (zh) | 数据处理方法、装置、存储介质和电子设备 | |
KR20200006841A (ko) | 어플리케이션의 포그라운드 서비스 실행시 보안을 제공하기 위한 통신 단말 및 방법 | |
AU2017202565A1 (en) | System for transferring states between electronic devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18824354 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20197027548 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2019563361 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2018824354 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2018824354 Country of ref document: EP Effective date: 20200130 |