Conversion Method, Device, and System between Interfaces

Abstract

The present application provides a method, device, and system for inter-interface conversion. The method includes an electronic device displaying a first interface after detecting a first operation performed by a user on the electronic device. The first interface includes a first element and a second element. The electronic device displays at least one transition interface, and then displays a second interface after detecting a second operation performed by the user on the first interface. The second interface includes a second element and a third element, and the transition interface includes a second element, the second element not including an element in a status bar on the first interface, the transition interface, or the second interface. According to the method, when conversion is performed between application interfaces, shared elements continuously exist or continuously change, resulting in an uninterrupted user experience.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the priority of Chinese Patent Application No. 202010943693.3, titled "METHOD AND DEVICE FOR CONVERSION BETWEEN APPLICATION INTERFACES", filed with the China National Intellectual Property Administration on September 9, 2020, the entire content of which is incorporated herein by reference. Additionally, this application claims the priority of Chinese Patent Application No. 202110482721.0, titled "INTER - INTERFACE CONVERSION METHOD, DEVICE, AND SYSTEM", filed with the China National Intellectual Property Administration on April 30, 2021, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of terminal technologies, and in particular, to an interface - to - interface conversion method, device, and system.

Background Art

[0003] With the improvement of device performance, when using an electronic device, users pay more attention to the effect experience during interface conversion.

[0004] Currently, when a conversion is performed between a first interface and a second interface, the first interface is directly switched to the second interface, leading to a monotonous conversion effect, relatively insufficient coherence, and a relatively insufficient user experience.

Summary of the Invention

Means for Solving the Problems

[0005] This application provides an interface - to - interface conversion method, device, and system to provide a conversion solution with relatively strong coherence.

[0006] According to the first aspect, an interface conversion method is provided. The method includes: After an 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. The electronic device displays at least one transition interface. Then, after the electronic device detects a second operation performed by the user on the first interface, the electronic device displays a second interface. The second interface includes a second element and a third element. The transition interface includes the second element, and the second element does not include an element within a status bar on the first interface, the transition interface, or the second interface.

[0007] Based on the foregoing method, in the process of switching from the first interface to the second interface, at least one transition interface is used for splicing. The transition interface includes the second element included in both the first interface and the second interface. As a result, in the process of switching between the first interface and the second interface, the change is natural and coherent, and the visual experience effect on the user is relatively good.

[0008] In a possible implementation, the first element on the first interface of the electronic device fades out, the third element on the second interface fades in, and the second element continuously exists on the first interface, at least one transition interface, and the second interface.

[0009] In a possible implementation, in the process of the electronic device switching from the first interface to the second interface, the electronic device executes a dynamic effect corresponding to the interface and / or the element based on a conversion dynamic effect configured for each interface or based on a conversion dynamic effect configured for an element on the interface.

[0010] In a possible implementation form, the first interface and the second interface are different display interfaces of the first application, or the first interface is the home screen of the electronic device, an interface adjacent to the home screen, or the leftmost 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.

[0011] According to a second aspect, an interface conversion method is provided, and the method includes: The electronic device determines an interface type based on an interface configuration command triggered by the user, the interface type includes a first interface, at least one transition interface, and a second interface, the transition interface is an intermediate splicing interface from the first interface to the second interface, the electronic device determines a first element and a second element on the first interface based on an element configuration command triggered by the user, determines a second element and a third element on the second interface, and the transition interface includes the second element.

[0012] Based on the foregoing method, in a conversion configuration for switching from a first interface to a second interface, at least one transition interface is configured for splicing, and the transition interface includes a second element included in both the first interface and the second interface. As a result, in the process of switching between the first interface and the second interface, the change is natural, coherent, and the visual experience effect on the user is relatively good. In addition, the application can configure various conversion types, element types, and animation effects during conversion based on its own requirements to achieve a more flexible and smooth dynamic effect experience. The overall application becomes simpler, the components are configurable, and the effects are better.

[0013] In a possible implementation, the electronic device determines the dynamic effects executed by the interface and / or elements in the process of switching from the first interface to the second interface based on the dynamic effect configuration instructions triggered by the user.

[0014] According to a third aspect, an interface conversion method is provided. The method includes: After the electronic device detects a first operation performed by the user on the electronic device, the first interface is displayed. The first interface includes a first element and a second element. The electronic device displays at least one transition interface. Then, after detecting a second operation performed by the user on the first interface, the second interface is displayed. The second interface includes a third element and a fourth element. In the process of switching from the first interface to the second interface by using 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, and the second element is partially the same as the third element.

[0015] Based on the foregoing method, in a conversion configuration for switching from a first interface to a second interface, at least one transition interface is configured for splicing, a second element on the first interface and a third element on the second interface are present on the transition interface, the second element is partially the same as the third element, and as a result, in the process of switching between the first interface and the second interface, the change is natural, coherent, and the visual experience effect on the user is relatively good.

[0016] In a possible implementation, a first element on a first interface of an electronic device fades out, a fourth element on the second interface fades in, and a second element on the transition interface gradually changes to a third element.

[0017] In a possible implementation, in the process of an electronic device switching from a first interface to a second interface, based on a conversion dynamic effect configured for each interface or based on a conversion dynamic effect configured for an element on the interface, a dynamic effect corresponding to the interface and / or the element is executed.

[0018] In a possible implementation, the first interface and the second interface are different display interfaces of a first application, or the first interface is the home screen of the electronic device, an interface adjacent to the home screen, or the leftmost 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.

[0019] According to a fourth aspect, an interface conversion method is provided, and the method includes An electronic device determines an interface type based on an interface configuration instruction triggered by a user. The interface type includes a first interface, at least one transition interface, and a second interface. The transition interface is an intermediate splicing interface from the first interface to the second interface. The electronic device determines a first element and a second element on the first interface, and a third element and a fourth element on the second interface based on an element configuration instruction triggered by the user. The electronic device determines that the second element gradually changes to the third element on the transition interface based on an element configuration instruction triggered by the user, and the second element is partially the same as the third element.

[0020] Based on the foregoing method, in a conversion configuration for switching from the first interface to the second interface, at least one transition interface is configured for splicing. The second element on the first interface and the third element on the second interface exist on the transition interface. The second element is partially the same as the third element. As a result, in the process of switching between the first interface and the second interface, the change is natural and coherent, and the visual experience effect on the user is relatively good. In addition, the application can configure various conversion types, element types, and animation effects during the conversion based on its own requirements to achieve a more flexible and smooth dynamic effect experience. The overall application becomes simpler, the components are configurable, and the effect is better.

[0021] In a possible implementation, the electronic device determines a dynamic effect executed by an interface and / or an element in the process of switching from the first interface to the second interface based on a dynamic effect configuration instruction triggered by the user.

[0022] According to a fifth aspect, an embodiment of the present application provides a method for switching an application interface. The method includes: receiving, for a target application, an interface conversion instruction triggered by a user, and determining an interface to be converted by the target application and shared elements included in the converted interface; and performing a conversion between corresponding interfaces based on the interface conversion instruction triggered by the user, where the shared elements on the converted interface are continuously presented in the interface conversion process.

[0023] Based on the foregoing method, an application can configure different transition types, element types, and animation effects during the transition according to the requirements of the application to achieve a more flexible and smoother dynamic effect experience. The overall application becomes simpler, the components become configurable, and the effects become better.

[0024] In a possible implementation, the conversion interface includes an end interface and an input interface, or the conversion interface includes an end interface, an input interface, and a shared interface. The end interface is the initial interface during the interface conversion, the input interface is the final interface during the interface conversion, and the shared interface is the intermediate splicing interface during the interface conversion.

[0025] In a possible implementation, the method further includes determining an end element and / or an input element on the conversion interface, where the end element on the conversion interface disappears after the end interface is converted, and the input element on the conversion interface is displayed after the end interface is converted to the input interface.

[0026] In a possible implementation form, the method further includes the step of executing corresponding dynamic effects in the conversion process based on the conversion dynamic effects configured for each interface on the conversion interface and / or based on the conversion dynamic effects configured for each element on the conversion interface.

[0027] It should be noted that the end interface in the fifth aspect is equivalent to the first interface in the first aspect and / or the second aspect, the input interface in the fifth aspect is equivalent to the second interface in the first aspect and / or the second aspect, the shared interface in the fifth aspect is equivalent to the transition interface in the first aspect and / or the second aspect, the end element in the fifth aspect is equivalent to the first element in the first aspect and / or the second aspect, the input element in the fifth aspect is equivalent to the third element in the first aspect and / or the second aspect, and the shared element in the fifth aspect is equivalent to the second element in the first aspect and / or the second aspect.

[0028] According to a sixth aspect, an embodiment of the present application provides a method for switching an application interface, and the method includes Based on the interface conversion configuration command triggered by the user, determining an interface type for conversion, where the interface type includes an end interface, an input interface, and a shared interface, the end interface refers to the initial interface during interface conversion, the input interface refers to the final interface during interface conversion, and the shared interface refers to the intermediate splicing interface during interface conversion; and based on the element configuration command triggered by the user, determining shared elements in the interface conversion process, where the shared elements are elements continuously presented in the interface conversion process.

[0029] Based on the foregoing method, the application can configure different transition types, element types, and animation effects during the transition based on the requirements of the application to achieve a more flexible and smoother dynamic effect experience. The overall application becomes simpler, the components can be configured, and the effects are better.

[0030] In a possible implementation form, the method includes determining end elements and / or input elements in the interface conversion process based on the element configuration command triggered by the user, where the end elements on the conversion interface disappear after the end interface is converted, and the input elements on the conversion interface are displayed after the end interface is converted to the input interface.

[0031] The end interface in the sixth aspect is equivalent to the first interface in the first aspect and / or the second aspect, the input interface in the sixth aspect is equivalent to the second interface in the first aspect and / or the second aspect, the shared interface in the sixth aspect is equivalent to the transition interface in the first aspect and / or the second aspect, the end element in the sixth aspect is equivalent to the first element in the first aspect and / or the second aspect, the input element in the sixth aspect is equivalent to the third element in the first aspect and / or the second aspect, and the shared element in the sixth aspect is equivalent to the second element in the first aspect and / or the second aspect. Note this.

[0032] According to the seventh aspect, an interface - between - devices is further provided. The device can be configured to execute operations in any possible implementation form of the first aspect, the third aspect, or the fifth aspect. For example, the device can include a module or unit configured to execute operations in any possible implementation form of the first aspect, the third aspect, or the fifth aspect. For example, a transceiver module and a processing module are included.

[0033] According to the eighth aspect, an electronic device between interfaces is further provided. The electronic device can be configured to execute operations in any possible implementation form of the second aspect, the fourth aspect, or the sixth aspect. For example, the electronic device can include a module or unit configured to execute operations in any possible implementation form of the second aspect, the fourth aspect, or the sixth aspect. For example, a transceiver module and a processing module are included.

[0034] According to a ninth aspect, there is provided a chip system including a processor and optionally further including a memory. The memory is configured to store a computer program, and the processor is configured to call the computer program from the memory and execute the computer program, whereby an electronic device in which the chip system is installed can execute any method in any possible implementation form from the first aspect to the sixth aspect.

[0035] According to a tenth aspect, there is provided a computer program product. The computer program product includes computer program code, and when the computer program code is executed by a processing module or a processor of an electronic device, the electronic device can execute any method in any possible implementation form from the first aspect to the sixth aspect.

[0036] According to an eleventh aspect, there is provided a computer-readable storage medium. The computer-readable storage medium stores a program, and the program enables an electronic device to execute any method in any possible implementation form from the first aspect to the sixth aspect.

[0037] According to a twelfth aspect, there is provided an electronic device including a display, one or more processors, and 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 is enabled to execute any method in any possible implementation form from the first aspect to the sixth aspect.

Brief Description of the Drawings

[0038]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16(a)

Figure 16(b)

Figure 16(c)

Figure 17(a)

Figure 17(b)

Figure 17(c)

Figure 17(d)

Figure 17(e)

Figure 17(f)

Figure 17(g)

Figure 17(h)

Figure 18

Figure 19

Figure 20

Figure 21(a)

Figure 21(b)

Figure 21(c)

Figure 22(a)

Figure 22(b)

Figure 23(a)

Figure 23(b)

Figure 23(c)

Figure 24(a)

Figure 24(b)

Figure 24(c)

Figure 24(d)

Figure 25(a)

Figure 25(b)

Figure 25(c)

Figure 25(d)

Figure 26(a)

Figure 26(b)

Figure 26(c)

Figure 26(d)

Figure 26(e)

Figure 26(f)

Figure 26(g)

Figure 27(a)

Figure 27(b)

Figure 27(c)

Figure 27(d)

Figure 27(e)

Figure 27(f)

Figure 28(a)

Figure 28(b)

Figure 28(c)

Figure 28(d)

Figure 28(e)

Figure 28(f)

Figure 29(a)

Figure 29(b)

Figure 29(c)

Figure 29(d)

Figure 29(e)

Figure 29(f)

Figure 30(a)

Figure 30(b)

Figure 30(c)

Figure 30(d)

Figure 30(e)

Figure 30(f)

Figure 31(a)

Figure 31(b)

Figure 31(c)

Figure 31(d)

Figure 31(e)

Figure 31(f)

Figure 31(g)

Figure 32(a)

Figure 32(b)

Figure 32(c)

Figure 32(d)

Figure 32(e)

Figure 32(f)

Figure 33(a)

Figure 33(b)

Figure 33(c)

Figure 34(a)

Figure 34(b)

Figure 34(c)

Figure 35(a)

Figure 35(b)

Figure 35(c)

Figure 36(a)

Figure 36(b)

Figure 36(c)

Figure 36(d)

Figure 36(e)

Figure 36(f)

Figure 36(g)

Figure 37(a)

Figure 37(b)

Figure 37(c)

Figure 37(d)

Figure 37(e)

Figure 37(f)

Figure 38(a)

Figure 38(b)

Figure 38(c)

Figure 38(d)

Figure 38(e)

Figure 38(f)

Figure 39(a)

Figure 39(b)

Figure 39(c)

Figure 39(d)

Figure 39(e)

Figure 39(f)

Figure 40(a)

Figure 40(b)

Figure 40(c)

Figure 40(d)

Figure 40(e)

Figure 40(f)

Figure 40(g)

Figure 41(a)

Figure 41(b)

Figure 41(c)

Figure 41(d)

Figure 41(e)

Figure 41(f)

Figure 42

Figure 43

Figure 44(a)

Figure 44(b)

Figure 45(a)

Figure 45(b)

Mode for Carrying Out the Invention

[0039] For ease of understanding, exemplary explanations of some concepts related to the embodiments of the present application are provided as follows for reference.

[0040] (1) Single shot: In the embodiments of the present application, when a switch is executed between a first interface and a second interface, there is at least one transition interface, and the transition interface includes elements on the first interface and / or the second interface. As a result, the switch between the two interfaces mainly means that it is more coherent without interrupting the user experience.

[0041] For example, in an optional manner of the embodiments of the present application, the transition interface includes elements that exist on both the first interface and the second interface. For example, there is an element 1 on the first interface, the transition interface also includes the element 1, and the second interface also includes the element 1. In other words, the element 1 continuously exists in the process of switching from the first interface to the second interface. As a result, the user feels that the interface switching transition is relatively natural, smooth, and coherent in terms of the visual sensory experience in the switching process.

[0042] For example, in another optional manner of the embodiments of the present application, when the element 1 on the first interface is switched to the second interface by using at least one transition interface, the element 1 gradually changes to the element 2, and the element 2 is partially similar to the element 1.

[0043] That the element 2 is partially similar to the element 1 may mean that 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.

[0044] The fact that Element 2 is partially similar to Element 1 can alternatively mean that the similarity between Element 2 and Element 1 is higher than the similarity threshold. For example, the presentation form of Element 1 on the first interface is a man wearing a hat. In the process of transitioning to the second interface, the man wearing a hat presented for Element 1 slowly takes off the hat and becomes Element 2 on the second interface. The presentation form of Element 2 on the second interface is a man holding the hat in his hand. In this way, from the perspective of the visual sensory experience in the switching process, the user feels that the interface switching transition is relatively natural, coherent, and more vivid and interesting.

[0045] (2) Conversion: In the embodiments of the present application, conversion mainly means that the display interface on the terminal display changes from the first interface to the second interface. It should be understood that conversion may also be referred to as transition.

[0046] The interface conversion can be, for example, the conversion between different interfaces within the same application, the interface conversion during the conversion between different applications, the interface conversion during the conversion between the terminal display desktop and the application cover, etc.

[0047] In addition, the conversion between interfaces in the embodiments of the present application may also be referred to as the conversion between interfaces, the transition between interfaces, or the switching between interfaces.

[0048] (3) Conversion object: In the embodiments of the present application, the conversion object can be understood as, for example, an application that needs to perform the interface conversion.

[0049] In the embodiments 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 referred to as the transition object.

[0050] (4) Conversion scenario: In the embodiments of the present application, the conversion scenario can be understood as an interface classification during interface conversion. It should be understood that the conversion scenario may also be referred to as a transition scenario.

[0051] In the embodiments of the present application, the conversion scenario may include an end scenario (which may also be referred to as a starting scenario), an input scenario (which may also be referred to as an entrance scenario), and a shared scenario (which may also be referred to as a transition scenario).

[0052] The end scenario may be understood as the first interface in the embodiments of the present application, the input scenario may be understood as the second interface in the embodiments of the present application, and the shared scenario may be understood as the transition interface in the embodiments of the present application.

[0053] (5) The input element refers to the type of elements included in the input scenario or can be understood as an element included in the second interface. It should be understood that the input element may also be referred to as an entrance element.

[0054] (6) The shared element is an element of a type that appears continuously and changes during conversion or can be understood as an element included in the transition interface.

[0055] (7) The end element is the type of element included in the end scenario or can be understood as an element included in the first interface. It should be understood that the end element may also be referred to as a starting element.

[0056] (8) The shared container is configured to carry at least one shared element, that is, in the conversion process, all elements within the shared container change continuously.

[0057] In the embodiments of the present application, there may be at least one shared element on the transition interface.

[0058] (9) The interface display area is an area where the first interface, the transition interface, and the second interface are displayed.

[0059] Generally, the interface of an electronic device is often divided into three parts from top to bottom. For example, as shown in FIG. 1, the interface of an electronic device includes a status bar in the upper area configured to display power information, network connection information, card insertion information, signal strength information, time information, etc. of the electronic device, an interface display area in the middle area configured to display an application scenario interface, etc., and a virtual navigation button area in the lower area.

[0060] It should be noted that the area division method of the interface of the electronic device in the embodiments of the present application is not limited to the above-mentioned cases. For example, the area of the interface of the electronic device may include only the status bar and the interface display area.

[0061] In the embodiments of the present application, when an interface switch is executed, the shared elements refer only to the elements that continuously exist within the interface display area.

[0062] When the electronic device executes an interface switch, the elements in the status bar within the upper area of the interface of the electronic device may continuously exist, and the virtual navigation button elements within the lower area of the interface of the electronic device may also continuously exist, but it can be understood that none of them are the shared elements described in the embodiments of the present application.

[0063] ( 10 ) ARR is a file format, that is, a binary archive file of an Android library project.

[0064] In an optional mode of the embodiments of the present application, files such as applications corresponding to methods for conversion between application interfaces are packaged in the ARR file format.

[0065] The files in the ARR package format in the embodiments of the present application include class files, res (resource) files, and the like.

[0066] ( 11 )The Jar package is a file format.

[0067] In an optional mode of the embodiments of the present application, files such as applications corresponding to methods for conversion between application interfaces are packaged in the Jar package file format. The files in the Jar package format in the embodiments of the present application include class files, list files, and the like.

[0068] In the embodiments of the present application, the term "at least one" means one or more, and the term "a plurality" means two or more. The term "and / or" describes the relationship between related objects and indicates that three relationships can exist. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists. A and B can be in singular or plural form. The character " / " usually indicates the "or" relationship between related objects. At least one of the following items (parts) or similar expressions refers to any combination of the singular item (part) or plural items (parts), including any combination of these items. For example, at least one of a, b, or c can indicate a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be in singular or plural form.

[0069] Unless otherwise specified, ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are intended to distinguish multiple objects and are not intended to limit the order, time sequence, priority, or importance of multiple objects. In addition, the terms "including" and "having" in the embodiments, claims, and accompanying drawings of this application are not exclusive. For example, a process, method, system, product, or device including a series of steps or modules is not limited to the listed steps or modules and may further include steps or modules not listed.

[0070] In addition, according to the description of the foregoing content, the first interface described in the embodiments of this application is equivalent to the end interface in the priority claim document (Application No. 202010943693.3), and the second interface described in this application is equivalent to the input interface in the priority claim document (Application No. 202010943693.3). It can be understood that the transition interface described in this application is equivalent to the shared interface in the priority claim document (Application No. 202010943693.3), the first element in the embodiments of this application is equivalent to the end element in the priority claim document (Application No. 202010943693.3), and the second element in the embodiments of this application is equivalent to the shared element in the priority claim document (Application No. 202010943693.3), and the third element in the embodiments of this application is equivalent to the input element in the priority claim document (Application No. 202010943693.3).

[0071] Hereinafter, the technical solutions of the embodiments of this application will be described with reference to the accompanying drawings of the embodiments of this application.

[0072] The interface conversion method provided in the embodiments of this application can be applied to the system architecture shown in FIG. 2. The system architecture includes at least one application-side device 1100 and a platform-side device 1200.

[0073] The application-side device 1100 and the platform-side device 1200 can be interconnected by using a communication network. The communication network may be a local area network or a wide area network transferred by using a relay device. When the communication network is a local area network, for example, the communication network may be a short-distance 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, for example, the communication network may be a 3rd generation mobile communication technology (3G) network, a 4th generation mobile communication technology (4G) network, a 5th generation mobile communication technology (5G) network, a future evolved public land mobile network (PLMN), or the Internet. In the scenario shown in FIG. 1, different electronic devices can exchange data with each other by using a communication network, for example, by transmitting an interface conversion effect, and can configure an interface conversion solution on the application. mobile communication technology, 4G) network, a 5th generation mobile communication technology (5G) network, a future evolved public land mobile network (public land mobile network, PLMN), or the Internet. In the scenario shown in FIG. 1, different electronic devices can exchange data with each other by using a communication network, for example, by transmitting an interface conversion effect, and can configure an interface conversion solution on the application.

[0074] In an optional manner, the application-side device 1100 accesses, through a communication interface established with the platform-side device 1200, an application framework within the platform-side device 1200 that is used for application interface conversion. The application-side device 1100 configures an interface conversion solution for the conversion object by using the application framework, that is, determines a first interface, a second interface, at least one transition interface, and shared elements within the conversion object. Therefore, when the conversion object performs interface conversion, the shared elements can be presented continuously, as a result, the interface conversion effect becomes smoother and the user experience becomes more coherent.

[0075] Furthermore, when the application-side device 1100 enables the interface conversion solution corresponding to the conversion object, the platform-side device 1200 parses the interface conversion solution corresponding to the conversion object within the application-side device 1100 and executes the interface conversion solution, as a result, the conversion object implements a coherent and smooth conversion effect.

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

[0077] In addition, the application-side device 1100 may alternatively complete the configuration of the conversion object's interface conversion solution with the platform-side device 1200 in advance and store the interface conversion solution in another server. Then, when the conversion object is started, an interface for communicating with the server is called, and the interface conversion solution is obtained through the interface. In addition, in the online integration method, the application-side device 1100 in this embodiment of the present application can further grant the user permission from the platform-side device 1200 to configure the interface conversion solution for the conversion object. For example, the user can, based on the user's intention, call an interface for communicating with the platform-side device 1200 and update and adjust the interface conversion solution of the conversion object at any time.

[0078] In the second alternative method of the embodiment of the present application, the application-side device 1100 obtains the application file package used to configure the interface conversion solution for the conversion object from the platform-side device 1200 and stores the file package. The application-side device 1100 parses the syntax of the file package stored locally in the application to obtain the application program used to configure the interface conversion solution for the conversion object. The application-side device 1100 determines the conversion object by using the application, and configures the interface conversion solution for the conversion object, that is, determines the first interface, the second interface, at least one transition interface, and the shared elements in the conversion object. Therefore, when the interface conversion is performed on the conversion object, the shared elements can be presented continuously, as a result, the interface conversion effect becomes smoother and the user experience becomes more coherent.

[0079] It is assumed that the file package of the application is an ARR file package, and the application-side device 1100 can obtain the file package of the application from the platform-side device 1200 and store the file package. When the application in the application-side device 1100 needs to use the interface conversion method described in the embodiments of the present application, the application can call the file package of the application in the application-side device 1100 and perform local integration based on the file package of the application.

[0080] For example, it is assumed that the application-side device 1100 is a mobile phone and the mobile phone has obtained the file package of the application. The calendar application in the mobile phone can call the file package of the application in the mobile phone, integrate the configuration file for interface conversion in this embodiment of the present application into the calendar application, and store the configuration file in the libs folder, so that the path can be subsequently introduced into the compilation script.

[0081] It is assumed that the file package of the application is a Jar file package, and the application-side device 1100 can obtain the file package of the application from the platform-side device 1200 and store the file package. When the application (i.e., the conversion object) in the application-side device 1100 needs to use the interface conversion method described in the embodiments of the present application, the application-side device 1100 can directly call the file package of the application.

[0082] Note that the system for performing interface conversion in the embodiments of this application is not limited to the architecture shown in FIG. 1. Any deformation form such as the system architecture can be applied to the embodiments of this application. For example, the system in the embodiments of this application may further include a third-party material supplier or the like.

[0083] The third-party material supplier described in the embodiments of this application may be configured to provide a dynamic effect template or the like.

[0084] For example, in an application included in the platform-side device 1200 and used for interface conversion, it is assumed that the provided dynamic effect template includes an explosion effect, a displacement effect, a scaling effect, a cropping effect, a rotation effect, etc. Compared with the dynamic effect template provided by the platform-side device 1200, the dynamic effect template provided by the third-party material supplier further includes a black hole effect, a snowflake effect, etc., and is more diverse. Therefore, in order to reduce the modification to the application in the platform-side device 1200, an interface used to communicate with the third-party material supplier can be added to the system. As a result, when designing a dynamic effect in the interface conversion solution, the user can call the dynamic effect template provided by the third-party material supplier.

[0085] The following separately describes the hardware structure and software structure of the platform-side device 1200 and the application-side device 1100 by using examples.

[0086] 1. Platform-side device: Specifically, in the scenario of the embodiment of the present application, the platform-side device 1200 can be a server or a cloud server that stores application code used to implement the interface conversion method provided in the present application.

[0087] It should be noted that in the embodiment of the present application, there may be multiple types of application codes stored in the platform-side device 1200 and used to implement the interface conversion method provided in the present application.

[0088] For example, the application code may be applicable to the Android (registered trademark) system and be the application code used to execute the interface conversion method, applicable to the Harmony (registered trademark) system and be the application code used to execute the interface conversion method, and applicable to the iOS (registered trademark) system and be the application code used to execute the interface conversion method. In the embodiment of the present application, the adapted application code used to execute the interface conversion method can be selected based on the system installed in the electronic device. This is not limited in this specification.

[0089] FIG. 3 is a framework diagram of a partial structure of the platform-side device 1200 related to the embodiment of the present application.

[0090] As shown in FIG. 3, the platform-side device 1200 can include a processor 1210, a memory 1220, and a transceiver 1230.

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

[0092] The processor 1210 in this embodiment of the present application can be a central processing unit (CPU), a digital processing device, or the like.

[0093] The processor 1210 is the control center of the platform-side device 1200. By using various interfaces and lines, it is connected to all parts of the entire platform-side device 1200, and executes various functions of the platform-side device 1200 by executing or performing the computer programs stored in the memory 1220.

[0094] In an optional manner of this embodiment of the present application, the processor 1210 is configured to determine a conversion object for interface conversion, a conversion scenario in the interface conversion process, elements in the scenario, and corresponding scenario dynamic effects and element dynamic effects based on the user's operation instructions. Then, based on the configuration procedure, the processor 1210 processes and packages the interface conversion solution of the conversion object, and stores the interface conversion solution locally.

[0095] When the application-side device 1100 starts the interface conversion effect of the conversion object, the processor 1210 is further configured to parse the interface conversion solution corresponding to the conversion object, that is, to determine the attributes corresponding separately to the conversion scenario and the elements in the conversion object. The attributes include dynamic effects, display rates, and the like.

[0096] Furthermore, the processor 1210 performs one-tap execution based on the interface conversion solution configured by the application-side device 1100 for the conversion object.

[0097] For example, the processor 1210 determines configuration parameters of related scenarios and elements within the conversion object based on an interface - to - interface conversion solution corresponding to the conversion object.

[0098] Subsequently, the processor 1210 can send the execution data of the related scenarios and elements in the form of a streaming medium to the application - side device 1100 for playback.

[0099] In another alternative manner of this embodiment of the present application, the processor 1210 is configured to determine a conversion object for interface - to - interface conversion, a conversion scenario in the interface - to - interface conversion process, elements within the scenario, and corresponding scenario dynamic effects and element dynamic effects based on a user's operation instruction. Then, the processor 1210 processes and packages the interface - to - interface conversion solution of the conversion object based on the configuration procedure, and sends the interface - to - interface conversion solution to the corresponding application - side device 1100.

[0100] The application - side device 1100 receives and stores the interface - to - interface conversion solution corresponding to the conversion object. When starting the interface - to - interface conversion effect of the conversion object, the application - side device 1100 calls the interface - to - interface conversion solution corresponding to the conversion object and parses the syntax of the interface - to - interface conversion solution corresponding to the conversion object, that is, determines attributes corresponding separately to the conversion scenario and elements within the conversion object. The attributes include dynamic effects, display rates, and the like.

[0101] Also, the application - side device 1100 performs one - tap execution based on the interface - to - interface conversion solution corresponding to the conversion object.

[0102] For example, the application-side device 1100 determines configuration parameters of related scenarios and elements within the conversion object based on an interface conversion solution corresponding to the conversion object.

[0103] Next, the application-side device 1100 executes execution data of related scenarios and elements of the conversion object, and displays the effect of the interface conversion executed on the conversion object on the display of the application-side device 1100.

[0104] In an optional manner, the transceiver 1230 is configured to receive an operation instruction triggered by a user and send the operation instruction to the processor 1210. As a result, the processor 1210 is used for interface conversion and, by using an application within the platform-side device 1200, configures an interface conversion solution for the corresponding conversion object based on the operation instruction, and / or In an optional manner, the transceiver is configured to send a file package of an application within the platform-side device 1200 to the application-side device 1100, and / or In an optional manner, the transceiver is configured to send a solution for the application-side device 1100 to perform an interface conversion on a conversion object within the platform-side device 1200 to the application-side device 1100.

[0105] The specific connection medium between the processor 1210 and the memory 1220 is not limited in this embodiment of the present application. In this embodiment of the present application, the memory 1220, the processor 1210, and the transceiver 1230 are connected via the bus 1240 in FIG. 3. The bus is represented by using a thick line in FIG. 3. The connection manners between other components are schematically described and are not limited thereto. The bus can be classified into an address bus, a data bus, a control bus, and the like. For the sake of easy expression, only one thick line is used to represent the bus in FIG. 3, but this does not indicate that there is only one bus or only one type of bus.

[0106] The memory 1220 may be a volatile memory, for example, a random-access memory (RAM). Alternatively, the memory 1220 may be a non-volatile memory, for example, a read-only memory, a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). Alternatively, the memory 1220 may be used to carry or store program code expected in the form of instructions or data structures and may be any other medium accessible by a computer, but is not limited thereto. The memory 1220 may be a combination of the aforementioned memories.

[0107] In addition, in this embodiment of the present application, an Android (registered trademark) system having a hierarchical architecture is used as an example to describe the software structure of the platform-side device 1200. It should be noted that in another operating system (for example, a Harmony (registered trademark) system or an iOS (registered trademark) system), the solution of the present application can still be implemented on the condition that the functions implemented by the functional modules are the same as the functions in the embodiments of the present application. This is not limited in this specification.

[0108] In an optional manner of this embodiment of the present application, a block diagram of the software structure of the platform-side device 1200 can be shown in FIG. 4.

[0109] The platform-side device 1200 divides software into multiple layers based on a hierarchical architecture, and each layer has a clear division of roles and labor. The layers communicate with each other via software interfaces.

[0110] For example, in some embodiments, the Android system is divided into four layers from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0111] (1) Application layer: In an optional manner of this embodiment of the present application, the application layer may include a series of application packages.

[0112] For example, the application layer in this embodiment of the present application may store the applications used to execute the interface conversion solution provided in the present application.

[0113] (2) Application framework layer: In an optional manner of this embodiment of the present application, the application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application framework layer may include some predefined functions.

[0114] (3) Android Runtime and system libraries: The Android Runtime can include kernel libraries and a virtual machine, and is configured to be responsible for the scheduling and management of the Android system.

[0115] Furthermore, the kernel libraries in this embodiment of the present application may include two parts, namely, functions that need to be called by the Java language and the core libraries of Android.

[0116] In this embodiment of the present application, the virtual machine is configured to execute functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection. For example, the application layer and the application framework layer operate on the virtual machine. The virtual machine executes the java files of the application layer and the application framework layer as binary files.

[0117] In this embodiment of the present application, the system libraries may include a plurality of functional modules, such as a surface manager, Media Libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0118] Furthermore, in this embodiment of the present application, the surface manager manages the display subsystem and is configured to provide the fusion of the 2D layer and the 3D layer for a plurality of applications.

[0119] The Media Libraries support the playback and recording of a plurality of generally used audio and video formats, still image files, etc. The Media Libraries can support a plurality of audio and video encoding formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0120] The three-dimensional graphics processing library is configured to implement three-dimensional graphics drawing, image rendering, composition, layer processing, and the like.

[0121] The 2D graphics engine is a drawing engine for 2D drawing.

[0122] (4) Kernel layer In this embodiment of the present application, the kernel layer may be understood as a layer between hardware and software, and includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

[0123] Furthermore, as shown in FIG. 4, the capability framework corresponding to the application used for interface conversion in this embodiment of the present application may include a configuration module, a syntax analysis module, and an execution module.

[0124] It should be noted that the system layer where the capability framework is located is not limited in this embodiment of the present application. For example, the capability framework described in this embodiment of the present application can be arranged in the application layer. Alternatively, the capability framework in this embodiment of the present application may be independent of the four layers included in the system. For example, the capability framework is an external layer, an extension based on the capabilities of the framework layer, and may be extended in the AAR format or the Jar format to facilitate the use of the application.

[0125] The configuration module in the platform-side device in this embodiment of the present application is configured to perform parameter configuration for the conversion scenario and elements of the determined conversion object.

[0126] Specifically, the configuration module receives the configuration instructions sent by the application-side device 1100, and based on the configuration instructions, performs parameter configuration on the conversion scenarios and elements of the conversion object for which interface conversion needs to be executed.

[0127] The syntax analysis module in the platform-side device in this embodiment of the present application is configured to syntax analyze the interface conversion solution corresponding to the conversion object and store the syntax-analyzed interface conversion solution.

[0128] For example, the interface conversion solution may include the name of the conversion object, the name of the shared element or shared container, the conversion dynamic effect ID configured for the end interface, the conversion dynamic effect ID configured for the input interface, the conversion dynamic effect ID configured for the shared element or shared container, etc.

[0129] It can be understood that the syntax analysis module mainly determines the conversion scenario in the conversion object, the elements in each conversion scenario, and the corresponding execution effect based on the interface conversion solution corresponding to the conversion object.

[0130] The execution module in the platform-side device in this embodiment of the present application is configured to execute different animation effects on different elements at different times based on the interface conversion solution.

[0131] 2. Application-side device The application-side device 1100 can be a portable electronic device such as a mobile phone, a tablet computer, or a wearable device (e.g., a smartwatch) that has a wireless communication function and further includes other functions such as a mobile information terminal and / or a music player function. Exemplary embodiments of the portable electronic device include, but are not limited to, portable electronic devices carrying iOS (registered trademark), Android (registered trademark), Microsoft (registered trademark), Harmony (registered trademark), or another operating system. Alternatively, the portable electronic device can be another portable electronic device, such as a laptop having a touch-sensitive surface (e.g., a touch panel). Hereinafter, for the sake of explanation, an example in which the application-side device 1100 is a mobile phone will be used. FIG. 5 is a block diagram of a partial structure of the application-side device 1100 related to an embodiment of the present application.

[0132] As shown in FIG. 5, the application-side device 1100 may be a mobile phone. The mobile phone 1100 includes a processor 1110, an external memory interface 1120, an internal memory 1121, a universal serial bus (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, a headset jack 1170D, a sensor module 1180, a button 1190, a motor 1191, an indicator 1192, a camera 1193, a display 1194, a subscriber identification module (SIM) card interface 1195, etc. The sensor module 1180 may include a pressure sensor 1180A, a gyro sensor 1180B, a barometric pressure sensor 1180C, a magnetic sensor 1180D, an acceleration sensor 1180E, a distance sensor 1180F, an optical proximity sensor 1180G, a fingerprint sensor 1180H, a temperature sensor 1180J, a touch sensor 1180K, an ambient light sensor 1180L, a bone conduction sensor 1180M, etc.

[0133] It can be understood that the structure shown in this embodiment of the present application does not constitute a specific limitation on the application-side device 1100. In some other embodiments of the present application, the application-side device 1100 may include more or fewer components than those shown in the figure, or some components may be combined, or some components may be divided, or different component arrangements may be used. The components shown in the figure may be implemented by using hardware, software, or a combination of software and hardware.

[0134] Processor 1 110 may include one or more processing units. For example, the processor 1110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or may be integrated into one or more processors. The controller may be the central center and command center of the mobile phone 1 100. The controller may generate an operation control signal based on an instruction operation code and a time-series signal to complete the control of instruction fetching and instruction execution. If the memory is further arranged in the processor 1 110, it may be configured to store instructions and data. In some embodiments, the memory 1 within the processor 110 is a cache. The memory may store instructions or data used by the processor 1 110 or periodically used. When the processor 1 110 needs to reuse an instruction or data, the processor can directly call the instruction or data from the memory. This avoids repeated accesses, reduces the latency of the processor 1 110, and improves system efficiency.

[0135] In some embodiments, the processor 1110 may include one or more interfaces. The interfaces 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, a universal serial bus (USB) interface, and / or the like.

[0136] The USB interface 130 is an interface compliant with the USB standard specifications, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 may be configured to connect to a charger to charge the mobile phone 1 100, or may be configured to perform data transmission between the mobile phone 1 100 and a peripheral device. The charge management module 140 is configured to receive a charging input from a charger. The charge management module 141 is configured to connect to the battery 142, the charge management module 140, and the processor 1 110. The charge management module 141 receives inputs from the battery 142 and / or the charge management module 140, and the processor 1 110, the internal memory 121, the external memory, the display 1It supplies power to 194, camera 193, wireless communication module 160, etc.

[0137] In an optional manner of this embodiment of the present application, the processor 1110 is configured to determine a conversion object, call an application that is within the platform - side device 1200 and is used for inter - interface conversion, and determine an inter - interface conversion method for the conversion object.

[0138] In a second optional manner of this embodiment of the present application, the processor 1110 is configured to determine a conversion object and an inter - interface conversion solution corresponding to the conversion object, and implement the inter - interface conversion of the conversion object based on the inter - interface conversion solution when the inter - interface conversion is performed on the conversion object.

[0139] In a third optional manner of this embodiment of the present application, the processor 1110 is further configured to instruct the platform - side device 1200 to display an inter - interface conversion effect of the conversion object based on the inter - interface conversion solution of the conversion object by the platform - side device 1200.

[0140] The wireless communication function of the mobile phone 1100 may be implemented by using antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, baseband processor, etc. Antenna 1 and antenna 2 are configured to transmit and receive electromagnetic wave signals. The mobile phone 1 Each antenna of 100 may be configured to cover one or more communication frequency bands. To improve antenna utilization, different antennas may be further multiplexed. For example, antenna 1 may be multiplexed as a diversity antenna in a wireless local area network. In some other embodiments, the antenna may be used in combination with a tuning switch.

[0141] The mobile communication module 1150 is applied to the mobile phone 1100 and can provide solutions including wireless communications such as 2G / 3G / 4G / 5G. The mobile communication module 1150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 1150 can receive electromagnetic waves through the antenna 1, perform processing such as filtering or amplification on the received electromagnetic waves, and transmit the electromagnetic waves to the modem processor for demodulation. The mobile communication module 1150 can further amplify the signal modulated by the modem processor and convert the signal 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 arranged within the processor 1110. In some embodiments, at least some of the functional modules of the mobile communication module 1150 can be arranged in the same device as at least some of the modules of the processor 1110.

[0142] The wireless communication module 1160 is applied to the mobile phone 1100 and can provide wireless communication solutions including wireless local area network (WLAN) (for example, wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC) technology, infrared (IR) technology, etc. The wireless communication module 1160 can be one or more components integrating at least one communication processor module. The wireless communication module 1160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and transmits the processed signals to the processor 1110. The wireless communication module 1160 can further receive signals to be transmitted from the processor 1110, perform frequency modulation and amplification on the signals, and convert the signals into electromagnetic waves for radiation through the antenna 2. For example, in this embodiment of the present application, the communication connection can be established between different electronic devices by using BT or WLAN.

[0143] In some embodiments, in mobile phone 1100, antenna 1 is coupled to mobile communication module 1150, and antenna 2 is coupled to wireless communication module 1160. As a result, mobile phone 1100 can communicate with a network and other devices by using wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM) for mobile communication, general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA (registered trademark)), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), future communication systems such as the fifth generation (5G) mobile communication system, the sixth generation (6G) system, BT, GNSS, WLAN, NFC, FM, and / or IR technology. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0144] The display 1194 is configured to display, such as, the display interface of an application. The display 1194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diode (QLED), or the like. In some embodiments, the mobile phone 1100 may include one or N displays 194, where N is a positive integer greater than 1. In this embodiment of the present application, the display 1194 may be configured to display an application interface.

[0145] The camera 1193 is configured to capture a still image or a video. The camera 1193 may include a front-facing camera and a rear-facing camera.

[0146] The internal memory 1121 can be configured to store computer-executable program code. The executable program code includes instructions. The processor 1110 implements various functional applications and data processing of the mobile phone 1100 by executing the instructions stored in the internal memory 1121. The internal memory 1121 may include a program storage area and a data storage area. The program storage area may store an operating system, software code of at least one application (for example, a voice playback function or an image playback function), and the like. The data storage area may store data (for example, images and videos) generated in the process of using the mobile phone 1100. In addition, the internal memory 1121 may include a high-speed random access memory and may further include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.

[0147] The external memory interface 1120 may be configured to connect to an external storage card, for example, a Micro SD card, to expand the storage capacity of the mobile phone 1100. The external storage card communicates with the processor 1110 via the external memory interface 1120 to implement a data storage function. Files such as images or videos are stored in the external storage card.

[0148] The mobile phone 1100 can implement audio functions, such as music playback and recording, via the audio module 1170, the speaker 1170A, the receiver 1170B, the microphone 1170C, the headset jack 1170D, and the application processor.

[0149] Button 1190 includes a power button, a volume button, etc. Button 1190 may be a mechanical button or a touch button. The mobile phone 1100 may receive button inputs and generate button signal inputs related to user settings and function controls of the mobile phone 1100. Motor 1191 may generate a vibration prompt. Motor 1191 may be configured to generate an incoming call vibration prompt and a touch vibration feedback. For example, touch operations performed on different applications (such as shooting and audio playback) may correspond to different vibration feedback effects. Indicator 1192 may be an indicator light and may be configured to indicate a charging status and a power change, or may be configured to indicate a message, a missed call, a notification, etc. The SIM card interface 1195 is configured to connect to a SIM card. The SIM card may be inserted into the SIM card interface 1195 or removed from the SIM card interface 1195 to implement contact and separation from the mobile phone 1100.

[0150] In addition, in this embodiment of the present application, an Android (registered trademark) system having a hierarchical architecture is used as an example to explain the software structure of the application-side device 1100. It should be understood that the Android (registered trademark) system is used as an example in this specification. In another operating system (such as the Harmony (registered trademark) system or the iOS (registered trademark) system), the solution of the present application can still be implemented on the condition that the functions implemented by the function modules are the same as the functions in the embodiments of the present application.

[0151] FIG. 6 is a block diagram of the software structure of the application-side device 1100 according to an embodiment of the present application.

[0152] In a layered architecture, software is divided into multiple layers, and each layer has a clear role and task. The layers communicate with each other via software interfaces.

[0153] In some embodiments, the Android system is divided into four layers from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0154] The application layer within the application-side device 1100 in this embodiment of the present application may include a series of application packages.

[0155] As shown in FIG. 6, the application packages can include applications such as dialer, camera, gallery, calendar, phone, map, navigation, WLAN, Bluetooth, music, video, and messages.

[0156] The application framework layer within the application-side device 1100 in this embodiment of the present application is mainly configured to provide application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application framework layer may include some predefined functions.

[0157] As shown in FIG. 6, the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0158] The window manager is configured to manage window programs. The window manager may obtain the size of the display, determine whether there is a status bar, execute a screen lock, take a screen shot, etc.

[0159] The content provider is configured to store and obtain data and enable the data to be accessed by applications. The data can include videos, images, audio, outgoing and incoming calls, browsing history and bookmarks, phone books, etc.

[0160] The view system includes visual controls such as controls for displaying text and controls for displaying images. The view system can be configured to build applications. The display interface may include one or more views. For example, a display interface including a message notification icon may include a text display view and a picture display view.

[0161] The phone manager is configured to provide the communication function of the application-side device 1100, for example, manage the call status (including answering, rejecting, etc.).

[0162] The resource manager provides various resources such as localized strings, icons, photos, layout files, video files, etc. to the application.

[0163] The notification manager can enable an application to display notification information in the status bar and can be configured to send messages of a notification type. The displayed information may automatically disappear without interaction with the user after a short pause. For example, the notification manager is configured to notify of download completion, provide message notifications, etc. The notification manager may alternatively be a notification that appears in the top status bar of the system in the form of a graph or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, text information is displayed in the status bar, an announcement is made, the electronic device vibrates, or an indicator light blinks.

[0164] In addition, the contents of the system library and kernel layer within the application-side device 1100 in this embodiment of the present application are the same as the contents of the system library and kernel layer within the platform-side device 1200. For the sake of brevity of description, for details, please refer to the description of the system library and kernel layer within the platform-side device 1200. The details will not be described again here.

[0165] When using an electronic device, the user pays more and more attention to bringing an interface experience.

[0166] Currently, when the first interface is switched to the second interface, the first interface is directly switched to the second interface. Therefore, the coherence is relatively poor and the user experience is relatively bad.

[0167] For example, as shown in FIG. 7, in the second interface switching configuration currently executed on the first interface, only the end element on the first interface, the dynamic effect executed by the end element during switching, and / or the input element on the second interface and the dynamic effect executed by the input element during switching are determined. In the switching process, in order to complete the switching from the first interface to the second interface, the end element on the first interface executes the corresponding end effect and ends, and the input element on the second interface executes the corresponding dynamic effect and inputs.

[0168] The end element in FIG. 7 may be understood as the end element in the priority claim document (Application No. 202010943693.3), and the input element may be understood as the input element in the priority claim document (Application No. 202010943693.3).

[0169] From the above content, it can be found that the processing logic of the current interface conversion solution is relatively simple, and only the dynamic effects of end and input are simply implemented. In addition, the process of switching between the first interface and the second interface is discontinuous, and the user's visual experience is insufficient. To solve this problem, the embodiments of the present application provide an interface conversion method, device, and system for efficiently and flexibly implementing a more coherent interface conversion effect.

[0170] With reference to the accompanying drawings and application scenarios, a method for performing interface conversion based on a single-shot effect provided in the embodiments of the present application will be described in detail below.

[0171] First, in this embodiment of the present application, the ability framework corresponding to the application used for interface conversion is specifically described, that is, the application framework layer in FIG. 4 is specifically described.

[0172] From the content of FIG. 4, it can be found that the application framework layer mainly includes a configuration module, a syntax analysis module, and an execution module. Therefore, in this embodiment of the present application, when the interface conversion is executed based on the application framework, as shown in FIG. 8, it can be understood that there may be three phases: a configuration phase, a syntax analysis phase, and an execution phase.

[0173] The application framework shown in FIG. 8 is mainly used to provide an efficient, flexible, and rich single-shot effect. Therefore, the application framework can be understood as the single-shot framework shown in FIG. 7 of the priority claim document (Application No. 202010943693.3).

[0174] Phase 1: Configuration Phase: Phase 1 mainly refers to performing parameter configuration on the scenarios and elements in the conversion object by using the configuration module in the application framework.

[0175] For details of the application framework in the configuration phase in this embodiment of the present application, please refer to FIG. 9.

[0176] The configuration phase shown in FIG. 9 of this application can be understood as the configuration module shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). Therefore, the end scenario shown in FIG. 9 of this application is equivalent to the end scenario shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). The input scenario shown in FIG. 9 of this application is equivalent to the input scenario shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). The shared scenario shown in FIG. 9 of this application is equivalent to the shared scenario shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). The end element shown in FIG. 9 of this application is equivalent to the end element shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). The input element shown in FIG. 9 of this application is equivalent to the input element shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). The shared element shown in FIG. 9 of this application is equivalent to the shared element shown in FIG. 8 of the priority claim document (Application No. 202010943693.3). Specifically, in this embodiment of this application, when an interface conversion solution is designed, a conversion object needs to be determined first.

[0177] For example, as shown in FIG. 10, assume that the application-side device is a mobile phone, and the applications in the mobile phone include a calendar, a gallery, an App gallery, weather, a phone, etc. The application-side device determines the gallery as the conversion object based on a selection command triggered by the user, and determines to execute an interface conversion solution for the internal application interface in the gallery, for example.

[0178] Next, in an optional manner of this embodiment of this application, a device (for example, a processor in the application-side device or a processor in the platform-side device) that configures the interface conversion solution for the conversion object determines the conversion scenario in the conversion object.

[0179] As shown in FIG. 11, it mainly includes determining an end scenario, a transition scenario, and an input scenario. It can be understood that different scenarios are arranged at different nodes within the conversion object. The end scenario shown in FIG. 11 of the present application is equivalent to the end scenario shown in FIG. 10 of the priority claim document (Application No. 202010943693.3). The transition scenario shown in FIG. 11 of the present application is equivalent to the shared scenario shown in FIG. 10 of the priority claim document (Application No. 202010943693.3). The input scenario shown in FIG. 11 of the present application is equivalent to the input scenario shown in FIG. 10 of the priority claim document (Application No. 202010943693.3).

[0180] As shown in FIG. 12, the application-side device determines an element type and a dynamic effect format based on an instruction triggered by a user. The element types include a shared element, an end element, and an input element. The end element shown in FIG. 12 of the present application is equivalent to the end element shown in FIG. 11 of the priority claim document (Application No. 202010943693.3). The shared element shown in FIG. 12 of the present application is equivalent to the continuous element shown in FIG. 11 of the priority claim document (Application No. 202010943693.3). The input element shown in FIG. 12 of the present application is equivalent to the input element shown in FIG. 11 of the priority claim document (Application No. 202010943693.3). Further, as shown in FIG. 13, a device configured to perform an interface conversion solution configuration for a conversion object determines, based on a selection instruction triggered by a user, the classification of elements in each conversion scenario, that is, which elements are used as end elements, which elements are used as shared elements, and which elements are used as input elements in each scenario, and determines a corresponding dynamic effect when the elements are converted. The end information container shown in FIG. 13 of the present application is equivalent to the end information container shown in FIG. 12 of the priority claim document (Application No. 202010943693.3). The input information container shown in FIG. 13 of the present application is equivalent to the input information container shown in FIG. 12 of the priority claim document (Application No. 202010943693.3). All the end elements shown in FIG. 13 of the present application are equivalent to all the end elements shown in FIG. 12 of the priority claim document (Application No. 202010943693.3). All the input elements shown in FIG. 13 of the present application are equivalent to all the input elements shown in FIG. 12 of the priority claim document (Application No. 202010943693.3).

[0181] It should be noted that in this embodiment of the present application, a device configured to perform an interface conversion solution configuration for a conversion object can further divide the element type based on the container in which the element is located. For example, it is assumed that Container 1 is determined as a shared container. It can be understood that all elements in Container 1 are shared elements.

[0182] In addition, in an optional manner of this embodiment of the present application, a device configured to perform an interface conversion solution configuration for a conversion object can further set the size of the information container based on a processing instruction triggered by a user.

[0183] For example, in this embodiment of the present application, the current mainstream Activity conversion type is used as an example for briefly explaining some parameters related to the elements in the conversion object of this embodiment of the present application.

[0184] The parameters related to the elements in this embodiment of the present application may include name, movement duration, control ID, dynamic effect, dynamic effect delay, interface (end and / or input) duration, etc.

[0185] It should be noted that the parameters related to the elements in this embodiment of the present application are not limited to the above-mentioned multiple types, and any configuration parameters applicable to the elements in this embodiment of the present application fall within the protection scope of this embodiment of the present application. For example, when multiple dynamic effects are set for an element, the configured parameters may further include the interval duration between each dynamic effect, etc.

[0186] For example, as shown in Table 1 below, in this embodiment of the present application, the parameters that may need to be configured for interface conversion for the selected conversion object are briefly listed in tabular form.

[0187]

Table 1

[0188] From the content of Table 1, it can be found that in this embodiment of the present application, when an interface conversion solution is configured for a conversion object, it is necessary to first determine the name of the conversion object for which the interface conversion needs to be executed. Then, the end element, shared element, and input element of the conversion object are determined, and the end dynamic effect, end duration, end dynamic effect delay, etc. related to the end element are determined, the input dynamic effect, input duration, input dynamic effect delay, etc. related to the input element are determined, and the shared dynamic effect, shared duration, shared dynamic effect delay related to the shared element are determined.

[0189] In this embodiment of the present application, when the end element, input element, or shared element is determined by setting the container ID, it can be understood that all elements within the container ID are set as the end element, input element, or shared element.

[0190] For example, it is assumed that there are three elements, namely Element 1, Element 2, and Element 3, in Container 1. When Container 1 is set as a shared element, all elements included in Container 1 become shared elements.

[0191] Also, when a shared dynamic effect is configured for Container 1, the dynamic effect may be individually configured for each shared element, or a unified dynamic effect may be configured for the entire container.

[0192] For example, when a dynamic effect is configured for an element in container 1, the dynamic effect configured for shared element 1 is flipping, and the dynamic effects configured for shared element 2 and shared element 3 are gradients. In this case, in the interface - to - interface conversion process, shared element 1 executes the flipping dynamic effect. Shared elements 2 and 3 execute the gradient dynamic effect. Alternatively, when a dynamic effect is configured for an element in container 1, a gradient dynamic effect may be configured for container 1. In this case, in the interface - to - interface conversion process, the gradient dynamic effect is uniformly executed by shared elements 1 - 3 in container 1.

[0193] In this embodiment of the present application, when conversion is performed between a plurality of interfaces, the intermediate interface where the conversion is performed can be regarded as a transition interface (which can also be referred to as a shared interface).

[0194] It should be noted that in this embodiment of the present application, when the end interface, the transition interface, and the input interface do not overlap in the interface - to - interface conversion process, the total conversion time T1 in this embodiment of the present application is the sum of the end time T2, the shared time T3, and the input time T4. When the end interface, the transition interface, and the input interface overlap in the interface - to - interface conversion process, the total conversion time T1 in this embodiment of the present application is smaller than the sum of the end time T2, the shared time T3, and the input time T4.

[0195] Furthermore, the dynamic effect forms in this embodiment of the present application include, but are not limited to, the following multiple types, namely, explosion effect, displacement effect, scaling effect, cropping effect, rotation effect, and fade - out and fade - in effects.

[0196] In addition, the dynamic effect format in this embodiment of the present application may alternatively be implemented through user-defined extensions. For example, the dynamic effect format may alternatively be set to a black hole effect, a hidden effect, etc. in a manner defined by the user.

[0197] The user can further set the attributes of the dynamic effect based on the user's requirements, such as when to trigger the start of the dynamic effect, when to trigger the end of the dynamic effect, the type of the dynamic effect, the application scenario (i.e., whether the dynamic effect is an end dynamic effect or an input dynamic effect), the total execution time of the dynamic effect, the delay time of the dynamic effect, the interpolator of the dynamic effect, etc.

[0198] For example, Table 2 shows the dynamic effect solution configured in this embodiment of the present application.

[0199]

Table 2

[0200] From the content of Table 2, it can be found that for the element named "AutoExplodeAnimCreator", the explosion dynamic effect is executed between the end and the input.

[0201] It should be noted that the conversion type is not limited in this embodiment of the present application. For example, the conversion type in this embodiment of the present application may alternatively be a ViewGroup conversion type, a Fragment conversion type, etc. Another way to set the conversion type is the same as the way to set the Activity conversion type. The main difference is that the control format is different, that is, the conversion settings are different. For a simple explanation, please refer to the above description of the Activity conversion type.

[0202] In this embodiment of the present application, three conversion types, namely Activity, ViewGroup, and Fragment, are selected, and the conversion settings will be separately and briefly described.

[0203] For example, in this embodiment of the present application, the conversion settings for the three conversion types, namely Activity, ViewGroup, and Fragment, can be shown in Table 3.

[0204]

Table 3

[0205] Furthermore, in this embodiment of the present application, when the conversion between interfaces is configured in the configuration phase, the interface conversion solution can be configured in a user-defined manner, or the interface conversion solution can be configured in a pre-set template manner. The following provides separate explanations.

[0206] Configuration Method 1: Configured in a user-defined manner In an optional manner of this embodiment of the present application, the application framework separately executes the corresponding parameter configuration based on the content selected by the user.

[0207] For example, as shown in FIG. 14, it is assumed that an interface conversion solution is configured for application A. The user, in a user-defined manner, determines that the element corresponding to block 2 in application A is a shared element, the dynamic effect configured for the end element is a vanishing gradient, the dynamic effect configured for the shared element is amplification, and the dynamic effect configured for the input element is a gradient appearance. Interface a (end scenario) shown in FIG. 14 of the present application is equivalent to interface a (end scenario) shown in FIG. 13 of the priority claim document (Application No. 202010943693.3). Interface b (transition scenario) shown in FIG. 14 of the present application is equivalent to interface b (shared scenario) shown in FIG. 13 of the priority claim document (Application No. 202010943693.3). Interface c (input scenario) shown in FIG. 14 of the present application is equivalent to interface c (input scenario) shown in FIG. 13 of the priority claim document (Application No. 202010943693.3). The end element of block 1 shown in FIG. 14 of the present application is equivalent to the end element of block 1 shown in FIG. 13 of the priority claim document (Application No. 202010943693.3). The shared element of block 2 shown in FIG. 14 of the present application is equivalent to the shared element of block 2 shown in FIG. 13 of the priority claim document (Application No. 202010943693.3). The input element of block 3 shown in FIG. 14 of the present application is equivalent to the input element of block 3 shown in FIG. 13 of the priority claim document (Application No. 202010943693.3).

[0208] When application A performs interface conversion, in this case, it is assumed that interface a in FIG. 13 is the end scenario of application A, interface b in FIG. 13 is the transition scenario of application A, interface c in FIG. 13 is the input scenario of application A, block 1 is the end element, block 2 is the shared element, and block 3 is the input element.

[0209] In the process of switching from interface a to interface b, block 2 used as a shared element always exists, an amplified dynamic effect is displayed, and block 1 used as an end element fades out.

[0210] Also, in the process of continuing the conversion, interface b is switched to interface c. In the switching process, block 2 used as a shared element always exists, and block 3 used as an input element fades in.

[0211] In this embodiment of the present application, the size and position of the information container may be set.

[0212] For example, as shown in FIG. 15, when the size of the information container for displaying the end scenario is set to the size of the dashed box 1 and the information container is displayed at the left boundary of the screen, the content of the end scenario is only displayed within the dashed box 1 in FIG. 15. When the size of the information container for displaying the transition scenario is set to the size of the dashed box 2 and the information container is displayed in the center of the screen, the content of the shared scenario is only displayed within the dashed box 2 in FIG. 15.

[0213] Composition method 2: Composed in a pre-set template method In an optional method of this embodiment of the present application, a plurality of high-speed configuration templates can be set. Specifically, in the high-speed configuration template, the related configuration parameters of the element are set in advance, and the user only needs to determine the name of the element. Thereby, high-speed configuration is implemented, and the complexity of the configuration is effectively reduced.

[0214] In an optional method of this embodiment of the present application, after the user determines the conversion object, the user can determine the elements that need to be configured by using the template by tapping the screen with a finger.

[0215] Specifically, after the user taps the screen with a finger, the mobile phone determines the name of the element or container displayed at that position based on the tapped screen position, binds the name of the element or container to the high-speed configuration template selected by the user, and as a result, when the element or container executes the interface conversion, the configuration corresponding to the selected high-speed configuration template is executed.

[0216] For example, when the user configures an interface conversion solution for Application A, assume that the current configuration interface is shown in Fig. 16(a), and the customized configuration and high-speed configuration are displayed on the current configuration interface. After the user taps the high-speed configuration with a finger, the current interface is shown in Fig. 16(b), and two high-speed configurations template , namely, the above-mentioned high-speed configuration template 1 and high-speed configuration template 2, are displayed.

[0217] The related configuration in high-speed configuration template 1 is as follows: The end dynamic effect is a translation from left to right, and the dynamic effect duration is 2 seconds. The input dynamic effect is a translation from right to left, and the dynamic effect duration is 2 seconds. The dynamic effect of the shared element or shared container is an explosion, and the dynamic effect duration is 1.5 seconds. The center point of the explosion dynamic effect is the center point of the shared element or shared container, and the explosion area is one-fourth the size of the interface, etc.

[0218] High-speed configuration template The related configuration in 2 is as follows: The end dynamic effect is a gradient, and the dynamic effect duration is 2 seconds. The input dynamic effect is flipping, and the dynamic effect duration is 2 seconds. The dynamic effect of the shared element or shared container is vibration, and the dynamic effect duration is 1.5 seconds. The center point of the vibration dynamic effect is, for example, the center point of the shared element or shared container. In the process of selecting a high-speed configuration template, it is assumed that the user selects high-speed configuration template 1.

[0219] After determining the applicable high-speed configuration template, the user only needs to determine the elements to which the template is applied.

[0220] For example, as shown in Fig. 16(c), the user determines the shared element from the content displayed on the current interface in a finger-tap manner based on the instructions on the screen. It is assumed that the user taps on the ship on the screen with a finger. In this case, the application framework can determine the ship as the shared element.

[0221] Therefore, when application A executes interface conversion, as shown in Figs. 17(a) to 17(h), in this case, it is assumed that interface a is the end scenario of application A and interface b is the input scenario of application A. In the process of ending interface a, interface a is translated from left to right to end, and the dynamic effect duration is 2 seconds. In the process of ending interface b, interface b is translated from right to left for input, and the dynamic effect duration is 2 seconds. The ship used as the shared element always exists, and the explosion dynamic effect is displayed in a size of one-fourth of the screen by using the center point of the ship as the center point of the shared element.

[0222] Furthermore, after a user constructs an interface - to - interface conversion solution for a conversion object by using the application framework provided in this embodiment of the present application, a configuration file of the interface - to - interface conversion solution can be generated. The configuration file can be called when the conversion object subsequently performs an interface - to - interface conversion display.

[0223] It should be noted that in this embodiment of the present application, an alternative way of combining a user - defined method and a preset template method can be used to construct an interface - to - interface conversion solution for a conversion object, etc. This is not limited to this embodiment of the present application.

[0224] Furthermore, in an optional way of this embodiment of the present application, in order to further improve the confidentiality of the interface - to - interface conversion solution executed on a conversion object, the interface - to - interface conversion solution corresponding to the conversion object can be encrypted by using a public key for encryption. In this way, only a device or application that knows the private key for decryption corresponding to the public key for encryption can parse the syntax of the interface - to - interface conversion solution corresponding to the conversion object and obtain the interface - to - interface conversion solution corresponding to the conversion object.

[0225] Phase 2: Syntax Analysis Phase: Phase 2 mainly means that a device configured to parse the syntax of the interface - to - interface conversion solution corresponding to the conversion object parses the interface - to - interface conversion solution obtained by the conversion object in the configuration phase, obtains information such as elements configured for interface - to - interface conversion and attributes of the elements in the interface - to - interface conversion solution, and determines the effect of the interface - to - interface conversion solution on the conversion object.

[0226] For example, the platform-side device parses the interface-to-interface conversion solution corresponding to the conversion object by using the syntax analysis module of the application framework. In another example, the application-side device parses the interface-to-interface conversion solution corresponding to the conversion object by using the processor of the application-side device or a chip having a syntax analysis function.

[0227] For details of the internal logic framework of the syntax analysis phase in this embodiment of the present application, please refer to FIG. 18. The syntax analysis phase shown in FIG. 18 of the present application can be understood as the syntax analysis module shown in FIG. 15 of the priority claim document (Application No. 202010943693.3). That is, FIG. 18 of the present application is equivalent to FIG. 15 of the priority claim document (Application No. 202010943693.3).

[0228] First, in the syntax analysis phase of this embodiment of the present application, a device configured to execute an interface-to-interface conversion solution for a conversion object determines a scenario type configured for interface-to-interface conversion in the interface-to-interface conversion solution and a layout type corresponding to the scenario type by using the interface-to-interface conversion solution corresponding to the conversion object to bind the scenario type to the layout type.

[0229] In this embodiment of the present application, the scenario is bound to the layout, and as a result, the conversion dynamic effect is extended based on the layout type. Therefore, the compatibility is better and the adhesion is higher.

[0230] Furthermore, a device configured to parse the interface-to-interface conversion solution corresponding to the conversion object determines the state of each converted interface based on the interface-to-interface conversion solution.

[0231] A device for parsing an interface - to - interface conversion solution corresponding to a conversion object can, based on the interface - to - interface conversion solution, determine the elements included in the end scenario and the states corresponding to the elements, the elements included in the transition scenario and the states corresponding to the elements, and the elements included in the input scenario and the states corresponding to the elements.

[0232] The state of an element in this embodiment of the present application mainly includes the type of the element, the dynamic effect format of the element, the dynamic effect duration, etc.

[0233] For example, assume that the conversion object is a calendar application. The configuration file obtained by the calendar application in Phase 1 and used for interface conversion is shown in Table 4.

[0234]

Table 4

[0235] A device configured to parse an interface - to - interface conversion solution corresponding to a conversion object can, based on the content of Table 4, determine that the end dynamic effect in the end scenario is a dynamic effect with a displacement of 20 pixels from left to right and a gradient of 2s, the input dynamic effect in the input scenario is a dynamic effect with a displacement of 20 pixels from right to left and a gradient of 2s, and the shared element is the year in the shared scenario. In the interface conversion process, the year element vibrates from left to right with a vibration amplitude of 2 pixels.

[0236] Phase 3: Execution Phase: Phase 3 mainly means that when an interface conversion is performed on a conversion object by a device configured to perform an interface conversion solution between interfaces corresponding to the conversion object, a conversion effect configured in the interface conversion solution is displayed based on the interface conversion solution corresponding to the conversion object.

[0237] For details of the internal logic framework of the execution phase in this embodiment of the present application, refer to FIG. 19. The execution phase shown in FIG. 19 of the present application can be understood as the execution module shown in FIG. 16 of the priority claim document (Application No. 202010943693.3). That is, FIG. 19 of the present application is equivalent to FIG. 16 of the priority claim document (Application No. 202010943693.3).

[0238] For example, in this embodiment of the present application, when the user starts the conversion, the platform-side device starts the conversion in a one-tap manner based on various parameters in the interface conversion solution corresponding to the conversion object obtained through syntax analysis, and displays an effect of performing an interface conversion on the conversion object.

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

[0240] Based on the foregoing descriptions of FIGS. 11 and 12 in the present application and the content of each module, it can be understood that the content shown in FIG. 27 in the priority claim document (Application No. 202010943693.3) can be obtained. The combination of FIGS. 9, 18, and 19 of the present application is equivalent to the content shown in FIG. 32 of the priority claim document (Application No. 202010943693.3).

[0241] Based on the above detailed description of the single-shot framework in the embodiments of the present application, an interface conversion method for an application-side device using the single-shot framework is provided. As shown in FIG. 20, the specific steps are as follows:

[0242] Phase 1: Configuration Phase: S2000: The application-side device determines the interface type based on the interface configuration instruction triggered by the user.

[0243] In this embodiment of the present application, the interface type includes a first interface, at least one transition interface, and a second interface. The transition interface is an intermediate splicing interface from the first interface to the second interface.

[0244] In this embodiment of the present application, it can be understood that the first interface is an end interface, the second interface is an input interface, and the transition interface is a shared interface.

[0245] S2001: The application-side device determines the containers and / or elements included in each interface based on the element configuration instruction triggered by the user.

[0246] In this embodiment of the present application, the containers and / or elements can be set based on different interfaces.

[0247] For example, on the end interface, at least one container and / or element is set as an end element, at least one container and / or element is set as a shared element, on the input interface, at least one container and / or element is set as an input element, and at least one container and / or element is set as a shared element.

[0248] In an optional manner of this embodiment of the present application, the shared element on the end interface is the same as the shared element on the input interface.

[0249] Specifically, the application-side device determines a first element and a second element on a first interface and a second element and a third element on a second interface based on an element configuration instruction triggered by a user, and the transition interface includes the second element.

[0250] In this embodiment of the present application, it can be understood that the first element is an end element, the second element is a shared element, and the third element is an input element. In another optional manner of this embodiment of the present application, the shared element on the end interface is partially similar to the shared element on the input interface.

[0251] Specifically, the application-side device determines a first element and a second element on a first interface and a third element and a fourth element on a second interface based on an element configuration instruction triggered by a user, and the electronic device determines that the second element gradually changes to the third element on the transition interface based on an element configuration instruction triggered by the user, and the second element is partially the same as the third element.

[0252] It can be understood that the second element on the first interface is element 2, the third element on the second interface is element 3, and element 2 is assumed to be partially similar to element 3.

[0253] S2002: The application-side device determines a dynamic effect executed by an interface, a container, and / or an element in the process of switching from the first interface to the second interface based on a dynamic effect configuration instruction triggered by a user.

[0254] Specifically, in this embodiment of the present application, different dynamic effects may be specified for different interfaces.

[0255] Furthermore, different dynamic effects can be specified for the containers and / or elements on the interface.

[0256] In this embodiment of the present application, various dynamic effect functions are provided for integration and use by the application. The dynamic effects in this embodiment of the present application may be used independently or in combination, and the present application may randomly combine the dynamic effects.

[0257] In this embodiment of the present application, the application-side device can obtain an interface conversion solution between interfaces corresponding to the conversion object by performing the above-described configuration operations. For specific implementation forms, refer to the description of the configuration module on the AAR side.

[0258] S2003: After completing the configuration, the application-side device can directly call the interface conversion solution corresponding to the conversion object to start the effect of the interface conversion.

[0259] Furthermore, in this embodiment of the present application, after the application-side device configures the interface conversion solution corresponding to the conversion object, the application-side device can integrate the interface conversion solution. Specifically, the application-side device encapsulates and stores the interface conversion solution corresponding to the conversion object, and as a result, when the interface conversion is executed again for the conversion object, the interface conversion effect of the conversion object is directly triggered to start.

[0260] It should be noted that the foregoing configuration steps do not constitute a limitation to this embodiment of the present application. When the interface conversion method in this embodiment of the present application is used to constitute an interface conversion solution, the steps to be executed can be flexibly adjusted based on the actual situation. For example, when the interface conversion solution is configured in this embodiment of the present application, the scenario type corresponding to the conversion interface can be further considered. In this way, a more appropriate, standard, and effective interface conversion solution can be designed based on the scenario type. In this embodiment of the present application, the scenario type of the conversion can be determined as one of Activity, ViewGroup, or Fragment. It should be noted that the conversion type in this embodiment of the present application is not limited to the foregoing three types and can be further extended.

[0261] Phase 2 : Execution phase: S2004: After detecting the first operation performed by the user on the electronic device, the application-side device displays the first interface, and the first interface includes a first element and a second element.

[0262] S2005: The application-side device displays at least one transition interface, and then, after detecting the second operation performed by the user on the first interface, displays the second interface.

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

[0264] In another alternative embodiment of this application, the second interface includes a third element and a fourth element, and in the process of switching from the first interface to the second interface by using at least one transition interface, the presentation form of the second element on the transition interface gradually changes to the presentation form of the third element. The second element is partially the same as the third element.

[0265] According to the above method, in the process of switching from the first interface to the second interface, the electronic device performs splicing by using at least one transition interface, and elements that are the same as or similar to the shared elements on the first interface and the second interface exist on the transition interface. Therefore, in the process of switching between the first interface and the second interface, the change is natural, coherent, and the visual experience effect on the user is relatively good.

[0266] The solution for performing interface conversion based on single-shot in this embodiment of this application is not limited by the conversion type or usage scenario. For example, the solution may be used within an application, between applications, or between a system and an application. This solution is also applicable to different screen scenarios, such as full-screen, split-screen, and projection scenarios.

[0267] Furthermore, in this embodiment of this application, there are multiple conversion effects for single-shot. Based on the display state of the shared elements, the conversion effects can be specifically classified into the following multiple application examples.

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

[0269] Based on different conversion types such as Activity conversion type, ViewGroup conversion type, and Fragment conversion type, in the following, by using examples, solutions for performing interface - to - interface conversion based on the single - shot effect provided in this embodiment of the present application will be separately described.

[0270] Conversion type 1: Fragment conversion type In this embodiment of the present application, the interface - to - interface conversion solution based on the Fragment conversion type can be further classified into multiple cases such as inter - application conversion, intra - application conversion, and conversion from desktop to application. Note that it is not limited to the following content.

[0271] Case 1: Intra - application conversion: As shown in FIGS. 21(a) - 21(c), in this embodiment of the present application, an example of the effect of intra - application conversion based on at least two Fragments is provided by using the call application as an example.

[0272] In this embodiment of the present application, corresponding ids can be set for the answer key and hang - up key in the response button, and the usage status of the call application is determined based on the answer or hang - up command triggered by the user. For example, as shown in Table 5, the configuration file applied in this embodiment of the present application is as follows:

[0273]

Table 5

[0274] When interface conversion is performed, it is assumed that the end interface and the input interface of the call application are as shown in FIGS. 21(a) to 21(c). From the end interface of the call application, it can be found that the end interface includes a response key icon and a hang-up key icon.

[0275] When the call application starts the interface conversion solution, in the process of switching from the end interface to the input interface, if the user triggers a response command, the response key is a shared element.

[0276] From the content of Table 5, when the answer key icon is a shared element, in the conversion process, it can be found that a 270-degree counterclockwise rotation, a rightward movement, and a color conversion are performed. In this case, the end element is the hang-up key icon, and when the interface conversion is performed, a fade-out dynamic effect is executed. The input elements are the hands-free icon and the keyboard icon, and when the interface conversion is performed, a fade-in dynamic effect is executed.

[0277] In this embodiment of the present application, the response key is used as a shared element, and after the dynamic effect conversion is executed, the presentation form of the response key is the same as that of the hang-up key used as the end element, but it should be noted that the icon of the response key is different from the icon of the hang-up key used as the end element on the switching interface.

[0278] Therefore, a rotation animation effect is presented in the interface conversion process.

[0279] Case 2: Conversion between applications: In the following, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where a user needs to switch to a message application when using a call application.

[0280] When a user configures an interface conversion solution between a call application and a message application, it is assumed that a response button in the call application is used as a shared element and continuously exists within the conversion process.

[0281] For example, as shown in FIGS. 22(a) and 22(b), when a user taps a message button on the call interface, the call application and the message application are triggered to perform an interface conversion. After the call application jumps to the message application, the response button of the call application continues to exist. In addition, the answer button performs an amplification effect, a bubble window appears, and an SMS message editing interface for editing an SMS message is displayed. After the SMS message is edited, the response button is tapped, and the response button performs a rotation and shrinking dynamic effect, and the call interface is displayed.

[0282] Case 3: Conversion from Desktop to Application: In the following, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where a user needs to switch to a call application from an application desktop.

[0283] When a user configures an interface conversion solution between an application desktop and a call application, it is assumed that a response button in the call application is used as a shared element and continuously exists within the conversion process.

[0284] For example, as shown in FIGS. 23(a) to 23(c), after the user taps the call application icon on the application desktop, the interface conversion between the application desktop and the call application is triggered. In the process of the application desktop jumping to the call application, a response button used as a shared element always exists, and a smooth downward movement dynamic effect is executed on the response button. Next, the call application interface is displayed.

[0285] Conversion Type 2: Activity Conversion Type In this embodiment of the present application, the interface conversion solution based on the Activity conversion type can be further classified into multiple cases such as inter-application conversion, intra-application conversion, and conversion from the desktop to the application. Note that it is not limited to the following content.

[0286] Case 1: Intra-application conversion: As shown in FIGS. 24(a) to 24(d), an embodiment of the present application provides a first example of the effect of interface conversion based on at least two Activities by using, as an example, a book application in the application market. For example, as shown in Table 6, the configuration file of the book application in the application market in this embodiment of the present application is as follows:

[0287]

Table 6

[0288] It is assumed that the end interface and the input interface of the book application when interface conversion is performed are shown in FIGS. 24(a) to 24(d). It can be found from the end interface of the book application that the end interface includes a title bar, a classification icon, and at least one book cover.

[0289] From the content of Table 6, it can be found that the book cover selected by the user is a shared element, and the shared element continuously exists during interface conversion. The end elements are the title bar, the classification icon, and another book cover not selected by the user. During interface conversion, a slide-down dynamic effect is executed. From the input interface of the book application, it can be found that the content introduction part, the evaluation bar, the function icon, etc. on the input interface are all input elements. During interface conversion, a slide-up dynamic effect is executed.

[0290] Therefore, when the book application starts the interface conversion solution, as shown in FIGS. 24(a) to 24(d), it is assumed that the book selected by the user is Book 4. Therefore, in the process of switching from the end interface to the input interface, the end interface is ended by sliding down, the icon of Book 4 always exists, and the input interface is input by sliding up.

[0291] As shown in FIGS. 25(a) to 25(d), an embodiment of the present application provides a second example of the effect of interface conversion based on at least two Activities by using, as an example, a gallery application in an application market. For example, as shown in Table 7, the configuration file of the gallery application in this embodiment of the present application is as follows:

[0292]

Table 7

[0293] When the interface conversion is executed, it is assumed that the end interface and the input interface of the gallery application are shown in FIGS. 25(a) to 25(d). It can be found from the end interface of the gallery application that the end interface includes a search bar, function icons, at least one picture, etc.

[0294] From the content of Table 7, it can be found that the picture selected by the user is a shared element and continuously exists during the interface conversion. The end elements are a search bar, function icons, another picture not selected by the user, etc. During the interface conversion, a left movement dynamic effect is executed. From the input interface of the gallery application, it can be found that the function icons on the input interface, another picture not selected by the user, etc. are all input elements. During the interface conversion, a central amplification dynamic effect is executed.

[0295] Therefore, when the book application starts the single-shot interface conversion, as shown in FIGS. 25(a) to 25(d), it is assumed that the photo selected by the user is a photo of a flower. Therefore, in the process of switching from the end interface to the input interface, the end interface is ended through left movement, the icon of the flower picture always exists, and the input interface is input.

[0296] As shown in FIGS. 26(a) to 26(g), one embodiment of the present application provides three examples of the effects of interface conversion based on at least two Activities by using a music application as an example. For example, as shown in Table 8, the configuration file of the music application in this embodiment of the present application is as follows:

[0297]

Table 8

[0298] When the conversion between interfaces is executed, it is assumed that the end interface and the input interface of the music application are shown in FIGS. 26(a) to 26(g). From the scenarios shown in FIGS. 26(a) to 26(g), it can be found that the end scenario may include a classification icon, at least one cover, function buttons, etc.

[0299] From the content of Table 8, it can be found that the cover picture selected by the user is a shared element and continuously exists during the interface conversion, and the end element executes a scaling dynamic effect during the interface conversion. From the input scenarios of the music application, it can be found that the song list, function icons, etc. on the input interface are all input elements. During the interface conversion, a slide-up dynamic effect is executed.

[0300] Therefore, when the book application starts the single-shot interface conversion, as shown in FIGS. 26(a) to 26(g), it is assumed that the cover selected by the user is the main cover. Therefore, in the process of switching from the end interface to the input interface, the end interface is ended through scaling, the main cover always exists, and the input interface is input through a slide-up.

[0301] In order to better implement the effect of interface conversion, in this embodiment, the startup interface of the application can be directly used as an end scenario. For example, as shown in FIGS. 27(a) to 27(f), the startup interface of the music application is considered as an end scenario, and the cover picture on the startup interface is used as a shared element. When the user continues to operate the application and enters a specific operation interface of the music application, the main cover always exists.

[0302] Case 2: Conversion between applications: As shown in FIGS. 28(a) to 28(f), hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where a user needs to switch to the gallery application when using the camera application.

[0303] When the user configures an interface conversion solution between the camera application and the gallery application, it is assumed that the thumbnail button in the camera application is used as a shared element and continuously exists within the conversion process.

[0304] For example, as shown in FIGS. 28(a) to 28(f), when the user taps the thumbnail button on the camera interface, the interface conversion between the camera application and the gallery application is triggered. After the camera application jumps to the gallery application, the taken photo is displayed. In this case, the thumbnail button of the camera application continuously exists, the shooting interface disappears, and the photos in the gallery appear. After the thumbnail button on the gallery interface is tapped, the thumbnail button continues to exist.

[0305] Case 3: Conversion from desktop to application: In the following, by using an example where a user needs to switch from an application desktop to a music application, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described.

[0306] When the user configures an interface conversion solution between the application desktop and the music application, it is assumed that the memo element in the music application icon is used as a shared element and the memo element continuously exists within the conversion process.

[0307] For example, as shown in FIGS. 29(a) to 29(f), after the user taps the music application icon on the application desktop, the interface conversion between the application desktop and the music application is triggered. In the process of the application desktop jumping to the music application, the memo used as the shared element always exists, a smooth downward movement dynamic effect is executed on the memo, and then the music application interface is displayed.

[0308] Conversion Type 3: ViewGroup Conversion Type In this embodiment of the present application, the interface conversion solution based on the ViewGroup conversion type can be further classified into multiple cases such as inter-application conversion, intra-application conversion, and conversion from the desktop to an application. Note that it is not limited to the following content.

[0309] Case 1: Intra-application conversion: As shown in FIGS. 30(a) to 30(f), an embodiment of the present application provides a first example of the effect of interface conversion based on at least two ViewGroups by using a calendar application as an example. For example, as shown in Table 9, the configuration file of the calendar application in this embodiment of the present application is as follows:

[0310]

Table 9

[0311] When the conversion between interfaces is executed, calendar Assume that the end interface and the input interface of the application are shown in FIGS. 30(a) to 30(f). Based on the content of Table 9, the end dynamic effect on the end interface is a dynamic effect with a displacement of 20 pixels from left to right and a gradient of 2s, and the input dynamic effect on the input interface is a dynamic effect with a displacement of 20 pixels from right to left and a gradient of 2s. In the interface conversion process, it can be determined that the shared element presents an effect of vibrating from left to right with a vibration amplitude of 2 pixels.

[0312] Therefore, when the calendar application starts the interface conversion, as shown in FIGS. 30(a) to 30(f), assume that the user taps the August icon on interface a of the calendar application, and the August icon is determined as the shared element. During the interface conversion, the August icon always exists.

[0313] Case 2: Conversion between applications: As shown in FIGS. 31(a) to 31(g), hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where the user needs to switch to the camera application when using the shopping application.

[0314] When a user configures an interface conversion solution between a shopping application and a camera application, it is assumed that the shooting button in the shopping application is used as a shared element and continuously exists within the conversion process.

[0315] For example, as shown in FIGS. 31(a) to 31(g), when the user taps the shooting button on the shopping interface, the interface conversion between the shopping application and the camera application is triggered. In the process where the shopping application jumps to the camera application, the shooting button of the camera application continuously exists, the shopping interface fades out, and the camera interface fades in.

[0316] Case 3: Conversion from Desktop to Application: In the following, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where the user needs to switch from the application desktop to the calendar application.

[0317] When a user configures an interface conversion solution between the application desktop and the calendar application, it is assumed that the date element within the calendar application icon is used as a shared element and continuously exists within the conversion process.

[0318] For example, as shown in FIGS. 32(a) to 32(f), after the user taps the calendar application icon on the application desktop, the interface conversion between the application desktop and the calendar application is triggered. In the process where the application desktop jumps to the calendar application, the date used as the shared element always exists.

[0319] Application Example 2: When Element 1 on the First Interface is Switched to the Second Interface by Using at Least One Transition Interface, Element 1 Gradually Changes to Element 2, and the Similarity between Element 2 and Element 1 is Higher than the Similarity Threshold.

[0320] Based on different conversion types such as Activity conversion type, ViewGroup conversion type, and Fragment conversion type, hereinafter, by using examples, solutions for performing interface - to - interface conversion based on the single - shot effect provided in this embodiment of the present application will be separately described.

[0321] Conversion Type 1: Fragment Conversion Type In this embodiment of the present application, the interface - to - interface conversion solution based on the Fragment conversion type can be further classified into multiple cases such as inter - application conversion, intra - application conversion, and conversion from the desktop to the application. Note that it is not limited to the following content.

[0322] Case 1: Intra - application conversion: As shown in FIGS. 33(a) - 33(c), an embodiment of the present application provides an example of the effect of intra - application conversion based on at least two Fragments by using a call application as an example.

[0323] In this embodiment of the present application, corresponding ids can be set for the response key and the hang - up key in the response button, and the usage status of the call application is determined based on the response or hang - up command triggered by the user.

[0324] For example, as shown in FIGS. 33(a) - 33(c), when the call application starts interface - to - interface conversion, in the process of switching from the first interface to the second interface, if the user triggers a response command, the response button is a shared element.

[0325] In other words, the transition interface in the process of switching from the first interface to the second interface includes shared elements. The presentation form of the shared elements on the first interface is Element 1, the presentation form of the shared elements on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0326] Furthermore, in the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 33(a) to 33(c), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content is that the call is gradually picked up. This enhances the interestingness and provides the user with a clearer interface switching experience.

[0327] In addition, the end element on the first interface fades out. For example, the end element is the hang-up key icon. During the interface switching, a fade-out dynamic effect is executed. The input elements on the second interface fade in. For example, the input elements are the hands-free icon and the keyboard icon. During the interface switching, a fade-in dynamic effect is executed.

[0328] Case 2: Conversion between applications: Hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where a user needs to switch to a message application when using a call application.

[0329] When the user configures an interface conversion solution between a call application and a message application, it is assumed that the response button in the call application is used as a shared element and continuously exists in the conversion process.

[0330] For example, as shown in FIGS. 34(a) to 34(c), when the user taps a message button on the call interface, the call application and the message application are triggered to perform interface conversion. In other words, the call interface can be understood as the first interface, and the message application interface can be understood as the second interface.

[0331] The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0332] Furthermore, during the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 34(a) to 34(c), in the process where Element 1 gradually changes to Element 2, it can be found that the presented content is that the call is gradually picked up. This enhances the interestingness and brings a clearer interface switching experience to the user.

[0333] In addition, the end element on the first interface fades out. For example, the end element is the hang-up key icon. During the interface switch, a fade-out dynamic effect is executed. The input element on the second interface fades in. For example, the input element is that an SMS message editing interface represented by using a bubble window fades in, and the interface is used to edit SMS messages.

[0334] Case 3: Conversion from Desktop to Application: The following uses an example where a user needs to switch from an application desktop to a call application to describe a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application.

[0335] When the user configures an interface conversion solution between the application desktop and the call application, it is assumed that the response button in the call application is used as a shared element and continuously exists within the conversion process.

[0336] For example, as shown in FIGS. 35(a) to 35(c), after the user taps the call application icon on the application desktop, the interface conversion between the application desktop and the call application is triggered. In other words, the application desktop interface may be understood as the first interface, and the call application interface may be understood as the second interface. The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0337] Furthermore, during the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 35(a) to 35(c), it can be found that in the process where Element 1 gradually changes to Element 2, the presented content is that the call is gradually picked up and a smooth downward movement dynamic effect is executed. This enhances the interestingness and brings a clearer interface switching experience to the user.

[0338] In addition, the end element on the first interface fades out. For example, the end element is an icon of another application. During the interface switch, a fade-out dynamic effect is executed. The input element on the second interface fades in to obtain the call application interface.

[0339] Conversion type 2: Activity conversion type In this embodiment of the present application, the interface conversion solution based on the Activity conversion type can be further classified into multiple cases such as inter-application conversion, intra-application conversion, and conversion from the desktop to an application. Note that it is not limited to the following content.

[0340] Case 1: Intra-application conversion: As shown in FIGS. 36(a) to 36(g), an embodiment of the present application provides an example of the effect of interface conversion based on at least two Activities by using, as an example, a book application in an application market.

[0341] For example, as shown in FIGS. 36(a) to 36(g), when a music application starts a single-shot conversion, in the process of switching from the first interface to the second interface, the cover picture selected by the user is used as a shared element. For example, the cover selected by the user is the main cover. In other words, the transition interface in the process of switching from the first interface to the second interface includes a shared element.

[0342] The presentation form of the shared element on the first interface is element 1, the presentation form of the shared element on the second interface is element 2, and the similarity between element 1 and element 2 is higher than the similarity threshold.

[0343] Furthermore, during the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 36(a) to 36(g), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content is that the singer gradually raises the microphone in his hand. This enhances the interestingness and brings a clearer interface switching experience to the user.

[0344] In addition, the end element on the first interface executes a scaling dynamic effect to end. For example, the end element is a classification icon, at least one cover, a function button, etc. During the interface switching, the scaling dynamic effect is executed for ending. The input element on the second interface appears by executing a slide-up dynamic effect. For example, the input element is a song list and a function icon, and fades in through the slide-up during the interface switching.

[0345] Case 2: Conversion between applications: As shown in FIGS. 37(a) to 37(f), hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where a user needs to switch to the gallery application when using the camera application.

[0346] When the user configures an interface conversion solution between the camera application and the gallery application, it is assumed that the thumbnail button in the camera application is used as a shared element and continuously exists within the conversion process.

[0347] For example, as shown in FIGS. 37(a) to 37(f), after the user taps a thumbnail icon in the camera application, an interface conversion between the camera application and the gallery application is triggered. In other words, the camera application can be understood as the first interface, and the gallery application interface can be understood as the second interface. The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0348] Furthermore, in the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 37(a) to 37(f), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content is that the picture is gradually displayed from partial to global. This enhances the interestingness and brings a more vivid interface switching experience to the user.

[0349] In addition, the end element on the first interface fades out, and the input element on the second interface fades in. For example, after the camera application jumps to the gallery application, the taken photo is displayed. In this case, the thumbnail button of the camera application continuously exists, the shooting interface disappears, and the photos in the gallery appear.

[0350] Case 3: Conversion from desktop to application: Hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where the user needs to switch from the application desktop to the music application.

[0351] When a user configures an interface conversion solution between an application desktop and a music application, it is assumed that a memo element within the music application icon is used as a shared element and continuously exists within the conversion process.

[0352] For example, as shown in FIGS. 38(a) to 38(f), after the user taps on a music application icon on the application desktop, an interface conversion between the application desktop and the music application is triggered. In other words, the application desktop interface may be understood as a first interface, and the music application interface may be understood as a second interface. The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than a similarity threshold.

[0353] Furthermore, during the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 38(a) to 38(f), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content gradually displays five line spectra on a music symbol and executes a smooth downward movement dynamic effect. This enhances the interestingness and provides the user with a more distinct interface switching experience.

[0354] In addition, the end element on the first interface fades out. For example, the end element is an icon of another application. During the interface switching, a fade-out dynamic effect is executed. The input element on the second interface fades in to obtain the music application interface.

[0355] Conversion Type 3: ViewGroup Conversion Type In this embodiment of the present application, the interface conversion solution based on the ViewGroup conversion type can be further classified into multiple cases such as inter-application conversion, intra-application conversion, and conversion from the desktop to an application. It should be noted that it is not limited to the following content.

[0356] Case 1: Intra-application conversion: As shown in FIGS. 39(a) to 39(f), an embodiment of the present application provides a first example of the effect of interface conversion based on at least two ViewGroups by using a calendar application as an example.

[0357] For example, as shown in FIGS. 39(a) to 39(f), when the calendar application starts interface conversion, in the process of switching from the first interface to the second interface, the icon of the month selected by the user is used as a shared element. For example, the month selected by the user is August. In other words, the transition interface in the process of switching from the first interface to the second interface includes a shared element.

[0358] The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0359] Furthermore, in the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 39(a) to 39(f), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content is that the circular shadow of the August icon fades out. This enhances the interestingness and brings a clearer interface switching experience to the user.

[0360] In addition, the end element on the first interface executes an amplification dynamic effect for the end. For example, the end element is another month. During interface switching, a scaling dynamic effect is executed for the end. The input element on the second interface is amplified and displayed. For example, when the input element is the calendar month corresponding to August, the interface is enlarged and gradually displayed during interface switching.

[0361] Case 2: Conversion between applications: As shown in FIGS. 40(a) to 40(g), hereinafter, a method for performing interface conversion based on a single-shot effect provided in an embodiment of the present application will be described by using an example in which a user needs to switch to a camera application when using a shopping application.

[0362] When the user configures an interface conversion solution between the shopping application and the camera application, it is assumed that the shooting button in the shopping application is used as a shared element and continuously exists within the conversion process.

[0363] For example, as shown in FIGS. 40(a) to 40(g), after the user taps the shooting icon in the shopping application, an interface conversion between the shopping application and the camera application is triggered. In other words, the shopping application may be understood as the first interface, and the camera application interface may be understood as the second interface. The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0364] Furthermore, during the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 40(a) to 40(g), it can be found that in the process of Element 1 gradually changing to Element 2, the presented content is that the camera lens gradually extends. This enhances the interestingness and provides the user with a clearer interface switching experience.

[0365] In the process of the shopping application jumping to the camera application, the shooting button of the camera application continuously exists, the shopping interface fades out, and the camera interface fades in.

[0366] Case 3: Conversion from desktop to application: Hereinafter, a method for performing interface conversion based on the single-shot effect provided in this embodiment of the present application will be described by using an example where the user needs to switch from the application desktop to the calendar application.

[0367] When the user configures an interface conversion solution between the application desktop and the calendar application, it is assumed that the date element in the calendar application icon is used as a shared element and continuously exists within the conversion process.

[0368] For example, as shown in FIGS. 41(a) to 41(f), after the user taps the calendar application icon on the application desktop, the interface conversion between the application desktop and the calendar application is triggered. In other words, the application desktop interface may be understood as the first interface, and the calendar application interface may be understood as the second interface. The presentation form of the shared element on the first interface is Element 1, the presentation form of the shared element on the second interface is Element 2, and the similarity between Element 1 and Element 2 is higher than the similarity threshold.

[0369] Furthermore, in the process of switching from the first interface to the second interface, Element 1 gradually changes to the presentation form of Element 2. From FIGS. 41(a) to 41(f), it can be found that in the process of Element 1 gradually changing to Element 2, the content presented is that the date element gradually displays a circular shadow. This enhances the interestingness and brings a clearer interface switching experience to the user.

[0370] In the process of the application desktop jumping to the calendar application, the date used as the shared element always exists.

[0371] In addition, the single-shot conversion method described in the embodiments of the present application can be further applied to application operations such as split-screen mode and multi-screen collaboration. This is not particularly limited to the following description.

[0372] Mode 1: Split-screen mode In daily life, when using a smart device, such as a mobile phone, the user may need to perform a split-screen operation on the mobile phone for reasons such as operational convenience. In this embodiment of the present application, in a split-screen operation scenario, the applications displayed on each screen still execute the interface conversion solution provided in the embodiment of the present application, which can reduce the user's visual jump width, enhance the interestingness of the display, and improve the user experience.

[0373] For example, as shown in FIG. 42, it is assumed that the display interface of the mobile phone is divided into two parts, namely, the upper part and the lower part. The upper interface displays a gallery application, and the lower interface displays a music application. In this case, when the user operates the gallery application on split-screen interface 1, the gallery application performs corresponding conversions based on a pre-set interface conversion solution. When the user operates the music application on split-screen interface 2, the music application performs corresponding conversions based on a pre-set interface conversion solution.

[0374] In another example, as shown in FIG. 43, it is assumed that the display interface of the mobile phone is divided into an upper layer and a lower layer, and the display interface of an application is suspended on top of the interface of another application. The upper layer interface displays a gallery application, and the lower layer interface displays a music application. In this case, when the user operates the gallery application on split-screen interface 1, the gallery application performs corresponding conversions based on a pre-set interface conversion solution. When the user operates the music application on split-screen interface 2, the music application performs corresponding conversions based on a pre-set interface conversion solution.

[0375] Preferably, the paused application interface may be used as a shared element of the lowest layer application interface, and when the lowest layer application interface is converted, the paused application interface always exists.

[0376] In this embodiment of the present application, in the split screen mode, the interface conversion may be performed simultaneously on a plurality of screens based on a corresponding interface conversion solution between interfaces, and it should be noted that it is not limited by the conversion type or the usage scenario. For example, the interface conversion may be performed based on different conversion types such as Activity conversion type, ViewGroup conversion type, Fragment conversion type, etc., and may be performed within an application, between applications, or between the system and an application. For details, refer to the descriptions of FIGS. 20 to 41(f) in the embodiments of the present application.

[0377] Mode 2: Multi-screen collaboration mode When the user sometimes performs an operation on an application, it may be necessary to perform a screen switch. For example, when the user performs an operation on a gallery application by using a mobile phone to facilitate browsing, the mobile phone may be connected to the PC end, multi-screen collaboration is performed, and the application interface in the mobile phone is displayed on the PC end.

[0378] In an optional manner of this embodiment of the present application, when the user performs a multi-screen collaboration operation, as shown in FIGS. 44(a) and 44(b), the content of the gallery application on the display interface of the mobile phone is switched to the PC side, and the entire PC side displays the content of the gallery application. In other words, the operation of the mobile phone is changed to the operation of the PC side, and the display interface of the mobile phone is the same as the display interface of the PC.

[0379] In another alternative manner of this embodiment of the present application, when the user performs a multi-screen collaboration operation, only the input content of the gallery application on the display interface of the mobile phone is switched to the PC side.

[0380] For example, as shown in FIGS. 45(a) and 45(b), the converted content and the sharing elements are displayed on the PC side, and the mobile phone side still retains the display interface of the end interface.

[0381] It should be noted that in the content shown in FIGS. 45(a) and 45(b), the sharing elements may also continue to be displayed on the display interface of the mobile phone terminal.

[0382] For example, as shown in FIGS. 45(a) and 45(b), on the PC side, only the converted input interface is displayed, and the sharing elements are not displayed. On the mobile phone side, the sharing elements and the end interface are displayed. In other words, in this case, the PC side is only used to expand and display the input interface. As a result, the user can view the input interface more clearly and intuitively by using the PC side. The user can continue to control the picture switching on the PC side by performing operations on the mobile phone.

[0383] In this embodiment of the present application, in the multi-screen collaboration mode, it should be noted that the interface conversion may be performed simultaneously on multiple screens based on the corresponding single-shot effect, and is not limited by the conversion type or the usage scenario. For example, the interface conversion may be performed based on different conversion types such as Activity conversion type, ViewGroup conversion type, Fragment conversion type, etc., and may be performed within an application, between applications, or between the system and an application. For details, refer to FIGS. 20 to in the embodiments of the present application.Figure 4 1 (f) Please refer to the description of

[0384] Based on the description of the implementation form, those skilled in the art can clearly understand that, for the purpose of a convenient and concise description, the division into the foregoing functional modules is merely used as an example for description. During the application of the actual form, the functions can be assigned to different functional modules for implementation based on requirements. In other words, the internal structure of the device is divided into different functional modules to implement all or part of the functions described above. For the specific operation processes of the foregoing system, device, and unit, reference may be made to the corresponding processes in the embodiments of the foregoing method, and the details will not be described again here.

[0385] The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may physically exist independently, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0386] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such understanding, essentially the technical solution of the embodiments of the present application, or the part contributing to the prior art, or all or part of the technical solution may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for instructing a computer device or processor (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. The storage medium includes any medium capable of storing program codes, such as flash memory, removable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0387] The above description is merely a specific implementation form of the embodiments of the present application and is not intended to limit the protection scope of the embodiments of the present application. Any modification or substitution within the technical scope disclosed in the embodiments of the present application shall fall within the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Description of Reference Numerals

[0388] 1 Antenna 2 Antenna 1100 Application - side Device 1100 Mobile Phone 1200 Platform - side Device 1210 Processor 1220 Memory 1230 Transceiver 1240 Bus 100 Mobile Phone 110 Processor 121 Internal Memory 130 USB Interface 140 Charge Management Module 141 Charge Management Module 142 Battery 150 Mobile Communication Module 160 Wireless Communication Module 193 Camera 194 Display 1110 Processor 1120 External Memory Interface 1121 Internal Memory 1130 USB Interface 1140 Charge Management Module 1141 Power Management Module 1142 Battery 1150 Mobile Communication Module 1160 Wireless Communication Module 1170 Audio Module 1170A Speaker 1170B Receiver 1170C Microphone 1170D Headset Jack 1180 Sensor Module 1180A Pressure Sensor 1180B Gyro Sensor 1180C Barometric Pressure Sensor 1180D Magnetic Sensor 1180E Acceleration Sensor 1180F Distance Sensor 1180G Proximity Light Sensor 1180H Fingerprint Sensor 1180J Temperature Sensor 1180K Touch Sensor 1180L Ambient Light Sensor 1180M Bone Conduction Sensor 1190 Button 1191 Motor 1192 Indicator 1193 Camera 1194 Display 1195 SIM Card Interface

Claims

1. A method for converting between interfaces, applicable to an electronic device, comprising: after detecting, by the electronic device, a first operation performed by a user on the electronic device, displaying a first interface, wherein the first interface includes a first element and a second element; after detecting, by the electronic device, a second operation performed by the user on the first interface, displaying at least one transition interface and then displaying a second interface, wherein the first element on the first interface of the electronic device fades out and a third element on the second interface fades in; including: the second interface includes the second element and the third element, the transition interface is an intermediate interface representing the transition from the first interface to the second interface, and the transition interface includes the second element; the second element does not include elements within a status bar on the first interface, the at least one transition interface, or the second interface.

2. The step of, after detecting, by the electronic device, a second operation performed by the user on the first interface, displaying at least one transition interface and then displaying a second interface, includes enabling the second element to continuously exist on the first interface, the at least one transition interface, and the second interface. The method according to claim 1.

3. further including the step of performing a dynamic effect corresponding to the interface and / or the element in the process of switching from the first interface to the second interface based on a conversion dynamic effect configured for each interface or based on a conversion dynamic effect configured for an element on the interface. The method according to claim 1 or 2.

4. the first interface and the second interface are different display interfaces of a first application, or the first interface is the home screen of the electronic device, an interface adjacent to the home screen, or the leftmost interface, and the second interface is a display interface of a 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 The method according to any one of claims 1 to 3, further comprising.

5. An interface conversion method applied to an electronic device, comprising: displaying a first interface by the electronic device after detecting a first operation performed by a user on the electronic device, the first interface including a first element and a second element; displaying at least one transition interface by the electronic device after detecting a second operation performed by the user on the first interface, and then displaying a second interface, wherein the first element on the first interface of the electronic device fades out and a fourth element on the second interface fades in; including the second interface includes a third element and the fourth element, and the transition interface is an intermediate interface representing a transition from the first interface to the second interface; in the process of switching from the first interface to the second interface by using the at least one transition interface, a presentation form of the second element on the transition interface gradually changes to a presentation form of the third element; the second element is partially the same as the third element.

6. the step of displaying at least one transition interface by the electronic device after detecting a second operation performed by the user on the first interface, and then displaying a second interface is Enabling the second element on the transition interface to gradually change to the third element The method according to claim 5, comprising: **Claim 7** Executing a dynamic effect corresponding to the interface and / or the element in a process of switching from the first interface to the second interface by the electronic device based on a conversion dynamic effect configured for each interface or based on a conversion dynamic effect configured for an element on the interface The method according to claim 5 or 6, further comprising: **Claim 8** The first interface and the second interface are different display interfaces of a first application, or The first interface is the home screen of the electronic device, an interface adjacent to the home screen, or the leftmost interface, and the second interface is a display interface of a 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 The method according to any one of claims 5 to 7, further comprising: **Claim 9** An electronic device, comprising: A display, one or more processors, and one or more memories, The one or more memories store one or more computer programs, the one or more computer programs include instructions, and when the instructions are executed by the one or more processors, the electronic device can execute the method according to any one of claims 1 to 4 or the method according to any one of claims 5 to 8. An electronic device **Claim 10** A computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed on an electronic device, the electronic device can execute the method according to any one of claims 1 to 4 or the method according to any one of claims 5 to 8. A computer-readable storage medium **Claim 11** A graphical user interface system on an electronic device, wherein the electronic device comprises a display, one or more memories, and one or more processors, the one or more processors being configured to execute one or more computer programs stored in the one or more memories, the graphical user interface system comprising a graphical user interface that is displayed when the electronic device executes the method according to any one of claims 1 to 8.

Images