Page display processing method and system, electronic equipment and program product

Abstract

The invention provides a page display processing method and system, electronic equipment and a program product, and the method comprises the steps: obtaining a target page identifier corresponding to a target application page in response to a monitored application page switching event of a target application, the target application page being an application page displayed after page switching; based on the target page identifier, target component configuration items corresponding to the target page identifier are obtained from preset configuration content corresponding to different page types, and the preset configuration content corresponding to each page type comprises a mapping relation between a page identifier corresponding to an application page of a component needing to be displayed and the component configuration items; and in response to successful acquisition of the target component configuration item, displaying the target component content corresponding to the target component configuration item in the target application page based on the target component configuration item, so that corresponding prompt or guide information can be accurately displayed according to the real-time application page currently used by the user, and the accuracy of displaying the component content of the page is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the computer technology field, and particularly relates to a page display processing method and system, an electronic device and a program product. BACKGROUND

[0002] With the continuous enrichment of the functions of mobile applications, the user interface becomes more and more complex, and when the application is updated, the guide information about the new function usually needs to be displayed, and in some user pages, there is usually a need to display some prompt information.

[0003] In the related art, the guide or prompt is usually performed by a fixed page or by a centralized message center. The method adopted in the related art cannot be adjusted in real time according to user behavior, cannot provide accurate guidance, and in the case of function iteration and update, the business code needs to be constantly modified to implant the prompt logic, which has a high development cost and low efficiency. SUMMARY

[0004] The embodiments of the present disclosure provide a page display processing method, system, electronic device and program product to solve the above technical problems to some extent.

[0005] In one aspect of the embodiments of the present disclosure, a page display processing method is provided, and the method comprises: In response to monitoring an application page switching event of a target application, a target page identifier corresponding to a target application page is acquired, the target application page being an application page displayed after page switching; Based on the target page identifier, a target component configuration item corresponding to the target page identifier is acquired from preset configuration content corresponding to different page types, wherein the preset configuration content corresponding to each page type comprises a mapping relationship between a page identifier corresponding to an application page requiring to display a component and a component configuration item; In response to successfully acquiring the target component configuration item, based on the target component configuration item, target component content corresponding to the target component configuration item is displayed in the target application page.

[0006] In one exemplary embodiment, the acquiring, based on the target page identifier, of the target component configuration item from the preset configuration content corresponding to different page types comprises: Based on an identifier type of the target page identifier, a target page type corresponding to the identifier type is determined, wherein different page types correspond to different identifier types; Based on the target page identifier, the target page identifier is searched in preset configuration content corresponding to the target page type to obtain a search result; In response to the search result indicating that the target page identifier exists in preset configuration content corresponding to the target page type, a target component configuration item corresponding to the target page identifier in the preset configuration content corresponding to the target page type is acquired.

[0007] In one example embodiment, the target page type corresponding to the identification type of the target page identifier is determined based on the target page identifier. The target page type corresponding to the identification type of the target page identifier is determined based on a preset mapping relationship between different identification types and different page types, the different page types including at least one of a plurality of native page types and a plurality of non-native page types.

[0008] In one example embodiment, the target component content corresponding to the target component configuration item is displayed in the target application page based on the target component configuration item. A display condition verification is performed based on a target display condition required for displaying the target component content indicated by the target component configuration item, and a condition verification result is obtained. In response to the condition verification result indicating that the target display condition is met, the target component content is displayed in the target application page.

[0009] In one example embodiment, the display condition verification based on the target display condition required for displaying the target component content indicated by the target component configuration item includes: In response to the target display condition required for displaying the target component content indicated by the target component configuration item including a multi-dimensional display condition, multi-dimensional information is acquired based on the multi-dimensional display condition. For any dimensional information, display condition verification is performed based on the display condition of the corresponding dimension, and the condition verification result is obtained. In response to the condition verification result indicating that the display condition is met, the target component content is displayed in the target application page. In response to the condition verification result indicating that the multi-dimensional display condition is met, the target component content is displayed in the target application page.

[0010] In one example embodiment, in response to the condition verification result indicating that the target display condition is met, the target component content is displayed in the target application page. In response to the condition verification result indicating that the target display condition is met, component content required to be displayed in the target application page and a component type of the target component are acquired. Based on the component type and the component content, render target component content, and display the target component content in the target application page.

[0011] In one exemplary embodiment, the target page identifier corresponding to the target application page is acquired, including: In response to monitoring the application page switching event of the target application, a target page display method is executed to display the target application page and acquire the target page identifier, and the target page display method includes page display logic and page identifier acquisition logic.

[0012] Another aspect of the embodiment provides a page display processing system, characterized in that the system includes: The monitoring module is configured to acquire a target page identifier corresponding to a target application page in response to monitoring an application page switching event of a target application, the target application page being an application page displayed after page switching. The business module is configured to acquire a target component configuration item corresponding to the target page identifier based on the target page identifier in preset configuration content corresponding to different page types, wherein the preset configuration content corresponding to each page type includes a mapping relationship between a page identifier corresponding to an application page requiring to display a component and a component configuration item. The display module is configured to display target component content corresponding to the target component configuration item in the target application page based on the target component configuration item in response to successfully acquiring the target component configuration item.

[0013] In one exemplary embodiment, the monitoring module includes a native page monitoring unit and a non-native page monitoring unit; the native page monitoring unit is configured to acquire a page identifier corresponding to a native page; and the non-native page monitoring unit is configured to acquire a page identifier corresponding to a non-native page. The business module includes a rule matching engine unit and a content loading management unit; the rule matching engine unit is configured to acquire a target component configuration item corresponding to the target page identifier based on the target page identifier in preset configuration content corresponding to different page types; and the content loading management unit is configured to provide the target component configuration item to the display module. The display module includes a content rendering unit, which is configured to acquire the target component configuration item from the content loading management unit and render target component content based on the target component configuration item.

[0014] Another aspect of the embodiment provides an electronic device, including: A memory configured to store a computer program. The processor is configured to execute a computer program stored in the memory, and the computer program, when executed, implements the page display processing method of any of the above embodiments.

[0015] In another aspect of the embodiment, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. The computer program, when executed by a processor, implements the page display processing method of any of the above embodiments.

[0016] In another aspect of the embodiment, a computer program product is provided, and the computer program product includes a computer program. The computer program, when executed by a processor, implements the page display processing method of any of the above embodiments.

[0017] In the embodiment of the present disclosure, for different page types, the related preset configuration content required for displaying the page component content is pre-configured, and the preset configuration content corresponding to each page type includes the mapping relationship between the page identifier of the application page in the application page corresponding to the page type and the component configuration item. When the application page switching event of the target application is monitored, the target page identifier corresponding to the target application page after switching is obtained, and based on the target page identifier, the target component configuration item corresponding to the target page identifier can be obtained from the preset configuration content corresponding to different page types. If the target component configuration item is successfully obtained, the target component content corresponding to the target component configuration item can be displayed in the target application page based on the target component configuration item. Therefore, based on the unified configuration of the mapping relationship between the component to be displayed and the application page of different types, when the application page of the target application is switched to any type of application page that needs to display component content, the corresponding component configuration item can be obtained from the preset configuration content, and the corresponding page component content can be displayed based on the component configuration item. Therefore, the application page of any page type can display the required page component content, so that the corresponding prompt or guidance information can be accurately displayed according to the real-time application page currently used by the user, and the accuracy of displaying the page component content is improved.

[0018] In addition, by pre-configuring the mapping relationship between the application page and the display component content, the original business code does not need to be modified, which can reduce the development cost and risk, and help to improve the display processing efficiency of the page component content. Moreover, the preset configuration content can be flexibly modified, which helps to improve the efficiency of modifying, adding, deleting and other operations of processing the page component content, and realizes the flexible display of the page component content.

[0019] The technical solutions of the present disclosure will be further described in detail below with reference to the drawings and embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0021] The present disclosure can be more clearly understood and appreciated from the following detailed description, taken in conjunction with the following drawings of which: Figure 1 A flowchart of a page display processing method provided for an exemplary embodiment of the present disclosure; Figure 2 A flowchart of obtaining a target component configuration item provided for another exemplary embodiment of the present disclosure; Figure 3 A flowchart of displaying page component content provided for an exemplary embodiment of the present disclosure; Figure 4 A flowchart of displaying page component content provided for yet another exemplary embodiment of the present disclosure; Figure 5 A flowchart of a page display processing method provided for yet another exemplary embodiment of the present disclosure; Figure 6 A display schematic diagram of page component content provided for an exemplary embodiment of the present disclosure; Figure 7 A flowchart of obtaining page route information of a Flutter page provided for an exemplary embodiment of the present disclosure; Figure 8 A flowchart of displaying page component content in a Flutter page provided for an exemplary embodiment of the present disclosure; Figure 9 A structural schematic diagram of a page display processing system provided for an exemplary embodiment of the present disclosure; Figure 10 A structural schematic diagram of a page display processing system provided for another exemplary embodiment of the present disclosure; Figure 11 A structural schematic diagram of an electronic device provided for an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] Various exemplary embodiments of the present disclosure will now be described in detail below with reference to the accompanying drawings. Note that the relative arrangement, numerical expressions, and values of components and steps set forth in these embodiments do not limit the scope of the present disclosure unless otherwise specifically stated.

[0023] Those skilled in the art can understand that the terms "first", "second", and the like in the embodiments of the present disclosure are only used to distinguish different steps, devices, or modules, and do not represent any specific technical meaning, nor do they represent a necessary logical sequence between them.

[0024] It should also be understood that, in the embodiments of the present disclosure, "multiple" can refer to two or more, and "at least one" can refer to one, two or more.

[0025] It should also be understood that, for any component, data or structure mentioned in the embodiments of the present disclosure, one or more can be generally understood without explicit limitation or in the context of the opposite implication.

[0026] In addition, the term "and / or" in the present disclosure is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " in the present disclosure generally represents an "or" relationship between the front and rear associated objects.

[0027] It should also be understood that the description of the embodiments of the present disclosure focuses on the differences between the embodiments, and the same or similar parts can be referred to each other, and for the sake of brevity, will not be repeated.

[0028] At the same time, it should be understood that, for the convenience of description, the size of each part shown in the drawings is not drawn according to the actual proportional relationship.

[0029] The following description of at least one example embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application or uses.

[0030] Techniques, methods, and devices known to those of ordinary skill in the relevant art can not be discussed in detail, but should be considered part of the specification where appropriate.

[0031] It should be noted that: similar labels and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0032] The embodiments of the present disclosure can be applied to terminal devices, computer systems, servers and other electronic devices, which can operate with many other general or special computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments and / or configurations suitable for use with terminal devices, computer systems, servers and other electronic devices include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, small computer systems, large computer systems and distributed cloud computing technology environments including any of the above systems, etc.

[0033] Electronic devices such as terminal devices, computer systems, and servers can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Typically, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer systems / servers can be implemented in distributed cloud computing environments, where tasks are executed by remote processing devices linked through communication networks. In distributed cloud computing environments, program modules can reside on local or remote computing system storage media, including storage devices.

[0034] In related technologies, guidance or prompts are usually pushed through fixed onboarding pages, push notifications, or centralized message centers. These methods cannot be adjusted according to real-time user behavior, cannot provide accurate guidance to users, and require modification of the original business code, resulting in poor configuration flexibility. With feature iteration and updates, the code needs to be modified multiple times to incorporate the prompt logic, leading to high development costs.

[0035] In this embodiment of the disclosure, the mapping relationship between the component content to be displayed (such as components including prompt information) and the application page can be pre-configured. The mapping relationship between various types of application pages and page component content can be configured. When the application page of the target application switches to the corresponding application page, the corresponding component content can be displayed to provide accurate guidance to the user.

[0036] In one possible embodiment, the embodiments of this disclosure can be applied to any scenario where page component content needs to be displayed, such as scenarios where an application releases new features, important notification reminders, marketing campaign promotions, operation guidance, version iteration notifications, and personalized content recommendations. In these scenarios, the page component content used to display corresponding prompts, guidance, or recommendation information can be processed and displayed based on the methods provided in the embodiments of this disclosure.

[0037] like Figure 1 The diagram illustrates a flowchart of a page display processing method provided by an exemplary embodiment of this disclosure. The method provided in this disclosure can be used in the electronic devices described in the above embodiments, such as... Figure 1 As shown, it includes the following steps 110-130: Step 110: In response to detecting the application page switching event of the target application, obtain the target page identifier corresponding to the target application page.

[0038] In a possible implementation, the monitoring of the page life cycle can be performed for any application page of the target application, including the process from the creation of the page to the destruction of the page. Optionally, the target application can be an application currently used by the user, that is, an application currently running in the foreground. Optionally, if the creation event of the target application page is monitored, the application page switching event of the target application can be considered to be monitored, and the target page identifier of the newly created (that is, the page to be displayed after switching) target application page is obtained. That is, the target application page is the page to be displayed after switching corresponding to the application page switching event.

[0039] Optionally, the target page identifier is a page identifier used to uniquely identify the target application page. In a possible implementation, different types of application pages use different types of identifiers to uniquely identify the pages, and when the target page identifier corresponding to the target application page is obtained, the target page identifier of the corresponding type can be obtained according to the page type of the target application page.

[0040] In an example, different types of page identifiers are used for different page types in the target application, such as native pages, Flutter pages, Web pages, and the like. For example, the file name or class name can be used as the page identifier for a native page; the page route can be used as the page identifier for a Flutter page; and the page address can be used as the page identifier for a Web page.

[0041] In a possible implementation, the target page identifier used to uniquely identify the target application page can be obtained according to the identifier type corresponding to the page type of the target application page in the preconfigured configuration. In an example, if the target application page is a native page type, the file name or class name corresponding to the target application page can be obtained as the target page identifier.

[0042] In step 120, the target component configuration item corresponding to the target page identifier is obtained from the preset configuration content corresponding to different page types based on the target page identifier.

[0043] Optionally, the mapping relationship between the page identifier and the component configuration item of the application page that needs to display the page component content is included in the preset configuration content corresponding to each page type. In the embodiment of the present disclosure, the page component content can be content displayed on the application page, such as a floating layer, a pop-up window, or a content layer fixed on the page.

[0044] Optionally, different page component contents can be displayed in different types of application pages, and for any page type, corresponding preset configuration content can be preconfigured. The preset configuration content corresponding to a page type can include a mapping relationship between a page identifier of an application page in which the page component content needs to be displayed and a component configuration item corresponding to the corresponding component content. The identifier type of the page identifier included in the preset configuration content corresponding to a page type corresponds to the page type. For example, the identifier type of the page identifier included in the preset configuration content corresponding to the native page type is a file name or a class name. The preset configuration content corresponding to the native page type can include a mapping relationship between a page identifier of a native page in which the page component content needs to be displayed and a component configuration item corresponding to the corresponding page component content.

[0045] Optionally, the component configuration item corresponding to a page component content can include display configuration information corresponding to the page component content, and the display configuration information can include at least one of component display content, component display mode, and component display type.

[0046] In a possible implementation, since the target application page can be any type of application page, after obtaining the target page identifier corresponding to the target application page, the target component configuration item corresponding to the target page identifier can be obtained from the preset configuration content corresponding to different page types that have been configured. Optionally, the target component configuration item corresponding to the target page identifier can be found in the preset configuration content corresponding to different page types based on the target page identifier.

[0047] Step 130, in response to successfully obtaining the target component configuration item, displaying the target component content corresponding to the target component configuration item in the target application page based on the target component configuration item.

[0048] In a possible implementation, if the target component configuration item corresponding to the target page identifier is successfully obtained from the preset configuration content corresponding to different page types, the corresponding target component content can be displayed in the target application page based on the display configuration information included in the target component configuration item, and the target component content is generated based on the configuration content included in the target component configuration item. For example, if the display configuration information included in the target component configuration item includes component display content, component display mode, and component display type, the corresponding target component content can be generated based on the component display content and the component display type, and the target component content can be displayed in the target application page based on the corresponding component display mode.

[0049] In a possible implementation, the target application page can not be configured with a corresponding target component configuration item, i.e., the target application page does not have a corresponding requirement of displaying page component content. If the target component configuration item corresponding to the target application page is not obtained, the target application can continue to be monitored, and when the next application page switching event is monitored, the page identifier of the application page after switching is re-obtained, and the corresponding component configuration item is obtained. That is, in the embodiment of the present disclosure, for any application page (including various types of application pages), when the application page is displayed, the page identifier of the application page can be used to obtain the component configuration item corresponding to the page identifier in the preset configuration content corresponding to different page types. If the corresponding component configuration item exists, the corresponding target component content can be displayed based on the component configuration item, so that the prompt information that needs to be prompted can be displayed according to the application page used by the user in real time.

[0050] In the embodiment of the present disclosure, for different page types, the related preset configuration content required for displaying page component content is pre-configured, and the preset configuration content corresponding to each page type includes the mapping relationship between the page identifier of the application page in the application page corresponding to the page type and the component configuration item. When the application page switching event of the target application is monitored, the target page identifier corresponding to the target application page after switching is obtained, and based on the target page identifier, the target component configuration item corresponding to the target page identifier can be obtained in the preset configuration content corresponding to different page types. If the target component configuration item is successfully obtained, the target component content corresponding to the target component configuration item can be displayed in the target application page based on the target component configuration item. Therefore, based on the unified configuration of the mapping relationship between the component to be displayed and the application page of different types, when the application page of the target application is switched to any type of application page that needs to display the component, the corresponding component configuration item can be obtained in the preset configuration content, so that the corresponding page component content can be displayed based on the component configuration item, so that the application page of any page type can display the page component content that needs to be displayed, so that the corresponding prompt or guidance information can be accurately displayed according to the real-time application page currently used by the user, and the accuracy of displaying the page component content is improved.

[0051] In addition, by pre-configuring the mapping relationship between the application page and the display component content, the original business code does not need to be modified, the development cost and risk can be reduced, and the display processing efficiency of the page component can be improved. Moreover, the preset configuration content can be flexibly modified, which helps to improve the efficiency of modifying, adding, deleting and other operations of processing the page component, and realizes flexible display of the page component.

[0052] In a possible implementation, on the basis of the above embodiment, as shown in Figure 2 The step 120 can include the following steps 1201-1203. In step 1201, a target page type corresponding to an identification type of the target page identification is determined based on the identification type of the target page identification.

[0053] Optionally, different page types correspond to different identification types. For example, the identification type corresponding to the native page type is a file name or a class name, and the identification type corresponding to the Flutter page is a page route. After obtaining the target page identification, the target page type corresponding to the identification type of the target page identification can be determined based on the identification type of the target page identification.

[0054] In a possible implementation, a mapping relationship between different page types and different identification types is pre-configured. For example, a developer can establish a mapping relationship between different page types and different identification types according to a page identification type used when developing different page types.

[0055] In a possible implementation, different page types can include a native page type and a non-native page type. The native page type can be a page developed based on a device-based operating system, for example, a page developed based on an ios system or an Android system. The non-native page type can be a page developed using other technologies, for example, a Flutter page developed based on a Flutter framework or a Web page developed based on Web technology.

[0056] Optionally, different page types can include multiple native page types, and the multiple native page types can include native page types developed based on different types of operating systems, for example, a native page type based on an ios system and a native page type based on an Android system. Optionally, different page types can also include multiple non-native page types, for example, a Flutter page type developed based on a Flutter framework and a Web page type developed based on Web technology.

[0057] In a possible implementation, different native page types can correspond to different identification types, i.e., different identification types of page identifications adopted by various native page types, for example, different identification types corresponding to an ios system-based native page type and an Android system-based native page type. Different non-native page types can correspond to different identification types, i.e., different identification types of page identifications adopted by various non-native page types, for example, different identification types corresponding to a Flutter framework-based Flutter page type and a Web technology-based Web page type. Optionally, a mapping relationship between various different page types (including multiple native page types and multiple non-native page types) and identification types can be preconfigured, and after determining the identification type of the target page identification, the target page type corresponding to the identification type of the target page identification can be determined based on the preset mapping relationship between different identification types and different page types.

[0058] In step 1202, the target page identification is searched in the preset configuration content corresponding to the target page type based on the target page identification, and a search result is obtained.

[0059] After determining the target page type corresponding to the target page identification, it can be determined whether the target page identification exists in the preset configuration content corresponding to the target page type based on the target page identification.

[0060] For example, if it is determined that the target page identification is a page route, the corresponding target page type is a Flutter page type, and it can be determined whether the target page identification exists in the preset configuration content corresponding to the Flutter page type based on the target page identification.

[0061] In step 1203, in response to the search result indicating that the target page identification exists in the preset configuration content corresponding to the target page type, the target component configuration item corresponding to the target page identification in the preset configuration content corresponding to the target page type is obtained.

[0062] If it is determined that the target page identification exists in the preset configuration content corresponding to the target page type, it indicates that the target application page needs to display corresponding target component content, and the target component configuration item corresponding to the target page identification can be obtained from the corresponding preset configuration content to display the target component content based on the target component configuration item.

[0063] In this embodiment, whether the target page identification exists in the preset configuration content of the corresponding target page type can be determined according to the identification type of the target page identification, and if the target page identification exists, the corresponding target component configuration item can be obtained, which helps to improve the efficiency and further helps to improve the display processing efficiency of the page component content.

[0064] On the basis of the above embodiments, as shown in Figure 3 The step 130 can include steps 1301-1302 as follows: In step 1301, based on the target display condition indicated by the target component configuration item and required for displaying the target component content, display condition verification is performed to obtain a condition verification result.

[0065] In one possible implementation, the target component configuration item can include a target display condition required for displaying the target component content. Optionally, the target display condition can include at least one of a page path condition, a time window condition, a geographic location condition, a device version condition, and a user role condition.

[0066] In one possible implementation, if the target component configuration item includes a target display condition required for displaying the target component content, information for verifying whether the target display condition is met can be obtained first, and based on the obtained information, display condition verification is performed to obtain a condition verification result.

[0067] In one possible implementation, if the target component configuration item does not include a target display condition, the target component configuration item can directly display the target component content in the target application page.

[0068] In one possible implementation, in response to the target display condition indicated by the target component configuration item and required for displaying the target component content including a multi-dimensional display condition, multi-dimensional information is obtained based on the multi-dimensional display condition. For any dimension information, display condition verification is performed based on the display condition of the corresponding dimension to obtain a condition verification result.

[0069] That is, in the case where the target display condition includes a multi-dimensional display condition, information for verifying the display condition of each dimension (i.e., multi-dimensional information) can be obtained respectively, so that based on any dimension information obtained, display condition verification is performed based on the display condition of the corresponding dimension to obtain a condition verification result.

[0070] Optionally, the multi-dimensional display condition can include multiple conditions of a page path condition, a time window condition, a geographic location condition, a device version condition, and a user role condition. The page path condition is a path condition required for the path of an application page jumping to a display page component content to meet. The time window condition is a time period required for the display of a page component content, for example, from May 1 to May 10. The geographic location condition is a geographic location limit range for displaying a page component content, for example, only A city and B city. The device version condition is a device version required for displaying a page component content, for example, the device version corresponding to the target application needs to reach the latest version. The user role condition can be a use role limit condition of the target application corresponding to the display of a page component content.

[0071] In a possible implementation, if the target display condition includes a page path condition, a page jump path corresponding to the target application page can be acquired to verify the page path condition and determine whether it is consistent with the page path indicated by the page path condition. If the target display condition includes a time window condition, time information corresponding to the target application page can be acquired to verify the time window condition and determine whether it is within the required display time period. If the target display condition includes a geographic location condition, geographic location information of the electronic device corresponding to the target application can be acquired to verify whether it is within the geographic location limit range of the display page component content. If the target display condition includes a device version condition, device version information corresponding to the target application can be acquired to determine whether the device version required for displaying the target component content is reached, and the device version condition is verified. If the target display condition includes a user role condition, user role information of the currently logged-in user of the target application can be acquired to verify the user role condition.

[0072] In step 1302, in response to the condition verification result indicating that the target display condition is met, the target component content is displayed in the target application page.

[0073] In a possible implementation, if the condition verification result indicates that the target display condition is met, it is determined that the display condition for displaying the target component content is currently met, and the target component content can be displayed in the target application page.

[0074] In this embodiment, the target component configuration item can be preconfigured with a display condition for displaying the corresponding page component content. After the target component configuration item is successfully acquired in the target page type based on the target page identifier, the display condition indicated by the target component configuration item can be verified first, and the target component content is displayed in the case where the display condition is met. In this way, by setting the target display condition for displaying the target component content, the target component content can be displayed in the target application page according to the state of the user using the target application page (for example, the page path, the time, the geographic location, the device version, and the user role), and the precise display of the page component content is realized, and precise prompt information is provided for the user.

[0075] In a possible implementation, as shown in Figure 4 The step 1302 can include steps 1320-1321 as follows: In step 1320, in response to the condition verification result indicating that the target display condition is met, the component content to be displayed in the target application page and the component type of the target component are acquired.

[0076] In a possible implementation, if the condition verification result indicates that the target display condition is met, the component content to be displayed and the component type can be obtained from the target component configuration item.

[0077] In a possible implementation, if the target display condition includes a multi-dimensional condition and the condition verification result indicates that the multi-dimensional display condition is met, the target component content can be displayed in the target application page. The multi-dimensional condition is met if any one of the dimensions of the condition is met.

[0078] Optionally, if the target component configuration item does not include the component type to be used by the target component, a preset default component type can be obtained. Optionally, the default component type can include a floating ball, a pop-up window, and the like.

[0079] In step 1321, the target component content is rendered based on the component type and the component content, and the target component content is displayed in the target application page.

[0080] After obtaining the component type and the component content, the target component content conforming to the component type and including the component content can be rendered, and the target component content is displayed in the target application page.

[0081] In a possible implementation, as shown in Figure 5 In the display process of the page component content, after obtaining the target page identifier of the target application page in the target application, the matching component configuration item can be found in the preset configuration content. The matching component configuration item can be found in the preset configuration content of the corresponding page type according to the identifier type of the target page identifier. If the matching is successful, the time window condition, the geographic location condition, and the device version condition included in the matching component configuration item are used to verify the time window, the geographic location, and the device version, respectively. Under the condition that all the display conditions are verified, the target application can send a request to the preset component interface to obtain the corresponding component content, and then render the corresponding page component content based on the obtained component content. Optionally, if the component type is not specified, a floating ball, a pop-up window, or the like can be rendered. As shown in Figure 6 Based on the obtained component content, the floating ball component can be rendered, and the floating ball component content 61 can be displayed in the target application page. Alternatively, based on the obtained component content, the pop-up window component can be rendered, and the pop-up window component content 62 can be displayed in the target application page. Optionally, based on the component content to be displayed, a plurality of types of target component content can be rendered, for example, a component including a floating ball type and a pop-up window type. Different types of target component content can be switched with each other, for example, the floating ball type component content and the pop-up window type component content can be switched with each other.

[0082] In a possible implementation, as shown in Figure 5As shown, if the target page identifier is successfully matched, but any condition is not met, i.e., there is a condition that is not verified, the display process of the page component can be aborted. If the target page identifier fails to be matched, the corresponding unmapping log can be recorded.

[0083] In a possible implementation, after displaying the target component content, a user interaction behavior of the user interacting with the target component content can be acquired, and the component display strategy configuration can be optimized based on the user interaction behavior. Optionally, the user interaction behavior can include user interaction time, user interaction times, and user interaction position, etc. Optionally, it can be determined that the target component content is validly displayed according to the user interaction behavior, for example, the user interaction time exceeds a preset time, the user interaction times exceeds a preset number, or the user interaction position is in a valid position, etc. If the user interaction behavior indicates that the target component content is invalidly displayed, a prompt information can be generated to prompt to optimize the display configuration strategy of the target component content.

[0084] In a possible implementation, to facilitate acquiring the target page identifier of the target application page, a method replacement technology can be used to replace the display method of the application page to add page identifier acquisition logic, so that the corresponding page identifier can be acquired when each application page of the target application is displayed.

[0085] Optionally, the method replacement technology can be a Method Swizzling technology. Optionally, the original method of displaying the application page can be replaced by the method replacement technology, for example, the viewwillAppear method can be replaced, and the page identifier acquisition method can be added on the basis of the original method of displaying the application page, so that the corresponding page identifier can be acquired when any application page is displayed.

[0086] In a possible implementation, in response to monitoring the application page switching event of the target application, a target page display method is executed to display the target application page and acquire the target page identifier, and the target page display method includes page display logic and page identifier acquisition logic. The executed target page display method can be a display method obtained by replacing the original page display method by using the method replacement technology. The target page display method obtained by replacement includes the page display logic included in the original page display method and the newly added page identifier acquisition logic.

[0087] In this embodiment, the page display method is replaced by using the method replacement technology to add the page identifier acquisition logic therein, so that the corresponding page identifier can be acquired when any application page is displayed, without modifying the business logic code, avoiding the influence of acquiring the page identifier on the original page display, and realizing the lightweight acquisition of the page identifier.

[0088] In a possible implementation, if the page type of the application page includes the native page type and the Flutter type, the page route of the Flutter page can be obtained through the Flutter routing layer, and the page class name of the native page can be obtained through the native monitoring layer. Optionally, page identification obtaining logic can be added in the page display method corresponding to the Flutter page and the native page, respectively, to realize identification monitoring and obtaining of any page.

[0089] In a possible implementation, as shown in Figure 7 FIG. 1 is a flowchart illustrating a process of displaying page component content in a Flutter page. The Flutter routing layer can monitor a route change event, and when the route change event is detected, the Flutter routing layer can send a route event to the notification bridging layer. The notification bridging layer is used for message transmission between the Flutter routing layer and the native monitoring layer. The notification bridging layer can forward the route event to the native monitoring layer, and the native monitoring layer can forward the route event to the business module. The business module can obtain the route information, that is, obtain the page identification, and then execute a page component content display process based on the page identification.

[0090] In a possible implementation, as shown in Figure 8 FIG. 2 is a flowchart illustrating a process of displaying page component content in a Flutter page. The process includes the following steps: Step 801, initializing a Flutter application.

[0091] Initializing the Flutter application means performing an initialization operation of starting the Flutter application, and starting the Flutter application.

[0092] Step 802, initializing route monitoring.

[0093] That is, page identification obtaining logic is added in the page display method of the Flutter application to realize route monitoring.

[0094] Step 803, monitoring a route event.

[0095] After initializing the route monitoring, the route change event can be monitored.

[0096] Step 804, sending a message notification.

[0097] In the case of monitoring the route change event, a corresponding message can be sent to the native monitoring layer. Different route events can be notified through different message channels. For example, the route event is a Push event, a Push notification can be sent through a Push channel, the route event is a Pop event, a Pop notification can be sent through a Pop channel, the route event is an Appear event, an Appear notification can be sent through an Appear channel, and the route event is a Disappear event, a Disappear notification can be sent through a Disappear channel.

[0098] In step 805, the native monitoring layer receives the message notification.

[0099] In step 806, the route state is updated.

[0100] The native monitoring layer can update the route state based on the received message. Based on the updated route state, the page identifier is obtained.

[0101] In step 807, it is determined whether there is a matching rule. If yes, step 808 is performed, and if no, the process ends.

[0102] After obtaining the page identifier, it can be determined whether there is a matching rule in the preset configuration content of different page types, i.e., whether there is a corresponding target component configuration item.

[0103] In step 808, the component content is displayed.

[0104] If there is, the corresponding component can be displayed based on the target component configuration item.

[0105] In step 809, the interaction behavior is counted.

[0106] In step 810, the component strategy is optimized.

[0107] After displaying the component, the user interaction behavior of the user and the component can be counted, and the component strategy of the component display can be optimized based on the user interaction behavior.

[0108] In this embodiment, when monitoring the page, the complete life cycle event can be monitored, including monitoring the complete life cycle events such as page switching, page creation, and disappearance, so as to determine whether to display the page component content based on accurate context information, which helps to improve the accuracy of page component content display.

[0109] In one possible implementation, as shown in Figure 9 FIG. 1 shows a structural schematic diagram of a page display processing system provided by an example embodiment of the present disclosure. The page display processing system can be deployed in the electronic device described above, and is used to implement the page display processing method described in any of the above embodiments. The system includes: The monitoring module 910 is configured to, in response to monitoring an application page switching event of a target application, acquire a target page identifier corresponding to a target application page, the target application page being an application page displayed after the page switching; The business module 920 is configured to, based on the target page identifier, acquire a target component configuration item corresponding to the target page identifier from preset configuration content corresponding to different page types, wherein the preset configuration content corresponding to each page type comprises a mapping relationship between a page identifier of an application page requiring to display a component and a component configuration item. The display module 930 is configured to, in response to successfully acquiring the target component configuration item, display target component content corresponding to the target component configuration item in the target application page based on the target component configuration item.

[0110] In an exemplary embodiment, as shown in Figure 10 The monitoring module 910 comprises a native page monitoring unit and a non-native page monitoring unit; the native page monitoring unit is configured to acquire a page identifier corresponding to a native page; and the non-native page monitoring unit is configured to acquire a page identifier corresponding to a non-native page. In an exemplary embodiment, as shown in Figure 10 The business module 920 comprises a rule matching engine unit and a content loading management unit; the rule matching engine unit is configured to, based on the target page identifier, acquire a target component configuration item corresponding to the target page identifier from preset configuration content corresponding to different page types; and the content loading management unit is configured to provide the target component configuration item to the display module. In an exemplary embodiment, as shown in Figure 10 The display module 930 comprises a content rendering unit, which is configured to acquire a target component configuration item from the content loading management unit and render target component content based on the target component configuration item.

[0111] Optionally, the display module 930 further comprises a floating ball management unit and a pop-up window management unit, which can be used to manage the rendering process of a floating ball component and the rendering process of a pop-up window component, respectively.

[0112] In an exemplary embodiment, the rule matching engine unit is further configured to: determine a target page type corresponding to an identifier type of the target page identifier based on the identifier type of the target page identifier; find the target page identifier in preset configuration content corresponding to the target page type based on the target page identifier to obtain a finding result; and In response to the search result indicating that the target page identifier exists in preset configuration content corresponding to the target page type, a target component configuration item corresponding to the target page identifier in the preset configuration content corresponding to the target page type is acquired.

[0113] In one exemplary embodiment, the rule matching engine unit is further configured to: Based on a preset mapping relationship between different identifier types and different page types, a target page type corresponding to an identifier type of the target page identifier is determined, the different page types including at least one of a plurality of native page types and a plurality of non-native page types.

[0114] In one exemplary embodiment, the rule matching engine unit is further configured to: Based on a target display condition required to display the target component content indicated by the target component configuration item, display condition verification is performed to obtain a condition verification result; In one exemplary embodiment, as Figure 10 The content rendering unit is further configured to: In response to the condition verification result indicating that the target display condition is met, the target component content is displayed in the target application page.

[0115] In one exemplary embodiment, the rule matching engine unit is further configured to: In response to the target display condition required to display the target component content indicated by the target component configuration item including a multi-dimensional display condition, multi-dimensional information is respectively acquired based on the multi-dimensional display condition; For any dimensional information, display condition verification is performed based on the display condition of the corresponding dimension to obtain the condition verification result; In one exemplary embodiment, the content rendering unit is further configured to: In response to the condition verification result indicating that the multi-dimensional display condition is met, the target component content is displayed in the target application page.

[0116] In one exemplary embodiment, the content rendering unit is further configured to: In response to the condition verification result indicating that the target display condition is met, component content required to be displayed in the target application page and a component type of the target component are acquired; Based on the component type and the component content, target component content is rendered, and the target component content is displayed in the target application page.

[0117] In one exemplary embodiment, the monitoring module 910 is further configured to: In response to monitoring the application page switching event of the target application, a target page display method is executed to display the target application page and obtain the target page identifier, the target page display method including page display logic and page identifier obtaining logic.

[0118] In one example embodiment, as shown in FIG. 9, the monitoring module 910 includes native page monitoring and non-native page monitoring, which can respectively obtain the page identifier of the native page and the page identifier of the non-native page to determine whether to display the page component content based on the page identifier. Figure 10

[0119] In one example embodiment, as shown in FIG. 9, the business module 920 further includes a content loading management unit, and when the content rendering unit included in the display module 930 renders the component, the content loading management unit included in the business module 920 can be used to obtain the component content for rendering. Optionally, the display module 930 further includes a floating ball management unit and a pop-up window management unit, which can be respectively used to manage the rendering process of the floating ball component and the rendering process of the pop-up window component. Figure 10

[0120] In one example embodiment, as shown in FIG. 9, the business module 920 further includes a content loading management unit, and when the content rendering unit included in the display module 930 renders the component, the content loading management unit included in the business module 920 can be used to obtain the component content for rendering. Optionally, the display module 930 further includes a floating ball management unit and a pop-up window management unit, which can be respectively used to manage the rendering process of the floating ball component and the rendering process of the pop-up window component. Figure 10

[0121] The page display processing system in the embodiments of the present disclosure and the embodiments of the page display processing method of the present disclosure correspond to each other, and the related content can be mutually referred to, which will not be described here again. The beneficial technical effects of the page display processing system in the embodiments of the present disclosure can be referred to the corresponding beneficial technical effects of the corresponding example method part, which will not be described here again.

[0122] In addition, the embodiments of the present disclosure also provide an electronic device, which includes: a memory for storing a computer program; a processor for executing the computer program stored in the memory, and when the computer program is executed, the page display processing method of any one of the embodiments of the present disclosure is implemented.

[0123] Figure 11 The structure schematic diagram of one application embodiment of the electronic device of the present disclosure is shown in FIG. 10. Hereinafter, the electronic device according to the embodiments of the present disclosure will be described with reference to FIG. 10. Figure 11 As shown in FIG. 10, the electronic device includes one or more processors and a memory. Figure 11

[0124] ​​​​The processor can be a central processing unit (CPU) or other form of processing unit having data processing and / or instruction executing capabilities, and can control other components in the electronic device to perform desired functions.

[0125] The memory can include one or more computer program products that can include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory, for example, can include random access memory (RAM), cache memory, and / or the like. The non-volatile memory, for example, can include read only memory (ROM), hard disk, flash memory, and / or the like. One or more computer program instructions can be stored on the computer-readable storage media, and the processor can execute the program instructions to implement the page display processing method of various embodiments of the present disclosure described above and / or other desired functions.

[0126] In one example, the electronic device can further include an input device and an output device, which are interconnected through a bus system and / or other forms of connection mechanisms (not shown).

[0127] In addition, the input device can further include, for example, a keyboard, a mouse, and / or the like.

[0128] The output device can output various information, including the determined distance information, direction information, and / or the like, to the outside. The output device can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and / or the like.

[0129] Of course, in order to simplify, Figure 11 In FIG. 1, only some of the components related to the present disclosure among the components in the electronic device are illustrated, and components such as buses, input / output interfaces, and / or the like are omitted. In addition to this, the electronic device can further include any other appropriate components according to a specific application.

[0130] In addition to the above-described method and device, an embodiment of the present disclosure can be a computer program product including computer program instructions that, when executed by a processor, cause the processor to perform the steps of the page display processing method according to various embodiments of the present disclosure described in the above parts of the specification.

[0131] The computer program product can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server.

[0132] In addition, the embodiments of the present disclosure can also be a computer readable storage medium, which stores computer program instructions, and the computer program instructions, when executed by a processor, cause the processor to perform the steps in the page display processing method according to various embodiments of the present disclosure described in the above part of the specification.

[0133] The computer readable storage medium can take the form of one or more combinations of any type of computer readable medium. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may, for example, include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the above. More specific examples (a non-exhaustive list) of the computer readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0134] Those skilled in the art can understand that all or part of the steps of the above method embodiments can be completed by program instruction related hardware, and the foregoing program can be stored in a computer readable storage medium, and the program executes the steps of the above method embodiments when executed; and the foregoing storage medium includes ROM, RAM, magnetic disc or optical disc and various storage program codes.

[0135] The above describes the basic principles of the present disclosure in combination with specific embodiments, but it should be noted that the advantages, advantages, effects and the like mentioned in the present disclosure are only examples and are not limited, and these advantages, advantages, effects and the like cannot be considered as the various embodiments of the present disclosure must have. In addition, the above specific details are only for the purpose of example and for the purpose of understanding, and the above details do not limit the present disclosure to the above specific details.

[0136] The various embodiments described in this specification are intended to be exemplary only. The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of "including," "comprising," "having" and "containing" and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms "connected," "coupled," and "pathway" are used broadly and encompass both direct and indirect connections, couplings and pathways.

[0137] The block diagrams of devices, apparatuses, equipment, systems referred to in this disclosure are only illustrative examples and are not intended to require or imply that the connections, arrangements, configurations must be as shown in the block diagrams. These devices, apparatuses, equipment, systems can be connected, arranged, configured in any way as those skilled in the art will recognize. Words such as "including," "containing," "comprising," and the like are meant to encompass the items listed thereafter as well as equivalents thereof as well as additional items. The words "or" and "and" are used in an inclusive and disjunctive sense and can be used generically or in the

[0138] The methods and apparatuses of the present disclosure can be implemented in numerous ways. For example, the methods and apparatuses of the present disclosure can be implemented using software, hardware, firmware, or any combination of software, hardware, and firmware. The order of any steps of the methods described above is merely exemplary and the steps of the methods of the present disclosure need not be performed in the order described unless otherwise specified. Furthermore, in some embodiments, the present disclosure can also be implemented as a program for use with a computer system, the program including a machine-readable instruction for instructing a machine to perform the steps of the methods according to the present disclosure. Thus, the present disclosure also covers a record medium storing the program for instructing a machine to perform the steps of the methods according to the present disclosure.

[0139] It is also important to note that the devices, equipment and methods of the present disclosure can be embodied in a variety of ways. In this respect, various embodiments of the present disclosure are merely illustrative of the principles of the present disclosure. The block diagrams of devices, apparatuses, equipment, systems referred to in this disclosure are only illustrative examples and are not intended to require or imply that the connections, arrangements, configurations must be as shown in the block diagrams. These devices, apparatuses, equipment, systems can be connected, arranged, configured in any way as those skilled in the art will recognize. Words such as "including," "containing," "comprising," and the like are meant to encompass the items listed thereafter as well as equivalents thereof as well as additional items. The words "or" and "and" are used in an inclusive and disjunctive sense and can be used generically or in the

[0140] The above description of the disclosed aspects is intended to be illustrative only and not restrictive of the present disclosure. Various modifications to the aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0141] The foregoing description has been presented for the purposes of illustration and description. Furthermore, the description is not intended to limit the embodiments of the disclosure to the forms disclosed herein. Although the various example aspects and embodiments have been described herein with regard to particular aspects and embodiments, those skilled in the art will recognize that certain modifications, changes, substitutions, additions and sub-combinations can be made without departing from the spirit of the disclosure.

Claims

1. A page display processing method characterized by comprising: The method comprises: in response to monitoring the application page switching event of the target application, obtaining a target page identifier corresponding to a target application page, the target application page being an application page displayed after page switching; based on the target page identifier, obtaining a target component configuration item corresponding to the target page identifier in preset configuration content corresponding to different page types, wherein the preset configuration content corresponding to each page type includes a mapping relationship between a page identifier corresponding to an application page requiring to display a component and a component configuration item; in response to successfully obtaining the target component configuration item, based on the target component configuration item, displaying target component content corresponding to the target component configuration item in the target application page.

2. The method of claim 1, wherein, The method comprises: based on the identifier type of the target page identifier, determining a target page type corresponding to the identifier type; based on the target page identifier, searching for the target page identifier in preset configuration content corresponding to the target page type to obtain a search result; in response to the search result indicating that the target page identifier exists in the preset configuration content corresponding to the target page type, obtaining a target component configuration item corresponding to the target page identifier in the preset configuration content corresponding to the target page type.

3. The method of claim 2, wherein, The method comprises: based on a preset mapping relationship between different identifier types and different page types, determining a target page type corresponding to the identifier type of the target page identifier, the different page types including at least one of a plurality of native page types and a plurality of non-native page types.

4. The method according to any one of claims 1 to 3, characterized in that, The method comprises: based on the target component configuration item, performing display condition verification based on a target display condition required to be met for displaying the target component content indicated by the target component configuration item to obtain a condition verification result; in response to the condition verification result indicating that the target display condition is met, displaying the target component content in the target application page.

5. The method of claim 4, wherein, The method comprises: in response to the target display condition required to be met for displaying the target component content indicated by the target component configuration item including a multi-dimensional display condition, based on the multi-dimensional display condition, obtaining multi-dimensional information; for any one-dimensional information, based on the display condition of the corresponding dimension, performing display condition verification to obtain the condition verification result; The method comprises: in response to the condition verification result indicating that the multi-dimensional display condition is met, displaying the target component content in the target application page.

6. The method of claim 4, wherein, The displaying the target component content in the target application page in response to the condition verification result indicating that the target display condition is met comprises: In response to the condition verification result indicating that the target display condition is met, obtaining component content required to be displayed in the target application page and a component type of a target component; Based on the component type and the component content, rendering target component content, and displaying the target component content in the target application page.

7. The method according to any one of claims 1 to 3, characterized in that, The obtaining of the target page identifier corresponding to the target application page comprises: In response to monitoring an application page switching event of a target application, executing a target page display method to display the target application page and obtain the target page identifier, the target page display method comprising page display logic and page identifier obtaining logic.

8. A page display processing system characterized by comprising: The system comprises: A monitoring module configured to, in response to monitoring an application page switching event of a target application, obtain a target page identifier corresponding to the target application page, the target application page being an application page displayed after page switching; A business module configured to, based on the target page identifier, obtain a target component configuration item corresponding to the target page identifier in preset configuration content corresponding to different page types, wherein the preset configuration content corresponding to each page type comprises a mapping relationship between a page identifier of an application page required to display a component and a component configuration item; A display module configured to, in response to successfully obtaining the target component configuration item, display target component content corresponding to the target component configuration item in the target application page based on the target component configuration item.

9. The system of claim 8, wherein, The monitoring module comprises a native page monitoring unit and a non-native page monitoring unit; the native page monitoring unit is configured to obtain a page identifier corresponding to a native page; and the non-native page monitoring unit is configured to obtain a page identifier corresponding to a non-native page; The business module comprises a rule matching engine unit and a content loading management unit; the rule matching engine unit is configured to, based on the target page identifier, obtain a target component configuration item corresponding to the target page identifier in preset configuration content corresponding to different page types; The content loading management unit is configured to provide the target component configuration item to the display module; The display module comprises a content rendering unit configured to obtain the target component configuration item from the content loading management unit and render target component content based on the target component configuration item.

10. An electronic device, comprising: The system comprises: A memory configured to store a computer program; A processor configured to execute the computer program stored in the memory, and when the computer program is executed, implement the page display processing method of any one of claims 1-7.

11. A computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, the page display processing method of any one of claims 1-7 is implemented.

Images