CN108572866B - Application program management method, application program management device and mobile terminal - Google Patents
Application program management method, application program management device and mobile terminal Download PDFInfo
- Publication number
- CN108572866B CN108572866B CN201810366928.XA CN201810366928A CN108572866B CN 108572866 B CN108572866 B CN 108572866B CN 201810366928 A CN201810366928 A CN 201810366928A CN 108572866 B CN108572866 B CN 108572866B
- Authority
- CN
- China
- Prior art keywords
- application program
- event
- jump
- jumped
- started
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
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
- 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
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
Abstract
The application discloses an application program management method, an application program management device, a mobile terminal and a computer readable storage medium, wherein the application program management method comprises the following steps: acquiring a monitoring event of an application program in the running process of the application program; when the obtained monitoring event is an event to be jumped to an application program, detecting whether a preset jump-preventing function is started by a mobile terminal where the application program is located; and if the anti-jump function is started, terminating the event to be jumped of the application program. According to the application program starting method and device, the situation that the user starts the application program which is not to be started due to misoperation in the process of running the application program can be avoided, and user experience is improved.
Description
Technical Field
The present application belongs to the technical field of mobile terminals, and in particular, to an application management method, an application management apparatus, a mobile terminal, and a computer-readable storage medium.
Background
Currently, most application programs are used, and advertisement pages or controls of other application programs are built in for the purposes of profit, bundling and the like. If the user does not carefully click on the advertisement pages or the controls of the other applications in the process of using the third-party application, the user starts and jumps to the corresponding applications, and actually, in most application scenes, the user does not want to jump to the other applications, which brings trouble to the normal use of the applications for the user.
Disclosure of Invention
In view of this, the present application provides an application management method, an application management apparatus, a mobile terminal, and a computer-readable storage medium, which can prevent a user from starting an application that is not to be started due to a misoperation in a process of running the application, and improve user experience.
A first aspect of the present application provides an application management method, where the application management method includes:
acquiring a monitoring event of an application program in the running process of the application program;
when the obtained monitoring event is an event to be jumped to an application program, detecting whether a preset jump-preventing function is started by a mobile terminal where the application program is located;
and if the anti-jump function is started, terminating the event to be jumped of the application program.
A second aspect of the present application provides an application management apparatus, including:
the event acquisition unit is used for acquiring a monitoring event of the application program in the running process of the application program;
the function detection unit is used for detecting whether a preset anti-jump function is started by a mobile terminal where the application program is located or not when the obtained monitoring event is an event to be jumped to the application program;
and the event control unit is used for terminating the event to be jumped of the application program if the anti-jump function is started.
A third aspect of the present application provides a mobile terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to the first aspect when executing the computer program.
A fourth aspect of the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of the first aspect as described above.
A fifth aspect of the application provides a computer program product comprising a computer program which, when executed by one or more processors, performs the steps of the method as described in the first aspect above.
According to the method and the device, firstly, in the running process of the application program, the monitoring event of the application program is obtained, when the obtained monitoring event is the event to be skipped of the application program, whether the preset anti-skipping function is started on the mobile terminal where the application program is located is detected, and if the anti-skipping function is started, the event to be skipped of the application program is terminated. According to the technical scheme, the jump-preventing function is provided for avoiding misoperation of the user, the jump operation between the application programs is ignored when the jump-preventing function is in the starting state, the situation that the user starts the application program which is not to be started due to misoperation in the process of running the application program can be avoided, and the user experience can be effectively improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic flowchart of an implementation of an application management method according to an embodiment of the present application;
FIG. 2 is a schematic flowchart of another implementation of an application management method according to an embodiment of the present application;
fig. 3 is a block diagram of an application management apparatus according to an embodiment of the present application;
fig. 4 is a schematic diagram of a mobile terminal provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution of the present application, the following description will be given by way of specific examples.
Example one
Referring to fig. 1, a method for managing an application program provided in an embodiment of the present application is described below, where the method for managing an application program in an embodiment of the present application includes:
in step 101, in the running process of an application program, acquiring a monitoring event of the application program;
in the embodiment of the present application, when an application program runs in the foreground of the mobile terminal, that is, when the mobile terminal runs and displays an interface of the application program, the application program is monitored to obtain a monitoring event of the application program.
In step 102, when the obtained monitoring event is an event to be jumped to an application program, detecting whether a preset jump-preventing function is started by a mobile terminal where the application program is located;
in this embodiment of the application, the event to be skipped to the application may be a skipped event that occurs after the user clicks an advertisement or a control of another application built in the application, or a skipped event that occurs after the user clicks a sharing button of the application, which is not limited herein. Specifically, because generally, the application program generates the event to be skipped to the application program only after receiving the instruction generated by the user through the touch click, and does not autonomously skip other application programs, in step 101, the monitoring event of the application program may be obtained based on the touch click operation of the user on the application program, that is, the monitoring event may be obtained only when the touch click operation of the user on the application program occurs, so as to avoid that the mobile terminal continuously obtains the monitoring event of the application program and occupies unnecessary system resources. Furthermore, the anti-jump function can be turned on or off by arranging a virtual key on the desktop of the mobile terminal; or, the anti-jump function may be turned on or off by one or a combination of physical keys existing in the mobile terminal; alternatively, a new physical key may be added to the mobile terminal, and the anti-jump function may be turned on or off by the new physical key, which is not limited herein.
In step 103, if the anti-jump function is already enabled, the event to be jumped of the application program is terminated.
In the embodiment of the application, when it is detected that the anti-jump function of the mobile terminal is started, the event to be jumped of the application program is terminated, that is, the subsequent jump operation is not executed, and the mobile terminal still keeps running on the interface of the application program.
Therefore, according to the embodiment of the application, the jump-preventing function is provided for avoiding misoperation of a user, jump operation between application programs is ignored when the jump-preventing function is in an open state, the situation that the user starts the application program which is not to be started due to misoperation in the process of running the application program can be avoided, and user experience can be effectively improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example two
On the basis of the first embodiment, the second embodiment of the present application provides another application management method. Referring to fig. 2, another application management method provided in the second embodiment of the present application is described below, where the application management method in the second embodiment of the present application includes:
in step 201, in the running process of an application program, acquiring a monitoring event of the application program;
in step 202, when the obtained monitoring event is an event to be skipped to an application program, detecting whether a preset anti-skipping function is started by a mobile terminal where the application program is located, if so, executing step 203, otherwise, executing step 204;
in step 203, terminating the event to be jumped of the application program;
in the embodiment of the present application, the steps 201, 202, and 203 are the same as or similar to the steps 101, 102, and 103, and reference may be specifically made to the related descriptions of the steps 101, 102, and 103, which are not repeated herein.
In step 204, a target application program pointed by the event to be skipped of the application program is obtained, and a jump is made to an interface of the target application program.
In this embodiment of the application, if it is detected that the anti-jump function is not turned on, it means that the current mobile terminal allows jumping between different applications, and therefore, at this time, the event to be jumped to the application may be responded to and executed, a target application pointed by the event to be jumped to the application may be obtained, and the target application may be started and jumped to an interface of the target application.
Optionally, after step 204, the method for managing an application program further includes:
and if a return instruction input by the user is received, returning to the interface before the jump from the interface of the target application program.
In the embodiment of the application, although the mobile terminal already provides the anti-jump function, a situation that the user forgets to turn on the anti-jump function may still occur, in which case, when an event to be jumped for the application is monitored, the application still jumps; or after the user actively selects to jump to the target application program, the operation required to be performed on the target application program is already completed, and the interface before the jump needs to be returned again; based on the application scenarios, in order to facilitate the operation of the user, another virtual key may be provided at a preset position, for example, a lower right corner, of the interface of the target application program after the jump, the user inputs a return instruction to the mobile terminal by pressing the virtual key, and the mobile terminal returns to the interface before the jump from the interface of the target application program based on the return instruction. Further, since the user may not perform any operation on the target application program in the case of a false jump, after step 204, the application program management method may further include: and if the target application program does not receive any operation input by the user within the preset time, returning to the interface before jumping from the interface of the target application program. That is, if the user does not perform further operation on the target application program within a period of time after the jump, the jump operation is considered to be a faulty operation, and the interface before the jump needs to be returned.
Optionally, after returning to the interface before the jump from the interface of the target application, whether the returning operation is performed based on a return instruction or based on any operation that the target application does not receive the user input, the target application further includes:
and clearing the target application program in the background of the mobile terminal.
In the embodiment of the present application, now that the page before the jump has been returned, it can be considered that the user has no need for the target application. After returning to the page before the jump, the target application program is usually kept running in the background of the mobile terminal, which may cause the power, network traffic and system resources of the mobile terminal to be occupied meaninglessly. Therefore, in consideration of energy saving, after returning to the interface before the jump, the target application needs to be cleared in the background of the mobile terminal, i.e. the process related to the target application in the mobile terminal is eliminated.
Optionally, after the anti-jump function is started, the application programs in the mobile terminal are controlled in a 'one-switch' manner, that is, all the application programs cannot realize jump operation. In some cases, some applications commonly used by the user, the user wants to retain the jump operation, and therefore, after the step 102 and the step 202, the method for managing the application further includes:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset first white list or not;
the steps 103 and 203 are embodied as follows:
and if the anti-jump function is started and the target application program is not in the first white list, terminating the event to be jumped of the application program.
In this embodiment of the present application, the first white list provides a possibility of flexibly performing a jump operation for the application management method. If the target application program is not in the first white list, when the anti-jump function is started, the event to be jumped of the application program is normally terminated; and if the target application program is in the first white list, the operation of skipping the current application program to the target application program can be still realized even if the jump-preventing function is started. For example, as social software which is popular at present, a user often shares information of other application programs on the WeChat to own WeChat friends, for example, sharing interesting blog in a commodity or a microblog of a Taobao center to the WeChat friends, that is, other application programs often jump to the WeChat under the instruction of the user to implement information sharing operation of the user. Therefore, in the application, by setting the first white list, the application (e.g., wechat) that the user frequently realizes the jump operation through other applications is stored in the first white list, so that the application (e.g., wechat) in the first white list is not limited by the jump prevention function, and other applications such as microblog or panning can still realize the jump operation to the wechat; that is, as long as the target application program pointed by the application program to-be-jumped event is in the first white list, the mobile terminal will continue to execute the application program to-be-jumped event regardless of whether the anti-jump function is turned on.
Optionally, after 102 and 202, the method for managing an application program further includes:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset second white list associated with the application program or not;
the above 103 and 203 are embodied as follows:
and if the anti-jump function is started and the target application program is not in the second white list, terminating the event to be jumped of the application program.
In the embodiment of the present application, the concept of the first white list has been proposed, which is directed to applications that a mobile terminal, like WeChat, may frequently jump to. However, there are some applications where the user typically jumps from only certain specific applications, for example, the user typically only wants to jump from the nam treasure to the pay treasure for account security, and ignores the operation of other applications jumping to the pay treasure. Therefore, in the embodiment of the present application, a concept of a second white list is further proposed, where the second white list is associated with the application programs, and it is understood that, for any application program a, if there are B, C application programs in the associated second white list, when the anti-jump function is turned on, the mobile terminal allows an application jump operation from a to B or from a to C, but does not allow other application programs to jump to B or C. That is, when the anti-jump function is turned on, any application program in the mobile terminal is allowed to jump to the application program in the first white list, and the application program associated with the second white list is allowed to jump to the application program in the second white list. Accordingly, each application may have a second whitelist associated with itself, i.e., without limitation to the number of second whitelists.
Optionally, after step 103 or 203, the application management method further includes:
and outputting a reminding message to prompt the user that the event to be jumped of the application program is terminated.
In the embodiment of the present application, the alert message may be output in one or a combination of voice, text, ring, vibration, etc. to prompt the user that the application to-be-skipped event has been terminated.
Therefore, according to the embodiment of the application, the jump-preventing function is provided for avoiding the misoperation of the user, the jump operation between the application programs is ignored when the jump-preventing function is in the starting state, the situation that the user starts the application program which is not to be started due to the misoperation in the process of running the application program can be avoided, and the user experience can be effectively improved; under the state that the jump-preventing function is not started, jumping to the interface of the corresponding application program, and returning to the interface before jumping quickly; meanwhile, a first white list and a second white list are provided, so that the mobile terminal is helped to realize the jump-preventing function more flexibly.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
EXAMPLE III
A third embodiment of the present application provides an application management apparatus, which may be integrated in a mobile terminal, as shown in fig. 3, an application management apparatus 300 in the third embodiment of the present application includes:
an event acquiring unit 301, configured to acquire a monitoring event of an application program in an operation process of the application program;
a function detecting unit 302, configured to detect whether a preset anti-jump function is started by a mobile terminal where the application program is located when the obtained monitoring event is an event to be jumped to the application program;
an event control unit 303, configured to terminate the event to be skipped of the application program if the anti-skipping function is already started.
Optionally, the event control unit 303 is further configured to, if the anti-jump function is not turned on, obtain a target application program pointed by an event to be jumped to by the application program, and jump to an interface of the target application program.
Optionally, the application management apparatus 300 further includes:
and the interface returning unit is used for returning to the interface before jumping from the interface of the target application program when receiving a returning instruction input by the user.
Optionally, the application management apparatus 300 further includes:
and the application clearing unit is used for clearing the target application program in the background of the mobile terminal.
Optionally, the application management apparatus 300 further includes:
the first white list detection unit is used for detecting whether a target application program pointed by the event to be jumped of the application program is in a preset first white list or not;
the event control unit 303 is specifically configured to terminate the event to be skipped for the application program if the anti-skip function is turned on and the target application program is not in the first white list.
Optionally, the application management apparatus 300 further includes:
the second white list detection unit is used for detecting whether the target application program pointed by the event to be jumped of the application program is in a preset second white list associated with the application program or not;
the event control unit 303 is specifically configured to terminate the event to be skipped for the application program if the anti-skipping function is turned on and the target application program is not in the second white list.
Optionally, the application management apparatus 300 further includes:
and the reminding unit is used for outputting a reminding message to remind a user that the event to be jumped of the application program is terminated.
Therefore, according to the embodiment of the application, the application management device provides the jump prevention function to avoid the misoperation of the user, and the jump operation between the applications is ignored when the jump prevention function is in the starting state, so that the situation that the user starts the application which is not to be started due to the misoperation in the process of running the application can be avoided, and the user experience can be effectively improved; under the state that the jump-preventing function is not started, jumping to the interface of the corresponding application program, and returning to the interface before jumping quickly; meanwhile, a first white list and a second white list are provided, so that the mobile terminal is helped to realize the jump-preventing function more flexibly.
Example four
In a fourth embodiment of the present application, referring to fig. 4, a mobile terminal includes: a memory 401, one or more processors 402 (only one shown in fig. 4), and computer programs stored on the memory 401 and executable on the processors. Wherein: the memory 401 is used for storing software programs and modules, and the processor 402 executes various functional applications and data processing by operating the software programs and units stored in the memory 401, so as to acquire resources corresponding to the preset events. Specifically, the processor 402, by running the above-mentioned computer program stored in the memory 401, implements the steps of:
acquiring a monitoring event of an application program in the running process of the application program;
when the obtained monitoring event is an event to be jumped to an application program, detecting whether a preset jump-preventing function is started by a mobile terminal where the application program is located;
and if the anti-jump function is started, terminating the event to be jumped of the application program.
Assuming that the above is the first possible implementation manner, in a second possible implementation manner provided on the basis of the first possible implementation manner, after the above-mentioned detecting whether the mobile terminal where the application program is located starts a preset anti-jump function, the processor 402 further implements the following steps when running the computer program stored in the memory 401:
and if the anti-jump function is not started, acquiring a target application program pointed by the event to be jumped of the application program, and jumping to an interface of the target application program.
In a third possible implementation manner provided on the basis of the second possible implementation manner, after jumping to the interface of the target application program, the processor 402 further implements the following steps when running the computer program stored in the memory 401:
and if a return instruction input by the user is received, returning to the interface before the jump from the interface of the target application program.
In a fourth possible implementation manner provided as the basis of the third possible implementation manner, after the interface of the target application program returns to the interface before the jump from the interface of the target application program when the return instruction input by the user is received, the processor 402 further implements the following steps when running the computer program stored in the memory 401:
and clearing the target application program in the background of the mobile terminal.
In a fifth possible implementation manner provided on the basis of the first possible implementation manner, the second possible implementation manner, the third possible implementation manner, or the fourth possible implementation manner, after detecting whether a preset anti-jump function is turned on by the mobile terminal where the application is located when the obtained monitored event is an event to be jumped by the application, the processor 402 further implements the following steps by running the computer program stored in the memory 401:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset first white list or not;
if the anti-jump function is started, terminating the event to be jumped of the application program, including:
and if the anti-jump function is started and the target application program is not in the first white list, terminating the event to be jumped of the application program.
In a sixth possible implementation manner provided on the basis of the first possible implementation manner, the second possible implementation manner, the third possible implementation manner, or the fourth possible implementation manner, after detecting whether a preset anti-jump function is turned on by the mobile terminal where the application is located when the obtained monitored event is an event to be jumped by the application, the processor 402 further implements the following steps by running the computer program stored in the memory 401:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset second white list associated with the application program or not;
if the anti-jump function is started, terminating the event to be jumped of the application program, including:
and if the anti-jump function is started and the target application program is not in the second white list, terminating the event to be jumped of the application program.
In a seventh possible implementation manner provided on the basis of the first possible implementation manner, the second possible implementation manner, the third possible implementation manner, or the fourth possible implementation manner, after the application program to-be-jumped event is terminated, the processor 402 further implements the following steps when running the computer program stored in the memory 401:
and outputting a reminding message to prompt the user that the event to be jumped of the application program is terminated.
Further, as shown in fig. 4, the mobile terminal may further include: one or more input devices 403 (only one shown in fig. 4) and one or more output devices 404 (only one shown in fig. 4). The memory 401, processor 402, input device 403, and output device 404 are connected by a bus 405.
It should be understood that in the embodiments of the present Application, the Processor 402 may be a Central Processing Unit (CPU), and the Processor may be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The input device 403 may include a keyboard, a touch pad, a fingerprint sensor (for collecting fingerprint information of a user and direction information of the fingerprint), a microphone, etc., and the output device 404 may include a display, a speaker, etc.
Therefore, according to the embodiment of the application, the mobile terminal provides the jump prevention function to avoid the misoperation of the user, and the jump operation between the application programs is ignored when the jump prevention function is in the starting state, so that the situation that the user starts the application program which is not to be started due to the misoperation in the process of running the application program can be avoided, and the user experience can be effectively improved; under the state that the jump-preventing function is not started, jumping to the interface of the corresponding application program, and returning to the interface before jumping quickly; meanwhile, a first white list and a second white list are provided, so that the mobile terminal is helped to realize the jump-preventing function more flexibly.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of external device software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the above-described modules or units is only one logical functional division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, all or part of the flow in the method of the embodiments described above may be implemented by a computer program, which may be stored in a computer readable storage medium and used by a processor to implement the steps of the embodiments of the methods described above. The computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file or some intermediate form. The computer-readable storage medium may include: any entity or device capable of carrying the above-described computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer readable Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable storage medium may contain other contents which can be appropriately increased or decreased according to the requirements of the legislation and the patent practice in the jurisdiction, for example, in some jurisdictions, the computer readable storage medium does not include an electrical carrier signal and a telecommunication signal according to the legislation and the patent practice.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (9)
1. An application management method, comprising:
acquiring a monitoring event of an application program in the foreground operation process of the application program;
when the obtained monitoring event is an event to be jumped to an application program, detecting whether a preset jump-preventing function is started by a mobile terminal where the application program is located;
if the anti-jump function is started, terminating the event to be jumped of the application program;
when the obtained monitoring event is an event to be skipped for an application program, after detecting whether a preset anti-skipping function is started by the mobile terminal where the application program is located, the method further comprises the following steps:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset first white list or not;
if the anti-jump function is started, terminating the event to be jumped of the application program, including:
if the jump-preventing function is started and the target application program is not in the first white list, terminating the event to be jumped of the application program;
the application program stored in the first white list is not limited by the jump-proof function, and as long as the target application program pointed by the event to be jumped of the application program is in the first white list, other application programs can jump to the interface of the target application program.
2. The method for managing application programs according to claim 1, wherein after detecting whether the mobile terminal where the application program is located starts a preset anti-jump function, the method further comprises:
and if the anti-jump function is not started, acquiring a target application program pointed by the event to be jumped of the application program, and jumping to an interface of the target application program.
3. The application management method of claim 2, further comprising, after jumping to the interface of the target application:
and if a return instruction input by the user is received, returning to the interface before the jump from the interface of the target application program.
4. The method for managing an application program according to claim 3, further comprising, after returning from the interface of the target application program to the interface before the jump if a return instruction input by a user is received, the step of:
and clearing the target application program in the background of the mobile terminal.
5. The application management method according to any one of claims 1 to 4, wherein after detecting whether a preset anti-jump function is started on a mobile terminal where the application is located when the obtained monitoring event is an application to-jump event, the method further comprises:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset second white list associated with the application program or not;
if the anti-jump function is started, terminating the event to be jumped of the application program, including:
and if the jump-preventing function is started and the target application program is not in the second white list, terminating the event to be jumped of the application program.
6. The application management method according to any one of claims 1 to 4, further comprising, after said terminating said application to-jump event:
and outputting a reminding message to prompt the user that the event to be jumped of the application program is terminated.
7. An application management apparatus, comprising:
the event acquisition unit is used for acquiring a monitoring event of the application program in the foreground operation process of the application program;
the function detection unit is used for detecting whether a preset anti-jump function is started by a mobile terminal where the application program is located or not when the obtained monitoring event is an event to be jumped to the application program;
the event control unit is used for terminating the event to be jumped of the application program if the anti-jump function is started;
when the obtained monitoring event is an event to be skipped for an application program, after detecting whether a preset anti-skipping function is started by the mobile terminal where the application program is located, the method further comprises the following steps:
detecting whether a target application program pointed by the event to be jumped of the application program is in a preset first white list or not;
if the anti-jump function is started, terminating the event to be jumped of the application program, including:
if the jump-preventing function is started and the target application program is not in the first white list, terminating the event to be jumped of the application program;
the application program stored in the first white list is not limited by the jump-proof function, and as long as the target application program pointed by the event to be jumped of the application program is in the first white list, other application programs can jump to the interface of the target application program.
8. A mobile terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 6 when executing the computer program.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810366928.XA CN108572866B (en) | 2018-04-23 | 2018-04-23 | Application program management method, application program management device and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810366928.XA CN108572866B (en) | 2018-04-23 | 2018-04-23 | Application program management method, application program management device and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108572866A CN108572866A (en) | 2018-09-25 |
| CN108572866B true CN108572866B (en) | 2021-05-14 |
Family
ID=63574127
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810366928.XA Active CN108572866B (en) | 2018-04-23 | 2018-04-23 | Application program management method, application program management device and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108572866B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109840418B (en) * | 2019-02-19 | 2021-01-01 | Oppo广东移动通信有限公司 | Jump control method and device for application program, storage medium and terminal |
| CN110008011B (en) * | 2019-02-28 | 2021-07-16 | 维沃移动通信有限公司 | Task switching method and terminal equipment |
| CN110471714B (en) * | 2019-08-16 | 2022-07-12 | 北京字节跳动网络技术有限公司 | Method, device, terminal and storage medium for controlling application starting |
| CN112000950A (en) * | 2020-06-30 | 2020-11-27 | 深圳点猫科技有限公司 | Anti-interception program operation and interaction control method and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107370740A (en) * | 2017-07-28 | 2017-11-21 | 北京五八信息技术有限公司 | Redirect hold-up interception method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514075B (en) * | 2012-06-18 | 2016-06-29 | 腾讯科技（深圳）有限公司 | The method and apparatus that monitoring api function is called in the terminal |
| CN103699485B (en) * | 2013-12-20 | 2018-04-10 | 金蝶软件（中国）有限公司 | Application program adjustment method and device |
| CN106528210B (en) * | 2016-10-20 | 2019-09-24 | Oppo广东移动通信有限公司 | A kind of operation method and device of application program |
-
2018
- 2018-04-23 CN CN201810366928.XA patent/CN108572866B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107370740A (en) * | 2017-07-28 | 2017-11-21 | 北京五八信息技术有限公司 | Redirect hold-up interception method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108572866A (en) | 2018-09-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108572866B (en) | Application program management method, application program management device and mobile terminal | |
| US11157864B2 (en) | Method and device for displaying logistics information and computer readable storage medium | |
| RU2635894C2 (en) | Method and device for processing task event | |
| CN106951335B (en) | Process daemon method and mobile terminal | |
| CN107748685B (en) | Application program starting control method and device, terminal equipment and storage medium | |
| CN108777033B (en) | Shared charger treasure leasing method based on shared leasing equipment and terminal equipment thereof | |
| CN107329659B (en) | Permission setting method and device, electronic equipment and storage medium | |
| CN108234744B (en) | Push message management method and mobile terminal | |
| CN105589623A (en) | Notification message checking method, apparatus and terminal | |
| CN104808991A (en) | Terminal processing method | |
| CN111695151A (en) | Application permission setting method and device, electronic equipment and readable storage medium | |
| CN111917628B (en) | Message processing method and device and electronic equipment | |
| CN107770845B (en) | mobile hotspot management method and device, terminal and storage medium | |
| CN110868693A (en) | Application program flow control method, terminal device and storage medium | |
| CN110851057A (en) | Method and device for configuring configuration options of BIOS | |
| CN110708294A (en) | Interactive information issuing and processing method and device, electronic equipment and medium | |
| CN111597009B (en) | Application program display method and device and terminal equipment | |
| CN112445588A (en) | Application task processing method, device and equipment and readable storage medium | |
| CN108650702B (en) | Broadcast information processing method and user terminal | |
| US20190156017A1 (en) | Terminal and method for managing launch of an application of a terminal | |
| CN104503674A (en) | Screenshot picture generating method | |
| CN112929254A (en) | Message processing method and device and electronic equipment | |
| CN112016080A (en) | Application authority management method and device and electronic equipment | |
| CN104809049A (en) | Terminal | |
| CN107943268B (en) | Scheduling job control method, device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |