Method and device for pushing application program interface, equipment and medium
By responding to user operations in mobile applications and displaying push interfaces when users are idle, the problem of users accidentally touching push pop-ups is solved, improving user experience and realizing accurate advertising delivery.
Patent Information
- Application Number
- CN202411880373.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-19
- Publication Date
- 2025-04-11
AI Technical Summary
When mobile applications push advertisements, notifications or personalized recommendations, they can easily cause users to accidentally touch pop-ups, and then enter pages they do not want to visit, resulting in poor user experience.
By responding to the user's operations on the application interface, register the push interface, and display the push interface after the user is idle for a preset duration, avoiding displaying the push interface in the user's operation gap and reducing false touch situations.
It effectively avoids users from accidentally touching push links, improves users' application experience, and meets the needs of precise advertising delivery.
Smart Images
Figure CN119806707A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information technology, and in particular to a method, device, equipment and medium for pushing an application program interface. Background Art
[0002] With the popularity of mobile applications, people have higher and higher requirements for the user experience of mobile applications. For example, interface style, fluency or false touch rate are all important indicators of user experience. The quality of these indicators determines the business indicators such as the retention rate and conversion rate of an application.
[0003] When people use mobile applications, it is easy to accidentally touch the application because the application needs to push advertisements, notifications or personalized recommendations. For example, when a personalized recommendation pop-up window suddenly appears during a click or slide, it is easy to click on the pop-up window and enter the page you don’t want to enter, resulting in a poor user experience. Summary of the invention
[0004] In view of this, the present invention provides a method, apparatus, device and medium for application program interface push to solve the problem of poor user experience caused by users accidentally touching an advertisement pop-up window to enter an advertisement link page.
[0005] In a first aspect, the present invention provides a method for pushing an application interface, the method comprising: in response to a first operation of a user on an application interface, displaying a first interface; in response to a second operation of the user on the first interface, registering a first push interface; if the user has not continued to operate the first interface for a preset time period, drawing the first push interface, displaying the first push interface, and the first push interface covering the first interface.
[0006] After the user performs the second operation on the first interface, the first push interface will be registered. During the user's operation on the first interface, the first push interface will not be displayed, which can effectively prevent the user from accidentally touching the push link in the first push interface. The first push interface is displayed after the user has been idle for a preset period of time. Compared with immediately displaying the first push interface when the current message queue is idle, this can further avoid accidental touches caused by displaying the first push interface during the gap between user operations, which can not only ensure the user's normal operation, but also push information to the user, thereby improving the user's application usage experience.
[0007] In an optional embodiment, the aforementioned method for pushing application interfaces further includes: in response to the second operation, registering the first push interface and registering the second push interface; in a case where the priority of the first push interface is higher than the priority of the second push interface, if the user has not continued to operate the first interface for a preset time period, drawing the first push interface and displaying the first push interface, with the first push interface covering the first interface; in response to the third operation of the user exiting the first push interface, drawing the second push interface and displaying the second push interface, with the second push interface covering the first interface.
[0008] In this way, when there are multiple push interfaces, the priority of the push interface can be set. By dividing the priority of the push tasks, the needs of the advertiser to achieve accurate advertising delivery can be met.
[0009] In an optional embodiment, the aforementioned method for application interface push also includes: in response to the first operation, displaying the first interface; in response to the second operation, registering the first push interface; in response to the fourth operation of the user exiting the first interface, canceling the registration of the first push interface.
[0010] In this way, after the user exits the first interface, the display of the push interface can be cancelled, which can improve the user experience and interaction effect.
[0011] In an optional embodiment, the aforementioned method for application interface push also includes: when displaying the first interface, registering the first push interface; if the user has not continued to operate the first interface for a preset time, drawing the first push interface, displaying the first push interface, and the first push interface covering the first interface.
[0012] When the first interface is displayed, the first push interface is registered. This design decouples the display of the first push interface from the user's operation, making the solution more flexible and scalable. In the future, if the display conditions or content of the first push interface need to be adjusted, only the relevant logic needs to be modified without changing the direct relationship between the user operation and the interface display.
[0013] In an optional embodiment, the aforementioned method for application interface push also includes: when displaying the first interface, registering the first push interface and registering the second push interface; when the priority of the first push interface is higher than the priority of the second push interface, if the user has not continued to operate the first interface for a preset time, drawing the first push interface, displaying the first push interface, and covering the first interface; in response to the user's third operation of exiting the first push interface, drawing the second push interface, displaying the second push interface, and covering the first interface.
[0014] The registration settings of multiple push interfaces are decoupled from user operations. In the future, if the display conditions or content of multiple push interfaces need to be adjusted, only the relevant logic needs to be modified without changing the direct relationship between user operations and the display of multiple push interfaces.
[0015] In an optional implementation, the aforementioned method for application program interface push further includes: setting a window time for the first push interface; drawing the second push interface, and displaying the second push interface after the window time has passed.
[0016] By setting a window time between push tasks, the application can respond to user clicks within the window time and exit the entire push task execution flow. The interface will not freeze.
[0017] In a second aspect, the present invention provides a device for pushing an application program interface, the device comprising: a display module, for displaying a first interface in response to a first operation of a user on the application program interface; a processing module, for registering a first push interface in response to a second operation of the user on the first interface or when the first interface is displayed; the processing module is also used to draw the first push interface and display the first push interface if the user has not continued to operate the first interface for a preset time, and the first push interface is covered on the first interface.
[0018] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method for application program interface push of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.
[0019] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to cause a computer to execute the method for application program interface push of the above-mentioned first aspect or any corresponding embodiment thereof.
[0020] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the method for application program interface push according to the first aspect or any corresponding embodiment thereof.
[0021] After the user performs the second operation on the first interface, the method for application interface push provided by the present invention will register the first push interface. During the user's operation on the first interface, the first push interface will not be displayed, which can effectively prevent the user from accidentally touching the push link in the first push interface. The first push interface is displayed after the user has been idle for a preset period of time. Compared with immediately displaying the first push interface when the current message queue is idle, this can further avoid accidental touches caused by displaying the first push interface during the gap between user operations, which can not only ensure the user's normal operation, but also push information to the user, thereby improving the user's application usage experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0023] Figure 1 A schematic diagram showing a flow chart of a method for application program interface push provided by an embodiment of the present invention;
[0024] Figure 2 A schematic diagram of the structure of a device for application program interface push is shown;
[0025] Figure 3 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0026] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.
[0027] The task scheduling method in the related art is IdleHandler, which is based on the Android message queue mechanism and executes pre-set tasks when the current message queue (MessageQueue, MQ for short) is idle. IdleHandler has the following problems:
[0028] First, IdleHandler will execute the task immediately when the current message queue is idle. It may execute the task in the gap between multiple user operations, which may cause accidental touches.
[0029] Second, executing tasks in the order in which they are added cannot meet the needs of complex operation scenarios.
[0030] Third, when multiple tasks are executed at the same time, it is easy for the page to get stuck and fail to respond to user clicks.
[0031] According to an embodiment of the present invention, a method embodiment for application program interface push is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0032] In this embodiment, a method for pushing an application program interface is provided, which can be used in a mobile terminal, such as a mobile phone, a notebook or a tablet computer. Figure 1 A schematic diagram of a process for pushing an application program interface provided by an embodiment of the present invention is shown. Figure 1 As shown, the process includes the following steps:
[0033] Step S101: In response to a first operation of a user on an application program interface, a first interface is displayed.
[0034] In this step, the first operation may be clicking a button, sliding the screen, or inputting text, etc. When the user opens the application for the first time or triggers the first operation, the application will display the first interface.
[0035] Step S102: registering a first push interface in response to a second operation of the user on the first interface.
[0036] In this step, the second operation may also be clicking a button, sliding the screen, or inputting text, etc. The second operation may be the same as the first operation or different from the first operation. When the user triggers the second operation, the application will register or prepare a first push interface. The first push interface is used to display promotional content or advertisements, etc.
[0037] Step S103: If it is not obtained that the user has operated the first interface for a preset time, a first push interface is drawn and displayed, and the first push interface is covered on the first interface.
[0038] In this step, the application program monitors the user's operation on the first interface. If the user does not perform any operation on the first interface within a preset time, that is, the user is in an idle state, the application program will automatically draw and display the first push interface.
[0039] The first push interface will be overlaid on the first interface, and the promotion information will be displayed to the user when the user is in an idle state. This can avoid the problem that the first push interface pops up during the user's operation on the first interface, causing the user to accidentally touch the promotion link and the user cannot continue to operate the first interface.
[0040] The preset duration can be determined based on the actual application scenario, for example, the preset duration can be set to 2000 milliseconds. The preset duration can also be determined based on the user's operating habits. The user's operating data during the use of the application can be collected. Including: the time when the user opens the application, the length of time spent on each interface of the application, and the frequency and order of performing various operations on the application interface, such as clicking, sliding or inputting.
[0041] The collected data needs to be analyzed to identify the user's operating habits and patterns. This can be achieved through statistical methods, machine learning algorithms, or data mining techniques. Determine the distribution of time intervals between user operations and how these intervals vary with different users, different times, such as different hours of the day, and different contexts (such as the type of task the user is performing).
[0042] Based on the results of data analysis, a prediction model for the interval between user operations can be established. This model can predict the interval between the user's next operation based on the user's current behavior and historical data. The model can be rule-based, statistical, or machine learning, depending on the characteristics of the data and the accuracy requirements of the prediction.
[0043] The preset duration can be adjusted dynamically based on the user's real-time operation data and model predictions. For example, if the user usually performs the next operation quickly after using a certain function, the application can shorten the preset duration; if the user usually takes a long break after using a certain function, the application can extend the preset duration.
[0044] The preset duration can be determined based on the user's operating habits, which helps to further improve the user experience and better understand the user's needs and behaviors.
[0045] In the method for pushing an application interface provided by an embodiment of the present invention, after the user performs a second operation on the first interface, the first push interface will be registered. During the user's operation on the first interface, the first push interface will not be displayed, which can effectively prevent the user from accidentally touching the push link in the first push interface. The first push interface is displayed after the user has been in an idle state for a preset period of time. Compared with immediately displaying the first push interface when the current message queue is in an idle state, this can further prevent accidental touches caused by displaying the first push interface during the gap between user operations, which can not only ensure the user's normal operation, but also push information to the user, thereby improving the user's application usage experience.
[0046] In the related art, multiple push tasks are executed in the order of addition, which cannot meet the needs of complex application scenarios. For example, push tasks executed sequentially cannot meet the needs of the advertiser to control the display frequency and exposure of advertisements in different locations, and cannot achieve accurate delivery.
[0047] In some optional embodiments, the aforementioned method for application interface push also includes: in response to a second operation, registering a first push interface, registering a second push interface; when the priority of the first push interface is higher than the priority of the second push interface, if the user's operation on the first interface is not obtained for a preset time period, drawing the first push interface, displaying the first push interface, and covering the first interface; in response to a third operation of the user exiting the first push interface, drawing the second push interface, displaying the second push interface, and covering the first interface.
[0048] In this embodiment, when there are multiple push interfaces, each push interface is registered. When the user does not perform any operation on the first interface, based on the priority of the push interface, the push interface with the highest priority is displayed, that is, the first push interface in this embodiment. If the user triggers a third operation, the third operation can be clicking a close button or sliding back, etc., to exit the current push interface, and based on the priority of the push interface, other push interfaces are displayed, that is, the second push interface in this embodiment.
[0049] The push interface and the priority of the push interface can be registered, stored and managed by the interface manager. The interface manager can determine which push interface should be displayed based on the logic of the embodiment of the present invention, the priority of the push interface and the preset rules.
[0050] The user's operation on the first interface may be monitored through a timer or a listener. If no user operation is detected within a first preset time period, the display logic of the first push interface may be triggered.
[0051] In this way, when there are multiple push interfaces, the priority of the push interface can be set. By dividing the priority of the push tasks, the needs of the advertiser to achieve accurate advertising delivery can be met.
[0052] In some optional embodiments, the aforementioned method for application interface push also includes: displaying the first interface in response to a first operation; registering the first push interface in response to a second operation; and canceling the registration of the first push interface in response to a fourth operation of the user exiting the first interface.
[0053] In this embodiment, the fourth operation may be clicking a close button, sliding back, or triggering an exit event, etc. The fourth operation may be the same as the third operation or different from the third operation. When the user performs the second operation, the first push interface may be added to the registration list of the push interface manager, and when the user performs the fourth operation, the first push interface may be removed from the registration list of the push interface manager.
[0054] In this way, after the user exits the first interface, the display of the push interface can be cancelled, which can improve the user experience and interaction effect.
[0055] In some optional embodiments, the aforementioned method for application interface push also includes: when displaying the first interface, registering the first push interface; if the user has not continued to operate the first interface for a preset time, drawing the first push interface, displaying the first push interface, and the first push interface covering the first interface.
[0056] In this embodiment, even if the user does not perform any operation on the first interface, the first push interface will be registered as long as the first interface is displayed. In this way, preparations for displaying the first push interface can be made in advance, and the first push interface can be displayed immediately when the user has not operated for a preset period of time, ensuring that the push information can be delivered to the user in a timely manner. In addition, when the first interface is displayed, the first push interface is registered. This design decouples the display of the first push interface from the user's operation, making this solution more flexible and scalable. In the future, if the display conditions or content of the first push interface need to be adjusted, only the relevant logic needs to be modified without changing the direct relationship between the user operation and the interface display.
[0057] In some optional embodiments, the aforementioned method for application interface push also includes: when displaying the first interface, registering the first push interface and registering the second push interface; when the priority of the first push interface is higher than the priority of the second push interface, if the user's operation on the first interface is not obtained for a preset time period, drawing the first push interface, displaying the first push interface, and covering the first interface; in response to the user's third operation of exiting the first push interface, drawing the second push interface, displaying the second push interface, and covering the first interface.
[0058] In this embodiment, as mentioned above, the registration settings of multiple push interfaces are decoupled from the user's operations. In the future, if the display conditions or content of multiple push interfaces need to be adjusted, only the relevant logic needs to be modified without changing the direct relationship between user operations and the display of multiple push interfaces.
[0059] In the related art, when multiple push interfaces are executed at the same time, it is easy for the page to fail to respond to user clicks and become stuck.
[0060] In some optional implementations, the aforementioned method for pushing an application program interface further includes: setting a window time for the first push interface; drawing a second push interface, and displaying the second push interface after the window time has passed.
[0061] In this embodiment, the window time can be set based on the actual program running situation, for example, it can be set to 500 milliseconds. Setting the window time between push tasks allows the application to respond to user clicks within the window time and exit the entire push task execution flow. There will be no interface freeze.
[0062] During the implementation of the embodiment of the present invention, the following customized UIIdleTaskManager may be used to check whether there is a push task to be executed.
[0063]
[0064]
[0065]
[0066] In the implementation process of the embodiment of the present invention, it can be realized in the following manner: when the first interface is visible, the first push interface and the second push interface are registered in their respective priority queues, and when the first interface is not visible, the registration of the first push interface and the second push interface is cancelled. At the same time, the user operation is monitored, and each operation of the user will reset the task manager, which can prevent the execution of the push task when the user operates the first interface.
[0067] classPageB:AppCompatActivity(){
[0068] val taskShowW1 = UIIdleTask{
[0069] W1Dialog.show()
[0070] }
[0071] val taskShowW2 = UIIdleTask{
[0072] W2Dialog.show()
[0073] }
[0074] override fun onCreate(savedInstanceState:Bundle?){
[0075] super.onCreate(savedInstanceState)
[0076] / / Set the page content
[0077] setContentView(R.layout.activity_page_b)
[0078] }
[0079] override fun onResume(){
[0080] super.onResume()
[0081] / / When the page is visible, insert the task of displaying W1 and W2 windows
[0082] UIIdleTaskManager.addTaskLevelOne(task1)
[0083] UIIdleTaskManager.addTaskLevelTwo(task2)
[0084] }
[0085] override fun onPause(){
[0086] super.onPause()
[0087] / / When the page is not visible, remove the task of displaying W1 and W2 windows
[0088] UIIdleTaskManager.removeTaskLevelOne(task1)
[0089] UIIdleTaskManager.removeTaskLevelTwo(task2)
[0090] }
[0091] / / Monitor user touch events. Each user touch will delay the task execution.
[0092] override fun onTouchEvent(event:MotionEvent?):Boolean{
[0093] UIIdleTaskManager.startOrReStartJob()
[0094] return super.onTouchEvent(event)
[0095] }
[0096] }
[0097] In this embodiment, a device for application program interface push is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0098] This embodiment provides a device for pushing an application program interface. Figure 2 A schematic diagram of the structure of a device for application program interface push is shown, Figure 2 As shown, including:
[0099] The display module 201 is configured to display a first interface in response to a first operation of the user on the application program interface.
[0100] The processing module 202 is used to register the first push interface in response to the user's second operation on the first interface or when the first interface is displayed.
[0101] The processing module 202 is further configured to draw a first push interface and display the first push interface if the user has not continued to operate the first interface for a preset time period, and the first push interface is covered on the first interface.
[0102] In some optional embodiments, the processing module is also used to register the first push interface and the second push interface in response to the second operation; when the priority of the first push interface is higher than the priority of the second push interface, if the user's operation on the first interface is not obtained for a preset time period, the first push interface is drawn and the first push interface is displayed, and the first push interface is covered on the first interface; in response to the third operation of the user exiting the first push interface, the second push interface is drawn and the second push interface is displayed, and the second push interface is covered on the first interface.
[0103] In some optional embodiments, the processing module is further used to display the first interface in response to the first operation; register the first push interface in response to the second operation; and cancel the registration of the first push interface in response to the fourth operation of the user exiting the first interface.
[0104] In some optional embodiments, the processing module is also used to register a first push interface when displaying the first interface; if the user has not continued to operate the first interface for a preset time, the first push interface is drawn and displayed, and the first push interface is covered on the first interface.
[0105] In some optional embodiments, the processing module is also used to register the first push interface and the second push interface when the first interface is displayed; when the priority of the first push interface is higher than the priority of the second push interface, if the user's operation on the first interface is not obtained for a preset time period, the first push interface is drawn and the first push interface is displayed, and the first push interface is covered on the first interface; in response to the user's third operation of exiting the first push interface, the second push interface is drawn and the second push interface is displayed, and the second push interface is covered on the first interface.
[0106] In some optional implementations, the processing module is further used to set a window time for the first push interface; draw a second push interface, and display the second push interface after the window time has passed.
[0107] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.
[0108] The device for application program interface push in this embodiment is presented in the form of a functional unit, where the unit refers to an application specific integrated circuit (ASIC) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.
[0109] The device for pushing application program interfaces provided by an embodiment of the present invention registers the first push interface after the user performs the second operation on the first interface. The first push interface will not be displayed while the user is operating the first interface, which can effectively prevent the user from accidentally touching the push link in the first push interface. The first push interface is displayed after the user has been in an idle state for a preset period of time. Compared with immediately displaying the first push interface when the current message queue is in an idle state, this can further prevent accidental touches caused by displaying the first push interface during the gap between user operations, thereby ensuring the user's normal operation and pushing information to the user, thereby improving the user's application usage experience.
[0110] The embodiment of the present invention also provides a computer device having the above Figure 2 The apparatus for application program interface push is shown.
[0111] See also Figure 3 , Figure 3 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 3 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the computer device, including instructions stored in or on the memory to display graphical information of a graphical user interface on an external input / output device (such as a display device coupled to an interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 3 A processor 10 is taken as an example.
[0112] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.
[0113] The aforementioned memory 20 stores instructions executable by at least one processor 10, so that the aforementioned at least one processor 10 executes the method shown in the above embodiment.
[0114] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0115] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.
[0116] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 3 The example of connecting through bus is taken in the following.
[0117] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator rod, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (such as a light emitting diode) and a tactile feedback device (such as a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.
[0118] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.
[0119] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.
[0120] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.
Claims
1. A method for application program interface push, characterized in that: The method comprises: In response to a first operation of the user on the application program interface, displaying a first interface; In response to a second operation of the user on the first interface, registering a first push interface; If it is not obtained that the user operates the first interface continuously for a preset time period, the first push interface is drawn and displayed, and the first push interface covers the first interface.
2. The method according to claim 1, characterized in that The method further comprises: In response to the second operation, registering the first push interface and registering the second push interface; In the case where the priority of the first push interface is higher than the priority of the second push interface, if the user has not operated the first interface for a preset time, the first push interface is drawn and displayed, and the first push interface is covered on the first interface; In response to a third operation of the user exiting the first push interface, the second push interface is drawn and displayed, and the second push interface covers the first interface.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: In response to the first operation, displaying the first interface; In response to the second operation, registering the first push interface; In response to a fourth operation of the user exiting the first interface, the registration of the first push interface is canceled.
4. The method according to claim 1, characterized in that: The method further comprises: When the first interface is displayed, registering the first push interface; If it is not obtained that the user operates the first interface continuously for a preset time period, the first push interface is drawn and displayed, and the first push interface covers the first interface.
5. The method according to claim 4, characterized in that The method further comprises: When the first interface is displayed, registering the first push interface and registering the second push interface; In the case where the priority of the first push interface is higher than the priority of the second push interface, if the user has not operated the first interface for a preset time, the first push interface is drawn and displayed, and the first push interface is covered on the first interface; In response to a third operation of the user exiting the first push interface, the second push interface is drawn and displayed, and the second push interface covers the first interface.
6. The method according to claim 5, characterized in that The method further comprises: Set the window time of the first push interface; The second push interface is drawn, and after the window time has passed, the second push interface is displayed.
7. A device for application program interface push, characterized in that: The device comprises: A display module, configured to display a first interface in response to a first operation of the user on the application program interface; A processing module, configured to register a first push interface in response to a second operation of the user on the first interface or when the first interface is displayed; The processing module is further configured to draw the first push interface and display the first push interface if the user has not continued to operate the first interface for a preset time period, and the first push interface is covered on the first interface.
8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for application program interface push according to any one of claims 1 to 6 by executing the computer instructions.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for application program interface push according to any one of claims 1 to 6.
10. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the method for application program interface push according to any one of claims 1 to 6.