Interface conversion method, device and system

Abstract

The invention provides an interface conversion method, device and system, and the method comprises the steps: displaying a first interface after an electronic device detects a first operation of a user on the electronic device; the first interface comprises a first element and a second element; after the electronic equipment detects a second operation acting on the first interface by the user, at least one transition interface is displayed, and then a second interface is displayed; the second interface comprises the second element and a third element; the transition interface contains the second element; the second element does not contain elements in a status bar in the first interface, the transition interface and the second interface. According to the method, when the application interfaces are converted, the shared elements continuously exist or continuously change, so that the effect that the user experience is not interrupted is achieved.

Description

[0001] This application is a divisional application. The application number of the original application is 202110482721.0, and the original application date is April 30, 2021. The entire contents of the original application are incorporated into this application by reference.

[0002] This application claims the priority of the Chinese patent application filed with the China Patent Office on September 9, 2020, with application number 202010943693.3 and application name “A method and device for conversion between application interfaces”, the entire contents of which are incorporated by reference in this application. Technical Field

[0003] The present application relates to the field of terminal technology, and in particular to a method, device and system for converting between interfaces. Background Art

[0004] As device performance improves, users pay more and more attention to the experience of switching between interfaces when using electronic devices.

[0005] Currently, when the first interface and the second interface are converted, the first interface is directly switched to the second interface, the conversion effect is single, the continuity is poor, and the user experience is low. Summary of the invention

[0006] The present application provides a method, device and system for converting between interfaces, so as to provide a conversion solution with strong consistency.

[0007] A first aspect provides a method for converting between interfaces, comprising:

[0008] After the electronic device detects a first operation performed by a user on the electronic device, the first interface is displayed; the first interface includes a first element and a second element; after the electronic device detects a second operation performed by a user on the first interface, the electronic device displays at least one transition interface and then displays a second interface; the second interface includes the second element and a third element; the transition interface includes the second element; the second element does not include the elements in the first interface, the transition interface, and the status bar of the second interface.

[0009] Based on the above method, in the process of switching from the first interface to the second interface, the connection is made through at least one transition interface, and the transition interface contains a second element contained in both the first interface and the second interface, so that the first interface and the second interface change naturally during the switching process, with strong coherence and better user visual experience.

[0010] In a possible implementation, the first element in the first interface of the electronic device gradually disappears, the third element in the second interface gradually appears, and the second element continues to exist in the first interface, the at least one transition interface, and the second interface.

[0011] In a possible implementation, the electronic device executes the corresponding animation of the interface and / or element according to the transition animation configured for each interface or according to the transition animation configured for the element in the interface during the process of switching from the first interface to the second interface.

[0012] In one possible implementation, the first interface and the second interface are different display interfaces of a first application; or, the first interface is the main interface of the electronic device or an adjacent interface of the main interface or a negative one-screen interface, and the second interface is the display interface of the first application; or, the first interface is the display interface of the first application, and the second interface is the display interface of the second application.

[0013] A second aspect provides a method for converting between interfaces, including:

[0014] The electronic device determines an interface type according to an interface configuration instruction triggered by a user, and the interface type includes a first interface, at least one transition interface, and a second interface; wherein the transition interface refers to an intermediate connecting interface from the first interface to the second interface; the electronic device determines a first element and a second element in the first interface, and determines a second element and a third element in the second interface according to an element configuration instruction triggered by a user; wherein the transition interface contains the second element.

[0015] Based on the above method, in the conversion configuration of switching from the first interface to the second interface, at least one transition interface is configured for connection, and the transition interface contains a second element contained in both the first interface and the second interface, so that the first interface and the second interface change naturally and coherently during the switching process, and the user's visual experience is better. In addition, the application can configure different conversion types, various element types in the conversion, and animation effects according to its own needs to achieve a more flexible and smoother dynamic effect experience. The overall application is simple, the components are configurable, and the effect is better.

[0016] In a possible implementation, the electronic device determines the motion effects executed by the interface and / or elements during the process of switching from the first interface to the second interface according to the motion effect configuration instruction triggered by the user.

[0017] A third aspect provides a method for converting between interfaces, including:

[0018] After the electronic device detects a first operation performed by a user on the electronic device, the electronic device displays a first interface; the first interface includes a first element and a second element; after the electronic device detects a second operation performed by a user on the first interface, the electronic device displays at least one transition interface and then displays a second interface; the second interface includes a third element and a fourth element; in the process of switching from the first interface to the second interface through the at least one transition interface, the display form of the second element in the transition interface gradually changes to the display form of the third element; wherein, the second element is partially identical to the third element.

[0019] Based on the above method, in the conversion configuration of switching from the first interface to the second interface, at least one transition interface is configured for connection, and the transition interface contains the second element of the first interface and the third element of the second interface, and the second element is partially identical to the third element, so that the first interface and the second interface change naturally during the switching process, with strong coherence and better user visual experience.

[0020] In a possible implementation, the first element in the first interface of the electronic device gradually disappears, the fourth element in the second interface gradually appears, and the second element in the transition interface gradually becomes the third element.

[0021] In a possible implementation, the electronic device executes the corresponding animation of the interface and / or element according to the transition animation configured for each interface or according to the transition animation configured for the element in the interface during the process of switching from the first interface to the second interface.

[0022] In one possible implementation, the first interface and the second interface are different display interfaces of a first application; or, the first interface is the main interface of the electronic device or an adjacent interface of the main interface or a negative one-screen interface, and the second interface is the display interface of the first application; or, the first interface is the display interface of the first application, and the second interface is the display interface of the second application.

[0023] A fourth aspect provides a method for converting between interfaces, including:

[0024] The electronic device determines an interface type according to an interface configuration instruction triggered by a user, and the interface type includes a first interface, at least one transition interface and a second interface; wherein the transition interface refers to an intermediate connecting interface from the first interface to the second interface; the electronic device determines a first element and a second element in the first interface, and determines a third element and a fourth element in the second interface according to an element configuration instruction triggered by the user; according to the element configuration instruction triggered by the user, determines that the second element in the transition interface gradually changes to the third element; wherein the second element is partially identical to the third element.

[0025] Based on the above method, in the conversion configuration of switching from the first interface to the second interface, at least one transition interface is configured for connection, and the transition interface contains the second element of the first interface and the third element of the second interface, and the second element is partially the same as the third element, so that the first interface and the second interface can be switched naturally and coherently, and the user visual experience is better. In addition, the application can configure different conversion types, element types and animation effects in the conversion according to its own needs to achieve a more flexible and smoother dynamic effect experience. The overall application is simple, the components are configurable, and the effect is better.

[0026] In a possible implementation, the electronic device determines the motion effects executed by the interface and / or elements during the process of switching from the first interface to the second interface according to the motion effect configuration instruction triggered by the user.

[0027] A fifth aspect further provides an inter-interface device, which can be used to perform the operations in any possible implementation of the first aspect or the third aspect. For example, the device may include a module or unit for performing each operation in any possible implementation of the first aspect or the third aspect. For example, it includes a transceiver module and a processing module.

[0028] A sixth aspect further provides an electronic device between interfaces, which can be used to perform operations in any possible implementation of the second aspect or the fourth aspect. For example, the electronic device may include modules or units for performing each operation in any possible implementation of the second aspect or the fourth aspect. For example, it includes a transceiver module and a processing module.

[0029] The seventh aspect provides a chip system, including a processor and optionally a memory; wherein the memory is used to store computer programs, and the processor is used to call and run computer programs from the memory, so that an electronic device equipped with the chip system executes any method in any possible implementation method of the above-mentioned first to fourth aspects.

[0030] The eighth aspect provides a computer program product, which includes: a computer program code, which, when executed by a processing module or processor of an electronic device, enables the electronic device to execute any method in any possible implementation of the first to fourth aspects above.

[0031] A ninth aspect provides a computer-readable storage medium storing a program, wherein the program enables an electronic device to execute any method in any possible implementation of the first to fourth aspects.

[0032] The tenth aspect provides an electronic device, comprising: a display; one or more processors; one or more memories; wherein the one or more memories store one or more computer programs, and the one or more computer programs include instructions, and when the instructions are executed by the one or more processors, the electronic device executes any method in any possible implementation manner of the above-mentioned first to fourth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of the area division of an electronic device interface provided by an embodiment of the present application;

[0034] Figure 2 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0035] Figure 3 A schematic diagram of the internal structure of a platform-side device provided in an embodiment of the present application;

[0036] Figure 4 A schematic diagram of the structure of an Android operating system for a platform-side device provided in an embodiment of the present application;

[0037] Figure 5 A schematic diagram of the internal structure of an application-side device provided in an embodiment of the present application;

[0038] Figure 6 A schematic diagram of the structure of an Android operating system of an application-side device provided in an embodiment of the present application;

[0039] Figure 7 A flowchart for configuring the existing one-shot solution;

[0040] Figure 8 A schematic diagram of a one-shot logic framework provided in an embodiment of the present application;

[0041] Fig. 9 A schematic diagram of a logical framework of a configuration phase provided in an embodiment of the present application;

[0042] Fig.10A schematic diagram of an application included in an application-side device provided in an embodiment of the present application;

[0043] Fig.11 A schematic diagram of a scenario category provided in an embodiment of the present application;

[0044] Fig.12 A schematic diagram of element categories provided in an embodiment of the present application;

[0045] Fig.13 A schematic diagram of a conversion configuration provided in an embodiment of the present application;

[0046] Fig.14 A schematic diagram of a conversion effect provided in an embodiment of the present application;

[0047] Fig.15 A schematic diagram of an information container configuration provided in an embodiment of the present application;

[0048] Fig.16 A schematic diagram of a fast conversion configuration provided in an embodiment of the present application;

[0049] Fig.17 A schematic diagram of a first one-shot to bottom conversion effect provided in an embodiment of the present application;

[0050] Fig.18 A schematic diagram of a logical framework of a parsing stage provided in an embodiment of the present application;

[0051] Fig.19 A schematic diagram of a logical framework of an execution phase provided for an embodiment of the present application;

[0052] Fig. 20 A schematic diagram of a one-shot configuration method flow chart provided in an embodiment of the present application;

[0053] Fig.21 A schematic diagram of a call application conversion effect provided in Example 1 of the present application;

[0054] Fig. 22 A schematic diagram of the first application-to-application conversion effect provided in Example 1 of the present application;

[0055] Fig.23 A schematic diagram of the first desktop and application conversion effect provided in the first embodiment of the present application;

[0056] Fig.24 A schematic diagram of a book application conversion effect provided in Example 1 of the present application;

[0057] Fig.25 A schematic diagram of a gallery application conversion effect provided in Example 1 of the present application;

[0058] Fig.26A schematic diagram of the first music application conversion effect provided in Example 1 of the present application;

[0059] Fig. 27 A schematic diagram of a second music application conversion effect provided in Example 1 of the present application;

[0060] Fig.28 A schematic diagram of the second application-to-application conversion effect provided in the first embodiment of the present application;

[0061] Fig.29 A schematic diagram of a second desktop and application conversion effect provided in the first embodiment of the present application;

[0062] Fig.30 A schematic diagram of a calendar application conversion effect provided in Example 1 of the present application;

[0063] Fig.31 A schematic diagram of the third application and application conversion effect provided in the first embodiment of the present application;

[0064] Fig.32 A schematic diagram of a third desktop and application conversion effect provided in the first embodiment of the present application;

[0065] Fig.33 A schematic diagram of a call application conversion effect provided in Embodiment 2 of the present application;

[0066] Fig.34 A schematic diagram of the first application-to-application conversion effect provided in Embodiment 2 of the present application;

[0067] Fig.35 A schematic diagram of the first desktop and application conversion effect provided in the second embodiment of the present application;

[0068] Fig.36 A schematic diagram of a music application conversion effect provided in Embodiment 2 of the present application;

[0069] Fig.37 A schematic diagram of the second application-to-application conversion effect provided in the second embodiment of the present application;

[0070] Fig.38 A schematic diagram of a second desktop and application conversion effect provided in Embodiment 2 of the present application;

[0071] Fig.39 A schematic diagram of a calendar application conversion effect provided in Embodiment 2 of the present application;

[0072] Fig.40 A schematic diagram of the third application-to-application conversion effect provided in the second embodiment of the present application;

[0073] Fig.41 A schematic diagram of a third desktop and application conversion effect provided in the second embodiment of the present application;

[0074] Fig.42 A schematic diagram of the first application conversion effect based on split screen provided in an embodiment of the present application;

[0075] Fig.43 A schematic diagram of a second application conversion effect based on split screen provided in an embodiment of the present application;

[0076] Fig.44 A schematic diagram of an application conversion effect based on multi-screen collaboration provided in an embodiment of the present application;

[0077] Fig.45 A schematic diagram of the second application conversion effect based on multi-screen collaboration provided in an embodiment of the present application. DETAILED DESCRIPTION

[0078] For ease of understanding, some examples of concepts related to the embodiments of the present application are provided for reference, as shown below:

[0079] 1) One shot from beginning to end, in the embodiment of the present application, mainly refers to the first interface and the second interface. When the two interfaces are switched, there is at least one transition interface, wherein the transition interface contains elements of the first interface and / or the second interface, so that the switching between the two interfaces is more coherent, so that the user experience is not interrupted.

[0080] For example, in an optional manner of the embodiment of the present application, the transition interface includes elements that exist in both the first interface and the second interface. For example, there is element 1 in the first interface, the transition interface also includes element 1, and the second interface also includes element 1, that is, element 1 continues to exist during the process of switching from the first interface to the second interface, so that the user's visual sensory experience during the switching process feels that the interface switching transition is more natural, not abrupt, and has strong coherence.

[0081] Exemplarily, in another optional manner of the embodiment of the present application, when element 1 in the first interface is switched to the second interface through at least one transition interface, element 1 gradually changes into element 2, wherein element 2 is partially similar to element 1.

[0082] Among them, the element 2 is partially similar to the element 1, and the display pattern of the element 2 is partially similar to the display pattern of the element 1. For example, the display pattern of the element 2 is ABCD, and the display pattern of the element 1 is ABEF.

[0083] The element 2 is partially similar to the element 1, and the similarity between the element 2 and the element 1 may be higher than the similarity threshold. For example, the element 1 in the first interface is displayed as a man wearing a hat. During the transition to the second interface, the man wearing a hat in the element 1 slowly takes off his hat and becomes the element 2 in the second interface, wherein the element 2 in the second interface is displayed as a man holding a hat. Thus, the user feels that the interface switching transition is more natural, more coherent, and more vivid and interesting in the visual sensory experience during the switching process.

[0084] 2) Conversion, in the embodiment of the present application, mainly refers to the display interface on the terminal display screen changing from the first interface to the second interface. It should be understood that conversion can also be called transition.

[0085] The interface conversion may be a conversion between different interfaces within the same application, an interface conversion when switching between different applications, or an interface conversion when switching between the terminal display desktop and the application cover.

[0086] In addition, the conversion between interfaces described in the embodiments of the present application can also be called a conversion between interfaces; or, a transition between interfaces; or, a switch between interfaces.

[0087] 3) Conversion object: In the embodiment of the present application, the conversion object can be understood as an application that needs to be converted between interfaces, etc.

[0088] In the embodiment of the present application, the terminal display desktop can also be understood as an application of the terminal device. It should be understood that the conversion object can also be called a transition object.

[0089] 4) Conversion scene: In the embodiment of the present application, the conversion scene can be understood as the interface classification when the interface is converted. It should be understood that the conversion scene can also be called the transition scene.

[0090] Among them, the conversion scenes in the embodiments of the present application may include an exit scene (also referred to as an exit scene), an entry scene (also referred to as an entry scene) and a shared scene (also referred to as a transition scene).

[0091] The exit scene can be understood as the first interface described in the embodiment of the present application, the entry scene can be understood as the second interface of the embodiment of the present application, and the sharing scene can be understood as the transition interface of the embodiment of the present application.

[0092] 5) Entry elements refer to a type of elements included in the entry scene, and can also be understood as elements included in the second interface. It should be understood that entry elements can also be called entry elements.

[0093] 6) Shared elements refer to a type of elements that appear and change continuously during the transition process. They can also be understood as elements contained in the transition interface.

[0094] 7) Exit elements refer to a type of elements included in the exit scene, and can also be understood as elements included in the first interface. It should be understood that exit elements can also be called exit elements.

[0095] 8) A shared container, used to contain at least one shared element, that is, during the conversion process, all elements in the shared container are continuously changed.

[0096] Among them, there may be at least one shared element in the transition interface in the embodiment of the present application.

[0097] 9.) The interface display area refers to the area where the first interface, transition interface and second interface are displayed.

[0098] Generally, the interface of an electronic device is often divided into three parts from top to bottom, for example Figure 1 As shown, the interface of the electronic device is divided into a status bar in the top area, which is used to display the power information, network information, card insertion information, signal strength information, time information, etc. of the electronic device; an interface display area in the middle area, which is used to display the application scenario interface, etc.; and a virtual navigation key area in the bottom area.

[0099] It should be noted that the area division method of the interface in the electronic device in the embodiment of the present application is not limited to the above situation. For example, the area of ​​the interface in the electronic device may only include the status bar and the interface display area.

[0100] Among them, in the embodiment of the present application, when switching interfaces, shared elements only refer to elements that persist in the interface display area.

[0101] It is understandable that when an electronic device switches interfaces, elements in the status bar in the top area of ​​the interface in the electronic device may continue to exist, and virtual navigation button elements in the bottom area of ​​the interface in the electronic device may also continue to exist, but neither is the shared element described in the embodiments of the present application.

[0102] 9) ARR, a file format, that is, a binary archive file of an Android library project.

[0103] An optional method of an embodiment of the present application is to package the application program and other files corresponding to the conversion method between application interfaces into an ARR file format.

[0104] Among them, the files in the ARR package format in the embodiment of the present application include class files and res resource files, etc.

[0105] 10) Jar package, a file format.

[0106] An optional method of the embodiment of the present application is to package the application program and other files corresponding to the conversion method between application interfaces into a Jar package file format. Among them, the files in the Jar package format in the embodiment of the present application include class files and manifest files.

[0107] Among them, the term "at least one" in the embodiments of the present application refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. The following at least one item (items) or similar expressions refer to any combination of these items, including any combination of single items (items) or plural items (items). For example, at least one item (items) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0108] Unless otherwise stated, ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects. In addition, the terms "including" and "having" in the embodiments of the present application, the claims and the drawings are not exclusive. For example, a process, method, system, product or device that includes a series of steps or modules is not limited to the listed steps or modules, and may also include steps or modules that are not listed.

[0109] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0110] The interface conversion method provided in the embodiment of the present application can be applied to Figure 2 The system architecture shown in FIG. 1 includes: at least one application-side device 1100 and a platform-side device 1200 .

[0111] Among them, the application side device 1100 and the platform side device 1200 can be interconnected through a communication network, and the communication network can be a local area network or a wide area network transferred through a relay device. When the communication network is a local area network, exemplarily, the communication network can be a short-range communication network such as a Wi-Fi hotspot network, a Wi-Fi P2P network, a Bluetooth network, a Zigbee network, or a near field communication (NFC) network. When the communication network is a wide area network, exemplarily, the communication network can be a third-generation wireless telephone technology (3G) network, a fourth-generation mobile communication technology (4G) network, a fifth-generation mobile communication technology (5G) network, a future-evolved public land mobile network (PLMN) or the Internet, etc. Figure 1 In the scenario shown, different electronic devices can exchange data through a communication network, such as transmitting conversion effects between interfaces, configuring interface conversion schemes for applications, etc.

[0112] In an optional manner, the application side device 1100 accesses the application framework for application interface conversion in the platform side device 1200 through the communication interface established with the platform side device 1200. The application side device 1100 configures an interface conversion scheme for the conversion object through the application framework, that is, determines the first interface, the second interface, at least one transition interface and the shared elements in the conversion object, so that when the conversion object converts between interfaces, the shared elements can be continuously displayed, making the conversion effect between interfaces smoother and the user experience more coherent.

[0113] Furthermore, when the application side device 1100 enables the inter-interface conversion scheme corresponding to the conversion object, the platform side device 1200 parses the inter-interface conversion scheme corresponding to the conversion object in the application side device 1100 and executes the inter-interface conversion scheme, thereby enabling the conversion object to achieve a continuous and smooth conversion effect.

[0114] It can be understood that the application side device 1100 performs online integration by accessing the platform side device 1200 .

[0115] In addition, the application-side device 1100 can also complete the configuration of the interface conversion scheme of a certain conversion object in advance with the platform-side device 1200, and store the interface conversion scheme in other servers. When the conversion object is subsequently started, the interface for communicating with the server is called to obtain the interface conversion scheme through the interface. And, through the online integration method, the application-side device 1100 described in the embodiment of the present application can also open the permission of the platform-side device 1200 to configure the interface conversion scheme of the conversion object to the user. For example, the user can call the interface for communicating with the platform-side device 1200 according to his own wishes, and update and adjust the interface conversion scheme of a certain conversion object at any time.

[0116] In a second optional manner of the embodiment of the present application, the application side device 1100 obtains a file package of an application for configuring a conversion scheme between interfaces of a conversion object from the platform side device 1200 and stores it. The application side device 1100 parses the application file package stored locally and obtains an application for configuring a conversion scheme between interfaces of a conversion object. The application side device 1100 determines the conversion object through the application and configures an interface conversion scheme for the conversion object, that is, determines the first interface, the second interface, at least one transition interface and a shared element in the conversion object, so that when the conversion object converts between interfaces, the shared elements can be continuously displayed, making the conversion effect between interfaces smoother and the user experience more coherent.

[0117] Among them, assuming that the file package of the application is an ARR type file package, the application side device 1100 can obtain the file package of the application from the platform side device 1200 and store it. When the application in the application side device 1100 needs to adopt the interface conversion method described in the embodiment of the present application, the application can call the file package of the application in the application side device 1100 and integrate it locally according to the file package of the application.

[0118] Exemplarily, assuming that the application-side device 1100 is a mobile phone, the mobile phone has obtained the application file package. The calendar application in the mobile phone can call the application file package in the mobile phone, integrate the configuration file for performing interface conversion described in the embodiment of the present application into the calendar application, and store the configuration file in the libs folder, so that the path can be introduced in the compilation script later.

[0119] Assuming that the file package of the application is a Jar type file package, the application side device 1100 can obtain the file package of the application from the platform side device 1200 and store it. When the application (i.e., the conversion object) in the application side device 1100 needs to adopt the interface conversion method described in the embodiment of the present application, the application side device 1100 can directly call the file package of the application.

[0120] It should be noted that the system for converting between interfaces in the embodiment of the present application is not limited to the above Figure 1 The architecture shown, any variation of the above system architecture, etc. can be applied to the embodiments of the present application. For example, the system described in the embodiments of the present application can also include a third-party material supplier, etc.

[0121] Among them, the third-party material supplier described in the embodiment of the present application can be used to provide animation templates, etc.

[0122] For example, suppose that in the application for transition between interfaces included in the platform-side device 1200, the provided dynamic effect templates include explosion effects, displacement effects, scaling effects, cropping effects, rotation effects, etc., and the dynamic effect templates provided by the third-party material supplier are more diverse than the dynamic effect templates provided by the platform-side device 1200, which also include black hole effects, snowflake effects, etc. Therefore, in order to reduce the modification of the application in the platform-side device 1200, an interface for communicating with the third-party material supplier can be added to the system, so that the user can call the dynamic effect template provided by the third-party material supplier when designing the dynamic effect in the transition between interfaces.

[0123] The hardware structure and software structure of the platform side device 1200 and the application side device 1100 are respectively described as follows:

[0124] 1. Platform side equipment:

[0125] Specifically, in one scenario of an embodiment of the present application, the platform-side device 1200 may be a server or a cloud server storing application code for implementing the method for converting between interfaces provided in the present application.

[0126] It should be noted that there may be multiple application codes stored in the platform-side device 1200 described in the embodiment of the present application for implementing the interface conversion method provided in the present application.

[0127] For example, for The system's application code for executing the interface conversion method is suitable for The system's application code for executing the interface conversion method is suitable for The system's application code for executing the method for converting between interfaces, etc., the embodiment of the present application can select the adapted application code for executing the method for converting between interfaces according to the system installed in the electronic device, which is not limited here.

[0128] in, Figure 3 Shown is a framework diagram of a partial structure of a platform-side device 1200 related to various embodiments of the present application.

[0129] like Figure 3 As shown, the platform side device 1200 may include:

[0130] The processor 1210 , the memory 1220 , and the transceiver 1230 .

[0131] One or more computer programs are stored in the memory 1220 and configured to be executed by the one or more processors 1210 .

[0132] The processor 1210 described in the embodiment of the present application may be a central processing unit (CPU) or a digital processing unit, etc.

[0133] Among them, the processor 1210 is the control center of the platform side device 1200, which uses various interfaces and lines to connect various parts of the entire platform side device 1200, and performs various functions of the platform side device 1200 by running or executing computer programs stored in the memory 1220.

[0134] In an optional manner of the embodiment of the present application, the processor 1210 is used to determine the conversion object for the conversion between interfaces, the conversion scene involved in the conversion between interfaces, the elements in the scene, and the corresponding scene animation and element animation according to the user's operation instruction. Then, the processor 1210 processes and packages the scheme for the conversion object to convert between interfaces according to the configuration process, and stores the scheme for the conversion between interfaces locally.

[0135] When the application side device 1100 starts the interface transition effect of the conversion object, the processor 1210 is also used to parse the interface transition scheme corresponding to the conversion object, that is, to determine the conversion scenes in the conversion object and the attributes corresponding to the elements respectively, and the attributes include animation, display ratio, etc.

[0136] Furthermore, the processor 1210 performs one-key execution of the scheme for converting between interfaces configured by the conversion object based on the application-side device 1100.

[0137] Exemplarily, the processor 1210 determines configuration parameters of related scenes and elements involved in the conversion object according to the interface conversion scheme corresponding to the conversion object.

[0138] Then, the processor 1210 can send the running data of the scene and elements related to the conversion object to the application side device 1100 in the form of streaming media for playback.

[0139] In another optional manner of the embodiment of the present application, the processor 1210 is used to determine the conversion object for the interface conversion, the conversion scene involved in the interface conversion process, the elements in the scene, and the corresponding scene animation and element animation according to the user's operation instruction. Then, the processor 1210 processes and packages the scheme for the conversion object to convert between interfaces according to the configuration process, and sends the scheme for the conversion between interfaces to the corresponding application side device 1100.

[0140] The application side device 1100 receives and stores the scheme for the interface conversion corresponding to the conversion object. When the application side device 1100 starts the interface conversion effect of the conversion object, the scheme for the interface conversion corresponding to the conversion object is called, and the scheme for the interface conversion corresponding to the conversion object is analyzed, that is, the conversion scene in the conversion object and the attributes corresponding to the elements are determined, and the attributes include motion effects, display ratios, etc.

[0141] Furthermore, the application-side device 1100 performs one-key execution based on the scheme of conversion between interfaces corresponding to the conversion object.

[0142] Exemplarily, the application-side device 1100 determines the configuration parameters of the relevant scenes and elements involved in the conversion object according to the interface conversion scheme corresponding to the conversion object.

[0143] Then, the application-side device 1100 runs the scene related to the conversion object and the running data of the elements, and displays the effect of converting the conversion object between interfaces on the display screen of the application-side device 1100 .

[0144] The transceiver 1230 is an optional method for receiving an operation instruction triggered by a user and sending the operation instruction to the processor 1210, so that the processor 1230 configures the interface conversion scheme for the corresponding conversion object through the application for performing interface conversion in the platform side device 1200 according to the operation instruction; and / or,

[0145] In an optional manner, the file package of the application in the platform side device 1200 is sent to the application side device 1100; and / or,

[0146] In an optional manner, a solution for the application-side device 1100 to convert the conversion object between interfaces in the platform-side device 1200 is sent to the application-side device 1100 .

[0147] The specific connection medium between the processor 1210 and the memory 1220 is not limited in the embodiment of the present application. Figure 3 The memory 1220, the processor 1210 and the transceiver 1230 are connected via a bus 1240. Figure 3 The connections between other components are shown in bold lines, which are only for schematic illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0148] The memory 1220 may be a volatile memory, such as a random-access memory (RAM); the memory 1220 may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), or the memory 1220 may be any other medium that can be used to carry or store program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1220 may be a combination of the above memories.

[0149] In addition, the embodiment of the present application is based on a layered architecture. The system is used as an example to illustrate the software structure of the platform side device 1200. It should be noted that in other operating systems (such as system, System, etc.), as long as the functions implemented by each functional module are similar to the embodiments of the present application, the solution of the present application can be implemented, and no limitation is made here.

[0150] In an optional manner of the embodiment of the present application, the software structure block diagram of the platform side device 1200 can be as follows Figure 4 shown.

[0151] The platform side device 1200 divides the software into several layers based on the layered architecture, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces.

[0152] For example, in some embodiments, the Android system is divided into four layers, namely, from top to bottom, an application layer, an application framework layer, an Android runtime and system library, and a kernel layer.

[0153] 1) Application layer:

[0154] In an optional manner in the embodiment of the present application, the application layer may include a series of application packages.

[0155] For example, in the embodiment of the present application, the application layer may store applications for executing the interface conversion solution provided by the present application, etc.

[0156] 2) Application framework layer:

[0157] In an optional manner in the embodiment of the present application, the application framework layer provides an application programming interface (API) and a programming framework for the application programs of the application layer, wherein the application framework layer may include some predefined functions.

[0158] 3) Android Runtime and system libraries:

[0159] The Android Runtime may include a core library and a virtual machine, which are responsible for scheduling and management of the Android system.

[0160] Furthermore, the core library described in the embodiment of the present application may include two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core library of Android.

[0161] The virtual machine described in the embodiment of the present application is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions. For example, the application layer and the application framework layer run in the virtual machine. The virtual machine executes the java files of the application layer and the application framework layer as binary files.

[0162] The system library in the embodiment of the present application may include multiple functional modules, such as a surface manager, a media library, a 3D graphics processing library (such as OpenGL ES), a 2D graphics engine (such as SGL), etc.

[0163] Furthermore, the surface manager described in the embodiment of the present application is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0164] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0165] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0166] A 2D graphics engine is a drawing engine for 2D drawings.

[0167] 4) Kernel layer:

[0168] The kernel layer described in the embodiment of the present application can be understood as a layer between hardware and software, which at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0169] Further, such as Figure 4 As shown, the capability framework corresponding to the application for performing interface conversion in the embodiment of the present application may include a configuration module, a parsing module and an execution module.

[0170] It should be noted that the embodiment of the present application does not limit which system layer the capability framework is located at. For example, the capability framework described in the embodiment of the present application may be at the application layer. Alternatively, the capability framework described in the embodiment of the present application may be independent of the four layers included in the above system. For example, the capability framework is an external layer, which is an extension based on the capabilities of the framework layer and can be expanded into the form of AAR or Jar for easy application use.

[0171] Among them, the configuration module in the platform-side device of the embodiment of the present application is used to perform parameter configuration of the conversion scene and elements for the determined conversion object.

[0172] Specifically, the configuration module receives the configuration instruction sent by the application-side device 1100, and performs parameter configuration of the conversion scene and elements for the conversion object that needs to be converted between interfaces according to the configuration instruction.

[0173] The parsing module in the platform-side device of the embodiment of the present application is used to parse the scheme of conversion between interfaces corresponding to the conversion object, and save the parsed scheme of conversion between interfaces.

[0174] Exemplarily, the scheme for transitioning between interfaces may include the name of the transition object, the name of a shared element or shared container, the transition animation ID of the exit interface configuration, the transition animation ID of the entry interface configuration, the transition animation ID of the shared element or shared container configuration, etc.

[0175] It can be understood that the parsing module mainly determines the conversion scene in the conversion object and the elements in each conversion scene and the corresponding execution effect according to the conversion scheme between the interfaces corresponding to the conversion object.

[0176] The execution module in the platform-side device of the embodiment of the present application is used to execute different animation effects for different elements at different times according to the scheme of transition between the interfaces.

[0177] 2. Application side equipment:

[0178] The application side device 1100 may be a portable electronic device that also includes other functions such as a personal digital assistant and / or a music player, such as a mobile phone, a tablet computer, a wearable device with a wireless communication function (such as a smart watch), etc. Exemplary embodiments of portable electronic devices include but are not limited to Or a portable electronic device with other operating systems. The portable electronic device may also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface (such as a touch panel). The following description is made by taking the application-side device 1100 as a mobile phone as an example. Figure 5 Shown is a block diagram of a partial structure of an application-side device 1100 related to various embodiments of the present application.

[0179] like Figure 5 As shown, the application side device 1100 is a mobile phone, which may include a processor 1110, an external memory interface 1120, an internal memory 1121, a USB interface 1130, a charging management module 1140, a power management module 1141, a battery 1142, an antenna 1, an antenna 2, a mobile communication module 1150, a wireless communication module 1160, an audio module 1170, a speaker 1170A, a receiver 1170B, a microphone 1170C, an earphone interface 1170D, a sensor module 1180, a button 1190, a motor 1191, an indicator 1192, a camera 1193, a display screen 1194, and a SIM card interface 1195, etc.

[0180] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the application side device 1100. In other embodiments of the present application, the application side device 1100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0181] The processor 1110 may include one or more processing units, for example: the processor 1110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and / or a neural network processor (Neural-network Processing Unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors. Among them, the controller can be the nerve center and command center of the application side device 1100. The controller can generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.

[0182] In the embodiment of the present application, the processor 1110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 1110 is a cache memory. The memory may store instructions or data that the processor 1110 has just used or cyclically used. If the processor 1110 needs to use the instruction or data again, it may be directly called from the memory. Repeated access is avoided, the waiting time of the processor 1110 is reduced, and the efficiency of the system is improved.

[0183] In some embodiments, the processor 1110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0184] In an optional manner of the embodiment of the present application, the processor 1110 is used to determine a conversion object, and to call an application for performing conversion between interfaces in the platform-side device 1200 to determine a scheme for the conversion object to perform conversion between interfaces.

[0185] In a second optional manner of the embodiment of the present application, the processor 1110 is used to determine a conversion object and a scheme for performing interface conversion corresponding to the conversion object, and when the conversion object performs interface conversion, the interface conversion of the conversion object is implemented according to the scheme for performing interface conversion.

[0186] In a third optional manner of the embodiment of the present application, the processor 1110 is further used to instruct the platform-side device 1200 to enable the platform-side device 1200 to display the inter-interface conversion effect of a conversion object based on the inter-interface conversion scheme of the conversion object.

[0187] The wireless communication function of the application side device 1100 can be implemented through the antenna module 1, the antenna module 2, the mobile communication module 1150, the wireless communication module 1160, the modem processor and the baseband processor.

[0188] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the application side device 1100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, a cellular network antenna can be reused as a wireless local area network diversity antenna. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0189] The mobile communication module 1150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G / 6G applied to the application side device 1100. The mobile communication module 1150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 1150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 1150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 1150 can be set in the processor 1110. In some embodiments, at least some of the functional modules of the mobile communication module 1150 can be set in the same device as at least some of the modules of the processor 1110.

[0190] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 1170A, a receiver 1170B, etc.), or displays an image or video through a display screen 1194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 1110 and be set in the same device as the mobile communication module 1150 or other functional modules.

[0191] The wireless communication module 1160 can provide wireless communication solutions including wireless local area networks (WLAN), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., applied to the application side device 1100. The wireless communication module 1160 can be one or more devices integrating at least one communication processing module. The wireless communication module 1160 receives electromagnetic waves via antenna 2, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 1110. The wireless communication module 1160 can also receive the signal to be sent from the processor 1110, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through antenna 2. In the embodiment of the present application, the application side device 1110 obtains the one-shot effect performed by the platform side device 1200 through the wireless communication module 1160.

[0192] In some embodiments, antenna 1 of the application side device 1100 is coupled to the mobile communication module 1150, and antenna 2 is coupled to the wireless communication module 1160, so that the application side device 1100 can communicate with the network and other devices through wireless communication technology.

[0193] The application side device 1100 implements the display function through a GPU, a display screen 1194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 1194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 1110 may include one or more GPUs that execute program instructions to generate or change display information. In an embodiment of the present application, the application side device 1100 implements the playback and display of short videos through a GPU, a display screen 1194, and an application processor.

[0194] The application side device 1100 can realize the shooting function through ISP, camera 1193, video codec, GPU, display screen 1194 and application processor.

[0195] The external memory interface 1120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the application-side device 1100. The external memory card communicates with the processor 1110 via the external memory interface 1120 to implement a data storage function.

[0196] The internal memory 1121 can be used to store computer executable program codes, which include instructions. The processor 1110 executes various functional applications and data processing of the application side device 1100 by running the instructions stored in the internal memory 1121. The memory 1121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the application side device 1100 (such as audio data, a phone book, etc.), etc. In addition, the memory 1121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0197] The application side device 1100 can implement audio functions such as music playing and recording through the audio module 1170, the speaker 1170A, the receiver 1170B, the microphone 1170C, the headphone interface 1170D, and the application processor.

[0198] In addition, the embodiment of the present application is based on a layered architecture. The system is used as an example to illustrate the software structure of the application side device 1100. For example, in other operating systems (such as system, System, etc.), as long as the functions implemented by each functional module are similar to the embodiments of the present application, the solution of the present application can also be implemented.

[0199] Figure 6 It is a software structure block diagram of the application side device 1100 according to an embodiment of the present invention.

[0200] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces.

[0201] In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime and system library, and a kernel layer.

[0202] Among them, the application layer in the application side device 1100 described in the embodiment of the present application may include a series of application packages.

[0203] like Figure 6 As shown, the application package may include applications such as phone, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0204] The application framework layer in the application side device 1100 in the embodiment of the present application is mainly used to provide an application programming interface (API) and a programming framework for the application of the application layer. The application framework layer may include some predefined functions.

[0205] like Figure 6 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0206] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0207] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0208] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0209] The phone manager is used to provide communication functions for the application-side device 1100, such as management of call status (including connection, disconnection, etc.).

[0210] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0211] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0212] In addition, the contents of the system library and the kernel layer in the application side device 1100 described in the embodiment of the present application are similar to the contents of the system library and the kernel layer in the above-mentioned platform side device 1200. For the sake of concise description, please refer to the introduction of the system library and the kernel layer in the above-mentioned platform side device 1200, which will not be repeated here.

[0213] When using electronic devices, users pay more and more attention to the interface experience.

[0214] Currently, when a first interface is switched to a second interface, the first interface is directly transformed into the second interface, which results in poor continuity and low user experience.

[0215] For example, Figure 7 As shown, in the current configuration of switching from the first interface to the second interface, only the element for exiting the first interface and the animation executed by the exit element when switching are determined; and / or the element for entering the second interface and the animation executed by the entering element when switching are determined. During the switching process, the exit element in the first interface executes the corresponding animation to exit, and the entry element in the second interface executes the corresponding animation to enter, thereby completing the switching from the first interface to the second interface.

[0216] From the above content, it can be understood that the current solution processing logic for the conversion between interfaces is relatively simple, and only the exit and entry animations are simply implemented, the effect is single, and the switching process between the first interface and the second interface is not coherent, and the user visual experience is poor. To solve this problem, the embodiments of the present application provide a method, device and system for conversion between interfaces, which are used to efficiently and flexibly achieve a more coherent conversion effect between interfaces.

[0217] The following will introduce in detail the method for converting between interfaces based on a one-shot effect provided in an embodiment of the present application in combination with the accompanying drawings and application scenarios.

[0218] First, the embodiment of the present application specifically introduces the capability framework corresponding to the application for performing interface conversion. Figure 4 The application framework layer described in is introduced in detail.

[0219] Among them, based on the above Figure 4 It can be seen from the content that the application framework layer mainly includes a configuration module, a parsing module, and an execution module. Therefore, it can be understood that when the embodiment of the present application performs interface conversion according to the application framework, Figure 8 As shown, it can be divided into three stages: configuration stage, parsing stage and execution stage.

[0220] Phase 1: Configuration phase:

[0221] The first stage mainly refers to parameter configuration of the scenes and elements involved in the conversion object through the configuration module in the application framework.

[0222] The application framework in the configuration phase described in the embodiments of the present application can be specifically found in Fig. 9 shown.

[0223] Specifically, when designing a scheme for converting between interfaces in the embodiments of the present application, it is first necessary to determine the conversion object.

[0224] For example, Fig.10 As shown, it is assumed that the application side device is a mobile phone, wherein the applications in the mobile phone include calendar, gallery, application store, weather, phone, etc. The application side device determines the gallery as a conversion object according to the selection instruction triggered by the user, for example, determines a scheme for converting the internal application interface in the gallery.

[0225] Then, an optional method in an embodiment of the present application is to use a device (for example, a processor in an application test device, or a processor in a platform side device, etc.) that configures an interface conversion scheme for a conversion object to determine a conversion scenario in the conversion object.

[0226] like Fig.11 As shown, it mainly includes determining the exit scene, transition scene and entry scene. It can be understood that different scenes are at different nodes in the conversion object. Fig.12 As shown, the application side device determines the element type and the animation form according to the instruction triggered by the user. The element types include shared elements, exit elements and entry elements.

[0227] Further, such as Fig.13 As shown, a device for configuring a conversion scheme between interfaces for a conversion object determines the classification of elements in each conversion scene according to a selection instruction triggered by a user, that is, which elements in each scene serve as exit elements, which elements serve as shared elements, and which elements serve as entry elements, as well as determines the corresponding animation effects when the elements are converted.

[0228] It should be noted that the device for configuring the interface conversion scheme for the conversion object in the embodiment of the present application can also classify the element types according to the container in which the element is located. For example, assuming that container 1 is determined to be a shared container, it can be understood that all elements in container 1 are shared elements.

[0229] In addition, an optional method of the embodiment of the present application is a device for configuring a conversion scheme between interfaces for a conversion object, which can also set the size of the information container according to a processing instruction triggered by a user.

[0230] Exemplarily, the present embodiment of the application takes the currently mainstream Activity conversion type as an example to briefly introduce some parameters involved in the elements in the conversion object in the present embodiment of the application.

[0231] The parameters involved in the elements in the embodiments of the present application may include name, motion duration, control ID, animation, animation delay, interface (exit and / or entry) duration, etc.

[0232] It should be noted that the parameters involved in the elements in the embodiments of the present application are not limited to the above-mentioned ones. Any configuration parameters of the elements that can be applied to the embodiments of the present application belong to the protection scope of the embodiments of the present application. For example, if there are multiple animations set for a certain element, the configuration parameters can also include the interval duration of each animation, etc.

[0233] For example, as shown in Table 1 below, the embodiment of the present application simply lists the parameters that may need to be configured for interface conversion of the selected conversion object in a tabular form.

[0234]

[0235]

[0236] Table 1 Parameter description of conversion object

[0237] Among them, according to the content of the above Table 1, it can be understood that when configuring the interface conversion scheme for the conversion object in the embodiment of the present application, it is first necessary to determine the name of the conversion object that needs to be converted between interfaces. Then, determine the exit element, shared element and entry element in the conversion object; and determine the exit animation, exit duration, exit animation delay, etc. involved in the exit element; determine the entry animation, entry duration, entry animation delay, etc. involved in the entry element; determine the shared animation, shared duration, shared animation delay, etc. involved in the shared element.

[0238] Among them, in the embodiment of the present application, if the exit element, entry element or shared element is determined by setting the container ID, it can be understood that all elements in the container ID are set as exit elements, entry elements or shared elements.

[0239] For example, suppose there are three elements in container 1, namely element 1, element 2 and element 3. If container 1 is set as a shared element, all elements contained in container 1 are shared elements.

[0240] Furthermore, when configuring shared animations for the container 1, animations may be configured for each shared element separately, or a unified animation may be configured for the entire container.

[0241] For example, when configuring animations for elements in container 1, you can configure the animation for shared element 1 as flipping, and the animation for shared elements 2 and shared elements 3 as gradient. In this case, during the interface transition, shared element 1 will perform a flipping animation, and shared elements 2 and shared elements 3 will perform a gradient animation. Alternatively, when configuring animations for elements in container 1, you can configure a gradient animation for container 1. In this case, during the interface transition, shared elements 1 to 3 in container 1 will uniformly perform a gradient animation.

[0242] Among them, if the embodiment of the present application involves conversion between multiple interfaces, then the intermediate interface for conversion can be regarded as a transition interface (also called a shared interface).

[0243] It should be noted that in the embodiment of the present application, when there is no overlap between the exit interface, the transition interface and the entry interface during the conversion between interfaces, the total conversion time T1 in the embodiment of the present application is the sum of the exit time T2, the sharing time T3 and the entry time T4; when there is overlap between the interfaces during the conversion between the exit interface, the transition interface and the entry interface, the total conversion time T1 in the embodiment of the present application is less than the sum of the exit time T2, the sharing time T3 and the entry time T4.

[0244] Furthermore, the forms of the animations in the embodiments of the present application include but are not limited to the following:

[0245] Explosion effect, displacement effect, zoom effect, cropping effect, rotation effect, fade-in and fade-out effect, etc.

[0246] In addition, the animation form described in the embodiment of the present application can also be implemented through customized extensions. For example, it can also be set to a black hole effect, a hidden effect, etc. in a customized manner.

[0247] Among them, users can also set the properties of the animation according to their needs, for example:

[0248] When to trigger the start of the animation, when to trigger the end of the animation, the type of animation, the application scenario (i.e., whether it is an exit animation or an entry animation), the total running time of the animation, the animation delay time, the animation interpolator, etc.

[0249] Exemplarily, as shown in Table 2, a motion effect scheme configured in the embodiment of the present application is:

[0250]

[0251]

[0252] Table 2 One-shot animation scheme 1

[0253] According to the content of Table 2, for the element named "AutoExplodeAnimCreator", the explosion animation is executed upon entry.

[0254] It should be noted that the embodiment of the present application does not limit the conversion type. For example, the conversion type in the embodiment of the present application can also be a ViewGroup conversion type, a Fragment conversion type, etc. Among them, the setting method of other conversion types is similar to the Activity conversion type. The main difference is that the form of the control is different, that is, the conversion setting is different. For a concise description, refer to the introduction of the above Activity conversion type.

[0255] Among them, the embodiment of the present application selects three conversion types: Activity, ViewGroup and Fragment, and briefly introduces the conversion settings respectively.

[0256] For example, in the embodiment of the present application, the conversion settings for the three conversion types of Activity, ViewGroup and Fragment can be as shown in Table 3 below:

[0257]

[0258] Table 3 Conversion settings for different conversion types

[0259] Further, in the embodiment of the present application, when performing the interface conversion configuration in the configuration stage, the interface conversion scheme can be configured in a customized manner or in a preset template manner, which are described below respectively:

[0260] Configuration method 1: Custom configuration.

[0261] In an optional manner of the embodiment of the present application, the application framework performs corresponding parameter configuration based on the content selected by the user.

[0262] For example, Fig.14 As shown, it is assumed that a scheme for transitioning between interfaces of application A is configured, wherein the user customizes the element corresponding to box 2 in application A as a shared element, the animation effect of the exit element configuration is gradual disappearance, the animation effect of the shared element configuration is magnification, and the animation effect of the entry element configuration is gradual appearance.

[0263] When the application A performs the interface conversion, it is assumed that at this time Fig.13 The a interface in the figure is the exit scene of application A. Fig.13 The b interface in the figure is the transition scene of application A. Fig.13 Interface c in the figure is the entry scene of application A, box 1 is the exit element, box 2 is the shared element, and box 3 is the entry element.

[0264] In the process of switching from interface a to interface b, box 2 as a shared element always exists and displays an enlarged dynamic effect, and box 1 as an exit element gradually disappears.

[0265] Furthermore, the conversion process continues, and the interface b is switched to the interface c. During the switching process, the box 2 as the shared element always exists, and the box 3 as the entry element gradually appears.

[0266] Among them, the embodiment of the present application can set the size of the information container and the position of the information container.

[0267] For example, Fig.15 As shown, the size of the information container for displaying the exit scene is set to the size of the virtual frame 1 and displayed at the left border of the screen. Then, the content of the exit scene is only displayed in the virtual frame 1. Fig.15 The information container size of the display transition scene is set to the size of the virtual frame 2 and displayed in the center of the screen, then the content of the shared scene is only displayed in the virtual frame 1; Fig.15 It is displayed in the dotted frame 2 in FIG.

[0268] Configuration method 2: Configuration using a preset template.

[0269] An optional method of the embodiment of the present application can set up multiple quick configuration templates, that is, in the quick configuration template, the relevant configuration parameters of the elements have been set in advance, and the user only needs to determine the name of the element, thereby realizing quick configuration and effectively reducing the complexity of configuration.

[0270] Among them, in an optional manner of the embodiment of the present application, after the user determines the conversion object, the user can click the screen with a finger to determine the elements that need to be configured using the template.

[0271] Specifically, when the user clicks the screen with his finger, the mobile phone determines the name of the element or container displayed at the clicked position based on the screen position, and binds the name of the element or container to the quick configuration template selected by the user, so that the element or container executes the configuration corresponding to the selected quick configuration module when switching between interfaces.

[0272] For example, suppose that when a user configures a scheme for switching between interfaces for application A, the current configuration interface is as follows: Fig.16 As shown in (a) in the figure, the current configuration interface displays custom configuration and quick configuration. After the user clicks on the quick configuration with his finger, the current interface is as follows Fig.16 As shown in (b) in FIG. 1 , two quick configuration modules are displayed, such as the quick configuration template 1 and the quick configuration template 2 introduced above.

[0273] The relevant configurations in the quick configuration template 1 are as follows:

[0274] The exit animation is a translation from left to right with a duration of 2 seconds. The entry animation is a translation from right to left with a duration of 2 seconds. The animation of a shared element or shared container is an explosion with a duration of 1.5 seconds. The center point of the explosion animation is the center point of the shared element or shared container, and the explosion area is one-fourth the size of the interface.

[0275] The relevant configurations in the quick configuration module 2 are as follows:

[0276] The exit animation is a gradual change with a duration of 2 seconds, the entry animation is a flip with a duration of 2 seconds, the shared element or shared container animation is a shake with a duration of 1.5 seconds, and the center point of the shake animation is the center point of the shared element or shared container. Assume that the user selects the quick configuration template 1 during the quick configuration template selection process.

[0277] After the user determines the quick configuration template for the application, the user only needs to determine the elements to which the template is applied.

[0278] For example, Fig.16As shown in (c) in FIG. 1 , the user determines the shared element from the content displayed on the current interface by clicking with a finger according to the instructions on the screen. Assuming that the user clicks on a ship on the screen with a finger, the application framework can determine that the ship is a shared element.

[0279] Therefore, when the application A performs a transition between interfaces, Fig.17 As shown in the figure, assume that interface a is the exit scene of application A and interface b is the entry scene of application A. When exiting from interface a, interface a moves from left to right, and the duration of the animation is 2s; when exiting from interface b, interface b moves from right to left, and the duration of the animation is 2s. The ship, as a shared element, always exists, and the explosion animation of about one-quarter of the screen size is displayed at the center point of the ship.

[0280] Furthermore, after the user completes the configuration of the interface conversion scheme for the conversion object through the application framework provided in the embodiment of the present application, a configuration file for the interface conversion scheme can be generated for subsequent calls when the conversion object performs interface conversion display.

[0281] It should be noted that the embodiment of the present application can also adopt a combination of a customized method and a preset template method to configure the interface conversion scheme for the conversion object, etc., and the embodiment of the present application is not limited here.

[0282] Furthermore, in an optional manner of the embodiment of the present application, in order to further enhance the confidentiality of the interface conversion scheme of the conversion object, the interface conversion scheme corresponding to the conversion object can be encrypted by an encryption public key. Thus, only the device or application that knows the decryption private key corresponding to the encryption public key can parse the interface conversion scheme corresponding to the conversion object and obtain the interface conversion scheme corresponding to the conversion object.

[0283] Phase 2: Analysis phase:

[0284] The second stage mainly refers to the equipment used to parse the interface conversion scheme corresponding to the conversion object. The equipment performs the analysis according to the interface conversion scheme obtained by the conversion object in the configuration stage, obtains the elements configured in the interface conversion scheme for performing interface conversion and the attributes of the elements, and other information, so as to determine the effect of the interface conversion scheme of the conversion object.

[0285] For example, the platform side device parses the interface conversion scheme corresponding to the conversion object through the parsing module of the application framework; for another example, the application side device parses the interface conversion scheme corresponding to the conversion object through its own processor or a chip with parsing function.

[0286] The internal logic framework of the parsing stage described in the embodiments of the present application can be specifically referred to in Fig.18 shown.

[0287] First, in the parsing stage, the embodiment of the present application is a device for executing the interface conversion scheme of the conversion object, which determines the scene type for interface conversion configured in the interface conversion scheme and the layout type corresponding to the scene type through the interface conversion scheme corresponding to the conversion object, thereby binding the scene type and the layout type together.

[0288] In the embodiment of the present application, by binding the scene with the layout, it helps to expand the conversion effect based on the layout type, which has better adaptability and higher adhesion.

[0289] Furthermore, a device for parsing an inter-interface conversion scheme corresponding to a conversion object determines a state of each converted interface according to the inter-interface conversion scheme.

[0290] It can be understood that the device that parses the interface conversion scheme corresponding to the conversion object determines the elements included in the exit scene and the states corresponding to the elements, the elements included in the transition scene and the states corresponding to the elements, and the elements included in the entry scene and the states corresponding to the elements according to the interface conversion scheme.

[0291] Among them, the state of an element in the embodiment of the present application mainly includes the type of element, the animation form of the element, and the duration of the animation.

[0292] Exemplarily, it is assumed that the conversion object is a calendar application, wherein the configuration file for performing interface conversion of the calendar application obtained through the stage 1 is shown in Table 4.

[0293]

[0294] Among them, the device for parsing the interface conversion scheme corresponding to the conversion object can determine, according to the content of Table 4, that the exit animation in the exit scene is a displacement of 20 pixels from left to right and a gradient of 2s, that the entry animation in the entry scene is a displacement of 20 pixels from right to left and a gradient of 2s, and that the shared element is the year in the shared scene, and during the interface conversion process, the year element presents a shaking effect from left to right with a shaking amplitude of 2 pixels.

[0295] Phase 3: Execution phase:

[0296] The stage three mainly refers to the equipment used to execute the interface conversion scheme corresponding to the conversion object. According to the interface conversion scheme corresponding to the conversion object, when the conversion object performs interface conversion, the conversion effect configured in the interface conversion scheme is displayed.

[0297] The internal logic framework of the execution phase described in the embodiments of the present application can be specifically referred to in Fig.19 shown.

[0298] Exemplarily, in the embodiment of the present application, when the user starts the conversion, the platform-side device starts the conversion with one click according to the various parameters in the interface conversion scheme corresponding to the conversion object previously parsed and obtained, and displays the effect of the conversion object in converting between interfaces.

[0299] Specifically, in the embodiment of the present application, the platform-side device performs different animation effects on different elements at different times according to the parameters.

[0300] Through the detailed introduction of the one-mirror-to-bottom frame in the embodiment of the present application, a method for converting between interfaces is provided for an application-side device using the one-mirror-to-bottom frame, such as Fig. 20 As shown, the specific steps are as follows:

[0301] Phase 1: Configuration phase:

[0302] S2000: The application-side device determines the interface type according to the interface configuration instruction triggered by the user.

[0303] Among them, the interface type described in the embodiment of the present application includes a first interface, at least one transition interface and a second interface, and the transition interface refers to the intermediate connection interface from the first interface to the second interface.

[0304] It can be understood that in the embodiment of the present application, the first interface is an exit interface, the second interface is an entry interface, and the transition interface is a sharing interface.

[0305] S2001, the application side device determines the containers and / or elements included in each interface according to the element configuration instruction triggered by the user.

[0306] Among them, in the embodiments of the present application, containers and / or elements can be set based on different interfaces.

[0307] For example, in the exit interface, at least one container and / or element is set as an exit element, and at least one container and / or element is set as a shared element; in the entry interface, at least one container and / or element is set as an entry element, and at least one container and / or element is set as a shared element.

[0308] Among them, in an optional manner in the embodiment of the present application, the shared element in the exit interface is the same as the shared element in the entry interface.

[0309] Specifically, the application-side device determines the first element and the second element in the first interface, and determines the second element and the third element in the second interface according to the element configuration instruction triggered by the user, wherein the transition interface includes the second element.

[0310] It is understandable that in the embodiment of the present application, the first element is an exit element, the second element is a shared element, and the third element is an entry element. In another optional manner of the embodiment of the present application, the shared element in the exit interface is partially similar to the shared element in the entry interface.

[0311] Specifically, the application side device determines the first element and the second element in the first interface, and determines the third element and the fourth element in the second interface according to the element configuration instruction triggered by the user; the electronic device determines that the second element in the transition interface gradually changes to the third element according to the element configuration instruction triggered by the user; wherein the second element is partially identical to the third element.

[0312] It can be understood that, assuming that the second element in the first interface is element 2, and the third element in the second interface is element 3, element 2 is partially similar to element 3.

[0313] S2002, the application side device determines the animation performed by the interface, container and / or element in the process of switching from the first interface to the second interface according to the animation configuration instruction triggered by the user.

[0314] Specifically, in the embodiments of the present application, different animation effects can be specified for different interfaces.

[0315] In addition, different animation effects can be specified for containers and / or elements in the interface.

[0316] In the embodiment of the present application, a variety of dynamic effect capabilities are provided for integrated use by applications. Among them, the dynamic effects in the embodiment of the present application can be used alone or in combination, and the application can be implemented by itself.

[0317] Among them, the application-side device described in the embodiment of the present application can obtain the interface conversion solution corresponding to the conversion object through the above-mentioned configuration operation. For the specific implementation, please refer to the description of the configuration module on the AAR side.

[0318] S2003, after the application-side device completes configuration, it can directly call the interface conversion scheme corresponding to the conversion object to start the effect of the interface conversion.

[0319] Furthermore, in the embodiment of the present application, after the application-side device completes the configuration of the interface conversion scheme corresponding to the conversion object, the application-side device can integrate the interface conversion scheme. In other words, the application-side device will encapsulate and store the interface conversion scheme corresponding to the conversion object, so that when the conversion object is converted between interfaces again, the interface conversion effect of the conversion object is directly triggered to start.

[0320] It should be noted that the above configuration steps do not constitute a limitation on the embodiments of the present application. When the interface conversion method described in the embodiments of the present application is used to configure the interface conversion scheme, the execution steps can be flexibly adjusted according to the actual situation. For example, when configuring the interface conversion scheme, the embodiment of the present application can also consider the scene type corresponding to the conversion interface. Thereby, a more fitting, more standardized and more effective interface conversion scheme can be designed in combination with the scene type. Among them, in the embodiments of the present application, the scene type of the conversion can be determined as one of Activity, ViewGroup and Fragment. It should be noted that the type of conversion described in the embodiments of the present application is not limited to the above three types and can be further expanded.

[0321] Phase 3: Execution phase:

[0322] S2004: After the application-side device detects a first operation performed by a user on the electronic device, the application-side device displays a first interface; the first interface includes a first element and a second element.

[0323] S2005: After the application-side device detects a second operation performed by the user on the first interface, it displays at least one transition interface and then displays the second interface.

[0324] In an optional manner of the embodiment of the present application, the second interface includes the second element and the third element; and the transition interface includes the second element.

[0325] In another optional manner of the embodiment of the present application, the second interface includes a third element and a fourth element; when the first interface switches to the second interface through the at least one transition interface, the display form of the second element in the transition interface gradually changes to the display form of the third element; wherein the second element is partially identical to the third element.

[0326] Through the above method, when the electronic device switches from the first interface to the second interface, it is connected through at least one transition interface, and the transition interface contains elements that are the same as or similar to the shared elements in the first interface and the second interface, so that the first interface and the second interface change naturally during the switching process, with strong coherence, and a better user visual experience.

[0327] Among them, the solution for converting between interfaces based on one mirror to the end described in the embodiment of the present application is not limited by the conversion type or the usage scenario. For example, it can be used within an application, between applications, and between the system and applications; it is also applicable to different screen scenarios, such as full screen, split screen and projection scenarios.

[0328] Furthermore, there are multiple one-shot conversion effects described in the embodiments of the present application, which can be specifically divided into the following application examples according to the display of shared elements.

[0329] Application example 1: The transition interface includes elements that exist in both the first interface and the second interface.

[0330] In the following, based on different conversion types such as Activity conversion type, ViewGroup conversion type and Fragment conversion type, the scheme for converting between interfaces based on a one-shot effect provided in the embodiments of the present application is introduced by examples.

[0331] Conversion type 1: Fragment conversion type.

[0332] Among them, the embodiment of the present application is based on the fragment transition type, and the solution for transitioning between interfaces can also be divided into multiple situations such as transition between applications, transition within an application, and transition from desktop to application, which are not limited to the following:

[0333] Case 1: In-app conversion:

[0334] like Fig.21 As shown, the embodiment of the present application takes a call application as an example and provides an example of an effect based on an in-application conversion between at least two Fragments.

[0335] Among them, the embodiment of the present application can set corresponding IDs for the answer key and the hang-up key in the answer button, and determine the usage status of the call application according to the answer or hang-up command triggered by the user.

[0336] Exemplarily, as shown in Table 5, the configuration files applied in the embodiments of the present application are as follows:

[0337]

[0338] Among them, assuming that when switching between interfaces, the exit interface and the entry interface of the call application are as follows: Fig.21 As shown, according to the exit interface of the call application, it can be known that the exit interface includes an answer key icon and a hang up key icon.

[0339] When the call application starts the interface conversion scheme, during the process of switching from the exit interface to the entry interface, if the user triggers an answer command, the answer key is a shared element.

[0340] According to the contents of Table 5 above, it can be known that when the answer key icon is a shared element, during the conversion process, it rotates 270 degrees counterclockwise, moves to the right, and performs a color change effect. At this time, the exit element is the hang-up key icon, and when the interface is converted, a fade-in effect is performed. The entry element is the hands-free icon and the keyboard icon, and a fade-in effect is performed when the interface is converted.

[0341] It should be noted that in the embodiment of the present application, the answer key is a shared element. After executing the conversion effect, its expression is similar to that of the hang-up key as an exit element, but it is a different icon from the hang-up key as an exit element of the cut-out interface.

[0342] Therefore, a rotating animation effect is presented during the interface conversion process.

[0343] Case 2: Inter-application conversion:

[0344] The following takes the example of a user using a call application and needing to switch to a text message application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0345] Assume that when a user configures a transition scheme between the call application and the text message application, the user uses the answer button in the call application as a shared element so that it persists during the transition process.

[0346] For example, Fig. 22 As shown, when the user clicks the SMS button in the call interface, the call application and the SMS application are triggered to switch between the interfaces. After the call application jumps to the SMS application, the answer button of the call application continues to exist, and the answer button performs a zoom-in animation, and a bubble window appears, displaying the SMS editing interface for SMS editing. When the SMS editing is completed, click the answer button, the answer button performs a rotation and reduction animation, and the call interface is displayed.

[0347] Case 3: Desktop to App Conversion:

[0348] The following takes the example of a user needing to switch from an application desktop to a call application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0349] Assume that when configuring a scheme for switching between the application desktop and the call application interface, the user uses the answer button in the call application as a shared element so that it persists during the switching process.

[0350] For example, Fig.23 As shown, when the user clicks the call application icon on the application desktop, the application desktop and the call application are triggered to switch between interfaces. In the process of jumping from the application desktop to the call application, the answer key as a shared element always exists, and the answer key performs a smooth downward movement effect, and then displays the call application interface.

[0351] Conversion type 2: Activity conversion type.

[0352] Among them, the scheme for converting between interfaces in the embodiment of the present application based on the Activity conversion type can also be divided into multiple situations such as conversion between applications, conversion within applications, and conversion from desktop to application, which are not limited to the following:

[0353] Case 1: In-app conversion:

[0354] like Fig.24 As shown, the embodiment of the present application takes the book application in the application market as an example, and provides a first example of the effect of the interface transition between at least two activities. Exemplarily, as shown in Table 6, the configuration file of the book application in the application market described in the embodiment of the present application is as follows:

[0355]

[0356] Among them, assuming that when switching between interfaces, the exit interface and the entry interface of the book application are as follows Fig.24 As shown, according to the exit interface of the book application, it can be understood that the exit interface includes a title bar, a category icon and at least one book cover.

[0357] According to the contents of Table 6 above, it can be known that the book cover selected by the user is a shared element, which persists when switching between interfaces; the exit elements are the title bar, category icons, and other book covers not selected by the user, which perform a downward slide effect when switching between interfaces. According to the entry interface of the book application, it can be known that the content introduction part, evaluation column, function icons, etc. in the entry interface are all entry elements, which perform an upward slide effect when switching between interfaces.

[0358] Therefore, when the book application starts the interface transition scheme, Fig.24As shown, it is assumed that the book selected by the user is Book 4. Therefore, in the process of switching from the exit interface to the entry interface, the exit interface slides down to exit, the icon of Book 4 always exists, and the entry interface slides up to enter.

[0359] like Fig.25 As shown, the embodiment of the present application takes the gallery application in the application market as an example and provides a second example of the effect of the transition between interfaces based on at least two Activities.

[0360] Exemplarily, as shown in Table 7, the configuration file of the gallery application in the embodiment of the present application is as follows:

[0361]

[0362] Among them, assuming that when switching between interfaces, the exit interface and entry interface of the gallery application are as follows Fig.25 As shown, according to the exit interface of the gallery application, it can be understood that the exit interface includes a search bar, function icons, and at least one picture.

[0363] According to the content of Table 7 above, it can be known that the picture selected by the user is a shared element, which persists when switching between interfaces; the exit element is the search bar, function icons, and other pictures not selected by the user, etc., which execute the left movement effect when switching between interfaces. According to the entry interface of the gallery application, it can be known that the function icons in the entry interface and other pictures not selected by the user are all entry elements, and the center zoom effect is executed when switching between interfaces.

[0364] Therefore, when the book application starts the one-shot interface transition, Fig.25 As shown, assuming that the picture selected by the user is a flower picture, therefore, in the process of switching from the exit interface to the entry interface, the exit interface is shifted left and cut out, the icon of the flower picture always exists, and the entry interface is cut in.

[0365] like Fig.26 As shown, the embodiment of the present application takes a music application as an example and provides three examples of effects based on the transition between interfaces between at least two Activities.

[0366] Exemplarily, as shown in Table 8, the configuration file of the music application in the embodiment of the present application is as follows:

[0367]

[0368] Assume that when switching between interfaces, the exit interface and entry interface of the music application are as follows: Fig.26 As shown, according to the Fig.26From the scene shown in the figure, it can be understood that the exit scene includes a classification icon, at least one cover and a function button, etc.

[0369] According to the contents of Table 8 above, it can be known that the cover image selected by the user is a shared element, which persists when switching between interfaces; when the exit element is used to switch between interfaces, a zooming animation is executed. According to the entry scenario of the music application, it can be known that the song list and function icons in the entry interface are all entry elements, and an upward sliding effect is executed when the interface is switched.

[0370] Therefore, when the book application starts a one-shot transition between interfaces, Fig.26 As shown, assuming that the cover selected by the user is the main cover, therefore, in the process of switching from the exit interface to the entry interface, the exit interface is scaled and cut out, the main cover always exists, and the entry interface is swiped up to cut in.

[0371] In order to better achieve the effect of switching between interfaces, in this embodiment, the startup interface of the application can be directly used as the exit scene, for example, Fig. 27 As shown, the startup interface of the music application is regarded as the exit scene, and the cover image in the startup interface is used as a shared element. When the user continues to operate the application and enters the specific operation interface of the music application, the main cover always exists.

[0372] Case 2: Inter-application conversion:

[0373] like Fig.28 As shown, the following takes the case where a user needs to switch to a gallery application when using a camera application as an example to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0374] Assume that when a user configures a transition scheme between the camera application and the gallery application, the user uses the thumbnail button in the camera application as a shared element so that it persists during the transition process.

[0375] For example, Fig.28 As shown, when the user clicks the thumbnail button in the camera interface, the camera application and the gallery application are triggered to switch between the interfaces. After the camera application jumps to the gallery application, the photographed pictures are displayed. At this time, the thumbnail button of the camera application continues to exist, the camera interface disappears, and the pictures in the gallery appear. After clicking the thumbnail button in the gallery interface, the thumbnail button continues to exist.

[0376] Case 3: Desktop to App Conversion:

[0377] The following takes the example of a user needing to switch from an application desktop to a music application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0378] Assume that when the user configures a scheme for switching between the photo application desktop and the music application interface, the user uses the musical note element in the music application icon as a shared element, which persists during the switching process.

[0379] For example, Fig.29 As shown, when the user clicks the music application icon on the application desktop, the interface transition between the application desktop and the music application is triggered. In the process of jumping from the application desktop to the music application, the musical note as a shared element always exists, and the musical note performs a smooth downward movement effect, and then displays the music application interface.

[0380] Conversion type three: ViewGroup conversion type.

[0381] Among them, the embodiment of the present application is based on the ViewGroup conversion type, and the solution for converting between interfaces can also be divided into multiple situations such as conversion between applications, conversion within applications, and conversion from desktop to application, which are not limited to the following:

[0382] Case 1: In-app conversion:

[0383] like Fig.30 As shown, the embodiment of the present application takes a calendar application as an example and provides a first example of the effect of transition between interfaces based on at least two ViewGroups.

[0384] Exemplarily, as shown in Table 9, the configuration file of the calendar application described in the embodiment of the present application is as follows.

[0385]

[0386] Assume that when switching between interfaces, the exit interface and entry interface of the music application are as follows: Fig.30 As shown, according to the content of Table 9 above, it can be determined that the exit animation in the exit interface is a 20-pixel displacement from left to right and a gradient of 2s, and the entry animation in the entry interface is a 20-pixel displacement from right to left and a gradient of 2s. It is determined that when the shared element is switching between interfaces, the shared element will shake from left to right with a shaking amplitude of 2 pixels.

[0387] Therefore, when the calendar application starts switching between interfaces, such as Fig.30 As shown, assuming that the user clicks the icon of month 8 in the interface a of the calendar application, the icon of month 8 is determined as a shared element. During the interface conversion process, the icon of month 8 always exists.

[0388] Case 2: Inter-application conversion:

[0389] like Fig.31 As shown, the following takes the case where a user needs to switch to a camera application when using a shopping application as an example to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0390] Assume that when a user configures a transition scheme between the interfaces of a shopping application and a camera application, the user uses the camera button in the shopping application as a shared element so that it persists during the transition process.

[0391] For example, Fig.31 As shown, when the user clicks the camera button in the shopping interface, the shopping application and the camera application are triggered to switch between the interfaces. In the process of the shopping application jumping to the camera application, the camera application's camera button continues to exist, the shopping interface gradually disappears, and the camera interface gradually appears.

[0392] Case 3: Desktop to App Conversion:

[0393] The following takes the example of a user needing to switch from an application desktop to a calendar application to introduce a method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0394] Assume that when configuring a conversion scheme between the application desktop and the calendar application interface, the user uses the date element in the calendar application icon as a shared element, which persists during the conversion process.

[0395] For example, Fig.32 As shown, when the user clicks the calendar application icon on the application desktop, the interface transition between the application desktop and the calendar application is triggered. In the process of the application desktop jumping to the calendar application, the date as a shared element always exists.

[0396] Application example 2: when element 1 in the first interface is switched to the second interface through at least one transition interface, element 1 gradually changes into element 2, wherein the similarity between element 2 and element 1 is higher than a similarity threshold.

[0397] In the following, based on different conversion types such as Activity conversion type, ViewGroup conversion type and Fragment conversion type, the scheme for converting between interfaces based on a one-shot effect provided in the embodiments of the present application is introduced by examples.

[0398] Conversion type 1: Fragment conversion type.

[0399] Among them, the embodiment of the present application is based on the fragment transition type, and the solution for transitioning between interfaces can also be divided into multiple situations such as transition between applications, transition within an application, and transition from desktop to application, which are not limited to the following:

[0400] Case 1: In-app conversion:

[0401] like Fig.33 As shown, the embodiment of the present application takes a call application as an example and provides an example of an effect based on an in-application conversion between at least two Fragments.

[0402] Among them, the embodiment of the present application can set corresponding IDs for the answer key and the hang-up key in the answer button, and determine the usage status of the call application according to the answer or hang-up command triggered by the user.

[0403] For example, Fig.33 As shown, when the call application starts switching between interfaces, during the process of switching from the first interface to the second interface, if the user triggers an answer command, the answer key is a shared element.

[0404] That is, the transition interface of the first interface in the process of switching to the second interface contains the shared element, wherein the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0405] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.33 It can be seen that in the process of element 1 gradually turning into element 2, the content expressed is that the phone is gradually answered, which enriches the fun and brings a more vivid interface switching experience to users.

[0406] In addition, the exit elements in the first interface gradually fade away, for example, the exit element hang-up key icon, and when the interface is switched, a gradual fading effect is performed. The entry elements in the second interface gradually appear, for example, the entry element hands-free icon and keyboard icon, and when the interface is switched, a gradual showing effect is performed.

[0407] Case 2: Inter-application conversion:

[0408] The following takes the example of a user using a call application and needing to switch to a text message application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0409] Assume that when a user configures a transition scheme between the call application and the text message application, the user uses the answer button in the call application as a shared element so that it persists during the transition process.

[0410] For example, Fig.34 As shown, when the user clicks the SMS button in the call interface, the call application and the SMS application are triggered to switch between the interfaces. That is, the call interface can be understood as the first interface, and the SMS application interface can be understood as the second interface.

[0411] The shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0412] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.34 It can be seen that in the process of element 1 gradually turning into element 2, the content expressed is that the phone is gradually answered, which enriches the fun and brings a more vivid interface switching experience to users.

[0413] In addition, the exit element in the first interface gradually fades away, for example, the exit element hang-up key icon performs a fade-out animation when switching interfaces. The entry element in the second interface gradually appears, for example, the entry element is a text message editing interface represented by a bubble window that gradually appears for text message editing.

[0414] Case 3: Desktop to App Conversion:

[0415] The following takes the example of a user needing to switch from an application desktop to a call application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0416] Assume that when configuring a scheme for switching between the application desktop and the call application interface, the user uses the answer button in the call application as a shared element so that it persists during the switching process.

[0417] For example, Fig.35 As shown, when the user clicks the call application icon on the application desktop, the interface transition between the application desktop and the call application is triggered. That is, the application desktop interface can be understood as the first interface, and the call application interface can be understood as the second interface. Among them, the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0418] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.35 It can be seen that in the process of element 1 gradually turning into element 2, the content shown is that the phone is gradually picked up and a smooth downward movement effect is performed, which enriches the fun and brings a more vivid interface switching experience to users.

[0419] In addition, the exit element in the first interface gradually fades away, for example, the icon of other applications of the exit element performs a fade-out animation when switching interfaces. The entry element in the second interface gradually appears to obtain the call application interface.

[0420] Conversion type 2: Activity conversion type.

[0421] Among them, the scheme for converting between interfaces in the embodiment of the present application based on the Activity conversion type can also be divided into multiple situations such as conversion between applications, conversion within applications, and conversion from desktop to application, which are not limited to the following:

[0422] Case 1: In-app conversion:

[0423] like Fig.36 As shown, the embodiment of the present application takes the book application in the application market as an example and provides an example of the effect of transition between interfaces based on at least two Activities.

[0424] For example, Fig.36 As shown, when the music application starts the one-shot conversion, the cover image selected by the user is used as a shared element during the process of switching from the first interface to the second interface. For example, the cover image selected by the user is used as the main cover image. That is, the transition interface of the first interface during the process of switching to the second interface includes the shared element.

[0425] The shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0426] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.36 It can be seen that in the process of element 1 gradually turning into element 2, the performance content is the singer gradually raising the microphone in his hand, which enriches the fun and brings a more vivid interface switching experience to users.

[0427] In addition, the exit elements in the first interface perform zooming animation cut-out, for example, the exit element classification icon, at least one cover and function button, etc., when the interface is switched, the zooming animation cut-out is performed. The entry elements in the second interface perform the sliding up effect to gradually appear, for example, the entry element song list and function icon, when the interface is switched, the sliding up effect gradually appears.

[0428] Case 2: Inter-application conversion:

[0429] like Fig.37As shown, the following takes the case where a user needs to switch to a gallery application when using a camera application as an example to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0430] Assume that when a user configures a transition scheme between the camera application and the gallery application, the user uses the thumbnail button in the camera application as a shared element so that it persists during the transition process.

[0431] For example, Fig.37 As shown, when the user clicks the thumbnail icon in the camera application, the interface conversion between the camera application and the gallery application is triggered. That is, the camera application can be understood as the first interface, and the gallery application interface can be understood as the second interface. Among them, the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0432] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.37 It can be seen that in the process of element 1 gradually turning into element 2, the content expressed is the gradual display of the picture from local to global, which enriches the fun and brings a more vivid interface switching experience to users.

[0433] In addition, the exit elements in the first interface gradually fade away, and the entry elements in the second interface gradually appear. For example, after the camera application jumps to the gallery application, the photos taken are displayed. At this time, the thumbnail button of the camera application continues to exist, the camera interface disappears, and the photos in the gallery appear.

[0434] Case 3: Desktop to App Conversion:

[0435] The following takes the example of a user needing to switch from an application desktop to a music application to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0436] Assume that when the user configures a conversion scheme between the application desktop and the interface of the music application, the user uses the musical note element in the music application icon as a shared element so that it persists during the conversion process.

[0437] For example, Fig.38 As shown, when the user clicks the music application icon on the application desktop, the interface transition between the application desktop and the music application is triggered. That is, the application desktop interface can be understood as the first interface, and the music application interface can be understood as the second interface. Among them, the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0438] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.38 It can be seen that in the process of element 1 gradually changing into element 2, the content is the gradual display of the five-line score on the music symbol, and the execution of a smooth downward movement effect, which enriches the fun and brings a more vivid interface switching experience to users.

[0439] In addition, the exit element in the first interface gradually fades away, for example, the icons of other applications of the exit element perform a fade-out animation when switching interfaces. The entry element in the second interface gradually appears to obtain the music application interface.

[0440] Conversion type three: ViewGroup conversion type.

[0441] Among them, the embodiment of the present application is based on the ViewGroup conversion type, and the solution for converting between interfaces can also be divided into multiple situations such as conversion between applications, conversion within applications, and conversion from desktop to application, which are not limited to the following:

[0442] Case 1: In-app conversion:

[0443] like Fig.39 As shown, the embodiment of the present application takes a calendar application as an example and provides a first example of the effect of transition between interfaces based on at least two ViewGroups.

[0444] For example, Fig.39 As shown, when the calendar application starts switching between interfaces, the month icon selected by the user is used as a shared element during the process of switching from the first interface to the second interface. For example, the month selected by the user is August. That is, the transition interface of the first interface in the process of switching to the second interface includes the shared element.

[0445] The shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0446] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.39 It can be seen that when element 1 gradually turns into element 2, the circular background of the August icon gradually disappears, which enriches the fun and brings a more vivid interface switching experience to users.

[0447] In addition, the exit element in the first interface performs a zoom-in animation cut-out, for example, the exit element is issued in other months, and when the interface is switched, the zoom-in animation cut-out is performed. The entry element in the second interface is enlarged and displayed, for example, the entry element corresponds to the month calendar of August, and it is enlarged and gradually displayed when the interface is switched.

[0448] Case 2: Inter-application conversion:

[0449] like Fig.40 As shown, the following takes the case where a user needs to switch to a camera application when using a shopping application as an example to introduce the method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0450] Assume that when a user configures a transition scheme between the interfaces of a shopping application and a camera application, the user uses the camera button in the shopping application as a shared element so that it persists during the transition process.

[0451] For example, Fig.40 As shown, when the user clicks the camera icon in the shopping application, the interface transition between the shopping application and the camera application is triggered. That is, the shopping application can be understood as the first interface, and the camera application interface can be understood as the second interface. Among them, the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0452] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.40 It can be seen that in the process of element 1 gradually turning into element 2, the content expressed is that the camera lens gradually lengthens, which enriches the fun and brings a more vivid interface switching experience to users.

[0453] Among them, when the shopping application jumps to the camera application, the camera application's photo button continues to exist, the shopping interface gradually disappears, and the camera interface gradually appears.

[0454] Case 3: Desktop to App Conversion:

[0455] The following takes the example of a user needing to switch from an application desktop to a calendar application to introduce a method for switching between interfaces based on a one-shot effect provided in an embodiment of the present application.

[0456] Assume that when a user configures a scheme for switching between the interface of a photo application desktop and a calendar application, the user uses a date element in the calendar application icon as a shared element, which persists during the switching process.

[0457] For example, Fig.41 As shown, when the user clicks the calendar application icon on the application desktop, the interface transition between the application desktop and the calendar application is triggered. That is, the application desktop interface can be understood as the first interface, and the calendar application interface can be understood as the second interface. Among them, the shared element is expressed as element 1 in the first interface and as element 2 in the second interface, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0458] Furthermore, during the switching process from the first interface to the second interface, element 1 gradually changes into the representation of element 2, such as Fig.41 It can be seen that in the process of element 1 gradually changing into element 2, the content displayed is that the date element gradually displays a circular background, which enriches the fun and brings a more vivid interface switching experience to users.

[0459] Among them, when the application desktop jumps to the calendar application, the date as a shared element always exists.

[0460] In addition, the one-shot to end conversion method described in the embodiment of the present application can also be applied to application operations such as split-screen mode and multi-screen collaboration, and is not limited to the following description.

[0461] Mode 1: Split screen mode.

[0462] In daily life, when using smart devices, such as mobile phones, users may need to split the screen of the mobile phone for convenience of operation. In order to reduce the visual jump amplitude of the user, increase the fun of the display, and thus enhance the user experience, in the split-screen operation scenario, the application displayed on each screen of the embodiment of the present application can still execute the interface conversion solution provided by the embodiment of the present application.

[0463] For example, Fig.42 As shown, it is assumed that the display interface of the mobile phone is divided into two parts, the upper part and the lower part. Among them, the upper interface displays the gallery application, and the lower interface displays the music application. When the user operates the gallery application in the split-screen interface 1, the gallery application is converted accordingly according to the pre-set interface conversion scheme. When the user operates the music application in the split-screen interface 2, the music application is converted accordingly according to the pre-set interface conversion scheme.

[0464] For example, Fig.43 As shown, it is assumed that the display interface of the mobile phone is divided into two layers, wherein the display interface of one application is suspended above the interface of another application. Among them, the upper interface displays the gallery application, and the lower interface displays the music application. When the user operates the gallery application in split-screen interface 1, the gallery application is converted accordingly according to the pre-set interface conversion scheme. When the user operates the music application in split-screen interface 2, the music application is converted accordingly according to the pre-set interface conversion scheme.

[0465] Preferably, the suspended application interface can be used as a shared element of the underlying application interface, and when the underlying application interface is converted, the suspended application interface always exists.

[0466] It should be noted that in the split-screen mode of the present application, multiple screens can simultaneously perform interface conversion based on the corresponding interface conversion scheme, without being restricted by the conversion type or the usage scenario. For example, it can be based on different conversion types such as Activity conversion type, ViewGroup conversion type, and Fragment conversion type, and can be used within an application, between applications, and between the system and applications. For details, please refer to the present application embodiment Figure 20 to Figure 41 Introduction.

[0467] Mode 2: Multi-screen collaboration mode.

[0468] When users are operating an application, they may need to switch screens. For example, when users are operating a gallery application on their mobile phone, in order to make viewing more convenient, they may connect the mobile phone to the PC and use multi-screen collaboration to display the application interface in the mobile phone on the PC.

[0469] In an optional manner of the embodiment of the present application, when a user performs a multi-screen collaborative operation, such as Fig.44 As shown, the content of the gallery application in the mobile phone display interface is switched to the PC side, wherein the entire PC side displays the content of the gallery application. In other words, the mobile phone operation is replaced by the PC side operation, and the mobile phone display interface is now the same as the PC side display interface.

[0470] Another optional method of the embodiment of the present application is that when the user performs multi-screen collaborative operation, only the entry content of the gallery application in the mobile phone display interface is switched to the PC.

[0471] For example, Fig.45 As shown, the converted content and shared elements are displayed on the PC side, and the mobile side still maintains the exit interface display interface.

[0472] It should be noted that if Fig.45 In the content shown, the shared elements can continue to be displayed in the display interface of the mobile phone.

[0473] For example, Fig.45 As shown, the PC side only displays the converted entry interface without displaying the shared elements, while the mobile side displays the shared elements and the exit interface. In other words, the PC side at this time only enlarges the entry interface so that the user can see the entry interface more clearly and intuitively through the PC side. The user can continue to control the image switching on the PC side by operating the mobile side.

[0474] It should be noted that in the multi-screen collaborative mode of the present application embodiment, multiple screens can simultaneously perform interface conversion based on the corresponding one-shot effect, without being restricted by the conversion type or the usage scenario. For example, it can be based on different conversion types such as Activity conversion type, ViewGroup conversion type, and Fragment conversion type, and can be used within an application, between applications, and between the system and applications. For details, please refer to the present application embodiment Figure 20 to Figure 34 Introduction.

[0475] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0476] Each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0477] 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 technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk.

[0478] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited thereto, and any changes or replacements within the technical scope disclosed in the embodiment of the present application should be included in the protection scope of the embodiment of the present application. Therefore, the protection scope of the embodiment of the present application should be based on the protection scope of the claims.

Claims

1. A method for converting between interfaces, applied to electronic equipment, characterized in that: The method comprises: After the electronic device detects a first operation performed by a user on the electronic device, the electronic device displays a first interface, where the first interface includes a first element and a second element; After the electronic device detects a second operation performed by the user on the first interface, it displays at least one transition interface and then displays the second interface; The second interface includes the second element and the third element; the transition interface includes the second element; The second element does not include the first interface, the transition interface, and the elements in the status bar of the second interface.

2. The method according to claim 1, characterized in that After the electronic device detects a second operation performed by the user on the first interface, after displaying at least one transition interface, displaying the second interface includes: The first element in the first interface of the electronic device gradually disappears, the third element in the second interface gradually appears, and the second element continues to exist in the first interface, the at least one transition interface, and the second interface.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The electronic device executes the corresponding animations of the interface and / or the element according to the transition animations configured for each interface or according to the transition animations configured for the elements in the interface during the process of switching from the first interface to the second interface.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The first interface and the second interface are different display interfaces of the first application; or, The first interface is the main interface of the electronic device or an interface adjacent to the main interface or a negative one-screen interface, the first interface includes an application icon of a first application, the second element is an element in the application icon, the first operation is an operation of clicking the application icon, and the second interface is a display interface of the first application; or, The first interface is a display interface of a first application, and the second interface is a display interface of a second application.

5. A method for converting between interfaces, applied to electronic equipment, characterized in that: The method comprises: The electronic device determines an interface type according to an interface configuration instruction triggered by a user, wherein the interface type includes a first interface, at least one transition interface, and a second interface; wherein the transition interface refers to an intermediate interface from the first interface to the second interface; The electronic device determines, according to the element configuration instruction triggered by the user, the first element and the second element in the first interface, and determines the second element and the third element in the second interface; Wherein, the transition interface includes a second element.

6. The method according to claim 5, characterized in that The method further comprises: The electronic device determines the motion effects executed by the interface and / or elements during the process of switching from the first interface to the second interface according to the motion effect configuration instruction triggered by the user.

7. A method for converting between interfaces, applied to electronic equipment, characterized in that: The method comprises: After the electronic device detects a first operation performed by a user on the electronic device, the electronic device displays a first interface; the first interface includes a first element and a second element; After the electronic device detects a second operation performed by the user on the first interface, it displays at least one transition interface and then displays the second interface; The second interface includes a third element and a fourth element; In the process of the first interface switching to the second interface through the at least one transition interface, the presentation form of the second element in the transition interface gradually changes to the presentation form of the third element; The second element is partially identical to the third element.

8. The method according to claim 7, characterized in that After the electronic device detects a second operation performed by the user on the first interface, after displaying at least one transition interface, displaying the second interface includes: The first element in the first interface of the electronic device gradually disappears, the fourth element in the second interface gradually appears, and the second element in the transition interface gradually becomes the third element.

9. The method according to claim 7 or 8, characterized in that The method further comprises: The electronic device executes the corresponding animations of the interface and / or the element according to the transition animations configured for each interface or according to the transition animations configured for the elements in the interface during the process of switching from the first interface to the second interface.

10. The method according to any one of claims 7 to 9, characterized in that: The method further comprises: The first interface and the second interface are different display interfaces of the first application; or, The first interface is the main interface of the electronic device or an adjacent interface of the main interface or a negative one-screen interface, the first interface includes an application icon of a first application, the second element is an element in the application icon, the first operation is an operation of clicking the application icon, and the second interface is a display interface of the first application; or, the first interface is the display interface of the first application, and the second interface is the display interface of the second application.

11. A method for converting between interfaces, applied to electronic equipment, characterized in that: The method comprises: The electronic device determines an interface type according to an interface configuration instruction triggered by a user, wherein the interface type includes a first interface, at least one transition interface, and a second interface; wherein the transition interface refers to an intermediate interface from the first interface to the second interface; The electronic device determines the first element and the second element in the first interface, and determines the third element and the fourth element in the second interface according to the element configuration instruction triggered by the user; According to the element configuration instruction triggered by the user, determining that the second element in the transition interface gradually changes to the third element; The second element is partially identical to the third element.

12. The method according to claim 11, characterized in that The method further comprises: The electronic device determines the motion effects executed by the interface and / or elements during the process of switching from the first interface to the second interface according to the motion effect configuration instruction triggered by the user.

13. An electronic device, characterized in that: include: monitor; one or more processors; one or more memories; The one or more memories store one or more computer programs, and the one or more computer programs include instructions. When the instructions are executed by the one or more processors, the electronic device executes the method as claimed in any one of claims 1 to 4; or executes the method as claimed in any one of claims 5 to 6; or executes the method as claimed in any one of claims 7 to 10; or executes the method as claimed in any one of claims 11 to 12.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a computer program. When the computer program is executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 4; or executes the method according to any one of claims 5 to 6; or executes the method according to any one of claims 7 to 10; or executes the method according to any one of claims 11 to 12.

15. A graphical user interface system on an electronic device, characterized in that: The electronic device has a display, one or more memories, and one or more processors, the one or more processors are used to execute one or more computer programs stored in the one or more memories, and the graphical user interface system includes a graphical user interface displayed when the electronic device executes any one of the methods described in claims 1 to 12.

Images