Interface configuration method of client application program, client equipment, server and storage medium

The method addresses interface compatibility issues by dynamically adjusting the client application interface based on user preferences and device information, ensuring smooth operation across different versions and enhancing user satisfaction.

CN119225844APending Publication Date: 2024-12-31UBTECH ROBOTICS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411149657.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-31

AI Technical Summary

Technical Problem

After a new version of the client APP is released, user-end devices running the old version may not function smoothly on the new interface due to interface changes, and compatibility issues arise due to varying operating system versions.

Method used

A method for configuring the client application interface by acquiring user preference information and device information, reporting to a server for a recommended interface allocation, and dynamically adjusting the interface to the latest version while monitoring performance data for compatibility.

Benefits of technology

Enhances user experience by ensuring compatibility and efficient version management, reducing user loss from incompatibility and improving application performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119225844A_ABST
    Figure CN119225844A_ABST
Patent Text Reader

Abstract

The invention belongs to the technical field of Internet, and provides an interface configuration method of a client application program, user side equipment, a server and a storage medium, the method comprises the following steps: the user side equipment obtains preference information of a user, and the preference information is generated based on behavior information generated by the user using a local client; then determining the equipment information of the user side equipment and the current version of the local client side; and reporting the preference information, the equipment information and the current version to a server, and finally enabling the server to distribute a recommendation type interface for the local client according to the preference information, the equipment information and the current version. The technical problem that after a server side pushes out a new version of a client APP, a client APP may not be normally used on a latest type interface when a client device operates a local client can be solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of Internet technology, and in particular, relates to an interface configuration method for a client application, a user terminal device, a server, and a storage medium. Background Art

[0002] With the rapid development of mobile Internet, frequent iteration and functional update requirements of APP (application) have become the norm in the industry.

[0003] However, after a new version of the APP is released on the server side, there are often interface changes. If users do not upgrade their local APP version on their terminal devices, the old version of the APP may not run smoothly on the new interface, or even fail to function. Summary of the invention

[0004] In view of this, an embodiment of the present application provides an interface configuration method for a client application, a user-end device, a server and a storage medium to solve the technical problem in the prior art that after a new version of the client APP is launched, the user-end device running the local client may not be able to use the client APP normally on the latest type of interface.

[0005] The first aspect of the embodiment of the present application provides a method for configuring an interface of a client application, the method being applied to a user terminal device having a local client installed thereon, the method comprising:

[0006] Acquire user preference information, where the preference information is generated based on behavior information generated by the user using the local client;

[0007] Determine device information of the user terminal device and a current version of the local client;

[0008] The preference information, the device information and the current version are reported to a server, so that the server allocates a recommended type interface to the local client according to the preference information, the device information and the current version.

[0009] In one embodiment, when the current version of the local client is not the latest version, the method includes:

[0010] Acquire recommended configuration information fed back by the server, where the recommended configuration information is generated based on the preference information, the device information and the current version, and the accessory configuration information includes a recommended type interface;

[0011] The local client is configured based on the recommended configuration information to cooperate with calling the recommended type interface.

[0012] In one embodiment, when the recommended configuration information includes version upgrade policy information, the method further includes:

[0013] In response to the user's upgrade confirmation operation, adjusting the interface type of the local client to the latest type of interface corresponding to the latest version of the client;

[0014] In the process of upgrading the current version of the local client from the original version to the latest version, collecting performance data of the local client when calling the latest type of interface;

[0015] The performance data is analyzed, and based on the performance data analysis result, the version and / or interface type currently used by the local client is adjusted.

[0016] In one embodiment, the method further comprises:

[0017] If the performance data does not meet the preset indicator conditions, the current version of the local client is rolled back from the latest version to the original version.

[0018] In one embodiment, the method comprises:

[0019] Configuring a first adapter for the target business application in a preset cache space, and configuring a second adapter for the public login module;

[0020] Establishing a channel connection between the public login module and the standard service application through the first adapter and the second adapter;

[0021] The first adapter is used to assist the target business application in monitoring messages sent by the public login module to the target business application, and the second adapter is used to assist the public login module in monitoring messages fed back by the target business application to the public login module.

[0022] In one embodiment, the method further comprises:

[0023] Responding to a user data update request initiated by the user to the public login module, so that the public login module updates the user portrait data in the user account according to the user data update request and generates new user portrait data;

[0024] After the public login module authorizes the user account to log in to the target business application, the new user portrait data is transmitted to the public login module, and the new user portrait data is used to assist the public login module in obtaining recommendation information related to the new user portrait data.

[0025] A second aspect of an embodiment of the present application provides an interface configuration method for a client application, the method being applied to a server, the method comprising:

[0026] Acquire user preference information fed back by a user terminal device on which a local client is installed, device information of the user terminal device, and a current version of the local client;

[0027] A recommended type interface is allocated to the client according to the preference information, the device information and the current version.

[0028] In one embodiment, the method further comprises:

[0029] When the current version of the local client is not the latest version, obtaining the current interface type of the local client and the latest type interface corresponding to the latest version;

[0030] determining the compatibility between the local client and the latest type of interface according to the preference information, the device information and the current interface type;

[0031] In a case where the compatibility does not satisfy a preset compatibility condition, the step of allocating a recommended type interface to the client according to the preference information, the device information and the current version is performed.

[0032] In one embodiment, allocating a recommended type interface to the client according to the preference information, the device information, and the current version includes:

[0033] generating recommended configuration information for the client according to the preference information, the device information and the current version, the accessory configuration information including a recommended type interface;

[0034] The recommended configuration information is sent to the user terminal device, so that the user terminal device configures the local client based on the recommended configuration information.

[0035] A third aspect of an embodiment of the present application provides a user terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the interface configuration method of the client application as described in the first aspect are implemented.

[0036] The fourth aspect of an embodiment of the present application provides a server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the interface configuration method of the client application as described in the second aspect are implemented.

[0037] A fifth aspect of an embodiment of the present application provides a storage medium, which is a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the interface configuration method of the client application described in the first aspect and the second aspect are implemented.

[0038] The beneficial effects of this application are: the user terminal device obtains the user's preference information, which is generated based on the behavior information generated by the user using the local client; then determines the device information of the user terminal device and the current version of the local client; then reports the preference information, the device information and the current version to the server, and finally enables the server to assign a recommended type interface to the local client based on the preference information, the device information and the current version. It can solve the technical problem that after the server launches a new version of the client APP, the user terminal device running the local client may not be able to use the client APP normally on the latest type of interface. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] Figure 1 It is a flowchart of an embodiment of a method for configuring an interface of a client application provided in an embodiment of the present application;

[0041] Figure 2 It is a flowchart of another embodiment of the method for configuring the interface of the client application provided in the embodiment of the present application;

[0042] Figure 3 It is a structural diagram of a server provided in an embodiment of the present application;

[0043] Figure 4 This is a structural block diagram of an interface configuration device for a client application provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0045] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0046] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0047] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0048] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0049] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0050] It is understandable that after the new version of the APP is released on the server side, there will often be changes in the interface. If the user does not upgrade the local APP version on his terminal device, it is easy to cause the old version of the APP to run poorly on the new interface, or even cause functional failures. In addition, due to the differences in the operating system versions of the terminal devices used by different users, the compatibility requirements for the new version are also different. Therefore, how to efficiently and intelligently manage and upgrade the client APP interface version while ensuring the compatibility of terminal devices has become a technical problem that needs to be solved urgently.

[0051] In response to the above technical problems, the embodiments of the present application provide an interface configuration method for a client application, a user terminal device, a server and a storage medium. The technical solution of the present invention is introduced below through specific embodiments.

[0052] Embodiment 1

[0053] like Figure 1 As shown, an embodiment of the present application provides an interface configuration method of a client application, and the method is applied to a user terminal device with a local client installed. The interface configuration method of a client application provided in this embodiment includes the following steps:

[0054] Step S10: The user terminal device obtains the user's preference information, where the preference information is generated based on the behavior information generated by the user using the local client;

[0055] In an embodiment of the present application, the client will collect user behavior information and generate user preference information. The preference information will help the data analysis module on the server side to subsequently determine which modules of the client are functional modules that are frequently used by the user, and help the auxiliary data analysis module to generate a relatively stable app version type interface API containing these functional modules.

[0056] Step S20: Determine the device information of the user terminal device and the current version of the local client;

[0057] In the embodiment of the present application, the client is responsible for collecting the behavior information generated by the user using the local client, and generating the user's preference information based on the behavior information;

[0058] The client is also responsible for collecting device information of the user terminal device, which may be a smart phone, desktop computer, laptop computer, tablet computer, intelligent robot, etc.

[0059] The client is also responsible for collecting the current version of the client (ie, the current APP version number). Different versions of the client correspond to different type interface APIs.

[0060] Step S30: reporting the preference information, the device information and the current version to the server, so that the server allocates a recommended type interface to the local client according to the preference information, the device information and the current version.

[0061] It is understandable that the user-side device will automatically report its device information, user preference information, and the current version of the client to the server. The server can determine the compatibility of the client and the interface based on the reported information, or formulate an upgrade strategy for the user client, and can also push corresponding upgrade instructions or data to the client; and the data analysis module collects user information, upgrade behavior and other data fed back by the user-side device to continuously optimize the upgrade strategy. It can solve the technical problem that after the server launches a new version of the client APP, the user-side device running the local client may not be able to use the client APP normally on the latest type of interface.

[0062] Further, refer to Figure 2 In the case where the current version of the local client is not the latest version, the server side executes the interface configuration method of the embodiment of the present application further comprising:

[0063] Step S01: The server side determines the compatibility between the local client and the latest type of interface according to the user's preference information, the device information of the user terminal device and the current interface type of the local client;

[0064] Step S02: when the compatibility does not meet the preset compatibility condition, executing the step S30 "assigning a recommended type interface to the client according to the preference information, the device information and the current version" and the specific step "generating recommended configuration information for the client according to the preference information, the device information and the current version";

[0065] Step S03: Send the recommended configuration information to the user terminal device, so that the user terminal device configures the local client based on the recommended configuration information.

[0066] In the specific implementation, a database will be deployed on the server side. The first data table of the database is used to show the compatibility relationship between the client's API version (i.e., interface type) and the device information on the user side. The first data can also be specifically expressed in a certain client version or a certain module function under a certain API version and the device information on the user side. In addition, a version mapping table is also established in the database. The version mapping table records the API interface type corresponding to each client APP version, so that the server side can intelligently match the server-side interface API type according to the user client APP version. In addition, the database can also establish a centralized API interface type table to store all historical API interface type information, including but not limited to interface URL, request parameters, response format, etc. The API interface type table and the mapping table form a primary and foreign key association relationship.

[0067] In the case that the current version of the user's local client is not the latest version, the server side will quickly determine whether the latest type of interface of the new version provided by the server side is applicable to the user's old version of the client based on the collected log information of the user's client. The log information may include the user's error log, for example, the log information will contain specific information of the compatibility error, which includes the unique identification ID of the user account, the device information of the user's terminal device, and the specific error information. Through log analysis, it is predicted that the local client used by the user may have potential compatibility issues, and the recommended type interface suitable for the device information of the user's terminal device is searched from the database.

[0068] In this embodiment, the server side generates recommended configuration information for the client based on the preference information, device information and current version. The recommended configuration information may include recommended type interface and version upgrade strategy information:

[0069] The local client of the user terminal device configures the local client based on the recommended configuration information sent by the server side, and dynamically adjusts its internal API call logic to correctly call the recommended type interface provided by the server side;

[0070] After the server provides version upgrade policy information to the user's local user terminal (it can be by sending upgrade prompt information to the user for selection, allowing the user to choose automatic upgrade or manual upgrade), the user can choose to upgrade, and the client responds to the user's upgrade confirmation operation and adjusts the interface type of the local client to the latest type of interface corresponding to the latest version of the client; in addition, in the process of upgrading the current version of the local client from the original version to the latest version, the server can collect performance data of the local client when calling the latest type of interface. It is understandable that after the server launches a new version of the client, the user is allowed to upgrade to the new version first, observe compatibility issues, and gradually expand the upgrade scope.

[0071] For example, in a specific implementation, monitoring points can be set at the entry point of the local client that calls the latest type of interface API, key business logic processing points, and database interaction points to collect performance data of various module functions of the client using the latest type of interface. Performance data can include indicators such as call status, success rate, and response time.

[0072] The data analysis module can analyze the collected performance data, and adjust the version and / or interface type currently used by the local client based on the performance data analysis result.

[0073] For example, if the performance data does not meet the preset indicator conditions, the current version of the local client is rolled back from the latest version to the original version. For example, it may be due to interface incompatibility, resulting in an error; another reason is that the application frequently exits, which may be due to incompatibility between the application version and the mobile phone. For example, after the client version is updated, most of the new functional modules cannot be used because the device type of the user-end device is incompatible with the new version. It is necessary to consider downgrading the version and provide the client with a one-click rollback function to the previous stable version to ensure user experience.

[0074] In some other embodiments, after the server launches a new version of the client APP, the server will push detailed upgrade instructions to the user's terminal device, introducing the main improvements and new features of the new version to stimulate the user's interest in upgrading.

[0075] When there are important updates or it is discovered that the client APP version used by the user no longer supports certain key functions, the user is guided to upgrade through push notifications or in-app prompts.

[0076] The beneficial effect of this embodiment is that by providing the client with recommended configuration information including recommended type interface and / or version upgrade strategy information, the automation level and efficiency of client APP upgrade can be significantly improved, and user loss caused by version incompatibility can be reduced. Through refined management, it is ensured that users in different device environments can obtain the best application experience, and user satisfaction and market competitiveness of client APP are enhanced.

[0077] Embodiment 2

[0078] Figure 3 The schematic diagram of the structure of the computer device on the server 1 side provided in the embodiment of the present application, that is, the server 1 can be a computer device such as a laptop computer, a desktop computer, etc., and the server obtains the user's preference information fed back by the user terminal device 2 installed with the local client, the device information of the user terminal device 2, and the current version of the local client; then the server allocates a recommended type interface to the client according to the preference information, the device information and the current version by calling its data analysis module. The user terminal device 2 can be a computer device such as a smart phone, a laptop computer, a desktop computer, etc.

[0079] The server 1 stores a computer program 22 related to the interface configuration of the client application program; Figure 3 As shown, the server 1 includes a processor 20, a memory 21, and a computer program 22 related to the interface configuration of the client application stored on the memory 21 (of course, since the user-end device 2 is also a computer device, it should also have a processor, a memory, and related computer programs stored on the memory, which will not be repeated in detail in the embodiments of the present application).

[0080] It should be understood that in the embodiment of the present application, the processor 20 may be a CPU, or may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0081] The memory 21 may include a read-only memory and a random access memory, and provide instructions and data to the processor 20. The memory 21 may also include a non-volatile random access memory. The memory 21 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct memory bus random access memory (DR RAM).

[0082] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid state drive (SSD).

[0083] Furthermore, in one embodiment, if Figure 4 As shown, the present invention also provides an interface configuration system for a client application, comprising:

[0084] The client information collection module 100 is used to collect the user's preference information, the device information of the user's terminal device, and the current version of the local client;

[0085] The server processing module 200 is used to allocate a recommended type interface to the local client according to the preference information, the device information and the current version;

[0086] The client information collection module 100 is further used to collect the performance data of the local client when calling the latest type of interface during the process of upgrading the current version of the local client from the original version to the latest version;

[0087] The data analysis module 300 is used to analyze the performance data and adjust the version and / or interface type currently used by the local client based on the performance data analysis result.

[0088] It should be noted that the client information collection module 100 can be deployed on the server 1 and / or the user terminal 2; the server processing module 200 and the data analysis module 300 are mainly deployed on the server 1; and in special cases, that is, for some user terminals 2 with relatively strong hardware performance, the data analysis module 300 can also be deployed.

[0089] Since the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application, their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0090] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / functional modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

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

[0092] An embodiment of the present application further provides a storage medium, which is a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the interface configuration method embodiments of the above-mentioned client application programs can be implemented.

[0093] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0094] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

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

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

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

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

[0099] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for configuring an interface of a client application, characterized in that: The method is applied to a user terminal device having a local client installed thereon, and the method comprises: Acquire user preference information, where the preference information is generated based on behavior information generated by the user using the local client; Determine device information of the user terminal device and a current version of the local client; The preference information, the device information and the current version are reported to a server, so that the server allocates a recommended type interface to the local client according to the preference information, the device information and the current version.

2. The method according to claim 1, characterized in that When the current version of the local client is not the latest version, the method includes: Acquire recommended configuration information fed back by the server, where the recommended configuration information is generated based on the preference information, the device information and the current version, and the accessory configuration information includes a recommended type interface; The local client is configured based on the recommended configuration information to cooperate with calling the recommended type interface.

3. The method according to claim 2, characterized in that In the case where the recommended configuration information includes version upgrade policy information, the method further includes: In response to the user's upgrade confirmation operation, adjusting the interface type of the local client to the latest type of interface corresponding to the latest version of the client; In the process of upgrading the current version of the local client from the original version to the latest version, collecting performance data of the local client when calling the latest type of interface; The performance data is analyzed, and based on the performance data analysis result, the version and / or interface type currently used by the local client is adjusted.

4. The method according to claim 3, characterized in that The method further comprises: When the performance data does not meet the preset indicator condition, the current version of the local client is rolled back from the latest version to the original version.

5. A method for configuring an interface of a client application, characterized in that: The method is applied to a server, and the method comprises: Acquire user preference information fed back by a user terminal device on which a local client is installed, device information of the user terminal device, and a current version of the local client; A recommended type interface is allocated to the client according to the preference information, the device information and the current version.

6. The method according to claim 5, characterized in that The method further comprises: When the current version of the local client is not the latest version, obtaining the current interface type of the local client and the latest type interface corresponding to the latest version; determining the compatibility between the local client and the latest type of interface according to the preference information, the device information and the current interface type; In a case where the compatibility does not satisfy a preset compatibility condition, the step of allocating a recommended type interface to the client according to the preference information, the device information and the current version is performed.

7. The method according to claim 5, characterized in that The allocating a recommended type interface to the client according to the preference information, the device information and the current version includes: generating recommended configuration information for the client according to the preference information, the device information and the current version, the accessory configuration information including a recommended type interface; The recommended configuration information is sent to the user terminal device, so that the user terminal device configures the local client based on the recommended configuration information.

8. A user terminal device, characterized in that: The user terminal device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the interface configuration method of the client application as described in any one of claims 1 to 4 when executing the computer program.

9. A server, characterized in that: The server includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the interface configuration method of the client application as described in any one of claims 5 to 7 when executing the computer program.

10. A storage medium, wherein the storage medium is a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein: When the computer program is executed by a processor, the steps of the interface configuration method of the client application program as claimed in claims 1 to 7 are implemented.