Popup window management method and device based on ordered priority control and storage medium

Abstract

The invention provides a pop-up window management method and device based on ordered priority control and a storage medium. The method comprises the following steps: determining a pop-up window style rule of a pop-up window, and appointing a pop-up window description protocol with a back end according to the pop-up window style rule; sending multiple pieces of request information to a back end, and screening out popup windows needing to be displayed according to response data returned by the back end to form a to-be-displayed popup window sequence; based on the to-be-displayed pop-up window sequence, determining the priority of the pop-up window according to the weight of the pop-up window on the influence of the function and / or the historical interaction behavior of the user, and generating an ordered pop-up window sequence according to the priority; according to popup window attribute information in the ordered popup window sequence, generating a popup window view according with a popup window style rule; and sequentially displaying the popup windows in the ordered popup window sequence, and after the current popup window finishes the user response and disappears, triggering the display of the next popup window according to the popup window sequence in the ordered popup window sequence. The popup window display sequence can be optimized, the module coupling degree is reduced, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of application technology, and in particular to a pop-up window management method, device and storage medium based on ordered priority control. Background Art

[0002] With the rapid development of mobile internet, pop-up windows are becoming increasingly common within applications (APPs), becoming an indispensable means of interaction in business processes. For example, upon startup, some car owner apps trigger multiple business-related pop-up windows, including privacy agreement confirmation, APP version update prompts, vehicle status warnings, user login status expiration reminders, community post update notifications, and maintenance order status updates.

[0003] Currently, the most common pop-up window implementation method in the market is to initiate a network request to the backend before displaying each pop-up window, and then decide whether to display the pop-up window based on the backend's response data. However, with the increasing complexity of business and the increase in the number of pop-ups, this traditional implementation method has gradually exposed the following problems:

[0004] The pop-up module is not only responsible for its own display and closing logic, but also needs to manage the display order and notification mechanism of other pop-ups. It cannot meet the design principle of "single responsibility" and increases the coupling between modules and code complexity.

[0005] Current technology lacks clear management of the priorities of multiple pop-up windows, which may cause the N+1th pop-up window to pop up prematurely before the Nth pop-up window disappears, causing visual overlap or logical conflicts, seriously affecting the user experience.

[0006] The style design of each pop-up window is independent, making it difficult to achieve visual consistency. In addition, when a new pop-up window is added, the entire APP code needs to be updated, increasing development and operation and maintenance costs.

[0007] Due to the uncertainty of pop-up window order and logic, users are unable to effectively handle the current pop-up window, further reducing the interactive experience and function availability. Summary of the Invention

[0008] In view of this, the embodiments of the present application provide a pop-up management method, device and storage medium based on ordered priority control to solve the problems of increased module coupling, uncontrollable pop-up order, high development and operation and maintenance costs, and poor user experience in the prior art.

[0009] According to a first aspect of an embodiment of the present application, a pop-up management method based on ordered priority control is provided, comprising: determining a pop-up style rule for a pop-up window, and agreeing on a pop-up description protocol with a back-end according to the pop-up style rule, wherein the pop-up description protocol is used to describe the attribute information of the pop-up window in a standardized data format; when the application is started, multiple request messages are sent to the back-end, and the pop-ups to be displayed are filtered out according to the response data returned by the back-end to form a sequence of pop-ups to be displayed; based on the sequence of pop-ups to be displayed, the priority of each pop-up window is determined according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and an ordered pop-up sequence is generated according to the priority; based on the pop-up attribute information in the ordered pop-up sequence, a pop-up view that complies with the pop-up style rule is generated; the pop-ups in the ordered pop-up sequence are displayed in sequence, and after the current pop-up window completes the user response and disappears, the display of the next pop-up window is triggered according to the order of the pop-ups in the ordered pop-up sequence.

[0010] According to a second aspect of an embodiment of the present application, a pop-up management device based on ordered priority control is provided, comprising: a determination module, which determines a pop-up style rule of a pop-up window, and agrees on a pop-up description protocol with a back-end according to the pop-up style rule, wherein the pop-up description protocol is used to describe the attribute information of the pop-up window in a standardized data format; an acquisition module, which sends multiple request messages to the back-end when the application is started, and filters out the pop-ups to be displayed according to the response data returned by the back-end to form a sequence of pop-ups to be displayed; a determination module, which determines the priority of each pop-up window based on the sequence of pop-ups to be displayed, according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generates an ordered sequence of pop-up windows according to the priority; a generation module, which generates a pop-up view that complies with the pop-up style rule according to the pop-up attribute information in the ordered sequence of pop-up windows; a display module, which displays the pop-ups in the ordered sequence of pop-ups in sequence, and triggers the display of the next pop-up window according to the order of the pop-ups in the ordered sequence of pop-ups after the current pop-up window completes the user response and disappears.

[0011] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the steps of the above method are implemented when the processor executes the computer program.

[0012] According to a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the steps of the above method are implemented.

[0013] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0014] By determining the pop-up style rules of the pop-up window, according to the pop-up style rules, agreeing on a pop-up description protocol with the backend, the pop-up description protocol is used to describe the attribute information of the pop-up window in a standardized data format; when the application starts, multiple request information is sent to the backend, and the pop-ups that need to be displayed are filtered out according to the response data returned by the backend to form a sequence of pop-ups to be displayed; based on the sequence of pop-ups to be displayed, the priority of each pop-up window is determined according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and an ordered pop-up sequence is generated according to the priority; based on the pop-up attribute information in the ordered pop-up sequence, a pop-up view that conforms to the pop-up style rules is generated; the pop-ups in the ordered pop-up sequence are displayed in sequence, and after the current pop-up window completes the user response and disappears, the display of the next pop-up window is triggered according to the order of the pop-ups in the ordered pop-up sequence. This application can optimize the order of pop-up display, reduce module coupling, and improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] Figure 1 Schematic diagram of a pop-up window management method based on ordered priority control provided by an embodiment of the present application;

[0017] Figure 2 is a schematic diagram of a sequence of pop-up windows to be displayed provided in an embodiment of the present application;

[0018] Figure 3 is a schematic diagram of an ordered pop-up window sequence provided in an embodiment of the present application;

[0019] Figure 4 This is a schematic diagram of the existing pop-up windows that pop up in disorder according to the embodiment of the present application;

[0020] Figure 5 This is a schematic diagram of the improved pop-up windows in an orderly manner provided by an embodiment of the present application;

[0021] Figure 6 Schematic diagram of the structure of a pop-up window management device based on ordered priority control provided by an embodiment of the present application;

[0022] Figure 7 It is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0024] It should be understood that the various steps described in the method embodiments of the present application can be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0025] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0026] It should be noted that the modifications of "one" and "multiple" mentioned in this application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0027] When the current car owner APP is started, there will be many business pop-ups, such as: privacy agreement, APP update, VHR authorization pop-up, vehicle warning pop-up, login expiration and need to re-login, community post replies, maintenance appointment order status update, etc.

[0028] The current processing method on the market is as follows: before each pop-up window appears, the following operations are performed. First, a request is initiated to ask the backend whether a pop-up window is required; if so, the APP pop-up window is displayed, if not, the process ends.

[0029] As the business of the car owner APP grows, the styles and functions of pop-up windows will only increase. According to the current processing method, as the number of pop-up windows increases, the following problems will inevitably arise:

[0030] 1. The codes for each pop-up window are scattered in different code blocks in the project, making the project code difficult to maintain.

[0031] 2. After each pop-up window disappears, other pop-up windows need to be notified. This means that the pop-up window module needs to handle other things in addition to the business of the pop-up window itself, which cannot well meet the "single responsibility" code design principle.

[0032] 3. The pop-up priority of the Nth pop-up window and the N+1th pop-up window cannot be determined.

[0033] 4. Before the Nth pop-up window disappears, the N+1th pop-up window has already popped up, covering the Nth pop-up window, resulting in a poor user experience.

[0034] 5. The pop-up window style cannot be unified, and the APP needs to be updated when a new pop-up window is added.

[0035] Therefore, the pop-up window implementation method in the prior art still has the following shortcomings: the codes for each pop-up window are scattered in different code blocks in the project, which makes the project code difficult to maintain. After each pop-up window disappears, other pop-up windows need to be notified, so that the pop-up window module needs to handle other things in addition to handling the business of the pop-up window itself, which cannot meet the code design principle of single responsibility well. It is impossible to determine the pop-up priority of the Nth pop-up window and the N+1th pop-up window. When the Nth pop-up window has not yet disappeared, the N+1th pop-up window has already popped up, covering the Nth pop-up window, resulting in a poor user experience. The pop-up window style cannot be unified, and the APP needs to be updated when a new pop-up window is added.

[0036] In view of the problems existing in the prior art, this application proposes a pop-up management method based on ordered priority control, aiming to achieve centralized management, modular design and dynamic generation of pop-up windows, and improve code maintainability and user experience.

[0037] First, define unified pop-up style rules, divide the pop-up into title area, content area and bottom button area, clarify the layout and style parameters of each area, and abstract the styles of all pop-up windows into a base class through style rules to achieve unification and standardization of pop-up styles.

[0038] Secondly, based on the style rules, a standardized pop-up description protocol is agreed upon with the back-end. The protocol describes the attribute information of the pop-up in a structured data format, including the type of pop-up, title content, prompt content, button style and function parameters, etc., thereby supporting flexible docking and dynamic configuration between the front-end and back-end.

[0039] Then, when the application starts, it sends asynchronous requests to the backend to obtain the display requirements of multiple pop-up windows, filters out the pop-up windows that need to be displayed based on the response data returned by the backend, forms a sequence of pop-up windows to be displayed, and further calculates the priority of the pop-up windows based on the functional impact weight of each pop-up window and the user's historical interaction behavior, and generates an ordered pop-up window sequence according to the priority.

[0040] Finally, based on the pop-up attribute information in the ordered pop-up sequence, a pop-up view is dynamically generated according to the pop-up style rules, ensuring that the pop-ups are displayed sequentially according to priority. To avoid direct coupling between pop-ups, an independent sequence control module manages the pop-up display order, ensuring that the current pop-up completes the user response and disappears before triggering the next pop-up display. Meanwhile, the pop-up itself is only responsible for data filling, user response, and disappearance logic, thus meeting the single responsibility design principle.

[0041] This application solution not only improves the scalability and maintainability of the code through unified management of pop-up styles, dynamic sorting of priorities and serialized display logic, but also optimizes the user's interactive experience, meeting the requirements for efficient and flexible pop-up management in complex business scenarios.

[0042] The contents of the technical solution of this application are described in detail below with reference to the accompanying drawings and specific embodiments.

[0043] Figure 1 This is a flow chart of a pop-up window management method based on ordered priority control provided by an embodiment of the present application. Figure 1 As shown, the pop-up window management method based on ordered priority control may specifically include:

[0044] S101, determining a pop-up window style rule, and agreeing on a pop-up window description protocol with the backend based on the pop-up window style rule. The pop-up window description protocol is used to describe attribute information of the pop-up window in a standardized data format;

[0045] S102, when the application is started, multiple request messages are sent to the backend, and pop-up windows to be displayed are screened out based on the response data returned by the backend to form a sequence of pop-up windows to be displayed;

[0046] S103, based on the sequence of pop-up windows to be displayed, determining the priority of each pop-up window according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generating an ordered pop-up window sequence according to the priority;

[0047] S104, generating a pop-up window view that complies with pop-up window style rules based on pop-up window attribute information in the ordered pop-up window sequence;

[0048] S105, displaying the pop-up windows in the ordered pop-up window sequence in sequence. After the current pop-up window completes the user response and disappears, triggering the display of the next pop-up window according to the order of the pop-up windows in the ordered pop-up window sequence.

[0049] In some embodiments, determining a pop-up window style rule includes:

[0050] Determine the popup style rules for all popups. The popup style rules include the layout and style parameters of the popup title area, content area, and bottom button area.

[0051] Based on the pop-up style rules, the layout and style parameters of the pop-up are abstracted to form a pop-up base class, which is used to uniformly manage the layout and style filling of the pop-up.

[0052] Specifically, establish pop-up window style rules. Pop-up window style rules are used to standardize the display form, layout structure, and style parameters of all pop-up windows to ensure consistency in visual presentation across different types of pop-ups while reducing the complexity of development and maintenance. In actual applications, pop-up window style rules can include the following:

[0053] 1. Pop-up window display location:

[0054] All pop-ups are positioned in the center of the screen, enhancing the user's visual focus. By maintaining a fixed display position, switching between pop-ups doesn't cause positional shifts, maintaining visual continuity.

[0055] 2. Pop-up window layout structure:

[0056] The overall layout of the pop-up window consists of three parts: the "title area", the "content area" and the "bottom button area", which are arranged from top to bottom.

[0057] Title area: This area displays the pop-up's title. The title text is centered, and the font and color can be adjusted to suit your needs. If the title is too long, it will automatically wrap to ensure full readability within the limited space.

[0058] Content area: used to display specific prompt content. The text is centered and supports dynamic line breaks. The font and color parameters are configurable to adapt to the length and complexity of different content.

[0059] Bottom button area: Used to place user interaction buttons. The buttons are arranged from left to right and support dynamic generation of 1 to N buttons. Each button occupies the same width of the space. Clicking any button will cause the pop-up window to disappear and the corresponding action logic to be executed, such as submitting data or closing the current pop-up window.

[0060] Through the above layout structure, the core interaction logic and content display of the pop-up window are unified, making it easier for developers to flexibly expand the pop-up window style and functions according to specific business needs.

[0061] Next, based on the above style rules, the layout and style parameters of the pop-up window are abstracted to form a pop-up window base class. The pop-up window base class is a code structure used to uniformly manage the pop-up window style and layout. By encapsulating the pop-up window layout and style rules in the base class, the style reusability and dynamic configuration capabilities are achieved. The following is the specific design and functions of the pop-up window base class:

[0062] 1 Definition of pop-up window base class:

[0063] The base class contains style parameters and layout logic for areas such as titles, content, and bottom buttons, such as the title's font size, color, and centering style, the content's automatic line wrapping mechanism, and the button arrangement.

[0064] 2. Abstraction of style parameters:

[0065] The popup base class supports parameterized configuration. Developers can define the style of specific popups by setting the base class properties. For example: setting the font, size, and color of the title; setting the alignment, font, and color of the content text; and defining the number, text content, and click event logic of the bottom buttons.

[0066] Through this parameterized design, the pop-up base class can adapt to different business scenarios without the need to repeatedly design specific pop-up style logic.

[0067] 3. Dynamically generate pop-up view:

[0068] The popup base class dynamically generates a popup view that conforms to style rules by receiving configuration data passed by the business logic. For example, the business logic can pass description data in JSON format, and the base class will fill in the style and layout of the corresponding title, content, and button areas based on the data content.

[0069] In an example of a specific scenario, such as the implementation of a privacy agreement pop-up window, it can be dynamically generated directly based on the pop-up window base class: the title area is filled with the title text of "Privacy Agreement", the content area displays the detailed information of the privacy agreement, and the bottom button area generates two action buttons: "Agree" and "Disagree".

[0070] Developers only need to define the above content through the configuration file, without having to design the style and layout logic of the pop-up window separately, which significantly reduces the development workload.

[0071] According to the method of the above embodiment, the pop-up window style rules of the present application realize the standardization and base class design of the pop-up window style, laying the foundation for the dynamic generation and management of subsequent pop-up window views.

[0072] In some embodiments, according to the pop-up style rules, a pop-up description protocol is agreed upon with the backend, including:

[0073] According to the pop-up style rules, a pop-up description protocol is agreed upon with the backend. The pop-up description protocol describes the attribute information of the pop-up in a standardized data format. The attribute information includes the type of pop-up, title content and style parameters, prompt content and style parameters, and the action type and style parameters of the bottom button.

[0074] Specifically, pop-up style rules are used to agree on the unified display format and style parameters for all pop-ups, providing a basis for the design of pop-up description protocols. Style rules define the layout and style of pop-ups, and may include:

[0075] The layout structure of the pop-up window: divided into the title area, content area and bottom button area;

[0076] Style parameters: including the font, size, and color of the title, the style of the content text, and the arrangement and interactive actions of the bottom buttons.

[0077] For example, in some examples, the title area must be centered and support line breaks; the content area automatically wraps and supports multiple paragraphs of text; the buttons at the bottom are arranged from left to right, the number can be dynamically generated, and the button style must be consistent.

[0078] Based on the above pop-up style rules, the pop-up description protocol is defined using a standardized data format to ensure that the data returned by the backend can fully describe the pop-up attribute information and support the dynamic generation of pop-up views. For example, the pop-up description protocol includes the following main fields:

[0079] Pop-up type (type): Identifies the purpose or function of the pop-up, for example, privacy indicates a privacy agreement pop-up, and update indicates a version update pop-up.

[0080] Title content and style parameters: including title text (title), font size (titleFontSize), font name (titleFontName) and color (titleColor).

[0081] Hint content and style parameters: including hint text (content), font size (contentFontSize), font name (contentFontName), and color (contentColor).

[0082] The action type and style parameters of the bottom button: including the button's action type (actionType), button text (actionTitle), font size (actionTitleSize), font name (actionTitleF ontName) and color (actionColor).

[0083] In some examples, the pop-up description protocol can be defined in JSON format, that is, describing the pop-up in the standard JSON format, and agreeing on the JSON fields according to business and style rules. For example, the agreed fields may include:

[0084] type, String type, used to describe the type of the pop-up window, such as: privacy represents the "protocol update" pop-up window, newVersion represents the "APP update" pop-up window, vhr represents the "VHR authorization pop-up window", etc.

[0085] title, String type, used to describe the specific content of the "title" in the "style rule", such as "hint", "newer version found", etc.

[0086] titleFontSize, Int type, used to describe the font size of "title".

[0087] titleFontName, String type, used to describe the font of "title".

[0088] titleColor, long type, HEX color value, used to describe the color of "title".

[0089] content, String type, used to describe the specific content of the "specific prompt content" in the "style rule".

[0090] contentFontSize, Int type, used to describe the font size of "content".

[0091] contentFontName, String type, used to describe the font of "content".

[0092] contentColor, long type, HEX color value, used to describe the color of "content".

[0093] actions, array type, used to describe what the "bottom buttons" are from left to right.

[0094] actionType, a String type, describes what the app should do after clicking the bottom button. For example: agreePrivacy for agreeing to the privacy agreement; disagreePrivacy for disagreeing to the privacy agreement; agreeVHR for agreeing to VHR authorization, etc.

[0095] actionTitle, String type, used to describe the specific content of a "bottom button".

[0096] actionTitleSize, Int type, used to describe the font size of a "bottom button".

[0097] actionTitleFontName, String type, used to describe the font of a "bottom button".

[0098] actionColor, long type, HEX color value, used to describe the color of a "bottom button".

[0099] In this embodiment, the front-end and back-end agree on the above-mentioned description protocol through negotiation, and standardize the protocol based on the style rules. For example, the following standardization definitions may be included:

[0100] 1. Enumeration convention of pop-up window type:

[0101] Defines a list of pop-up window types that can be returned by the backend, such as privacy, update, warning, etc. Each type corresponds to a specific business scenario.

[0102] 2. Configurability of style parameters:

[0103] All style parameters (such as font, font size, color, etc.) can be dynamically configured through the protocol, thereby supporting flexible adjustment of pop-up window styles.

[0104] 3. Conventions for button action types:

[0105] Agree on the action type of each button and the corresponding functional processing logic of the front-end. For example, agreePrivacy corresponds to the action of agreeing to the privacy agreement, and disagreePrivacy corresponds to the action of disagreeing to the privacy agreement.

[0106] Through this standardized description protocol, the front-end can dynamically generate pop-up views based on the protocol content without hard-coding any specific pop-up logic or style.

[0107] In actual operation, when the application starts, it sends a request to the backend, which returns JSON data that conforms to the description protocol. The frontend generates a pop-up window by parsing the data. The following is a specific application example:

[0108] When the user launches the app, the frontend initiates a request to check whether a privacy agreement pop-up window needs to be displayed;

[0109] The backend returns the above JSON description of the agreement, and the frontend generates a pop-up window titled "Privacy Agreement" and containing "Please read and agree to our Privacy Agreement" based on the agreement content;

[0110] Generate two buttons at the bottom: "Agree" and "Disagree", which are bound to the corresponding action types agreePrivacy and disagreePrivacy respectively;

[0111] When the user clicks the "Agree" button, the front-end executes the corresponding processing logic according to the definition of agreePrivacy.

[0112] According to the method described above, this embodiment achieves dynamic configuration of pop-up content and style by agreeing on a standardized pop-up description protocol with the backend, avoiding the high maintenance costs associated with hard-coded pop-up logic while improving the efficiency of front-end and back-end collaboration. Furthermore, the protocol's scalability enables it to support new pop-up types and styles without requiring app code updates, significantly improving the system's flexibility and maintainability.

[0113] In some embodiments, when the application is started, multiple request messages are sent to the backend, and pop-up windows to be displayed are filtered out based on the response data returned by the backend to form a sequence of pop-up windows to be displayed, including:

[0114] When the application starts, it asynchronously sends display request information corresponding to multiple pop-up windows to the backend, and each display request information corresponds to a pop-up window type;

[0115] Get the response data returned by the backend, where the response data includes information indicating whether the corresponding pop-up window needs to be displayed. Based on the information, filter out the pop-up windows that need to be displayed and discard the pop-up windows that do not need to be displayed.

[0116] The pop-up windows to be displayed are organized into a sequence of pop-up windows to be displayed according to the attribute information in the corresponding pop-up window description protocol.

[0117] Specifically, when the app starts, it checks whether it needs to display business-related pop-ups. For example, a privacy agreement pop-up, an app update pop-up, a VHR authorization pop-up, a vehicle warning pop-up, etc. To do this, the app sends multiple network requests to the backend, each corresponding to the pop-up type.

[0118] Figure 2 Schematic diagram of the sequence of pop-up windows to be displayed provided by the embodiment of the present application. Figure 2 As shown, the process of generating the sequence of pop-up windows to be displayed may include the following:

[0119] Each pop-up type corresponds to an independent network request. For example, a privacy agreement corresponds to one display request; an APP update corresponds to another display request. The same applies to other pop-up types such as VHR authorization and vehicle warnings.

[0120] All these network requests are organized into a request sequence and initiated simultaneously through asynchronous multithreading to improve network request efficiency. Asynchronous requests can avoid blocking the main thread, thereby ensuring the startup speed and smoothness of the application.

[0121] The backend returns corresponding response data for each pop-up window type request, including information indicating whether the pop-up window should be displayed. For example, for a privacy agreement pop-up window, the backend may return {"show":true} to indicate that it should be displayed; for an app update pop-up window, the backend may return {"show":false} to indicate that it does not need to be displayed. The return value structure of other pop-up window types is similar.

[0122] In some examples, the application starts filtering the response data after receiving it from all backends:

[0123] First, traverse the response data of all requests and check the show field value. Only the pop-ups with show set to true are retained, indicating that these pop-ups need to be displayed. For pop-ups with show set to false, they are directly discarded.

[0124] Next, for the pop-up windows that need to be displayed, the corresponding pop-up window data to be displayed is generated according to its type and attribute information (such as title, content, button configuration, etc.), and organized into a "pop-up window sequence to be displayed" in order.

[0125] For example, in a specific scenario, the application sent the following seven pop-up network requests: privacy agreement (privacy), APP update (update), VHR authorization (vhr), vehicle warning (vehi cleWarning), login expired and need to re-login (sessionExpired), community post reply (postReply) and maintenance order status update (maintenanceOrder).

[0126] Based on the response data, the pop-ups that need to be displayed are: VHR authorization pop-up (vhr), vehicle warning pop-up (vehicleWarning), community post reply pop-up (postReply), and maintenance order status update pop-up (maintenanceOrder).

[0127] According to the method of this embodiment described above, this embodiment uses asynchronous multi-threaded concurrent request backends, which can significantly improve data acquisition efficiency while avoiding main thread blocking and ensuring smooth application startup. By filtering and displaying only the pop-ups that need to be displayed, unnecessary pop-up logic processing is reduced, user interference is reduced, and the interactive experience is optimized. The selected pop-ups are generated into a unified sequence of pop-up windows to be displayed according to their attribute information, laying the foundation for subsequent priority sorting and pop-up display.

[0128] Through the above implementation, the application dynamically acquires and filters pop-up display requirements, significantly improving the flexibility and controllability of pop-up logic. The generation of a sequence of pop-up windows to be displayed provides clear input data for subsequent prioritization and sequential display, making pop-up management more efficient, standardized, and easy to maintain.

[0129] In some embodiments, the priority of each pop-up window is determined based on the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and an ordered pop-up window sequence is generated based on the priority, including:

[0130] The weight of the pop-up window is calculated based on the proportion of the function affected by the pop-up window in all functions of the application, and the first priority of the pop-up window is determined based on the weight of the pop-up window;

[0131] Alternatively, a user preference value for the pop-up window is calculated based on the user's historical interaction behavior with the pop-up window, and the second priority of the pop-up window is determined based on the user preference value;

[0132] Alternatively, a final priority score of the pop-up window is calculated based on the weight of the pop-up window and the user preference value, and the third priority of the pop-up window is determined based on the final priority score;

[0133] The pop-up windows in the sequence of pop-up windows to be displayed are sorted according to any one of the first priority, the second priority, and the third priority to generate an ordered pop-up window sequence.

[0134] Specifically, the first priority of the pop-up window is calculated based on the impact ratio of the pop-up window to the overall function of the application (hereinafter referred to as "impact ratio").

[0135] The impact ratio indicates the importance of the function associated with a pop-up window to the overall functionality of the app. The higher the ratio, the more important the function is to the core value of the app, and the higher the priority of the pop-up window.

[0136] In actual applications, the impact of each pop-up window is evaluated based on business logic and policies and regulations. For example:

[0137] "Privacy Agreement Pop-up": If the user does not agree to the privacy agreement, he or she will not be able to use any functions of the application, and the impact accounts for 100%.

[0138] "Community post reply pop-up": If users ignore this pop-up, it will only affect the time experience of post browsing and will have no impact on core functions. The impact is 0%.

[0139] Through this evaluation, the functional importance ranking of pop-up windows can be determined, for example: "Privacy Agreement Pop-up Window" > "APP Update Pop-up Window" > "Vehicle Warning Pop-up Window" > "Community Post Reply Pop-up Window".

[0140] The user preference value of the pop-up window (hereinafter referred to as the "preference value") is calculated based on the user's historical interaction behavior with the pop-up window, and the second priority of the pop-up window is determined based on this.

[0141] The preference value indicates the user's acceptance or interest in a certain type of pop-up window, and is calculated based on the user's historical interaction behavior.

[0142] Count the ratio of the number of users' positive responses to a pop-up window to the total number of pop-ups of the pop-up window: preference value = number of positive responses / total number of pop-ups.

[0143] A positive response means that the user clicks the positive action button in the pop-up window, such as agreeing to the agreement, accepting the update, viewing the details, etc. A negative response means that the user closes the pop-up window or does not take any action.

[0144] For example, if the total number of pop-up windows for "community posts with reply pop-ups" is 10,000, and users actively responded 8,000 times, then its preference value is 0.8.

[0145] The "Maintenance Appointment Order Status Update Pop-up" popped up 10,000 times in total, of which users actively responded 4,000 times, so its preference value is 0.4.

[0146] From this we can conclude that "community posts with reply pop-up windows" have a higher priority than "maintenance appointment order status update pop-up windows."

[0147] In some examples, to further integrate function importance and user preference, a composite model is used to calculate the final priority score of the pop-up window, and the third priority of the pop-up window is determined based on this.

[0148] Priority scoring formula: Final priority = Impact ratio × 1000 + Preference value × 10; Among them, the impact ratio has a larger weight (multiplied by 1000), ensuring that pop-ups with higher functional importance always have priority display rights, while the Preference value (multiplied by 10) is used to fine-tune the priority order.

[0149] For example, the pop-up windows are sorted according to the final priority score, and the priority order is: "Privacy Agreement Pop-up Window" > "APP Update Pop-up Window" > "Appointment Maintenance Order Status Update Pop-up Window" > "Community Post Reply Pop-up Window".

[0150] Through the above calculation, the pop-up windows in the sequence of pop-up windows to be displayed are sorted according to any one of the first priority, the second priority or the third priority to generate an ordered pop-up window sequence.

[0151] Figure 3 This is a schematic diagram of an ordered pop-up sequence provided by an embodiment of the present application. Figure 3 As shown, the process of generating the ordered pop-up window sequence may include the following:

[0152] The original sequence of pop-up windows to be displayed: "Community post reply pop-up window", "Privacy agreement pop-up window", "Maintenance appointment order status update pop-up window", and "APP update pop-up window".

[0153] After sorting by final priority score: "Privacy Agreement Pop-up Window", "APP Update Pop-up Window", "Appointment Maintenance Order Status Update Pop-up Window", and "Community Post Reply Pop-up Window".

[0154] The resulting ordered pop-up sequence will be used in the subsequent step-by-step display process to ensure that the display order of the pop-ups meets the requirements of functional importance and user preferences.

[0155] Based on the impact of pop-ups on the core functions of the application, ensure that pop-ups related to key functions are displayed first. For example, necessary pop-ups such as privacy agreements always have the highest priority.

[0156] Dynamically adjust the priority of pop-up windows based on the user's historical interaction behavior, increase the display frequency of pop-up windows that the user is interested in, and optimize the user experience.

[0157] Taking into account the importance of functions and user preferences, a composite model is used to accurately determine the priority of pop-up windows to ensure that they meet both business needs and user habits.

[0158] The priority calculation logic is flexible, and the weight or formula can be adjusted according to business needs to adapt to diverse business scenarios.

[0159] Based on the methods of the above embodiments, this application provides a priority calculation method that effectively solves the user experience problem caused by the disordered display order of pop-up windows. This method sorts the pop-up windows to be displayed by combining the importance of functions and the user's historical behavior, generating an ordered pop-up sequence, thereby achieving efficient management of pop-up windows and a friendly user interaction experience.

[0160] In some embodiments, generating a pop-up window view that complies with pop-up window style rules based on pop-up window attribute information in an ordered pop-up window sequence includes:

[0161] Extract the attribute information of each pop-up window in turn according to the elements in the ordered pop-up window sequence;

[0162] Based on the attribute information, the pop-up view is divided into the title area, content area, and bottom button area, and the layout and style parameters of each area are constrained according to the pop-up style rules;

[0163] According to the attribute information in the pop-up description protocol, the title area, content area and bottom button area are filled with style and content, and based on the filled pop-up view, the corresponding pop-up instance is generated.

[0164] Specifically, in the process of generating the pop-up window view, the attribute information of each pop-up window is first extracted one by one from the ordered pop-up window sequence.

[0165] An ordered pop-up sequence refers to a list of pop-ups to be displayed after sorting by priority. Each pop-up contains all necessary attribute information in the form of structured data.

[0166] According to the pop-up description protocol, attribute information includes but is not limited to the following fields:

[0167] Title attributes: title text (title), font size (titleFontSize), font name (titleFontName), color (titleColor);

[0168] Content attributes: prompt content text (content), font size (contentFontSize), font name (contentFontName), color (contentColor);

[0169] Button properties: button action type (actionType), button text (actionTitle), font size (actionTitleSize), font name (actionTitleFontName), and color (actionColor).

[0170] According to the pop-up style rules, the pop-up view is divided into three areas: title area, content area and bottom button area.

[0171] Title area: Displays the pop-up window's title, supporting center alignment and multi-line wrapping. The title's font size, font name, and color must conform to the parameters in the pop-up window's properties.

[0172] Content area: Used to display specific prompt content, supporting automatic line wrapping and multi-segment display. Text content and style parameters (such as font size, font name, color, etc.) must be read from the pop-up window attribute information.

[0173] Bottom button area: Used to display user interaction buttons. Buttons are arranged from left to right and support dynamic generation of 1 to N buttons. The style (such as text content, font, color, etc.) and click operation logic of each button are defined by the button field in the pop-up window attribute information.

[0174] Among them, pop-up style rules refer to the unified agreement on the layout and style parameters of each area of the pop-up view, which is used to ensure the consistency of the pop-up visual style and the standardization of content display.

[0175] Dynamic generation refers to dynamically creating view components based on the content of pop-up window attribute information, rather than hard-coding a fixed view structure, thereby supporting diverse pop-up window requirements.

[0176] Based on the extracted pop-up window attribute information, the title area, content area, and bottom button area are dynamically filled with style and content. For example, the title text content and style are set based on the attribute information:

[0177] Fill the title field with title text, such as "Privacy Agreement";

[0178] Set the font size according to titleFontSize, for example 18;

[0179] Set the font name according to titleFontName, such as Arial;

[0180] Set the text color according to titleColor, for example black (#000000).

[0181] In addition, if the title text is too long, the line break logic is automatically enabled to ensure that the text is displayed completely.

[0182] Furthermore, specific prompt content and style are filled in according to the attribute information:

[0183] Fill the content field with prompt text, such as "Please read and agree to our privacy agreement.";

[0184] Set the font size according to contentFontSize, for example 14;

[0185] Set the font name according to contentFontName, such as Arial;

[0186] Set the text color according to contentColor, for example, dark gray (#333333).

[0187] The content area supports paragraph wrapping logic to adapt to text contents of different lengths.

[0188] Furthermore, the button view is dynamically generated based on the attribute information:

[0189] Traverse the array of the actions field and create buttons one by one;

[0190] Set the actionTitle field to the button text, such as "Agree" or "Disagree";

[0191] Set the font size of the button text according to actionTitleSize, for example 16;

[0192] Set the font name of the button text according to actionTitleFontName, such as Arial;

[0193] Set the color of the button text according to actionColor, such as blue (#007AFF) or red (#FF3B30);

[0194] Bind actionType to the button's click event. For example, agreePrivacy corresponds to the operation logic of agreeing to the privacy agreement.

[0195] Generate the final popup instance based on the populated popup view. The popup instance is a specific implementation of the popup view, with independent display, user interaction, and closing logic.

[0196] Generate a pop-up window instance through the encapsulated pop-up window base class (such as the AlertView class), embed the filled title area, content area, and bottom button area into the pop-up window view, and set the pop-up window display animation and closing event.

[0197] The content and style of pop-up instances are dynamically generated based on the pop-up attribute information. There is no need to design a separate view for each pop-up type, which significantly improves the flexibility and scalability of pop-up management.

[0198] Use pop-up style rules to constrain the layout and style of the title, content, and button areas to ensure visual consistency across all pop-ups.

[0199] Dynamically generate pop-up views based on pop-up attribute information to support diverse business scenario requirements and avoid the limitations of fixed view design.

[0200] Dividing the pop-up view into independent areas makes it easier for developers to fill in the title, content, and buttons based on attribute information, enhancing the reusability and maintainability of the code.

[0201] Based on the methods of the above embodiments, this application provides a technical solution for dynamically generating pop-up views based on pop-up attribute information. This solution achieves modularization, dynamism, and standardization of pop-up view generation, laying the foundation for subsequent pop-up display and interaction, while also meeting the demand for efficient pop-up management in complex business scenarios.

[0202] The following describes the process of generating a pop-up window instance using a specific example. The process may include the following:

[0203] 1) Style protocol definition

[0204] A popup window is a view that is customized according to style rules and style protocols. Taking iOS (Swift code) as an example, the style protocol is defined as follows:

[0205]

[0206]

[0207] Furthermore, the style rules are implemented as follows:

[0208]

[0209]

[0210] 2) Generate an ordered sequence of pop-up elements

[0211] The elements in the ordered sequence of windows to be popped up are data that conforms to the style protocol. Now, we create pop-ups according to these elements and fill them with these elements. Then, they pop up in order.

[0212] In some embodiments, the pop-up windows in the ordered pop-up window sequence are displayed sequentially. After the current pop-up window completes the user response and disappears, the display of the next pop-up window is triggered according to the order of the pop-up windows in the ordered pop-up window sequence, including:

[0213] Pop up each pop-up window in sequence according to the order of the pop-up windows in the ordered pop-up window sequence, and send a notification to the sequence control module after the current pop-up window completes the user response and triggers the close event;

[0214] After receiving the notification that the current pop-up window is closed, the sequence control module searches for the next pop-up window from the ordered pop-up window sequence and triggers the display of the next pop-up window so that the next pop-up window is displayed after the current pop-up window is fully responded and disappears, until all pop-up windows in the ordered pop-up window sequence are displayed.

[0215] Specifically, in the business scenario of the car owner APP, the display requirements of each pop-up window are obtained through the back-end network request. The randomness of the network response may cause multiple pop-ups to pop up at the same time in an unordered manner. Figure 4 This is a schematic diagram of the existing pop-up windows that pop up in disorder according to the embodiment of the present application. Figure 4 As shown, for example: pop-up window D pops up first, followed by pop-up windows A and B, resulting in multiple pop-up windows overlapping, which users cannot effectively handle, seriously affecting the interactive experience.

[0216] To solve this problem, the ordered pop-up window sequence generated by the aforementioned embodiment is used to sort the pop-up windows that need to be displayed according to a preset priority. Figure 5 This is a schematic diagram of the improved pop-up windows provided in the embodiment of the present application. Figure 5 As shown, for example, assume the priority rules are as follows:

[0217] A pop-up window (highest priority)

[0218] B pop-up window (second highest priority)

[0219] D pop-up window (lower priority)

[0220] After sorting, we get an ordered sequence of pop-up windows: [Pop-up window A, pop-up window B, pop-up window D].

[0221] Furthermore, to comply with the single responsibility principle in software engineering, the responsibilities of each pop-up window are limited to the following functions:

[0222] Data filling: fill in the title, content and button style according to the pop-up description protocol;

[0223] Popup: Controls the display of pop-up windows;

[0224] User response: Process user click operations;

[0225] Disappear: Close the popup window after user operation and trigger the close event.

[0226] The pop-up window itself is not responsible for managing the pop-up and disappearance logic of other pop-ups, avoiding strong coupling between modules.

[0227] Furthermore, in order to achieve the sequential display of pop-up windows, the sequence control is managed by the sequence control module, which is responsible for triggering the pop-up of pop-up windows one by one according to the order in the ordered pop-up sequence. The specific implementation method is as follows:

[0228] According to the first element of the ordered pop-up window sequence (such as pop-up window A), the sequence control module triggers its pop-up and monitors the closing event of the pop-up window.

[0229] When the current pop-up window completes the user response and triggers a close event, the sequence control module is notified. For example, after pop-up window A is responded to by the user and disappears, a close notification is sent to the sequence control module. After receiving the notification, the sequence control module searches for the next pop-up window (such as pop-up window B) in the ordered pop-up window sequence and triggers the display of pop-up window B.

[0230] The sequence control module ensures that the next pop-up window is displayed only after the current pop-up window disappears completely, avoiding the simultaneous display of multiple pop-ups.

[0231] Following the above logic, all pop-up windows in the ordered pop-up sequence are displayed one by one. For example, after the user responds to pop-up window B, it disappears, notifying the sequence control module; the sequence control module then triggers the display of pop-up window D.

[0232] Finally, all pop-up windows are displayed and the whole process ends (such as Figure 5 shown).

[0233] For example, in some examples, assuming the current ordered pop-up window sequence is: [Pop-up window A, Pop-up window B, Pop-up window D], the specific process is as follows:

[0234] First, the display and closing of pop-up window A:

[0235] The sequence control module triggers the A pop-up display;

[0236] After the user clicks the button of pop-up window A, pop-up window A disappears and a close event is triggered;

[0237] A pop-up window sends the closing event to the sequence control module through the notification mechanism;

[0238] The sequence control module finds the next pop-up window (Pop-up window B) from the ordered pop-up window sequence and triggers its display.

[0239] Next, the display and closing of pop-up window B:

[0240] The sequence control module triggers the B pop-up display;

[0241] After the user completes the operation, pop-up window B disappears, triggering a close event.

[0242] After receiving the notification, the sequence control module triggers the display of the D pop-up window.

[0243] Finally, the display and closing of D pop-up window:

[0244] The sequence control module triggers the D pop-up display;

[0245] After the user completes the operation, the D pop-up window disappears and the process ends.

[0246] Through the combined management of ordered pop-up sequence and sequence control module, it completely avoids Figure 4 To address the issue of multiple pop-ups stacking out of order, ensure that pop-ups are displayed one by one according to priority. Separating the pop-up display order logic from the pop-up module reduces the coupling between pop-ups and enhances code maintainability and scalability. Ensure that the next pop-up is displayed only after the current pop-up has fully responded and disappeared, avoiding visual distractions and operational confusion for users.

[0247] In existing technologies, the order in which pop-ups are displayed is completely dependent on the randomness of network responses. For example, pop-up D may be displayed first, followed by pop-up A, resulting in pop-ups B, A, and D stacking together, creating a confusing user interface.

[0248] This application uses an ordered pop-up sequence and sequence control module to manage pop-ups, displaying them in order of priority. The pop-up, response, and disappearance of each pop-up are strictly controlled according to the process, ultimately ensuring the clarity of the user interface and the efficiency of operation.

[0249] This embodiment creates an ordered pop-up sequence and manages the order in which pop-up windows are displayed using a sequence control module, achieving sequential and orderly display of pop-ups. Compared to existing technologies, this solution avoids the problem of random pop-up overlap, enhances the modularity and scalability of the code, and significantly improves the user experience and interface interaction.

[0250] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0251] Figure 6 Schematic diagram of the structure of the pop-up window management device based on ordered priority control provided by the embodiment of the present application. Figure 6 As shown, the pop-up window management device based on ordered priority control includes:

[0252] The style rule determination module 601 determines the pop-up window style rule of the pop-up window and agrees on a pop-up window description protocol with the backend based on the pop-up window style rule. The pop-up window description protocol is used to describe the attribute information of the pop-up window in a standardized data format.

[0253] The acquisition module 602 sends multiple request messages to the backend when the application is started, and filters the pop-up windows to be displayed based on the response data returned by the backend to form a sequence of pop-up windows to be displayed;

[0254] Priority determination module 603 determines the priority of each pop-up window based on the sequence of pop-up windows to be displayed, according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generates an ordered pop-up window sequence based on the priority;

[0255] Generating module 604, generating a pop-up window view that complies with pop-up window style rules based on pop-up window attribute information in the ordered pop-up window sequence;

[0256] The display module 605 displays the pop-up windows in the ordered pop-up window sequence in sequence. After the current pop-up window completes the user response and disappears, the display of the next pop-up window is triggered according to the order of the pop-up windows in the ordered pop-up window sequence.

[0257] In some embodiments, Figure 6 The style rule determination module 601 determines the pop-up style rules of all pop-up windows, and the pop-up style rules include the layout and style parameters of the pop-up title area, content area and bottom button area; based on the pop-up style rules, the layout and style parameters of the pop-up window are abstracted to form a pop-up base class, which is used to uniformly manage the layout and style filling of the pop-up window.

[0258] In some embodiments, the attribute information includes the type of pop-up window, title content and style parameters, prompt content and style parameters, and the action type and style parameters of the bottom button.

[0259] In some embodiments, Figure 6 When the application is started, the acquisition module 602 asynchronously sends display request information corresponding to multiple pop-up windows to the backend, and each display request information corresponds to a pop-up window type; obtains the response data returned by the backend, where the response data includes indication information on whether the corresponding pop-up window needs to be displayed, and based on the indication information, filters out the pop-up windows that need to be displayed and discards the pop-up windows that do not need to be displayed; organizes the pop-up windows that need to be displayed into a sequence of pop-up windows to be displayed according to the attribute information in the corresponding pop-up window description protocol.

[0260] In some embodiments, Figure 6 The priority determination module 603 calculates the weight of the pop-up window according to the proportion of the function affected by the pop-up window in all functions of the application, and determines the first priority of the pop-up window according to the weight of the pop-up window; or calculates the user preference value of the pop-up window according to the historical interaction behavior of the user with the pop-up window, and determines the second priority of the pop-up window according to the user preference value; or calculates the final priority score of the pop-up window according to the weight of the pop-up window and the user preference value, and determines the third priority of the pop-up window according to the final priority score; and sorts the pop-up windows in the sequence of pop-up windows to be displayed according to any one of the first priority, the second priority and the third priority to generate an ordered pop-up window sequence.

[0261] In some embodiments, Figure 6 The generation module 604 extracts the attribute information of each pop-up window in turn according to the elements in the ordered pop-up window sequence; divides the pop-up window view into a title area, a content area and a bottom button area according to the attribute information, and constrains the layout and style parameters of each area according to the pop-up window style rules; fills the title area, content area and bottom button area with style and content according to the attribute information in the pop-up window description protocol, and generates a corresponding pop-up window instance based on the filled pop-up window view.

[0262] In some embodiments, Figure 6 The display module 605 pops up each pop-up window in sequence according to the order of the pop-up windows in the ordered pop-up window sequence, and sends a notification to the sequence control module after the current pop-up window completes the user response and triggers the close event; after receiving the notification that the current pop-up window is closed, the sequence control module searches for the next pop-up window from the ordered pop-up window sequence and triggers the display of the next pop-up window, so that the next pop-up window is displayed after the current pop-up window is fully responded to and disappears, until all pop-up windows in the ordered pop-up window sequence are displayed.

[0263] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0264] Figure 7Schematic diagram of the structure of the electronic device 7 provided in the embodiment of the present application. Figure 7 As shown, the electronic device 7 of this embodiment includes: a processor 701, a memory 702, and a computer program 703 stored in the memory 702 and executable on the processor 701. When the processor 701 executes the computer program 703, the steps of the above-mentioned method embodiments are implemented. Alternatively, when the processor 701 executes the computer program 703, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0265] For example, the computer program 703 may be divided into one or more modules / units, which are stored in the memory 702 and executed by the processor 701 to implement the present application. The one or more modules / units may be a series of computer program instruction segments capable of implementing specific functions, and the instruction segments are used to describe the execution process of the computer program 703 in the electronic device 7.

[0266] The electronic device 7 may be a desktop computer, a notebook, a PDA, a cloud server or other electronic device. The electronic device 7 may include but is not limited to a processor 701 and a memory 702. Those skilled in the art will understand that Figure 7 It is only an example of the electronic device 7 and does not constitute a limitation of the electronic device 7. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0267] The processor 701 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0268] The memory 702 can be an internal storage unit of the electronic device 7, such as a hard disk or memory of the electronic device 7. The memory 702 can also be an external storage device of the electronic device 7, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the electronic device 7. Furthermore, the memory 702 can include both an internal storage unit of the electronic device 7 and an external storage device. The memory 702 is used to store computer programs and other programs and data required by the electronic device. The memory 702 can also be used to temporarily store data that has been output or is about to be output.

[0269] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0270] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0271] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0272] In the embodiments provided in this application, it should be understood that the disclosed apparatus / computer equipment and methods can be implemented in other ways. For example, the apparatus / computer equipment embodiments described above are merely schematic. For example, the division of modules or units is merely a logical function division. In actual implementation, there may be other division methods. Multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of the apparatus or unit, which may be electrical, mechanical or other forms.

[0273] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0274] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0275] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0276] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A pop-up window management method based on ordered priority control, characterized in that: include: Determine a pop-up window style rule for the pop-up window, and agree with the backend on a pop-up window description protocol based on the pop-up window style rule. The pop-up window description protocol is used to describe attribute information of the pop-up window in a standardized data format; When the application starts, it sends multiple request messages to the backend and filters the pop-up windows that need to be displayed based on the response data returned by the backend to form a sequence of pop-up windows to be displayed; Based on the sequence of pop-up windows to be displayed, determine the priority of each pop-up window according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generate an ordered pop-up window sequence according to the priority; Generating a pop-up window view that complies with the pop-up window style rules according to the pop-up window attribute information in the ordered pop-up window sequence; The pop-up windows in the ordered pop-up window sequence are displayed in sequence. After the current pop-up window completes the user response and disappears, the display of the next pop-up window is triggered according to the order of the pop-up windows in the ordered pop-up window sequence.

2. The method according to claim 1, characterized in that The pop-up window style rule of determining the pop-up window includes: Determine pop-up window style rules for all pop-up windows, including layout and style parameters of the pop-up window title area, content area, and bottom button area; Based on the pop-up window style rules, the layout and style parameters of the pop-up window are abstracted to form a pop-up window base class, which is used to uniformly manage the layout and style filling of the pop-up window.

3. The method according to claim 1, characterized in that The attribute information includes the type of pop-up window, title content and style parameters, prompt content and style parameters, and the action type and style parameters of the bottom button.

4. The method according to claim 1, wherein When the application starts, multiple request messages are sent to the backend, and the pop-up windows to be displayed are filtered out according to the response data returned by the backend to form a sequence of pop-up windows to be displayed, including: When the application is started, multiple display request messages corresponding to the pop-up windows are asynchronously sent to the backend, each display request message corresponding to a pop-up window type; Obtaining response data returned by the backend, wherein the response data includes indication information of whether a corresponding pop-up window needs to be displayed, and filtering out the pop-ups that need to be displayed based on the indication information, and discarding the pop-ups that do not need to be displayed; The pop-up windows to be displayed are organized into the sequence of pop-up windows to be displayed according to the attribute information in the corresponding pop-up window description protocol.

5. The method according to claim 1, wherein Determining the priority of each pop-up window based on the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generating an ordered pop-up window sequence based on the priority, includes: Calculating a weight of the pop-up window based on a proportion of the function affected by the pop-up window in all functions of the application program, and determining a first priority of the pop-up window based on the weight of the pop-up window; Alternatively, a user preference value for the pop-up window is calculated based on historical interaction behaviors between the user and the pop-up window, and a second priority level for the pop-up window is determined based on the user preference value; Alternatively, a final priority score of the pop-up window is calculated according to the weight of the pop-up window and the user preference value, and a third priority of the pop-up window is determined according to the final priority score; The pop-up windows in the sequence of pop-up windows to be displayed are sorted according to any one of the first priority, the second priority, and the third priority to generate the ordered pop-up window sequence.

6. The method according to claim 1, characterized in that Generating a pop-up window view that complies with the pop-up window style rule according to the pop-up window attribute information in the ordered pop-up window sequence includes: Extracting attribute information of each pop-up window in sequence according to the elements in the ordered pop-up window sequence; Divide the pop-up window view into a title area, a content area, and a bottom button area according to the attribute information, and constrain the layout and style parameters of each area according to the pop-up window style rules; According to the attribute information in the pop-up description protocol, the title area, content area and bottom button area are filled with style and content, and based on the pop-up view that has been filled, a corresponding pop-up instance is generated.

7. The method according to claim 1, characterized in that The sequentially displaying the pop-up windows in the ordered pop-up window sequence, and triggering the display of the next pop-up window according to the order of the pop-up windows in the ordered pop-up window sequence after the current pop-up window completes the user response and disappears, includes: Pop up each pop-up window in sequence according to the pop-up window order in the ordered pop-up window sequence, and send a notification to the sequence control module after the current pop-up window completes the user response and triggers a close event; After receiving the notification that the current pop-up window is closed, the sequence control module searches for the next pop-up window from the ordered pop-up window sequence and triggers the display of the next pop-up window, so that the next pop-up window is displayed after the current pop-up window is fully responded and disappears, until all pop-up windows in the ordered pop-up window sequence are displayed.

8. A pop-up window management device based on ordered priority control, characterized in that: include: A style rule determination module determines a pop-up window style rule for the pop-up window, and agrees on a pop-up window description protocol with the backend based on the pop-up window style rule. The pop-up window description protocol is used to describe the attribute information of the pop-up window in a standardized data format; The acquisition module sends multiple request messages to the backend when the application starts, and filters the pop-up windows that need to be displayed based on the response data returned by the backend, forming a sequence of pop-up windows to be displayed; A priority determination module, based on the sequence of pop-up windows to be displayed, determines the priority of each pop-up window according to the weight of the pop-up window's impact on the function and / or the user's historical interaction behavior, and generates an ordered sequence of pop-up windows according to the priority; A generating module, which generates a pop-up window view that complies with the pop-up window style rules according to the pop-up window attribute information in the ordered pop-up window sequence; The display module displays the pop-up windows in the ordered pop-up window sequence in sequence, and after the current pop-up window completes the user response and disappears, triggers the display of the next pop-up window according to the order of the pop-up windows in the ordered pop-up window sequence.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images