APP page full-period management platform

Abstract

The invention provides an APP page full-period management platform, and the platform comprises an APP version management module which is used for managing versions of different ends of an APP; the page management module is in communication connection with the APP version management module and is used for managing page contents of the APP; the data analysis module is in communication connection with the page management module and is used for collecting and analyzing page data of the APP; the version mapping module is in communication connection with the APP version management module, the page management module and the data analysis module and is used for maintaining the mapping relation between the APP version and the page; according to the application, the management efficiency of different versions of pages of the APP can be effectively improved, the operation efficiency of the APP and the user body feeling are improved, and the operation and maintenance cost is reduced.

Description

Technical Field

[0001] The present application belongs to the technical field of software page management, and relates to a page management platform, and in particular to an APP page full-cycle management platform. Background Art

[0002] With the development of mobile Internet, software (Application, App) has become the core entrance for enterprises to connect with users. Modern Apps have the following characteristics: diversified release channels, including iOS, Android, Hongmeng, various mini-programs, etc.; frequent version updates: usually one version iteration every 1-2 weeks; frequent page changes: the average daily page changes can reach dozens of times; complex user devices: different system versions, models, resolutions, etc.

[0003] Existing solutions mainly adopt a dual-track management model, namely App version management and page content management. App version management mainly involves: using a version control system (such as Git) to manage code, using a CI / CD (continuous integration / continuous deployment) release process, distributing versions through the app store, and using version numbers (such as 1.0.0) to identify different versions. Page content management mainly involves using a CMS (content management system) to manage pages, updating pages through a configuration system, using an H5 dynamic solution to achieve hot updates, and using timestamps or version numbers to identify page versions. The current mainstream dynamic solutions mainly use offline package solutions and Web container solutions. The offline package solution mainly uses pre-set basic frameworks, dynamically download resource packages, and local parsing and rendering, while the Web container solution uses WebView rendering, JSBridge interaction, and support for real-time updates.

[0004] However, the above solution has the following problems due to the separation of technical architecture, organizational collaboration mode, historical technical debt, scenario complexity and imperfect tool chain:

[0005] 1. The life cycle is separated. The App version and the page version are managed independently and lack connection. It is impossible to track the performance of the page on different client versions. The version dependency is unclear, which easily causes compatibility issues.

[0006] 2. Low operational efficiency. Page publishing requires repeated confirmation of client compatibility. Multi-terminal adaptation requires repeated configuration and verification. The problem location cycle is long and involves cross-verification of multiple systems.

[0007] 3. Insufficient risk control, lack of unified version dependency management, lack of pre-verification of client versions before page publishing, and difficulty in quickly rolling back and locating online problems.

[0008] 4. Data analysis is limited. Monitoring data is scattered across different systems. There is a lack of cross-version performance comparison analysis, making it impossible to accurately attribute problems. Summary of the invention

[0009] The purpose of this application is to provide an APP page full-cycle management platform to solve the problem of low APP page management and operation efficiency in the prior art.

[0010] In the first aspect, the present application provides an APP page full-cycle management platform, including:

[0011] APP version management module, used to manage versions of different APP terminals;

[0012] A page management module, which is in communication with the APP version management module and is used to manage the page content of the APP;

[0013] A data analysis module, which is in communication with the page management module and is used to collect and analyze the page data of the APP;

[0014] The version mapping module is respectively connected to the APP version management module, the page management module and the data analysis module for maintaining the mapping relationship between the APP version and the page.

[0015] Optionally, the version mapping module includes a mapping relationship management unit, a dependency analysis unit, a compatibility checking unit, an impact scope assessment unit and a version tracking unit. The mapping relationship management unit is used to create a mapping relationship between the version of the APP and the page version, and set the effectiveness conditions and effectiveness period of the mapping relationship, while maintaining the status of the mapping relationship. The dependency analysis unit is used to analyze the dependency of the current page on the current version of the APP, and the dependency includes basic capability dependency, business capability dependency, component dependency and framework dependency. The compatibility checking unit is used to verify the compatibility of the page with the APP version. The impact scope assessment unit is used to assess the impact scope after the APP version is changed. The version tracking unit is used to track the usage of the page on different APP versions. When a new version of the page is released, the version status is changed or the version configuration is updated, the mapping relationship management unit updates the mapping relationship between the page version and the APP version, and the dependency analysis unit rebuilds the dependency between the page and the APP version.

[0016] Optionally, the mapping relationship includes basic mapping information, mapping rules and mapping direction, the basic mapping information includes APP version number, page version number, mapping identifier, creation time and creator information, the APP version number and the page version number correspond one to one, the mapping rules include at least one of forced mapping, compatible mapping and exclusion mapping, and the mapping direction includes at least one of forward mapping, reverse mapping and mutually associated mapping.

[0017] Optionally, the basic capability dependencies include system API calls, device permission requirements and basic component usage, the business capability dependencies include business interface calls, data storage requirements and functional module references, the component dependencies include native component usage, custom component references and third-party component integration, and the framework dependencies include SDK version requirements, operating environment requirements and framework feature usage.

[0018] Optionally, the compatibility checking unit verifies the compatibility of the page and the APP version through static verification and dynamic testing, the static verification includes checking whether the API requirements declared in the page match the API requirements provided by the current version of the APP, verifying whether the component version applicable to the page is supported by the current version of the APP, and checking whether the basic information of the configuration parameters of the page meets the version requirements, and the basic information of the configuration parameters includes parameter integrity, type and value range; the dynamic test includes running the page in an isolated environment, verifying whether the page function is running normally, testing the performance of the page under different network conditions, and checking whether the loading performance and running performance of the page are qualified;

[0019] The impact scope assessment unit assesses at least one of version impact assessment, user impact assessment and business impact assessment;

[0020] The version tracking unit is used to collect data of the page in different APP versions, compare the indicator data of the APP before and after the version change, and monitor the usage status of the page in different versions.

[0021] Optionally, the data analysis module includes a data collection unit and a multi-dimensional analysis unit, the data collection unit is used to collect data of the page running in different versions, and the multi-dimensional analysis unit is used to analyze the page from different dimensions.

[0022] Optionally, the data collected by the data collection unit includes at least one of page access data, page performance data, user behavior data and business data, and the analysis dimensions of the multidimensional analysis unit include at least one of version dimension, time dimension, user dimension and scenario dimension.

[0023] Optionally, the page access data includes page views PV, unique visitors UV, page dwell time and bounce rate; the performance data includes page loading time, first screen time, resource loading time and interface response time; the user behavior data includes click behavior, sliding operations, page paths and dwell hotspots; and the business data includes conversion rate, retention rate, transaction amount and usage frequency.

[0024] Optionally, the page management module includes a page lifecycle management unit and a page version control unit, the page lifecycle management unit is used to manage the lifecycle of the page, the lifecycle of the page includes creation, development, release, operation and maintenance, and offline, the page version control unit is used to control and manage the version of the page, and the control and management of the page version includes version creation, difference comparison, version switching and version rollback;

[0025] The APP version management module includes an APP version information management unit and an APP version publishing unit. The APP version information management unit is used to manage the basic information of different versions of the APP, including recording the basic version information of the APP, maintaining the version status of the APP, and managing the version capability set of the APP. The APP version publishing unit 12 is used to manage the version publishing process of the APP, including the creation of a new version of the APP, page association, compatibility check before the release of the APP version, release control and version rollback, and the APP version publishing unit implements compatibility check of the APP version through a rule engine.

[0026] Optionally, the page management process includes:

[0027] The page is created by the page lifecycle management unit, basic information of the page is set and corresponding configuration functions are configured, and the target version of the APP that the page is to support is determined by the page version control unit;

[0028] Performing a compatibility check on the configured page and the APP by the compatibility check unit;

[0029] If the page passes the compatibility check, the APP version publishing unit performs publishing verification; and after determining that the page passes the publishing verification, the mapping relationship between the page and the APP in the current version is established through the mapping relationship management unit, and the operation of the page is monitored in real time;

[0030] If the page fails the compatibility check, the target version of the APP supported by the page is adjusted and the compatibility check is performed again.

[0031] As described above, the APP page full-cycle management platform described in this application has the following beneficial effects:

[0032] The present application scheme establishes a mapping relationship between different versions of APP and pages through the version mapping module, and manages different versions of APP through the APP version management module, thereby realizing unified management of App version and page version, providing complete version tracking capability, reducing operation and maintenance costs and error risks; at the same time, the version mapping module is used to implement compatibility detection of the page content to achieve accurate compatibility management of the page content; and the data analysis module collects and analyzes page data, which can realize multi-dimensional data analysis and quickly locate problems; and the APP version management module is used to realize flexible release control of different versions of APP; the entire platform can effectively improve the management efficiency of pages, improve the operation efficiency and user experience of APP, and reduce operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 Shown is a structural block diagram of the APP page full-cycle management platform described in an embodiment of the present application.

[0034] Figure 2 Shown is a schematic diagram of the mapping relationship stored in the mapping relationship management unit in the APP page full-cycle management platform described in the embodiment of the present application.

[0035] Figure 3 Shown is a flow chart of page management in the APP page full-cycle management platform described in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0037] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0038] The following embodiments of the present application provide a full-cycle management platform for APP pages. Figure 1 ,include:

[0039] APP version management module 1, used to manage the versions of different APP terminals;

[0040] The page management module 2 is connected to the APP version management module 1 for managing the page content of the APP;

[0041] The data analysis module 3 is connected to the page management module 2 for collecting and analyzing the page data of the APP;

[0042] The version mapping module 4 is respectively connected to the APP version management module 1, the page management module 2 and the data analysis module 3 for maintaining the mapping relationship between the APP version and the page.

[0043] In this embodiment, the APP version management module 1 is responsible for managing the versions of different ends of the APP, including IOS, Andriod and mini-programs, as the entry for version release, and the page management module 2 is used to manage the page content of the APP throughout its life cycle, and the version mapping module 4 is responsible for maintaining the mapping relationship between the APP version and the page version, so as to facilitate the update and maintenance of pages of different versions of the APP, and the data analysis module 3 is used to collect and analyze the operating data of different versions of the page, so as to study the performance of the page on different versions of the APP, realize global monitoring and give optimization suggestions.

[0044] Specifically, for the version release process, the APPAPP version management module 1 first creates a new version of the APP and provides basic version information. After the version mapping module 4 receives the version information of the new version of the APP, it analyzes the dependencies. At the same time, the page management module 2 provides the compatibility information of all current pages. After the version mapping module 4 determines that the version of the APP is compatible with the page, the version mapping module 4 establishes the correspondence between the new version of the APP and the page; at the same time, the data analysis module 3 starts to collect the operating data of the new version, thereby realizing the release process of the new version of the APP.

[0045] As for the page update process, when the page version needs to be updated, the page management module 2 first submits a page update request, the version mapping module 4 checks the affected App version, and the App version management module 1 confirms the compatibility between the updated page and the current version of the APP. After confirming the compatibility, the version mapping module 4 updates the mapping relationship between the page and the APP. At the same time, the data analysis module 3 monitors the running data of the updated page in real time, so as to grasp the running status of the page after the update in real time.

[0046] .In the process of data analysis module 3 monitoring page operation data, data analysis module 3 continuously collects operation data, and notifies version mapping module 4 when an abnormality is found, evaluates the impact scope of the abnormality through version mapping module 4, and pushes optimization suggestions to page management module 2 and APPAPP version management module 1, such as version switching or version rollback, and tracks the execution effect of optimization measures in real time.

[0047] Through the above-mentioned collaboration mechanism, the controllability of APP version release, the security of page updates, the timeliness of problem handling and the stability of system operation can be effectively achieved.

[0048] In some embodiments, the APP version management module 1 includes an APP version information management unit 11 and an APP version release unit 12. The APP version information management unit 11 is used to manage the basic information of different versions of the APP, including recording the basic version information of the APP, maintaining the version status of the APP, and managing the version capability set of the APP. The APP version release unit 12 is used to manage the version release process of the APP, including the creation of a new version of the APP, page association, compatibility check before APP version release, release control and version rollback, and the APP version release unit implements compatibility check of APP versions through a rule engine.

[0049] In this embodiment, the basic version information of the APP includes the internal version number, the external version number and the release time, the version status of the APP includes the five states of under development, under testing, under review, released and disabled, and the version capabilities of the APP are the functional characteristics supported by each version of the APP. The creation of a new version of the APP includes creating a new version after entering the basic version information of the new version, the page association includes determining the page set included in the new version of the APP, the compatibility check includes verifying the availability of all page sets in the current version of the APP before the APP version is released, the release control includes grayscale release and full release, and the version rollback is used to provide an emergency rollback mechanism to deal with emergencies.

[0050] Furthermore, the APP version publishing unit 12 implements compatibility check on the APP version through a rule engine, and the specific process includes:

[0051] First, the basic structure of the rule engine is set before the check, including rule definition, priority setting and execution strategy. The rule definition includes the definition of the rule ID, type, condition and action of the matching rule. The rule type includes API compatibility rules for checking API version matching, functional feature rules for verifying functional support, system requirement rules for checking environmental compatibility, and business rules for verifying compatibility at the business level. The priority setting includes setting the execution order of different types of rules, and the execution strategy includes setting the matching logic and processing method of each rule. By setting the above basic structure, a complete rule engine is obtained. Subsequently, the page set of the current version is checked for compatibility through the set rule engine, that is, the availability of the page set in the current version of the APP is verified. When the page set is checked for compatibility, the first step is the data preparation process to obtain the version information of the APP to be released and the page requirements of the APP, and load the relevant verification rules at the same time for subsequent verification. The version information of the APP includes the API version, functional features and system requirements, and the page requirements include the API dependency, functional dependency and operating environment requirements of the page.

[0052] After completing the above data preparation process, the subsequent execution verification process is carried out. First, according to the priority settings set above, the version information of the APP and the page requirements of the APP are verified according to the set priority, and the matching verification results of each rule are collected at the same time. Then, the matching verification results of each rule are merged together to obtain the final verification report.

[0053] Subsequently, the compatibility of the current version of the APP with the page set before release will be determined based on the final verification report. When the APP version and the page set are fully compatible, they can be released directly; when the APP version and the page set are only compatible under certain conditions, it is necessary to add corresponding restrictions before the APP version is released; when the APP version and the page set are completely incompatible, the current APP version needs to be upgraded or prohibited from use.

[0054] The above method is used to implement compatibility check before APP version release. Due to the use of dynamic verification based on rule engine, not only can global compatibility check be implemented before APP version release, but also dynamic verification based on rule engine can realize automatic compatibility pre-check, and timely issue accurate problem warning before problems occur, realize quantifiable compatibility evaluation, and fully meet the global compatibility check requirements before APP version release.

[0055] The process of the APP version release unit 12 releasing the new version of the APP includes an internal process and an external process. The internal process includes code review, automated testing, test submission, package signing and submission review in sequence; the external process includes:

[0056] First, the APP is reviewed in the application store of the release channel. After the review is passed, it is released in grayscale. After the release, the data of the APP is collected and monitored through the data analysis module 3. After confirming that the data is normal, the APP is fully released. When an abnormal situation occurs, the APP version is rolled back through the APP version release unit 12 to ensure the normal operation of the APP.

[0057] Through the above solution, the entire life cycle management of each version of the APP can be achieved, the controllability of the release process can be guaranteed, a complete emergency response plan can be provided, and unified release through multiple channels can be achieved.

[0058] It should be noted that when the APP version information management unit 11 manages the basic information of different versions of the APP, it manages it according to the application type of the APP and the version information of the APP respectively. The application types include local applications, multi-platform applications and mini-program applications. The version information of the APP includes the external version number, the internal version number and the build number.

[0059] In some other embodiments, the page management module 2 includes a page lifecycle management unit 21 and a page version control unit 22. The page lifecycle management unit 21 is used to manage the lifecycle of the page, and the lifecycle of the page includes creation, development, release, operation and maintenance, and offline. The page version control unit 22 is used to control and manage the version of the page, and the control and management of the page version includes version creation, difference comparison, version switching, and version rollback.

[0060] In this embodiment, during the process of the page lifecycle management unit 21 managing the page lifecycle, the page creation process includes configuring the basic information of the page, the page development stage includes content development and testing, the page publishing stage includes associating available versions, the page operation and maintenance stage includes monitoring and optimizing the page, and the page offline management includes deactivating and archiving the page. During the process of the page version control unit 22 controlling the page version, the version creation includes creating a new page version, the difference comparison includes comparing the content of the page in different versions, the version switching includes switching the version of the page, and the version rollback includes rolling back the version of the page in an abnormal situation.

[0061] Among them, the page version control unit 22 mainly compares the differences of different versions of the page from the following four dimensions, namely structural differences, configuration differences, resource differences and dependency differences. Structural differences include changes in the document object model (DOM) structure of the page; configuration differences include changes in parameter configuration of the page; resource differences include changes in resource files used by the page; dependency differences include changes in component dependencies of the page.

[0062] In the specific comparison process, for example, the comparison by level is as follows:

[0063] The first layer: basic information of the page, including page ID, title, type, etc.

[0064] The second layer: page layout structure, including area division and component arrangement;

[0065] The third layer: component configuration, including property settings and event binding;

[0066] The fourth layer: data configuration, including interface configuration and static data.

[0067] When doing the comparison, we obtain the configuration information of different versions of the page, including basic page information, page layout structure, component configuration, and data configuration. After converting the page configuration information into a standard format, we generate a difference report after comparing them at different levels. We also mark the change types in the difference report, including addition, deletion, modification, and location change. And for the comparison results of the difference report, we display the changes in a structured manner, highlight the differences, provide change instructions, and support change confirmation or rollback.

[0068] In some other embodiments, the data analysis module 3 includes a data collection unit 31 and a multi-dimensional analysis unit 32. The data collection unit 31 is used to collect data of the page running in different versions, and the multi-dimensional analysis unit 32 is used to analyze the page from different dimensions, so as to find problems existing in the page and optimize it according to the analysis results, and to timely understand user needs and behaviors, so as to provide decision support for the improvement of the APP. Through a comprehensive data analysis perspective, problems can be accurately located.

[0069] Specifically, the data collected by the data collection unit 31 includes at least one of page access data, page performance data, user behavior data and business data, and the analysis dimensions of the multidimensional analysis unit 32 include at least one of version dimension, time dimension, user dimension and scenario dimension.

[0070] Furthermore, the page access data includes page views PV, unique visitor number UV, page dwell time and bounce rate. The page views PV is used to record the event log of each page loading, the unique visitor number UV is used to count the number of unique identifiers of visiting users, the dwell time is used to record the time difference between users entering and leaving the page, and the bounce rate is used to count the proportion of users who leave after browsing only one page. By collecting the above-mentioned page access data, it is convenient to understand the overall access trend of the current version of the page after analysis, evaluate the popularity of the page and analyze user retention.

[0071] The performance data includes page loading time, first screen time, resource loading time, interface response time, crash rate and error rate. The page loading time is used to record the time from request initiation to page interactivity, the first screen time is used to record the event that the first screen content of the page is fully displayed, the resource loading time is used to count the loading time of various resources of the page, the interface response time is used to record the round-trip time of the page interface call, the crash rate is used to record the proportion of page crashes, and the error rate is used to record the error proportion of the page. By collecting and analyzing the above performance data, it is possible to monitor the performance of the page in different versions, discover performance bottlenecks, and optimize in time to improve user experience.

[0072] The user behavior data includes click behavior, sliding operation, page path and hotspot. The click behavior is used to record the elements, time and location clicked by the user on the page. The sliding operation is used to count the sliding records, direction and speed of the user on the page. The page path is used to track the jump path of the user between different pages. The hotspot is used to record the length of time the user stays in each area of ​​the page. By collecting the above-mentioned user behavior data, it is convenient to analyze the user behavior data later to understand the user's usage habits, and optimize the page interaction design and improve the functional layout of the page according to the user's usage habits.

[0073] The business data includes conversion rate, retention rate, transaction amount and usage frequency. The conversion rate is used to count the number of completions or total visits of the target behavior of the page, the retention rate is used to calculate the proportion of users who visit the page repeatedly in subsequent time periods, the retention rate is used to calculate the proportion of users who visit the page repeatedly, the transaction amount is used to count the total amount of transactions completed on the page, and the usage frequency is used to record the number of times a user repeatedly uses the page. By collecting the above business data, it is convenient to evaluate the achievement of business goals and analyze user value to guide subsequent operational decisions.

[0074] By collecting the above-mentioned page access data, page performance data, user behavior data and business data, subsequent analysis can be facilitated to discover problems with the page and optimize it. At the same time, user needs and behaviors can be understood in a timely manner to provide decision-making support for APP improvements.

[0075] In some other embodiments, the analysis dimensions of the multidimensional analysis unit 32 include at least one of version dimension, time dimension, user dimension and scenario dimension, so as to analyze the data collected from the page through the four dimensions of version dimension, time dimension, user dimension and scenario dimension.

[0076] Exemplarily, when the multi-dimensional analysis unit 32 analyzes the page data according to the version dimension, it first groups the data collected by the data collection unit 31 according to the page version, uses the page version number as the primary key, and aggregates the data indicators of each version to facilitate the calculation of the data differences between versions. After the grouping is completed, the grouped indicator data are compared respectively, including performance indicators, stability indicators and business indicators. The performance indicators include loading time and response speed, the stability indicators include error rate and crash rate, and the business indicators include conversion rate and stay time. By comparing the data of the page in different versions to generate the corresponding version analysis results, it is convenient to compare the advantages and disadvantages of different versions, as well as the performance change trend of the page in different versions, and mark the abnormal situation of the page to facilitate timely handling of the abnormal situation.

[0077] When analyzing the collected page data of different versions according to the time dimension, the multi-dimensional analysis unit 32 first processes the page data according to the time series, groups them according to hours / days / weeks / months, calculates the average of the indicators of the page data in each time group, and analyzes the periodic changes of the page data in different groups. At the same time, the month-on-month and year-on-year changes of various indicators of the page data are calculated, and abnormal fluctuations are identified to predict the change trend of the indicator data of the page.

[0078] When the multi-dimensional analysis unit 32 analyzes the collected page data of different versions according to the user dimension, it first groups the users, including grouping according to user attributes, usage behavior and value. Grouping according to user attributes includes grouping according to new and old users or activity levels, grouping according to usage behavior includes grouping according to usage frequency and usage path, and grouping according to value includes grouping according to purchase frequency and transaction amount. After completing the user grouping, according to the group characteristics analysis, the usage indicators of each group are calculated, the behavioral differences of different groups are compared, and the characteristics of high-value users are identified, so as to facilitate the user changes on different versions of the page.

[0079] When the multi-dimensional analysis unit 32 analyzes the collected page data of different versions according to the scenario dimension, the scenario of the page data is first identified and classified, including time scenario, environment scenario and device scenario. The time scenario includes weekdays and holidays, the environment scenario includes WIFI, 4G and 5G, and the device scenario includes IOS and Android. After the page data is grouped according to the scenario identification, the performance of different versions of the page data in different scenarios is compared respectively, so as to obtain the change trend of the page data in different scenarios, so as to timely discover the problems in different scenarios after the page version is updated, and timely optimize to improve the user experience.

[0080] In some other embodiments, the version mapping module 4 includes a mapping relationship management unit 41, a dependency analysis unit 42, a compatibility check unit 43, an impact range assessment unit 44 and a version tracking unit 45. The mapping relationship management unit 41 is used to create a mapping relationship between the version of the APP and the page version, and set the effective conditions and effective period of the mapping relationship, while maintaining the state of the mapping relationship. The dependency analysis unit 42 is used to analyze the dependency of the current page on the current version of the APP, and the dependency includes basic capability dependency, business capability dependency, component dependency and framework dependency. The compatibility check unit 43 is used to verify the compatibility of the page with the APP version. The impact scope assessment unit 44 is used to assess the impact scope after the APP version is changed, and the version tracking unit 45 is used to track the usage of the page on different APP versions; when a new version of the page is released, the version status is changed, or the version configuration is updated, the mapping relationship management unit 41 updates the mapping relationship between the page version and the APP version, and the dependency analysis unit 42 rebuilds the dependency relationship between the page and the APP version. At the same time, the compatibility check unit 43 re-verifies the compatibility of the page version and the APP version, and the impact scope assessment unit 44 assesses the impact scope after the page version is changed, and the version tracking unit 45 tracks the usage of the page after the version is changed. The mapping relationship between the page version and the APP version is managed by the version mapping module 4, which can achieve real-time synchronization and status tracking of the page version and the APP version, ensure the controllability of version release and update, automatic relationship management, reduce manual maintenance costs, support complex multi-version dependency analysis, and provide complete version traceability.

[0081] Specifically, the mapping relationship includes basic mapping information, mapping rules and mapping direction. The basic mapping information includes APP version number, page version number, mapping identifier, creation time and creator information. The APP version number corresponds to the page version number one by one. The mapping rules include at least one of mandatory mapping, compatible mapping and exclusion mapping. The mapping direction includes at least one of forward mapping, reverse mapping and mutual correlation mapping. The mandatory mapping must be used between the two mappings. The page version and the APP version are uniquely corresponding. For example, a certain version of the page must use the corresponding version of the APP. The compatible mapping is that the page version and the APP version can use a specified version range. For example, the current version of the page can use the corresponding two versions of the APP. The exclusion mapping is prohibited between the page version and the APP version. For example, the current version of the APP prohibits the use of the corresponding version of the APP. The forward mapping is mapped to the page version according to the APP version, the reverse mapping is mapped to the APP version according to the page version, and the bidirectional mapping is the mutual mapping between the APP version and the page version. By establishing a mapping relationship between the page version and the APP version, version management is achieved, including ensuring that the App and page versions match, preventing version conflicts and incompatibilities, and supporting smooth version upgrades. Version release control is achieved, including controlling the page update scope, managing the version release rhythm, supporting grayscale release strategies, and implementing problem tracking, specifically including quickly locating version problems, tracking version usage, and analyzing version correlations.

[0082] Furthermore, the mapping relationship management unit 41 is not only used to establish a mapping relationship between the page version and the APP version, but can also set the mapping effectiveness conditions, maintain the status of the mapping relationship, and control the effectiveness period of the mapping relationship, thereby achieving effective management of the entire mapping relationship and facilitating the management and maintenance of the page version and APP version.

[0083] In this embodiment, reference Figure 2 The mapping relationship management unit 41 records the mapping relationship between the page version and the APP version through a version mapping relationship table (VersionMapping) for the established mapping relationship between the page version and the APP version.

[0084] In some other embodiments, by analyzing the dependency of the current page on the current version of the APP through the dependency analysis unit 42, compatibility assurance of the page version and the APP version can be achieved, including prevention of compatibility issues and upgrade risk assessment. Prevention of compatibility issues includes early detection of version conflicts, avoidance of functional deficiencies and ensuring smooth operation of the APP. Upgrade risk assessment includes assessing the impact of upgrades, formulating upgrade measurements and preparing emergency plans. At the same time, performance optimization of the page and the APP can be achieved, including dependency optimization and resource optimization. The dependency optimization includes streamlining unnecessary dependencies, optimizing dependency structures and reducing coupling. The resource optimization includes optimizing resource usage, improving loading performance and reducing resource redundancy. It can also achieve rapid location of problems in the page and the APP, including problem location and upgrade decision support. The problem location includes locating version-related issues, tracking dependency links and analyzing abnormal causes. The upgrade decision support includes evaluating upgrade feasibility, formulating testing strategies and planning rollback plans.

[0085] The dependency relationship analyzed by the dependency relationship analysis unit 42 is stored in a directed acyclic graph for easy calling.

[0086] Specifically, the dependencies include basic capability dependencies, business capability dependencies, component dependencies and framework dependencies. The basic capability dependencies include system API calls, device permission requirements and basic component usage. The business capability dependencies include business interface calls, data storage requirements and functional module references. The component dependencies include native component usage, custom component references and third-party component integration. The framework dependencies include SDK version requirements, operating environment requirements and framework feature usage. Through the analysis results of the dependencies, it is possible to support and optimize the version decision, ensure the stability of the version and discover potential problems in advance. Version decision support includes release decisions and upgrade suggestions. The release decision includes determining the release scope, controlling the release rhythm, and arranging the release time. The upgrade suggestions include providing upgrade guidance, suggesting the test scope, and recommending the upgrade path. The optimization guidance includes architecture optimization and performance improvement. The architecture optimization includes optimizing the dependency structure, improving component design, and improving code quality. The performance improvement includes optimizing resource usage, increasing response speed, and reducing memory usage.

[0087] When the dependency analysis unit 42 performs dependency analysis on the page and APP version, it first performs a capability set scan on the page, including dynamic scanning and static scanning. The static scan is used to analyze the API call status and component usage in the page code, and the dynamic scan is to obtain the actual dependency calls captured by the page at runtime, and generate a complete dependency graph based on the results of the static scan and the dynamic scan. Then, capability matching is performed based on the obtained dependency graph, including basic capability matching and business capability matching. The basic capability matching includes system API call checking, device permission requirement verification and basic component compatibility checking, and the business capability matching includes business interface version verification, data storage requirement confirmation and functional module dependency analysis.

[0088] It should be noted that the specific analysis process of the dependency of the page analyzed by the dependency analysis unit 42 on the APP version is the content of the existing technology, including the process of capability set scanning and capability matching. This solution does not involve improvements to the specific dependency analysis process and will not be repeated here.

[0089] Furthermore, the version mapping module 4 can also realize real-time synchronization of mapping relationships and dependency relationships. When a new version of a page or APP is released, the version status is updated, or the version configuration is updated, the mapping relationship management unit 41 synchronously updates the version mapping relationship table, the dependency relationship analysis unit 42 rebuilds the dependency relationship, and checks the compatibility of the page version and the APP version through the compatibility check unit 43; at the same time, the page version is tracked through the version tracking unit 45, including the time dimension, dependency dimension, and usage dimension. In this way, the automatic management of mapping relationships and dependency relationships after the page version is updated can be realized, the manual maintenance cost can be reduced, complex multi-version dependency analysis can be supported, and complete version traceability can be provided.

[0090] In some other embodiments, the compatibility check unit 43 verifies the compatibility of the page and the APP version through static verification and dynamic testing. The static verification includes checking whether the API requirements declared by the page match the API requirements provided by the current version of the APP, verifying whether the component version applicable to the page is supported by the current version of the APP, and checking whether the basic information of the configuration parameters of the page meets at least one of the version requirements, and the basic information of the configuration parameters includes parameter integrity, type and value range; the dynamic test includes running the page in an isolated environment, verifying whether the page function is running normally, testing the performance of the page under different network conditions, and checking whether the loading performance and running performance of the page are qualified. The compatibility check unit 43 realizes automatic checking of the compatibility of the page version and the APP version, so that accurate early warning of potential compatibility issues can be achieved, improving the inspection effect.

[0091] Specifically, during the inspection process of the compatibility inspection unit 43, according to the results of the static verification and the dynamic test, when the results of the static verification and the dynamic test are both qualified, it is determined that the page version and the APP version are fully compatible; when the results of the static verification and the dynamic test are partially qualified, it is determined that the page version and the APP version are partially compatible, with restrictions; when the results of the static verification and the dynamic test are both unqualified, it is determined that the page version and the APP version are completely incompatible. In this way, the compatibility issues between the page version and the APP version are discovered in time, and the quality of page publishing and user experience are guaranteed.

[0092] It should be noted that the compatibility check unit 43 is used to perform a compatibility check on the current page and the APP version when the page is updated, which is complementary to the compatibility check on the APP version implemented by the aforementioned APP version publishing unit 12 through the rule engine, thereby ensuring that compatibility checks can be implemented both when the page is updated and before the APP version is released, ensuring that compatibility issues are discovered in time before the APP page update and version update, and ensuring that the APP page update and version update are accurately carried out.

[0093] The impact scope assessment unit 44 assesses content including at least one of version impact assessment, user impact assessment and business impact assessment.

[0094] Exemplarily, the version impact assessment includes checking the number and type of associated pages affected, assessing whether the changed core functions affect key business processes, and identifying other functional components that depend on the version;

[0095] User impact assessment includes counting the changes in the number of active users of the version, analyzing the usage scenarios and behavioral characteristics of affected users, and evaluating the degree of impact on different user groups (such as new users and old users);

[0096] Business impact assessment includes evaluating changes to core business indicators (such as conversion rate and transaction volume) and estimating possible business losses.

[0097] This will provide support for subsequent page version change decisions based on the results of the impact assessment.

[0098] The version tracking unit 45 is used to collect data of the page in different APP versions, compare the indicator data of the APP before and after the version change, and monitor the usage status of the page in different versions.

[0099] In this embodiment, the usage of the current page in different versions is tracked by the version tracking unit 45, which is convenient for subsequent analysis of the current page. When tracking specifically, the data on the page is first used, including page access data, performance indicators, user behavior and abnormal data. The page access data includes PV, UV, access time, and bounce rate; the performance indicators include page loading time, response time, and resource loading; the user behavior includes click path, function usage frequency, and interactive operation record; the abnormal data includes error rate, crash rate, and freeze frequency. After obtaining the above data, the performance comparison results of different versions of pages are obtained by comparing the loading speed and response time of different versions of pages, and the user experience comparison results of different versions of pages are obtained by comparing the user stay time and completion rate of different versions; the conversion rate and target completion status of different versions of pages are compared to obtain the business indicator comparison results of different versions of pages; the abnormal rate and error rate of different versions of pages are compared to obtain the problem occurrence rate comparison results of different versions of pages. By monitoring the operating status of each version of the page in real time, recording the user distribution of different versions, tracking version switching and rollback operations, and monitoring changes in key business indicators of different versions of pages, the usage status monitoring process of different versions of pages can be realized.

[0100] It should be noted that the key business indicators, core business indicators, key business processes and other information of the page in the above process are all related to the corresponding APP. The corresponding key information is different for different APPs. This solution does not make any special limitations on this and will not be repeated here.

[0101] In some embodiments, reference Figure 3 , the page management process includes:

[0102] S301, creating the page through the page lifecycle management unit, setting basic information of the page and corresponding configuration functions, and determining the target version of the APP that the page is to support through the page version control unit;

[0103] S302, performing a compatibility check between the configured page and the APP by the compatibility check unit;

[0104] S303: If the page passes the compatibility check, the APP version publishing unit performs publishing verification; and after determining that the page passes the publishing verification, the mapping relationship between the page and the APP in the current version is established through the mapping relationship management unit, and the operation of the page is monitored in real time;

[0105] S304: If the page fails the compatibility check, adjust the target version of the APP supported by the page and then re-perform the compatibility check.

[0106] The above process realizes the full-cycle management of page versions, effectively improving the management efficiency of different versions of pages.

[0107] The modules / units described as separate components may or may not be physically separated, and the components displayed as modules / units may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules / units may be selected according to actual needs to achieve the purpose of the embodiments of the present application. For example, the functional modules / units in the various embodiments of the present application may be integrated into one processing module, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit.

[0108] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. 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 to be beyond the scope of this application.

[0109] The descriptions of the processes or structures corresponding to the above-mentioned figures have different emphases. For parts that are not described in detail in a certain process or structure, please refer to the relevant descriptions of other processes or structures.

[0110] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. An APP page full-cycle management platform, characterized in that: include: APP version management module, used to manage versions of different APP terminals; A page management module, which is in communication with the APP version management module and is used to manage the page content of the APP; A data analysis module, which is in communication with the page management module and is used to collect and analyze the page data of the APP; The version mapping module is respectively connected to the APP version management module, the page management module and the data analysis module for maintaining the mapping relationship between the APP version and the page.

2. The APP page full-cycle management platform according to claim 1 is characterized in that: The version mapping module includes a mapping relationship management unit, a dependency analysis unit, a compatibility check unit, an impact scope assessment unit and a version tracking unit. The mapping relationship management unit is used to create a mapping relationship between the version of the APP and the page version, and set the effectiveness conditions and effectiveness period of the mapping relationship, while maintaining the status of the mapping relationship. The dependency analysis unit is used to analyze the dependency of the current page on the current version of the APP, and the dependency includes basic capability dependency, business capability dependency, component dependency and framework dependency. The compatibility check unit is used to verify the compatibility of the page with the APP version. The impact scope assessment unit is used to assess the impact scope after the APP version is changed. The version tracking unit is used to track the usage of the page on different APP versions. When a new version of the page is released, the version status is changed or the version configuration is updated, the mapping relationship management unit updates the mapping relationship between the page version and the APP version, and the dependency analysis unit rebuilds the dependency between the page and the APP version.

3. The APP page full-cycle management platform according to claim 2 is characterized in that: The mapping relationship includes basic mapping information, mapping rules and mapping direction. The basic mapping information includes APP version number, page version number, mapping identifier, creation time and creator information. The APP version number and the page version number correspond one to one. The mapping rules include at least one of forced mapping, compatible mapping and exclusion mapping. The mapping direction includes at least one of forward mapping, reverse mapping and mutually associated mapping.

4. The APP page full-cycle management platform according to claim 2 is characterized in that: The basic capability dependencies include system API calls, device permission requirements and basic component usage; the business capability dependencies include business interface calls, data storage requirements and functional module references; the component dependencies include native component usage, custom component references and third-party component integration; the framework dependencies include SDK version requirements, operating environment requirements and framework feature usage.

5. The APP page full-cycle management platform according to claim 2 is characterized in that: The compatibility checking unit verifies the compatibility of the page and the APP version through static verification and dynamic testing, wherein the static verification includes checking whether the API requirements declared by the page match the API requirements provided by the current version of the APP, verifying whether the component version applicable to the page is supported by the current version of the APP, and checking whether the basic information of the configuration parameters of the page meets the version requirements, wherein the basic information of the configuration parameters includes parameter integrity, type and value range; the dynamic test includes running the page in an isolated environment, verifying whether the page function is running normally, testing the performance of the page under different network conditions, and checking whether the loading performance and running performance of the page are qualified; The impact scope assessment unit assesses at least one of version impact assessment, user impact assessment and business impact assessment; The version tracking unit is used to collect data of the page in different APP versions, compare the indicator data of the APP before and after the version change, and monitor the usage status of the page in different versions.

6. The APP page full-cycle management platform according to claim 2, characterized in that: The data analysis module includes a data collection unit and a multi-dimensional analysis unit. The data collection unit is used to collect data of the page running in different versions, and the multi-dimensional analysis unit is used to analyze the page from different dimensions.

7. The APP page full-cycle management platform according to claim 6, characterized in that: The data collected by the data collection unit includes at least one of page access data, page performance data, user behavior data and business data, and the analysis dimensions of the multidimensional analysis unit include at least one of version dimension, time dimension, user dimension and scenario dimension.

8. The APP page full-cycle management platform according to claim 7, characterized in that: The page access data includes page views PV, unique visitors UV, page dwell time and bounce rate; the performance data includes page loading time, first screen time, resource loading time and interface response time; the user behavior data includes click behavior, sliding operation, page path and dwell hotspots; the business data includes conversion rate, retention rate, transaction amount and usage frequency.

9. The APP page full-cycle management platform according to claim 2, characterized in that: The page management module includes a page lifecycle management unit and a page version control unit. The page lifecycle management unit is used to manage the lifecycle of the page, which includes creation, development, release, operation and maintenance, and offline. The page version control unit is used to control and manage the version of the page, which includes version creation, difference comparison, version switching, and version rollback. The APP version management module includes an APP version information management unit and an APP version publishing unit. The APP version information management unit is used to manage the basic information of different versions of the APP, including recording the basic version information of the APP, maintaining the version status of the APP, and managing the version capability set of the APP. The APP version publishing unit is used to manage the version publishing process of the APP, including the creation of a new version of the APP, page association, compatibility check before APP version release, release control and version rollback, and the APP version publishing unit implements compatibility check of APP versions through a rule engine.

10. The APP page full-cycle management platform according to claim 9, characterized in that: The page management process includes: The page is created by the page lifecycle management unit, basic information of the page is set and corresponding configuration functions are configured, and the target version of the APP that the page is to support is determined by the page version control unit; Performing a compatibility check on the configured page and the APP by the compatibility check unit; If the page passes the compatibility check, the APP version publishing unit performs publishing verification; and after determining that the page passes the publishing verification, the mapping relationship between the page and the APP in the current version is established through the mapping relationship management unit, and the operation of the page is monitored in real time; If the page fails the compatibility check, the target version of the APP supported by the page is adjusted and the compatibility check is performed again.

Images