Performance evaluation method and device for card type interface generation tool, medium and equipment

By identifying the lifecycle stages of the card-based interface generation tool, filtering relevant evaluation dimensions and matching weights, the problem of the relevance and accuracy of performance evaluation in existing technologies is solved, resulting in more accurate evaluation results and tool optimization.

CN121637181APending Publication Date: 2026-03-10INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-05
Publication Date
2026-03-10

AI Technical Summary

Technical Problem

Existing performance evaluation methods for card-based interface generation tools lack specificity and accuracy, making it difficult to effectively identify core performance bottlenecks at each lifecycle stage, resulting in evaluation results that do not match actual performance.

Method used

By identifying the current lifecycle stage of the card-style interface, the most relevant performance evaluation dimensions are selected and their evaluation weights are matched. Performance data is collected based on the target evaluation dimensions to generate a target performance score, ensuring that the evaluation focus is locked on the core performance bottlenecks of the current lifecycle stage.

Benefits of technology

It significantly improves the relevance and accuracy of performance evaluation, drives developers to make targeted optimizations for each lifecycle node, and enables continuous iteration and upgrading of tool capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121637181A_ABST
    Figure CN121637181A_ABST
Patent Text Reader

Abstract

The invention discloses a performance evaluation method and device for a card type interface generation tool, a storage medium and electronic equipment, and the method comprises the steps: in a process of generating a card type interface for mobile equipment through employing a to-be-evaluated tool, carrying out the recognition of a current life cycle stage of the card type interface, and obtaining a current life stage of the card type interface; determining a target evaluation dimension from the candidate evaluation dimensions based on the current life stage of the card type interface, and determining a target evaluation weight from the candidate evaluation weights based on the target evaluation dimension; acquiring performance evaluation data of the to-be-evaluated tool based on the target evaluation dimension to obtain target performance data, and determining a target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight; and determining a performance evaluation result of the to-be-evaluated tool in the current life stage based on the target performance score and the target evaluation weight. By executing the technical scheme of the invention, the accuracy of performance evaluation can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the fields of artificial intelligence and software development technology, and can be applied to financial technology scenarios. Specifically, this application relates to a performance evaluation method, apparatus, storage medium, and electronic device for a card-type interface generation tool. Background Technology

[0002] With the rapid development of mobile internet technology, card-based user interfaces have become the mainstream design paradigm for mobile applications due to their simplicity, information aggregation, and cross-platform adaptability. To improve development efficiency, various card-based interface generation tools have emerged, using automation technology to help developers quickly build interactive interfaces suitable for mobile devices such as smartphones and tablets.

[0003] Performance evaluation of card-based interface generation tools can provide a reliable basis for tool selection, continuous optimization, and quality monitoring, which is of great significance for further improving the efficiency and quality of mobile application development. Summary of the Invention

[0004] This application provides a method, apparatus, storage medium, and electronic device for evaluating the performance of a card-based interface generation tool, which can improve the accuracy of performance evaluation for card-based interface generation tools.

[0005] According to a first aspect of this application, a performance evaluation method for a card-based interface generation tool is provided, the method comprising:

[0006] In the process of generating a card-style interface for a mobile device using the tool to be evaluated, the current life cycle stage of the card-style interface is identified to obtain the current life cycle stage of the card-style interface.

[0007] Based on the current life stage of the card-style interface, the target evaluation dimension is determined from the candidate evaluation dimensions, and the target evaluation weight is determined from the candidate evaluation weights based on the target evaluation dimension.

[0008] Based on the target evaluation dimensions, the performance evaluation data of the tool to be evaluated is collected to obtain target performance data, and based on the target performance data, the target evaluation dimensions, and the target evaluation weights, the target performance score corresponding to the current life stage is determined.

[0009] Based on the target performance score and the target evaluation weight, the performance evaluation result of the tool to be evaluated at the current life stage is determined.

[0010] According to a second aspect of this application, a performance evaluation apparatus for a card-based interface generation tool is provided, the apparatus comprising:

[0011] The lifecycle stage identification module is used to identify the current lifecycle stage of the card-style interface during the process of generating a card-style interface for a mobile device using the tool to be evaluated.

[0012] The dimension and weight determination module is used to determine the target evaluation dimension from the candidate evaluation dimensions based on the current life stage of the card-style interface, and to determine the target evaluation weight from the candidate evaluation weights based on the target evaluation dimension.

[0013] The performance data acquisition module is used to collect performance evaluation data of the tool to be evaluated based on the target evaluation dimension to obtain target performance data, and to determine the target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight.

[0014] The evaluation result determination module is used to determine the performance evaluation result of the tool to be evaluated at the current life stage based on the target performance score and the target evaluation weight.

[0015] According to a third aspect of the present invention, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a performance evaluation method for a card-based interface generation tool as described in embodiments of this application.

[0016] According to a fourth aspect of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements a performance evaluation method for a card-based interface generation tool as described in the embodiments of the present application.

[0017] According to a fifth aspect of this application, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements a performance evaluation method for a card-based interface generation tool as described in embodiments of this application.

[0018] This technical solution identifies the current lifecycle stage of the card-style interface, filters the most relevant performance evaluation dimensions for that stage, and matches evaluation weights accordingly. This ensures that the performance evaluation focus remains on the core performance bottlenecks of the current lifecycle stage, significantly improving the relevance and timeliness of the evaluation. Furthermore, performance data collected based on the target evaluation dimensions provides quantitative evidence, the target evaluation dimensions organize the evaluation logic framework, and the target evaluation weights quantify the relative influence of different dimensions on the performance of the tool being evaluated. The target performance score generated collaboratively by these three factors objectively reflects the true performance of the tool on the key evaluation dimensions. Finally, the performance evaluation result of the tool at the current lifecycle stage is determined based on the target evaluation weights and the target performance score, ensuring that the performance of high-weight dimensions dominates the final conclusion and guaranteeing the effectiveness and accuracy of the performance evaluation. This technical solution not only significantly improves the consistency between the evaluation results and the actual performance of the tool but also drives developers to optimize the key performance at each lifecycle node in a targeted manner, achieving continuous iterative upgrades of the tool's capabilities.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of the performance evaluation method for the card-type interface generation tool provided in Embodiment 1;

[0022] Figure 2 This is a flowchart of the performance evaluation method for the card-type interface generation tool provided in Embodiment 2;

[0023] Figure 3 This is a schematic diagram of the performance evaluation device for the card-type interface generation tool provided in Embodiment 3 of this application;

[0024] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," "target," and "candidate," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Example 1

[0028] Figure 1 This is a flowchart of the performance evaluation method for the card-type interface generation tool provided in Embodiment 1. This embodiment is applicable to the performance evaluation of the card-type interface generation tool in scenarios such as tool selection, tool optimization, or tool quality monitoring. The method is executed by the performance evaluation model of the card-type interface generation tool, and can be executed by the performance evaluation device of the card-type interface generation tool. The performance evaluation device of the card-type interface generation tool is implemented in hardware and / or software and can be integrated into the electronic device running this system.

[0029] like Figure 1 As shown, the method includes:

[0030] S110. During the process of generating a card-style interface for a mobile device using the tool to be evaluated, the current lifecycle stage of the card-style interface is identified to obtain the current lifecycle stage of the card-style interface.

[0031] S120. Based on the current life stage of the card-style interface, determine the target evaluation dimension from the candidate evaluation dimensions, and based on the target evaluation dimension, determine the target evaluation weight from the candidate evaluation weights.

[0032] S130. Collect target performance data based on the target evaluation dimension of the performance evaluation data of the tool to be evaluated, and determine the target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight.

[0033] S140. Based on the target performance score and the target evaluation weight, determine the performance evaluation result of the tool to be evaluated in the current life stage.

[0034] The tool to be evaluated refers to the card-based interface generation tool whose performance needs to be evaluated. The tool to be evaluated constructs a card-based user interface for mobile devices based on the device environment and material data. A card-based user interface is a design method that displays information by dividing content into independent modules, or cards, characterized by clear structure, strong responsiveness, and distinct visual hierarchy. Mobile devices are electronic terminal devices that are portable, have wireless communication capabilities, and can independently run applications. They are typically operated by hand and possess mobility and multitasking capabilities. Examples of mobile devices include smartphones and tablets. The device environment includes device hardware, system version, and network conditions. Material data is the core input for constructing the card-based user interface and can include visual materials, interactive materials, and content materials. Optionally, the card-based interface generation tool constructs the card-based user interface based on a benchmark card library. This benchmark card library defines at least two types of general cards, each type including an architecture template, data architecture, interaction scripts, and access rules.

[0035] Optionally, during the process of generating a card-style interface for a mobile device using the device to be evaluated, the current lifecycle stage of the card-style interface can be identified through state monitoring or behavior analysis to obtain the current lifecycle stage of the card-style interface.

[0036] The lifecycle stages of a card-based interface include: the card-based interface generation stage, the card-based interface construction stage, the card-based interface runtime stage, and the card-based interface update stage. The current lifecycle stage refers to the current stage of the card-based interface's lifecycle. The current lifecycle stage is used to determine the evaluation dimensions used to assess the performance of the tool being evaluated. The key performance bottlenecks may differ at different lifecycle stages, and the evaluation dimensions used for performance evaluation will vary accordingly.

[0037] Among them, candidate evaluation dimensions refer to different aspects used to measure tool performance, which can cover key performance bottlenecks that may occur throughout the entire lifecycle of the card-based interface. Each lifecycle stage of the card-based interface has corresponding evaluation indicator dimensions, and the target evaluation dimension is a subset of performance dimensions that are most important to focus on and evaluate at the current lifecycle stage, selected from the candidate evaluation dimensions.

[0038] Different evaluation dimensions have significantly different impacts on tool performance. Evaluation weights are used to quantify the impact of evaluation dimensions on tool performance; the greater the impact, the higher the evaluation weight. Optionally, the evaluation weights corresponding to the evaluation dimensions can be determined based on a weight allocation logic that prioritizes core functionality and user experience, supported by basic safeguards and internal efficiency. Optionally, the target evaluation weights can be determined by judging whether the target evaluation dimension belongs to core functionality and affects user experience, or whether it belongs to basic safeguards and affects internal efficiency.

[0039] Among them, performance evaluation data refers to indicators that can reflect the performance of the tool being evaluated. Target performance data refers to the actual collected indicator values ​​corresponding to the target evaluation dimension, which can show the actual performance of the tool being evaluated in the target evaluation dimension.

[0040] Target performance data, target evaluation dimensions, and target evaluation weights are used to determine the target performance score of the tool to be evaluated at the current stage of its life cycle.

[0041] Target performance data serves as the foundational quantitative basis, providing data support for determining whether each evaluation dimension in the target evaluation framework meets the standards. Target evaluation dimensions organize the scoring logic, categorizing scattered performance data into specific evaluation dimensions to ensure comprehensive scoring. Target evaluation weights clarify the relative importance of different evaluation dimensions to the tool's performance evaluation by assigning weight values. The target performance data, target evaluation dimensions, and target evaluation weights work together to determine the target performance score, quantifying the performance of the tool under evaluation at its current lifecycle stage across the target evaluation dimensions.

[0042] The performance evaluation result of the tool under evaluation at its current lifecycle stage is determined based on the target performance score and the target evaluation weight. Optionally, the target performance score is weighted using the target evaluation weight, and the weighted result is used as the performance evaluation result of the tool under evaluation at its current lifecycle stage. This technical solution identifies the current lifecycle stage of the card-style interface, filters the most relevant performance evaluation dimensions for the current lifecycle stage, and matches evaluation weights, ensuring that the performance evaluation focus is always locked on the core performance bottlenecks of the current lifecycle stage, significantly improving the relevance and timeliness of the evaluation. Furthermore, performance data collected based on the target evaluation dimensions provides quantitative evidence, the target evaluation dimensions organize the evaluation logic framework, and the target evaluation weight quantifies the relative influence of different dimensions on the performance of the tool under evaluation. The target performance score generated by the collaboration of these three factors objectively reflects the true performance of the tool under evaluation on key evaluation dimensions. Finally, the performance evaluation result of the tool under evaluation at its current lifecycle stage is determined based on the target evaluation weight and the target performance score, ensuring that the performance of high-weight dimensions dominates the final conclusion and guaranteeing the effectiveness and accuracy of the performance evaluation. The technical solution proposed in this application not only significantly improves the consistency between the evaluation results and the actual performance of the tool, but also drives developers to optimize the key performance of each lifecycle node in a targeted manner, thereby achieving continuous iterative upgrades of the tool's capabilities.

[0043] In an optional embodiment, the current lifecycle stage of the card-style interface is: the card-style interface generation stage, the card-style interface construction stage, the card-style interface operation stage, or the card-style interface update stage.

[0044] The card-based interface generation phase refers to the stage where the interface code is generated for the mobile device using the tool to be evaluated. This generation phase marks the beginning of the card-based interface's lifecycle. The building phase involves packaging the interface code into an installation package using the tool to be evaluated. The running phase involves running the installation package on the mobile device. The updating phase involves updating the content within the card-based interface. The generation phase is the end of the card-based interface's lifecycle; in other words, it is the final stage in its lifecycle.

[0045] The specific lifecycle stage of the card-style interface depends on the actual situation and is not specified here.

[0046] The above technical solution divides the lifecycle of the card-based interface into four stages: generation, construction, operation, and update, making performance evaluation time-specific. It supports dynamically matching evaluation dimensions and weights to the core performance bottlenecks at each lifecycle stage, which helps improve the accuracy of performance evaluation for card-based interface generation tools.

[0047] In an optional embodiment, determining the target evaluation weight from the candidate evaluation weights based on the target evaluation dimension includes: if the target evaluation dimension is an operational performance dimension or a generation capability dimension, then determining the target evaluation weight as the first-level weight among the candidate evaluation weights; if the target evaluation dimension is an experience quality dimension or an engineering efficiency dimension, then determining the target evaluation weight as the second-level weight among the candidate evaluation weights; if the target evaluation dimension is an operational health dimension, then determining the target evaluation weight as the third-level weight among the candidate evaluation weights; wherein, the weight value corresponding to the first-level weight is the largest, the weight value corresponding to the second-level weight is the smallest, and the weight value corresponding to the second-level weight is between the weight value corresponding to the first-level weight and the weight value corresponding to the third-level weight.

[0048] The candidate evaluation weights include three levels: high, medium, and low. A weight allocation logic is adopted, with core functionality and user experience at the core, and basic support and internal efficiency as supporting factors. Evaluation dimensions related to core functionality and user experience are assigned high-level evaluation weights, those related to basic support are assigned medium-level evaluation weights, and those related to internal efficiency are assigned low-level evaluation weights.

[0049] If the target evaluation dimension is either operational performance or generation capability, the first-level weight among the candidate evaluation weights will be determined as the target evaluation weight. The first-level weight is considered a high-level evaluation weight. The operational performance dimension evaluates the performance of the card-based interface. The performance of the card-based interface directly impacts the end-user experience; its performance in a real-world device environment is the ultimate test of the tool's output quality. Furthermore, performance bottlenecks in the card-based interface can reveal deficiencies in the tool being evaluated. The generation capability dimension evaluates the interface generation capability of the tool being evaluated. As the core output of the tool being evaluated, the card-based interface determines its fundamental value and functional implementation.

[0050] If the target evaluation dimension is either the experience quality dimension or the engineering efficiency dimension, then the second-level weight among the candidate evaluation weights will be determined as the target evaluation weight. The second-level weight belongs to the medium-level evaluation weight. The experience quality dimension evaluates the quality of the card experience, influencing user experience and being a crucial factor in improving user satisfaction. The engineering efficiency dimension evaluates the tool's engineering efficiency, primarily concerning the internal efficiency during the development or maintenance phases, with a relatively indirect direct impact on end users.

[0051] If the target evaluation dimension is the operational health dimension, then the third-level weight among the candidate evaluation weights will be determined as the target evaluation weight. The third-level weight is a low-level evaluation weight. The operational health dimension is used to evaluate the operational health of the cards, primarily concerning the long-term stable operation of the system. In the initial or core function verification phase, its priority may be lower than direct performance and user experience. The weight values ​​of the first, second, and third-level weights are determined based on the actual situation and are not limited here. For example, the first-level weights include 30% and 25%, setting the evaluation weight corresponding to the operational performance dimension to 30% and the evaluation weight corresponding to the generation capability dimension to 25%. The second-level weights include 20% and 15%, setting the evaluation weight corresponding to the card experience quality to 20% and the evaluation weight corresponding to the engineering efficiency dimension to 15%. The third-level weight includes 10%, setting the evaluation weight corresponding to the operational health dimension to 10%.

[0052] The above technical solution provides a weight allocation logic centered on core functionality and user experience, supported by basic safeguards and internal efficiency, to determine the evaluation weights corresponding to the evaluation dimensions. Quantifying the evaluation weights to determine the relative influence of different dimensions on the performance of the evaluation tool helps improve the accuracy of performance evaluation for card-based interface generation tools.

[0053] In an optional embodiment, determining the target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension, and the target evaluation weight includes: determining the total performance evaluation score corresponding to the target evaluation dimension based on the weight value of the target evaluation weight; determining the single-dimensional score corresponding to the target evaluation dimension based on the total performance evaluation score and the number of dimensions included in the target evaluation dimension; determining whether the target performance data corresponding to each dimension in the target evaluation dimension meets expectations to obtain the compliance evaluation dimension; and determining the target performance score corresponding to the current life stage based on the single-dimensional score and the number of dimensions of the compliance evaluation dimension.

[0054] The target evaluation dimension includes at least one indicator item, with each indicator item corresponding to one dimension. The total performance evaluation score refers to the sum of scores corresponding to all indicator items in the target evaluation dimension. Optionally, the weight value of the target evaluation weight can be used as the total performance evaluation score for the target evaluation dimension. For example, if the evaluation weight for the runtime performance dimension is 30%, the total performance evaluation score for the runtime performance dimension is 30 points.

[0055] Given a defined target evaluation dimension, determine the total number of metrics included within that dimension, and thus the total number of dimensions included in the target evaluation dimension. For example, the runtime performance dimension could include: cold start time, warm start time, frame rate during scrolling, CPU utilization during scrolling, memory usage during loading, and memory usage during loading—a total of six metrics. Therefore, the runtime performance dimension comprises six dimensions.

[0056] Here, the single-dimensional score refers to the score corresponding to each indicator item in the target evaluation index. Optionally, the quotient obtained by dividing the total performance evaluation score by the number of dimensions included in the target evaluation dimension is determined as the single-dimensional score corresponding to the target evaluation dimension. Continuing with the previous example, the single-dimensional score corresponding to the operational performance dimension is... .

[0057] Among them, the achievement evaluation dimension refers to the target evaluation dimension in which the target performance data meets expectations. The achievement evaluation dimension is used to determine the target performance score corresponding to the current life cycle stage. Optionally, the target performance score corresponding to the current life cycle stage can be determined by multiplying the number of achievement evaluation dimensions by the score of a single dimension.

[0058] The above technical solution utilizes the weight values ​​of the target evaluation weights to determine the total performance evaluation score corresponding to the target evaluation dimensions, ensuring that the differences in importance of different dimensions are objectively reflected in the performance score, making the evaluation results more aligned with actual business priorities. By dividing the total performance evaluation score by the number of dimensions included in the target evaluation dimensions to standardize it into a single-dimensional score, the impact of differences in the number of evaluation dimensions on the total performance evaluation score is eliminated, ensuring the horizontal comparability of scores across scenarios. Furthermore, by verifying the target performance data compliance dimensionally, the key dimensions that meet expectations are accurately identified, making the score not only reflect overall performance but also focus on the completion of core indicators. Finally, the total score is calculated by combining the number of compliant dimensions and the standardized single-dimensional scores, so that the scoring results simultaneously take into account the breadth of coverage of target achievement dimensions and the quality level of each dimension, forming a multi-dimensional balanced quantitative assessment. This design avoids subjective bias in weight allocation, solves the cardinality effect of dimensions through standardization, and strengthens the rigid constraints of key indicator achievement, thereby ensuring the accuracy of performance scoring.

[0059] In an optional embodiment, after determining the performance evaluation result of the tool to be evaluated in the current life stage based on the target performance score and the target evaluation weight, the method further includes: determining whether the current life stage is the update stage of the card-style interface; wherein the update stage of the card-style interface is the last life stage in the life cycle stages; if so, obtaining the performance evaluation results corresponding to the historical life stages; and performing a comprehensive performance evaluation of the tool to be evaluated based on the performance evaluation results corresponding to the current life stage and the performance evaluation results corresponding to the historical life stages.

[0060] Optionally, the current lifecycle stage of the card-based interface can be: the card-based interface generation stage, the card-based interface construction stage, the card-based interface runtime stage, or the card-based interface update stage.

[0061] If the current lifecycle stage is the update stage of the card-style interface, it means that the card-style interface has reached its final lifecycle stage. Historical lifecycle stages refer to all completed stages preceding the current lifecycle stage.

[0062] Each lifecycle stage has corresponding performance evaluation results. Optionally, the performance evaluation results refer to the evaluation output of the tool being evaluated at a certain lifecycle stage.

[0063] If the current lifecycle stage is the update stage of the card-style interface, then the historical lifecycle stages, combined with the current lifecycle stage, cover the entire lifecycle of the card-style interface. The comprehensive performance evaluation integrates the performance evaluation results from multiple lifecycle stages. Optionally, the performance evaluation results corresponding to the current lifecycle stage and the performance evaluation results corresponding to the historical lifecycle stages can be integrated to obtain the comprehensive performance evaluation of the tool being evaluated.

[0064] The aforementioned technical solution uses the final stage of the card-based interface as an evaluation opportunity. It not only assesses the performance of the tool under evaluation at its current lifecycle stage but also traces its performance throughout this stage, thereby generating a more comprehensive and dynamic overall performance evaluation. This helps to capture the performance trends, potential problems, and improvement opportunities of the tool throughout its entire lifecycle, improving the accuracy of performance evaluation and its decision support value, while also reflecting an optimization strategy based on a complete lifecycle perspective.

[0065] Example 2

[0066] Figure 2 This is a flowchart of the performance evaluation method for the card-based interface generation tool provided in Embodiment 2. This embodiment is a further optimization based on the above embodiments.

[0067] like Figure 2 As shown, the method includes:

[0068] S210. During the process of generating a card-style interface for a mobile device using the tool to be evaluated, the current lifecycle stage of the card-style interface is identified to obtain the current lifecycle stage of the card-style interface.

[0069] S220. If the current life stage of the card-style interface is the generation stage of the card-style interface, then the generation capability dimension used to evaluate the tool generation capability among the candidate evaluation dimensions is determined as the target evaluation dimension.

[0070] The card-based interface generation phase refers to the stage where the interface code is generated for the mobile device using the tool to be evaluated. This generation phase marks the beginning of the card-based interface's lifecycle.

[0071] During the card-based interface generation phase, generation capability was selected as the core evaluation indicator, focusing on the tool's performance in core capabilities such as content generation quality and creative adaptability.

[0072] S230. If the current life stage of the card-type interface is the construction stage of the card-type interface, then the engineering efficiency dimension used to evaluate the engineering efficiency of the tool among the candidate evaluation dimensions is determined as the target evaluation dimension.

[0073] The card-based interface development phase involves packaging the interface code into an installation package using the evaluation tool. Once in this phase, the evaluation focus shifts to engineering efficiency, emphasizing metrics such as code quality, development speed, and resource utilization.

[0074] S240. If the current life stage of the card-type interface is the running stage of the card-type interface, then the performance experience dimension used to evaluate the card experience quality and card running performance among the candidate evaluation dimensions is determined as the target evaluation dimension.

[0075] The card-style interface runtime phase refers to the phase in which the card-style interface installation package is run on the mobile device.

[0076] During the construction phase of the card-based interface, performance experience is used as the target evaluation metric, comprehensively considering runtime experience elements such as user interaction smoothness, response latency, and stability.

[0077] S250. If the current life stage of the card-type interface is the update stage of the card-type interface, then the operation and maintenance health dimension used to evaluate the operation and maintenance health of the card among the candidate evaluation dimensions is determined as the target evaluation dimension.

[0078] The update phase of a card-based interface refers to the phase where the content within the card-based interface is updated. The generation phase of a card-based interface marks the end of its lifecycle; in other words, the generation phase is the final stage in its lifecycle.

[0079] During the update phase of the card-style interface, the operational health dimension is used as the target evaluation dimension, focusing on sustainable operation and maintenance indicators such as error repair efficiency, version compatibility, and system maintainability.

[0080] S260. Determine the target evaluation weight from the candidate evaluation weights based on the target evaluation dimension.

[0081] S270. Collect target performance data based on the target evaluation dimension of the tool to be evaluated, and determine the target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight.

[0082] S280. Based on the target performance score and the target evaluation weight, determine the performance evaluation result of the tool to be evaluated in the current life stage.

[0083] The technical solution of this application dynamically matches the evaluation dimensions that best fit the core objectives of the current lifecycle stage according to the different lifecycle stages of the card-style interface. By establishing a strong correlation mapping between "lifecycle stage - evaluation dimension", it ensures that the evaluation focus of each stage is always consistent with the core task characteristics of that stage. This avoids misalignment of evaluation dimensions and accurately captures the key performance of each link, thereby providing a staged and targeted decision-making basis for tool optimization. It forms an adaptive evaluation dimension system that is synchronized with the lifecycle evolution, which not only ensures the independent evaluation accuracy of key capabilities at each stage, but also provides a continuous and traceable performance baseline for the overall evolution of the tool, ultimately achieving a leap in quality and efficiency from fragmented evaluation to systematic optimization.

[0084] In an optional embodiment, the generation capability dimension includes at least one of layout configuration, data operation, event binding, logic rendering, built-in component support and custom component support, style configuration, and script execution capability; the engineering efficiency dimension includes at least one of card building time and cross-platform reusability; the performance experience dimension includes experience quality dimension and runtime performance dimension, wherein the experience quality dimension includes at least one of device adaptability, card compatibility, layout misalignment rate, and rendering defect rate; the runtime performance dimension includes at least one of cold start time, warm start time, sliding frame rate, CPU utilization during sliding, memory usage during loading, and memory usage during loading; the operation and maintenance health dimension includes at least one of hot update success rate, interface crash rate, and degradation strategy effectiveness.

[0085] The generation capability dimension is used to evaluate the interface generation capabilities of the tool under evaluation. Layout configuration evaluates whether the tool supports setting and adjusting the size of the card-style interface; data manipulation evaluates whether the tool supports setting, obtaining, and modifying data; event binding evaluates whether the tool supports assigning click, long-press, and other operation events to the card-style interface; logic rendering evaluates whether the tool supports using conditional and loop logic to execute card-style interface rendering; built-in component support and custom component support evaluates whether the tool supports common user interface components such as text, rich text, images, partitions, carousels, and scrolling, and whether custom components are possible; style configuration evaluates whether the tool supports setting styles such as coordinates and layout for the card-style interface; and script execution capability evaluates whether the tool supports using functions. Optionally, the metrics corresponding to the generation capability dimension are verified based on the tool's application programming interface (API).

[0086] The engineering efficiency dimension is used to evaluate the engineering efficiency of the tool. Card build time refers to the time it takes to create a card-style interface using the tool being evaluated. Cross-platform reusability is used to evaluate whether the card-style interface created using the tool being evaluated can be directly used on mobile devices with different operating systems.

[0087] Among these, the experience quality dimension evaluates the card-based user experience, influencing user perception and being a crucial factor in improving user satisfaction. Device compatibility evaluates the display of the same card-based interface on mobile devices within the mobile device matrix. This mobile device matrix includes high-end, mid-range, and low-end mobile devices with different operating systems, screen sizes, and network conditions. Card compatibility refers to whether the same card-based interface displays correctly on mobile devices within the mobile device matrix. Layout misalignment rate reflects whether layout misalignment occurs on mobile devices within the mobile device matrix. Rendering defect rate reflects whether user interface anomalies occur on mobile devices within the mobile device matrix.

[0088] The performance dimension is used to evaluate the performance of the card-based interface. Cold start time refers to the time taken to initially load and display the card-based interface. Warm start time refers to the time taken to load and display the card-based interface again after the initial loading. Frame rate during scrolling refers to the frame rate while scrolling; CPU utilization during scrolling refers to the CPU utilization during scrolling; memory usage during loading refers to the memory used when the interface is loading; and memory usage during scrolling refers to the memory used when the interface is scrolling.

[0089] The operational health dimension is used to evaluate the operational health of the card interface. Hot update success rate refers to the requirement that the client needs to retrieve and display cards from the server in real time after the card interface is placed on the server. Based on this, the ability of the client to successfully update the card interface in real time is verified. Interface crash rate is obtained by statistically analyzing client display anomalies caused by data source anomalies and server timeouts. The effectiveness of the degradation strategy is verified by setting the default graph loading capability for the cards, and then verifying whether the card interface has a degradation strategy and whether the degradation is effective after the data source anomaly or server timeout prevents updating the card interface. In an optional embodiment, the performance evaluation results of the tool under evaluation at the current lifecycle stage are visualized, and further, the corresponding indicators can be displayed independently. Performance optimization suggestions for the tool are also provided.

[0090] The aforementioned technical solution, through the deep coupling of highly detailed dimensional indicators and lifecycle stages, establishes a complete value chain from code development to user reach and tool resilience, ensuring that the evaluation direction accurately matches the core objectives of each stage. This is beneficial for improving the accuracy of tool performance evaluation.

[0091] Example 3

[0092] Figure 3 This is a schematic diagram of the performance evaluation device for the card-type interface generation tool provided in Embodiment 3 of this application. This embodiment is applicable to the performance evaluation of the card-type interface generation tool in scenarios such as tool selection, tool optimization, or tool quality monitoring. The device is implemented by software and / or hardware and can be integrated into electronic devices such as smart terminals.

[0093] like Figure 3 As shown, the performance evaluation device 300 for the card-based interface generation tool may include:

[0094] Life stage identification module 310- is used to identify the current life stage of the card interface during the process of generating a card interface for a mobile device using the tool to be evaluated.

[0095] The dimension and weight determination module 320 is used to determine the target evaluation dimension from the candidate evaluation dimensions based on the current life stage of the card-style interface, and to determine the target evaluation weight from the candidate evaluation weights based on the target evaluation dimension.

[0096] The performance data acquisition module 330 is used to acquire the performance evaluation data of the tool to be evaluated based on the target evaluation dimension to obtain target performance data, and to determine the target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight.

[0097] The evaluation result determination module 340 is used to determine the performance evaluation result of the tool to be evaluated in the current life stage based on the target performance score and the target evaluation weight.

[0098] This technical solution identifies the current lifecycle stage of the card-style interface, filters the most relevant performance evaluation dimensions for that stage, and matches evaluation weights accordingly. This ensures that the performance evaluation focus remains on the core performance bottlenecks of the current lifecycle stage, significantly improving the relevance and timeliness of the evaluation. Furthermore, performance data collected based on the target evaluation dimensions provides quantitative evidence, the target evaluation dimensions organize the evaluation logic framework, and the target evaluation weights quantify the relative influence of different dimensions on the performance of the tool being evaluated. The target performance score generated collaboratively by these three factors objectively reflects the true performance of the tool on the key evaluation dimensions. Finally, the performance evaluation result of the tool at the current lifecycle stage is determined based on the target evaluation weights and the target performance score, ensuring that the performance of high-weight dimensions dominates the final conclusion and guaranteeing the effectiveness and accuracy of the performance evaluation. This technical solution not only significantly improves the consistency between the evaluation results and the actual performance of the tool but also drives developers to optimize the key performance at each lifecycle node in a targeted manner, achieving continuous iterative upgrades of the tool's capabilities.

[0099] Optionally, the current lifecycle stage of the card-style interface can be: the card-style interface generation stage, the card-style interface construction stage, the card-style interface operation stage, or the card-style interface update stage.

[0100] Optionally, the dimension and weight determination module 320 includes: a first dimension determination submodule, configured to determine the generation capability dimension used to evaluate tool generation capability among the candidate evaluation dimensions as the target evaluation dimension if the current life stage of the card interface is the generation stage of the card interface; a second dimension determination submodule, configured to determine the engineering efficiency dimension used to evaluate tool engineering efficiency among the candidate evaluation dimensions as the target evaluation dimension if the current life stage of the card interface is the construction stage of the card interface; a third dimension determination submodule, configured to determine the performance experience dimension used to evaluate card experience quality and card running performance among the candidate evaluation dimensions as the target evaluation dimension if the current life stage of the card interface is the running stage of the card interface; and a fourth dimension determination submodule, configured to determine the operation and maintenance health dimension used to evaluate card operation and maintenance health among the candidate evaluation dimensions as the target evaluation dimension if the current life stage of the card interface is the update stage of the card interface.

[0101] Optionally, the generation capability dimension includes at least one of layout configuration, data operation, event binding, logic rendering, built-in component support and custom component support, style configuration, and script execution capability; the engineering efficiency dimension includes at least one of card building time and cross-platform reusability; the performance experience dimension includes experience quality dimension and runtime performance dimension, wherein the experience quality dimension includes at least one of device adaptability, card compatibility, layout misalignment rate, and rendering defect rate; the runtime performance dimension includes at least one of cold start time, warm start time, sliding frame rate, central processing unit utilization during sliding, memory usage during loading, and memory usage during loading; the operation and maintenance health dimension includes at least one of hot update success rate, interface crash rate, and degradation strategy effectiveness.

[0102] Optionally, the dimension and weight determination module 320 includes: a first weight determination submodule, used to determine the target evaluation weight by selecting the first-level weight from the candidate evaluation weights if the target evaluation dimension is an operational performance dimension or a generation capability dimension; a second weight determination submodule, used to determine the target evaluation weight by selecting the second-level weight from the candidate evaluation weights if the target evaluation dimension is an experience quality dimension or an engineering efficiency dimension; and a third weight determination submodule, used to determine the target evaluation weight by selecting the third-level weight from the candidate evaluation weights if the target evaluation dimension is an operational health dimension; wherein the weight value corresponding to the first-level weight is the largest, the weight value corresponding to the first-level weight is the smallest, and the weight value corresponding to the second-level weight is between the weight value corresponding to the first-level weight and the weight value corresponding to the third-level weight.

[0103] Optionally, the performance data acquisition module 330 includes: a total evaluation score determination submodule, used to determine the total performance evaluation score corresponding to the target evaluation dimension based on the weight value of the target evaluation weight; a dimension score determination submodule, used to determine the single dimension score corresponding to the target evaluation dimension based on the total performance evaluation score and the number of dimensions included in the target evaluation dimension; a target-compliant dimension determination submodule, used to determine whether the target performance data corresponding to each dimension in the target evaluation dimension meets expectations, so as to obtain the target-compliant evaluation dimension; and a performance score determination submodule, used to determine the target performance score corresponding to the current life stage based on the single dimension score and the number of dimensions of the target-compliant evaluation dimension.

[0104] Optionally, the device further includes: a final stage discrimination module, configured to determine whether the current life stage is an update stage of the card-style interface after determining the performance evaluation result of the tool to be evaluated in the current life stage based on the target performance score and the target evaluation weight; wherein the update stage of the card-style interface is the final life stage in the life cycle stages; an evaluation result acquisition module, configured to acquire the performance evaluation result corresponding to the historical life stage if so; and a comprehensive performance evaluation module, configured to perform a comprehensive performance evaluation of the tool to be evaluated based on the performance evaluation result corresponding to the current life stage and the performance evaluation result corresponding to the historical life stage.

[0105] The performance evaluation device for the card-type interface generation tool provided in the embodiments of the invention can execute the performance evaluation method for the card-type interface generation tool provided in any embodiment of this application, and has the corresponding performance modules and beneficial effects for executing the performance evaluation method for the card-type interface generation tool.

[0106] In the technical solution of this application, the user data involved is information and data authorized by the user or fully authorized by all parties. The collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0107] Example 4

[0108] According to embodiments of this application, this application also provides an electronic device, a readable storage medium, and a computer program product.

[0109] Figure 4 A schematic diagram of an electronic device 410, which can be implemented using an embodiment, is shown. The electronic device 410 includes at least one processor 411 and a memory, such as a read-only memory 412 or a random access memory 413, communicatively connected to the at least one processor 411. The memory stores computer programs executable by the at least one processor. The processor 411 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 412 or loaded from storage unit 418 into the random access memory 413. The random access memory 413 may also store various programs and data required for the operation of the electronic device 410. The processor 411, read-only memory 412, and random access memory 413 are interconnected via a bus 414. An input / output interface 415 is also connected to the bus 414.

[0110] Multiple components in electronic device 410 are connected to input / output interface 415, including: input unit 416, such as keyboard, mouse, etc.; output unit 417, such as various types of monitors, speakers, etc.; storage unit 418, such as disk, optical disk, etc.; and communication unit 419, such as network card, modem, wireless transceiver, etc. Communication unit 419 allows electronic device 410 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0111] Processor 411 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 411 performs the various methods and processes described above, such as performance evaluation methods for card-based interface generation tools.

[0112] In some embodiments, the performance evaluation method for the card-based interface generation tool can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 410 via read-only memory 412 and / or communication unit 419. When the computer program is loaded into random access memory 413 and executed by processor 411, one or more steps of the performance evaluation method for the card-based interface generation tool described above can be performed. Alternatively, in other embodiments, processor 411 can be configured to execute the performance evaluation method for the card-based interface generation tool by any other suitable means (e.g., by means of firmware).

[0113] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), systems-on-a-chip (SoCs), complex programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0114] Computer programs used to implement the methods of this application may be written in any combination of one or more programming languages. These computer programs may be provided to the processor of a performance evaluation device for a general-purpose computer, a special-purpose computer, or other programmable card-based interface generation tool, such that when executed by the processor, the computer programs enable the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0115] In the context of this application, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory or flash memory, optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0116] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a cathode ray tube or liquid crystal display monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0117] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., a performance evaluation server as a card-based interface generation tool), or middleware components (e.g., an application server), or frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0118] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to address the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0119] This application also discloses a computer program product, which includes a computer program that, when executed by a processor, implements the performance evaluation method for the card-based interface generation tool provided in any embodiment of this application. This program product and the performance evaluation method for the card-based interface generation tool disclosed in the embodiments of this application belong to the same inventive concept, and therefore will not be described in detail here.

[0120] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this application can be achieved, and this is not limited herein.

[0121] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method of evaluating performance of a card interface generation tool, characterized by, The method comprises: In the process of generating a card interface for a mobile device by using a tool to be evaluated, a current life stage of the card interface is identified to obtain a current life stage of the card interface; A target evaluation dimension is determined from candidate evaluation dimensions based on the current life stage of the card interface, and a target evaluation weight is determined from candidate evaluation weights based on the target evaluation dimension; Target performance data of the tool to be evaluated is collected based on the target evaluation dimension to obtain target performance data, and a target performance score corresponding to the current life stage is determined based on the target performance data, the target evaluation dimension and the target evaluation weight; A performance evaluation result of the tool to be evaluated in the current life stage is determined based on the target performance score and the target evaluation weight.

2. The method of claim 1, wherein, The current life stage of the card interface is a generation stage, a construction stage, a running stage or an update stage of the card interface.

3. The method of claim 2, wherein, The target evaluation dimension is determined from the candidate evaluation dimensions based on the current life stage of the card interface, comprising: If the current life stage of the card interface is the generation stage of the card interface, a generation capability dimension for evaluating generation capability of the tool in the candidate evaluation dimensions is determined as the target evaluation dimension; If the current life stage of the card interface is the construction stage of the card interface, an engineering efficiency dimension for evaluating engineering efficiency of the tool in the candidate evaluation dimensions is determined as the target evaluation dimension; If the current life stage of the card interface is the running stage of the card interface, a performance experience dimension for evaluating card experience quality and card running performance in the candidate evaluation dimensions is determined as the target evaluation dimension; If the current life stage of the card interface is the update stage of the card interface, an operation and maintenance health dimension for evaluating card operation and maintenance health in the candidate evaluation dimensions is determined as the target evaluation dimension.

4. The method of claim 3, wherein, The generation capability dimension comprises at least one of layout configuration, data operation, event binding, logic rendering, built-in component support and custom component, style configuration and script execution capability; The engineering efficiency dimension comprises at least one of card construction duration and cross-platform reuse rate; the performance experience dimension comprises experience quality dimension and running performance dimension respectively, wherein the experience quality dimension comprises at least one of device adaptability, card compatibility, layout misplacement rate and rendering defect rate; the running performance dimension comprises at least one of cold start time, hot start time, sliding frame rate, sliding time central processing unit occupancy rate, loading time memory occupancy and loading time memory occupancy; the operation and maintenance health dimension comprises at least one of hot update success rate, interface crash rate and degradation strategy effectiveness.

5. The method of claim 1, wherein, The target evaluation weight is determined from the candidate evaluation weights based on the target evaluation dimension, comprising: If the target evaluation dimension is the running performance dimension or the generation capability dimension, a first level weight in the candidate evaluation weights is determined as the target evaluation weight; If the target evaluation dimension is the experience quality dimension or the engineering efficiency dimension, a second level weight in the candidate evaluation weight is determined as the target evaluation weight; If the target evaluation dimension is the operation and maintenance health dimension, a third level weight in the candidate evaluation weight is determined as the target evaluation weight; The first level weight corresponds to the largest weight value, the second level weight corresponds to the weight value between the weight value corresponding to the first level weight and the weight value corresponding to the third level weight.

6. The method of claim 1, wherein, The method further comprises: determining a total performance evaluation score corresponding to the target evaluation dimension based on the weight value of the target evaluation weight; determining a single dimension score corresponding to the target evaluation dimension based on the total performance evaluation score and the number of dimensions included in the target evaluation dimension; determining whether the target performance data corresponding to each dimension in the target evaluation dimension meets the expectation to obtain a dimension meeting the standard; determining the target performance score corresponding to the current life stage based on the single dimension score and the number of dimensions meeting the standard.

7. The method of claim 1, wherein, After determining the performance evaluation result of the tool to be evaluated in the current life stage based on the target performance score and the target evaluation weight, the method further comprises: determining whether the current life stage is an update stage of the card interface; wherein the update stage of the card interface is the last life stage in the life cycle stage; if yes, obtaining a performance evaluation result corresponding to a historical life stage; performing comprehensive performance evaluation on the tool to be evaluated based on the performance evaluation result corresponding to the current life stage and the performance evaluation result corresponding to the historical life stage.

8. A performance evaluation apparatus for a card interface generation tool, characterized by comprising: a card interface generation tool; a card interface generation tool performance evaluation program; and a card interface generation tool performance evaluation program execution unit. The device comprises: a life stage identification module configured to identify a current life stage of a card interface in a process of generating the card interface for a mobile device by using a tool to be evaluated to obtain a current life stage of the card interface; a dimension and weight determination module configured to determine a target evaluation dimension from candidate evaluation dimensions based on the current life stage of the card interface, and determine a target evaluation weight from candidate evaluation weights based on the target evaluation dimension; a performance data collection module configured to collect performance evaluation data of the tool to be evaluated based on the target evaluation dimension to obtain target performance data, and determine a target performance score corresponding to the current life stage based on the target performance data, the target evaluation dimension and the target evaluation weight; an evaluation result determination module configured to determine a performance evaluation result of the tool to be evaluated in the current life stage based on the target performance score and the target evaluation weight.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the performance evaluation method of the card interface generation tool according to any one of claims 1-7. The program is executed by the processor to implement the performance evaluation method of the card interface generation tool according to any one of claims 1-7.

10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The performance evaluation method of the card interface generation tool according to any one of claims 1-7 is implemented when the processor executes the computer program.