Method, device, and system for conversion between interfaces

Abstract

To provide a method, device, and system for conversion between interfaces.SOLUTION: The present method includes an electronic device that displays 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 the second element and a third element. The transition interface includes the second element. The second element does not include an element in a status bar on the first interface, the transition interface, or the second interface. According to this method, when conversion is performed between application interfaces, shared elements continuously exist or continuously change, resulting in an uninterrupted user experience.SELECTED DRAWING: Figure 20

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202010943693.3, entitled "METHOD AND DEVICE FOR CONVERSION BETWEEN APPLICATION INTERFACES," filed with the State Intellectual Property Office of the People's Republic of China on September 9, 2020, which is incorporated herein by reference in its entirety, and to Chinese Patent Application No. 202110482721.0, entitled "INTER-INTERFACE CONVERSION METHOD, DEVICE, AND SYSTEM," filed with the State Intellectual Property Office of the People's Republic of China on April 30, 2021, which is incorporated herein by reference in its entirety.

[0002] The present application relates to the field of terminal technology, and in particular to an interface conversion method, device, and system. [Background technology]

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

[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 poor coherence, and a relatively poor user experience. Summary of the Invention [Means for solving the problem]

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

[0006] According to a first aspect, there is provided an interface conversion method, the method comprising: The electronic device displays a first interface after detecting a first operation performed by a user on the electronic device, the first interface including 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 including a second element and a third element, the transition interface including the second element, and the second element does not include an element in a status bar on the first interface, the transition interface, or the second interface.

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

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

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

[0010] In possible implementations, the first interface and the second interface are different display interfaces of the first application, or the first interface is a home screen, an interface adjacent to the home screen, or a left-most interface of the electronic device, and the second interface is a display interface of the first application, or the first interface is a display interface of the first application and the second interface is a display interface of the second application.

[0011] According to a second aspect, there is provided an interface conversion method, the method comprising: The electronic device determines an interface type based on an interface configuration command triggered by a user, the interface type including a first interface, at least one transition interface, and a second interface, the transition interface being 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, and determines a second element and a third element on the second interface, and the transition interface includes the second element.

[0012] Based on the above method, in the transformation 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 and coherent, and the visual experience effect for the user is relatively good. In addition, the application can configure various transformation types and element types and animation effects during the transformation based on its own requirements to achieve a more flexible and smooth dynamic effect experience. The overall application is simpler, the components are configurable, and the effects are better.

[0013] In a possible implementation, the electronic device determines the dynamic effects performed 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 command triggered by the user.

[0014] According to a third aspect, there is provided an interface conversion method, the method comprising: The electronic device displays a first interface after detecting a first operation performed by a user on the electronic device, the first interface including 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 including a third element and a fourth element, and in a process of switching from the first interface to the second interface by using the at least one transition interface, the presentation format of the second element in the transition interface gradually changes to the presentation format of the third element, and the second element is partially the same as the third element.

[0015] Based on the above method, in the conversion configuration for switching from a first interface to a second interface, at least one transition interface is configured for splicing, and a second element on the first interface and a third element on the second interface exist on the transition interface, and the second element is partially the same as the third element, so that in the process of switching between the first interface and the second interface, the change is natural and coherent, and the visual experience effect for 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 a second interface fades in, and a second element on a transitional interface gradually changes to a third element.

[0017] In a possible implementation, in the process of switching from the first interface to the second interface, the electronic device executes dynamic effects corresponding to the interfaces and / or elements based on transformational dynamic effects configured for each interface or based on transformational dynamic effects configured for elements on the interfaces.

[0018] In possible implementations, the first interface and the second interface are different display interfaces of the first application, or the first interface is a home screen, an interface adjacent to the home screen, or a left-most interface of the electronic device, and the second interface is a display interface of the first application, or the first interface is a display interface of the first application and the second interface is a display interface of the second application.

[0019] According to a fourth aspect, there is provided an interface conversion method, the method comprising: The electronic device determines an interface type based on an interface configuration command triggered by a user, the interface type including a first interface, at least one transition interface, and a second interface, the transition interface being 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 the element configuration command triggered by the user, the electronic device determines that the second element gradually changes to the third element on the transition interface based on the element configuration command triggered by the user, and the second element is partially identical to the third element.

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

[0021] In a possible implementation, the electronic device determines the dynamic effects performed 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 command triggered by the user.

[0022] According to a fifth aspect, an embodiment of the present application provides a method for switching application interfaces, the method comprising: The method includes a step of determining an interface to be transformed by the target application and shared elements included in the transformed interface after receiving an interface transformation command triggered by a user, the interface being of the target application; and a step of performing a transformation between the corresponding interfaces based on the interface transformation command triggered by the user, wherein the shared elements on the transformed interface are presented consecutively in the interface transformation process.

[0023] Based on the above method, an application can configure different transition types and element types as well as animation effects during transitions based on the requirements of the application, so as to achieve a more flexible and smoother dynamic effect experience, making the overall application simpler, the components configurable, and the effects better.

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

[0025] In a possible implementation, the method further includes a step of determining an end element and / or an input element on the conversion interface, wherein 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 into an input interface.

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

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

[0028] According to a sixth aspect, an embodiment of the present application provides a method for switching application interfaces, the method comprising: The method includes: determining an interface type for conversion based on an interface conversion configuration command triggered by a user, the interface type including an end interface, an input interface, and a shared interface, the end interface referring to an initial interface during the interface conversion, the input interface referring to a final interface during the interface conversion, and the shared interface referring to an intermediate splicing interface during the interface conversion; and determining shared elements in the interface conversion process based on an element configuration command triggered by a user, the shared elements being elements that are presented consecutively in the interface conversion process.

[0029] Based on the above method, an application can configure different transition types and element types as well as animation effects during transitions based on the requirements of the application, so as to achieve a more flexible and smoother dynamic effect experience, making the overall application simpler, the components configurable, and the effects better.

[0030] In a possible implementation, the method includes a step of determining an end element and / or an input element in an interface transformation process based on an element configuration command triggered by a user, wherein the end element on the transformation interface disappears after the end interface is transformed, and the input element on the transformation interface is displayed after the end interface is transformed into an input interface.

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

[0032] According to a seventh aspect, there is further provided an inter-interface device. The device may be configured to perform operations in any possible implementation form of the first, third, or fifth aspects. For example, the device may include a module or unit configured to perform operations in any possible implementation form of the first, third, or fifth aspects. For example, the device may include a transceiver module and a processing module.

[0033] According to an eighth aspect, there is further provided an inter-interface electronic device. The electronic device may be configured to perform operations in any possible implementation form of the second, fourth, or sixth aspects. For example, the electronic device may include a module or unit configured to perform operations in any possible implementation form of the second, fourth, or sixth aspects. For example, the electronic device may include a transceiver module and a processing module.

[0034] According to a ninth aspect, there is provided a chip system including a processor and optionally further including a memory, wherein the memory is configured to store a computer program, and the processor is configured to call and execute the computer program from the memory, such that an electronic device having the chip system installed therein is capable of performing any method in any possible implementation form of the first to sixth aspects.

[0035] According to a tenth aspect, there is provided a computer program product comprising computer program code which, when executed by a processing module or processor of an electronic device, enables the electronic device to perform any method in any possible implementation form of the first to sixth aspects.

[0036] According to an eleventh aspect, there is provided a computer-readable storage medium storing a program that enables an electronic device to perform any of the methods in any possible implementation forms of the first to sixth aspects.

[0037] According to a twelfth aspect, there is provided an electronic device including a display, one or more processors, and one or more memories, wherein the one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, enable the electronic device to perform any method in any possible implementation of the first to sixth aspects. [Brief explanation of the drawings]

[0038] [Figure 1] 1 is a schematic diagram of interface area division of an electronic device according to an embodiment of the present application; [Figure 2] FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present application. [Figure 3]1 is a schematic diagram of the internal structure of a platform-side device according to an embodiment of the present application; [Figure 4] 1 is a schematic diagram of the structure of the Android® operating system of a platform-side device according to an embodiment of the present application; [Figure 5] 2 is a schematic diagram of the internal structure of an application-side device according to an embodiment of the present application; [Figure 6] 1 is a schematic diagram of the structure of the Android operating system of an application-side device according to an embodiment of the present application; [Figure 7] 1 is a schematic flow chart of an existing configuration for a single-shot solution. [Figure 8] FIG. 1 is a schematic diagram of a single-shot logic framework according to an embodiment of the present application. [Figure 9] FIG. 1 is a schematic diagram of a logical framework for the configuration phase according to an embodiment of the present application. [Figure 10] 2 is a schematic diagram of an application included in an application side device according to an embodiment of the present application; [Figure 11] FIG. 1 is a schematic diagram of scenario categories according to an embodiment of the present application. [Figure 12] FIG. 1 is a schematic diagram of element categories according to an embodiment of the present application. [Figure 13] FIG. 1 is a schematic diagram of a conversion configuration according to an embodiment of the present application. [Figure 14] FIG. 2 is a schematic diagram of a transformation effect according to an embodiment of the present application; [Figure 15] FIG. 1 is a schematic diagram of setting up an information container according to an embodiment of the present application; [Figure 16(a)] FIG. 1 is a schematic diagram of a high-speed conversion configuration according to an embodiment of the present application. [Figure 16(b)] FIG. 1 is a schematic diagram of a high-speed conversion configuration according to an embodiment of the present application. [Figure 16(c)] FIG. 1 is a schematic diagram of a high-speed conversion configuration according to an embodiment of the present application. [Figure 17(a)]FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(b)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(c)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(d)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(e)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(f)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(g)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 17(h)] FIG. 1 is a schematic diagram of a single-shot first transformation effect according to an embodiment of the present application; [Figure 18] FIG. 2 is a schematic diagram of a logical framework for the parsing phase according to an embodiment of the present application. [Figure 19] FIG. 2 is a schematic diagram of a logical framework of the execution phase according to an embodiment of the present application. [Figure 20] 1 is a schematic flow chart of a single-shot configuration method according to an embodiment of the present application. [Figure 21(a)] FIG. 2 is a schematic diagram of a conversion effect of a calling application according to Embodiment 1 of the present application; [Figure 21(b)] FIG. 2 is a schematic diagram of a conversion effect of a calling application according to Embodiment 1 of the present application; [Figure 21(c)] FIG. 2 is a schematic diagram of a conversion effect of a calling application according to Embodiment 1 of the present application; [Figure 22(a)] FIG. 2 is a schematic diagram of a first inter-application conversion effect according to Embodiment 1 of the present application; [Figure 22(b)]FIG. 2 is a schematic diagram of a first inter-application conversion effect according to Embodiment 1 of the present application; [Figure 23(a)] FIG. 2 is a schematic diagram illustrating a first effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 23(b)] FIG. 2 is a schematic diagram illustrating a first effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 23(c)] FIG. 2 is a schematic diagram illustrating a first effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 24(a)] FIG. 1 is a schematic diagram illustrating a conversion effect of a book application according to Embodiment 1 of the present application; [Figure 24(b)] FIG. 1 is a schematic diagram illustrating a conversion effect of a book application according to Embodiment 1 of the present application; [Figure 24(c)] FIG. 1 is a schematic diagram illustrating a conversion effect of a book application according to Embodiment 1 of the present application; [Figure 24(d)] FIG. 1 is a schematic diagram illustrating a conversion effect of a book application according to Embodiment 1 of the present application; [Figure 25(a)] FIG. 1 is a schematic diagram of a transformation effect of a gallery application according to Embodiment 1 of the present application; [Figure 25(b)] FIG. 1 is a schematic diagram of a transformation effect of a gallery application according to Embodiment 1 of the present application; [Figure 25(c)] FIG. 1 is a schematic diagram of a transformation effect of a gallery application according to Embodiment 1 of the present application; [Figure 25(d)] FIG. 1 is a schematic diagram of a transformation effect of a gallery application according to Embodiment 1 of the present application; [Figure 26(a)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(b)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(c)]FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(d)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(e)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(f)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 26(g)] FIG. 2 is a schematic diagram of a first transformation effect of a music application according to Embodiment 1 of the present application; [Figure 27(a)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 27(b)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 27(c)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 27(d)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 27(e)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 27(f)] FIG. 10 is a schematic diagram of a second transformation effect of the music application according to Embodiment 1 of the present application. [Figure 28(a)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 28(b)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 28(c)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 28(d)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 28(e)]FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 28(f)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 1 of the present application; [Figure 29(a)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 29(b)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 29(c)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 29(d)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 29(e)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 29(f)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 30(a)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 30(b)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 30(c)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 30(d)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 30(e)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 30(f)] FIG. 1 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 1 of the present application; [Figure 31(a)]FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(b)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(c)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(d)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(e)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(f)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 31(g)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 1 of the present application; [Figure 32(a)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 32(b)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 32(c)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 32(d)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 32(e)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 32(f)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 1 of the present application; [Figure 33(a)] FIG. 10 is a schematic diagram of a conversion effect of a calling application according to Embodiment 2 of the present application; [Figure 33(b)]FIG. 10 is a schematic diagram of a conversion effect of a calling application according to Embodiment 2 of the present application; [Figure 33(c)] FIG. 10 is a schematic diagram of a conversion effect of a calling application according to Embodiment 2 of the present application; [Figure 34(a)] FIG. 10 is a schematic diagram of a first inter-application conversion effect according to Embodiment 2 of the present application; [Figure 34(b)] FIG. 10 is a schematic diagram of a first inter-application conversion effect according to Embodiment 2 of the present application; [Figure 34(c)] FIG. 10 is a schematic diagram of a first inter-application conversion effect according to Embodiment 2 of the present application; [Figure 35(a)] FIG. 10 is a schematic diagram showing a first effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 35(b)] FIG. 10 is a schematic diagram showing a first effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 35(c)] FIG. 10 is a schematic diagram showing a first effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 36(a)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(b)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(c)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(d)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(e)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(f)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 36(g)] FIG. 10 is a schematic diagram of a transformation effect of a music application according to Embodiment 2 of the present application; [Figure 37(a)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 37(b)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 37(c)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 37(d)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 37(e)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 37(f)] FIG. 10 is a schematic diagram of a second inter-application conversion effect according to Embodiment 2 of the present application; [Figure 38(a)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 38(b)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 38(c)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 38(d)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 38(e)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 38(f)] FIG. 10 is a schematic diagram of a second effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 39(a)] FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 39(b)] FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 39(c)]FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 39(d)] FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 39(e)] FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 39(f)] FIG. 10 is a schematic diagram of a conversion effect of a calendar application according to Embodiment 2 of the present application; [Figure 40(a)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(b)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(c)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(d)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(e)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(f)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 40(g)] FIG. 10 is a schematic diagram of a third inter-application conversion effect according to Embodiment 2 of the present application; [Figure 41(a)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 41(b)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 41(c)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 41(d)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 41(e)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 41(f)] FIG. 10 is a schematic diagram of a third effect of the conversion between the desktop and the application according to Embodiment 2 of the present application; [Figure 42] FIG. 1 is a schematic diagram of a first application transformation effect based on screen division according to an embodiment of the present application; [Figure 43] FIG. 10 is a schematic diagram of a second application transformation effect based on screen division according to an embodiment of the present application; [Figure 44(a)] FIG. 1 is a schematic diagram of an application transformation effect based on multi-screen collaboration according to an embodiment of the present application; [Figure 44(b)] FIG. 1 is a schematic diagram of an application transformation effect based on multi-screen collaboration according to an embodiment of the present application; [Figure 45(a)] FIG. 10 is a schematic diagram of a second application transformation effect based on multi-screen collaboration according to an embodiment of the present application; [Figure 45(b)] FIG. 10 is a schematic diagram of a second application transformation effect based on multi-screen collaboration according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

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

[0040] (1) Single-shot: In the embodiments of the present application, single-shot primarily means that when switching between a first interface and a second interface is performed, there is at least one transition interface, and the transition interface includes elements on the first interface and / or the second interface, so that switching between the two interfaces is more coherent without interrupting the user experience.

[0041] For example, in an optional manner of an embodiment of the present application, the transition interface includes an element that exists in both the first interface and the second interface. For example, there is an element 1 on the first interface, the transition interface also includes element 1, and the second interface also includes element 1. In other words, element 1 exists continuously in the process of switching from the first interface to the second interface, so that 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 an embodiment of the present application, when element 1 on a first interface is switched to a second interface by using at least one transition interface, element 1 gradually changes to element 2, and element 2 is partially similar to element 1.

[0043] Element 2 being partially similar to element 1 may mean that the display pattern of element 2 is partially similar to the display pattern of element 1. For example, the display pattern of element 2 is ABCD, and the display pattern of element 1 is ABEF.

[0044] Alternatively, the partial similarity of element 2 to element 1 may be that the similarity between element 2 and element 1 is higher than a similarity threshold. For example, the presentation format 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 on element 1 slowly takes off the hat and becomes element 2 on the second interface. The presentation format of element 2 on the second interface is a man holding a hat in his hand. In this way, from the perspective of the visual sensory experience in the switching process, the user finds the interface switching transition relatively natural, coherent, clearer, and more interesting.

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

[0046] The interface transformation may be a transformation between different interfaces within the same application, an interface transformation during transformation between different applications, an interface transformation during transformation between a terminal display desktop and an application cover, and so on.

[0047] Additionally, the inter-interface conversion in the embodiments of the present application may also be referred to as inter-interface conversion, inter-interface transition, or inter-interface switching.

[0048] (3) Conversion object: In the embodiment of the present application, the conversion object may be understood as an application or the like that needs to perform inter-interface conversion.

[0049] In the embodiment of the present application, the terminal display desktop may also be understood as an application of the terminal device. It should be understood that the transformation object may also be referred to as a transition object.

[0050] (4) Conversion scenario: In the embodiment 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 an embodiment of the present application, the transformation scenario may include an end scenario (which may also be referred to as a departure scenario), an input scenario (which may also be referred to as an entrance scenario), and a sharing scenario (which may also be referred to as a transition scenario).

[0052] The exit scenario may be understood as a first interface in an embodiment of the present application, the input scenario may be understood as a second interface in an embodiment of the present application, and the shared scenario may be understood as a transition interface in an embodiment of the present application.

[0053] (5) The input element refers to the type of element 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 can also be referred to as an entrance element.

[0054] (6) Shared elements can be understood as elements of a type that continuously emerges and changes during the transformation, or as elements included in a transition interface.

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

[0056] (8) The shared container is configured to carry at least one shared element, i.e., in the transformation process, all elements within the shared container are continuously changed.

[0057] In an embodiment 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 is divided into a status bar in the upper region 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 region configured to display an application scenario interface, etc., and a virtual navigation button area in the lower region.

[0060] It should be noted that the region division manner of the interface of the electronic device in the embodiment of the present application is not limited to the above case, for example, the region of the interface of the electronic device may only include a status bar and an interface display region.

[0061] In the embodiment of the present application, when interface switching is performed, the shared elements refer only to elements that are continuously present in the interface display area.

[0062] It may be understood that when an electronic device performs interface switching, elements in the status bar in the upper region of the interface of the electronic device may be continuously present, and virtual navigation button elements in the lower region of the interface of the electronic device may also be continuously present, but none of them are shared elements as described in the embodiments of the present application.

[0063] (9) ARR is a file format, i.e., a binary archive file for Android library projects.

[0064] In an optional manner in an embodiment 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 embodiment of the present application include class files, res (resource) files, and the like.

[0066] (10) A Jar package is a file format.

[0067] In an optional manner in an embodiment of the present application, files such as applications corresponding to methods for converting between application interfaces are packaged in a Jar package file format. The Jar package format files in an embodiment of the present application include class files, list files, etc.

[0068] In the embodiments of the present application, the term "at least one" means one or more, and the term "plurality" means two or more. The term "and / or" describes a relational relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A is present, both A and B are present, and only B is present. A and B may be singular or plural. The character " / " typically indicates an "or" relationship between the related objects. At least one of the following items (moieties) or similar expressions refers to any combination of these items, including a singular item (moiety) or any combination of multiple items (moieties). For example, at least one of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0069] Unless otherwise specified, ordinal numbers such as "first" and "second" referred to in the embodiments of the present application are intended to distinguish between multiple objects and are not intended to limit the order, time sequence, priority, or importance of the multiple objects. In addition, the terms "comprise" and "have" in the embodiments, claims, and accompanying drawings of the present application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the enumerated steps or modules and may include additional steps or modules that are not enumerated.

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

[0071] The following describes the technical solutions of the embodiments of the present application with reference to the accompanying drawings of the embodiments of the present application.

[0072] The interface conversion method provided in the embodiment of the present application can be applied to the system architecture shown in Figure 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 may be interconnected by using a communication network. The communication network may be a local area network or a wide area network forwarded by using a relay device. When the communication network is a local area network, for example, the communication network may be a short-range communication network such as a Wi-Fi hotspot network, a Wi-Fi P2P network, a Bluetooth network, a Zigbee network, or a near field communication (NFC) network. When the communication network is a wide area network, for example, the communication network may be a third generation wireless telephone technology (3G) network, a fourth generation mobile communication technology (4G) network, a fifth generation mobile communication technology (5G) network, a future evolved public land mobile network (PLMN), or the Internet. In the scenario shown in FIG. 1, different electronic devices can exchange data with each other by using the communication network, for example, by transmitting inter-interface conversion effects, and configure inter-interface conversion solutions on the application.

[0074] In an optional manner, the application-side device 1100 accesses an application framework that is in the platform-side device 1200 and is used for application interface conversion through a communication interface established with the platform-side device 1200. The application-side device 1100 configures an inter-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 in the conversion object. Therefore, when the conversion object performs inter-interface conversion, the shared elements can be presented continuously, resulting in a smoother inter-interface conversion effect and a more coherent user experience.

[0075] Furthermore, when the application-side device 1100 activates the inter-interface conversion solution corresponding to the conversion object, the platform-side device 1200 parses the inter-interface conversion solution corresponding to the conversion object in the application-side device 1100 and executes the inter-interface conversion solution, so that 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 inter-interface conversion solution of the conversion object with the platform-side device 1200 in advance and store the inter-interface conversion solution in another server. After that, when the conversion object is started, an interface for communicating with the server is invoked, and the inter-interface conversion solution is obtained through the interface. In addition, in the online integration manner, the application-side device 1100 in this embodiment of the present application can further grant the user permission for the platform-side device 1200 to configure the inter-interface conversion solution for the conversion object. For example, the user can invoke the interface for communicating with the platform-side device 1200 based on the user's intention, and update and adjust the inter-interface conversion solution of the conversion object at any time.

[0078] In a second optional manner of the embodiment of the present application, the application-side device 1100 obtains a file package of an application used to configure an inter-interface conversion solution for a conversion object from the platform-side device 1200 and stores the file package. The application-side device 1100 parses the locally stored file package of the application to obtain the application program used to configure an inter-interface conversion solution for the conversion object. The application-side device 1100 determines the conversion object by using the application and configures the inter-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 inter-interface conversion is performed on the conversion object, the shared elements can be presented continuously, resulting in a smoother inter-interface conversion effect and a more coherent user experience.

[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 inter-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 acquired an application file package. A calendar application in the mobile phone can call the application file package in the mobile phone, integrate a 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 an application (i.e., a conversion object) in the application-side device 1100 needs to use the inter-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] It should be noted that the system for performing inter-interface conversion in the embodiment of the present application is not limited to the architecture shown in Fig. 1. Any variation in system architecture, etc. may be applied to the embodiment of the present application. For example, the system in the embodiment of the present application may further include a third-party material supplier, etc.

[0083] The third party material suppliers described in the embodiments of the present application may be configured to provide dynamic effect templates and the like.

[0084] For example, assume that in an application included in the platform-side device 1200 and used for inter-interface conversion, the provided dynamic effect templates include explosion effects, displacement effects, scaling effects, cropping effects, rotation effects, etc. Compared with the dynamic effect templates provided by the platform-side device 1200, the dynamic effect templates provided by the third-party material supplier are more diverse, further including black hole effects, snowflake effects, etc. Therefore, in order to reduce modifications to the application in the platform-side device 1200, an interface used to communicate with the third-party material supplier may be added to the system, so that when designing dynamic effects in the inter-interface conversion solution, a user can call the dynamic effect templates provided by the third-party material supplier.

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

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

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

[0088] For example, the application code may be application code applicable to an Android® system and used to perform an inter-interface conversion method, application code applicable to a Harmony® system and used to perform an inter-interface conversion method, and application code applicable to an iOS® system and used to perform an inter-interface conversion method. In an embodiment of the present application, the adapted application code used to perform the inter-interface conversion method may be selected based on the system installed on the electronic device. This is not limited herein.

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

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

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

[0092] The processor 1210 in this embodiment of the present application may 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, and is connected to all parts of the entire platform-side device 1200 by using various interfaces and lines, and performs various functions of the platform-side device 1200 by executing or carrying out 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, based on a user's operation command, a transformation object for inter-interface transformation, a transformation scenario in the inter-interface transformation process, elements in the scenario, and corresponding scenario dynamic effects and element dynamic effects. Then, the processor 1210 processes and packages an inter-interface transformation solution of the transformation object based on a configuration procedure, and locally stores the inter-interface transformation solution.

[0095] When the application-side device 1100 initiates an inter-interface transformation effect of the transformation object, the processor 1210 is further configured to parse the inter-interface transformation solution corresponding to the transformation object, i.e., determine attributes corresponding to the transformation scenario and the elements in the transformation object separately. The attributes include dynamic effects, display ratios, etc.

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

[0097] For example, the processor 1210 determines configuration parameters of the associated scenarios and elements in the transformation object based on the inter-interface transformation solution corresponding to the transformation object.

[0098] The processor 1210 can then transmit the execution data of the associated scenarios and elements in the form of streaming media to the application side device 1100 for playback.

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

[0100] The application-side device 1100 receives and stores an inter-interface conversion solution corresponding to the conversion object. When starting the inter-interface conversion effect of the conversion object, the application-side device 1100 calls the inter-interface conversion solution corresponding to the conversion object and parses the inter-interface conversion solution corresponding to the conversion object, i.e., determines the conversion scenario and attributes corresponding to the elements in the conversion object separately. The attributes include dynamic effects, display ratios, etc.

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

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

[0103] The application-side device 1100 then executes the execution data of the associated scenario and element of the conversion object, and displays on the display of the application-side device 1100 the effect of the inter-interface conversion performed on the conversion object.

[0104] In an optional manner, the transceiver 1230 is configured to receive an operation command triggered by a user and send the operation command to the processor 1210, so that the processor 1210 is used for inter-interface conversion, and configures an inter-interface conversion solution for a corresponding conversion object based on the operation command by using an application in the platform-side device 1200; and / or Optionally, the transceiver is configured to transmit a file package of the application in the platform-side device 1200 to the application-side device 1100; and / or In an optional manner, the transceiver is configured to transmit to the application-side device 1100 a solution that causes the application-side device 1100 to perform an inter-interface transformation on a transformation object in the platform-side device 1200 .

[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 a bus 1240 in FIG. 3. The bus is represented by using a thick line in FIG. 3. The connection scheme between the other components is described schematically and is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, 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] Memory 1220 may be volatile memory, such as random-access memory (RAM). Alternatively, memory 1220 may be non-volatile memory, such as read-only memory, flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). Alternatively, memory 1220 may be any other medium that can be used to carry or store program code, such as instructions or data structures, and that can be accessed by a computer, including, but not limited to, any other medium. Memory 1220 may be a combination of the foregoing memories.

[0107] In addition, in this embodiment of the present application, the Android® system having a layered architecture is used as an example to describe the software structure of the platform-side device 1200. It should be noted that the solution of the present application can still be implemented in another operating system (e.g., the Harmony® system or the iOS® system), provided that the functions implemented by the function modules are similar to those in the embodiment of the present application. This is not limited herein.

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

[0109] The platform-side device 1200 divides its software into multiple layers based on a layered architecture, with each layer having a clear role and division of labor. The layers communicate with each other through software interfaces.

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

[0111] (1) Application layer: In an optional manner in 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 applications used to implement the inter-interface translation solutions 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 an application programming interface (API) and a programming framework for applications in the application layer, and the application framework layer may include some predefined functions.

[0114] (3) Android Runtime and System Libraries: The Android Runtime may include a kernel library and a virtual machine, and is configured to be responsible for scheduling and managing the Android system.

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

[0116] In this embodiment of the present application, the virtual machine is configured to perform 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 run on the virtual machine. The virtual machine executes java files of the application layer and the application framework layer as binary files.

[0117] In this embodiment of the present application, the system library may include multiple 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 is configured to manage the display subsystem and provide blending of 2D and 3D layers for multiple applications.

[0119] The media library supports playback and recording of multiple commonly used audio and video formats, still image files, etc. The media library can support multiple audio and video encoding formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0120] The 3D graphics processing library is configured to implement 3D graphics drawing, image rendering, compositing, 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 inter-interface conversion in this embodiment of the present application may include a configuration module, a parsing module, and an execution module.

[0124] It should be noted that the system layer in which 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 located 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 AAR format or JAR format to facilitate application use.

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

[0126] Specifically, the configuration module receives 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 inter-interface conversion needs to be performed.

[0127] The parsing module in the platform-side device in this embodiment of the present application is configured to parse the inter-interface conversion solution corresponding to the conversion object, and store the parsed inter-interface conversion solution.

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

[0129] It can be understood that the parsing module mainly determines the conversion scenarios in the conversion object, the elements in each conversion scenario, and the corresponding execution effects based on the inter-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 perform different animation effects on different elements at different times based on the inter-interface conversion solution.

[0131] 2. Application device The application-side device 1100 may be a portable electronic device such as a mobile phone with wireless communication capabilities, a tablet computer, or a wearable device (e.g., a smart watch) that further includes other functions such as a personal digital assistant and / or music player. An exemplary embodiment of the portable electronic device includes, but is not limited to, a portable electronic device running iOS®, Android®, Microsoft®, Harmony®, or another operating system. Alternatively, the portable electronic device may be another portable electronic device, such as a laptop with a touch-sensitive surface (e.g., a touch panel). For the purposes of explanation, the following uses an example in which the application-side device 1100 is a mobile phone. Figure 5 is a block diagram of a partial structure of the application-side device 1100 related to an embodiment of the present application.

[0132] 5, the application side device 1100 may be a mobile phone. The mobile phone 1100 may include 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, an air 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, and the like.

[0133] It may 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 a different component arrangement may be used. The components shown in the figure may be implemented using hardware, software, or a combination of software and hardware.

[0134] The processor 110 may include one or more processing units. For example, the processor 110 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 integrated into one or more processors. The controller may be a central control center and command center for the mobile phone 100. The controller may generate operation control signals based on instruction operation codes and time-series signals to complete the control of instruction fetching and instruction execution. A memory may also be disposed in the processor 110 and configured to store instructions and data. In some embodiments, the memory in the processor 110 is a cache. The memory may store instructions or data that have been used or are periodically used by the processor 110. If the processor 110 needs to use the instructions or data again, the processor can retrieve the instructions or data directly from memory, which avoids repeated accesses, reduces the latency of the processor 110, and improves system efficiency.

[0135] In some embodiments, the processor 1110 may include one or more interfaces, which 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, and may be, for example, a Mini USB interface, a Micro USB interface, or a USB Type C interface. The USB interface 130 may be configured to connect to a charger to charge the mobile phone 100, or to transmit data between the mobile phone 100 and a peripheral device. The charging management module 140 is configured to receive a charging input from the charger. The charging management module 141 is configured to connect to the battery 142, the charging management module 140, and the processor 110. The charging management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, etc.

[0137] In an optional manner in this embodiment of the present application, the processor 1110 is configured to determine a conversion object and invoke an application located in the platform-side device 1200 and used for inter-interface conversion to 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 transformation object and an inter-interface transformation solution corresponding to the transformation object, and implement an inter-interface transformation of the transformation object based on the inter-interface transformation solution when the inter-interface transformation is performed on the transformation 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 transformation effect of the transformation object based on the inter-interface transformation solution of the transformation object.

[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, a modem processor, a baseband processor, etc. Antenna 1 and Antenna 2 are configured to transmit and receive electromagnetic signals. Each antenna of the mobile phone 100 may be configured to cover one or more communication frequency bands. Different antennas may be further multiplexed to improve antenna utilization. For example, Antenna 1 may be multiplexed as a diversity antenna in a wireless local area network. In some other embodiments, the antennas may be used in combination with a tuning switch.

[0141] The mobile communication module 1150 may be applied to the mobile phone 1100 to 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 may receive electromagnetic waves through the antenna 1, perform processing such as filtering or amplification on the received electromagnetic waves, and send the electromagnetic waves to the modem processor for demodulation. The mobile communication module 1150 may further amplify signals modulated by the modem processor and convert the signals into electromagnetic waves for emission through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 1150 may be disposed within the processor 1110. In some embodiments, at least some of the functional modules of the mobile communication module 1150 may be disposed 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 a wireless local area network (WLAN) (e.g., a wireless fidelity (Wi-Fi) network), Bluetooth (BT), a 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, a communication connection may be established between different electronic devices by using BT or WLAN.

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

[0144] The display 1194 is configured to display an application display interface, etc. 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), etc. 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 still images or video and may include a front-facing camera and a rear-facing camera.

[0146] The internal memory 1121 may 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 for at least one application (e.g., an audio playback function or an image playback function), etc. The data storage area may store data (e.g., images and videos) generated in the process of using the mobile phone 1100, etc. In addition, the internal memory 1121 may include high-speed random access memory and may further include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc.

[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 capabilities of the mobile phone 1100. The external storage card communicates with the processor 1110 via the external memory interface 1120 to implement data storage functions. The external storage card stores files, such as images or videos.

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

[0149] The buttons 1190 include a power button, a volume button, etc. The buttons 1190 may be mechanical buttons or touch buttons. The mobile phone 1100 may receive the button input and generate button signal inputs related to user settings and function control of the mobile phone 1100. The motor 1191 may generate a vibration prompt. The motor 1191 may be configured to generate an incoming call vibration prompt and touch vibration feedback. For example, touch operations performed on different applications (e.g., taking pictures and playing audio) may correspond to different vibration feedback effects. The indicator 1192 may be an indicator light and may be configured to indicate charging status and power changes, or to indicate messages, missed calls, notifications, etc. The SIM card interface 1195 is configured to connect to a SIM card. The SIM card may be inserted into or removed from the SIM card interface 1195 to implement contact and separation with the mobile phone 1100.

[0150] In addition, in this embodiment of the present application, the Android® system having a layered architecture is used as an example to describe the software structure of the application-side device 1100. It should be understood that in this specification, the Android® system is used as an example. The solution of the present application can still be implemented in another operating system (e.g., the Harmony® system or the iOS® system), provided that the functions implemented by the function modules are similar to those in the embodiment of the present application.

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

[0152] In a layered architecture, software is divided into layers, each with a distinct role and task. The layers communicate with each other through 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 in 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 package may include applications such as dialer, camera, gallery, calendar, phone, map, navigation, WLAN, Bluetooth, music, video, and messaging.

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

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

[0158] A 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, perform screen locking, take screenshots, etc.

[0159] Content providers are configured to store and retrieve data and make it accessible by applications. Data can include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0160] A 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. A display interface can include one or more views. For example, a display interface that includes a message notification icon may include a text display view and a picture display view.

[0161] The telephone manager is configured to provide communication functions of the application side device 1100, such as managing call status (including answering, rejecting, etc.).

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

[0163] The notification manager may be configured to allow applications to display notification information in the status bar and to send notification-type messages. The displayed information may disappear automatically after a short pause without user interaction. For example, the notification manager may be configured to notify of download completion, provide message notifications, etc. The notification manager may alternatively provide notifications that appear in the system's top status bar in the form of graphs or scrollbar text, notifications for applications running in the background, or notifications that appear on the screen in the form of dialog windows. For example, text information may be displayed in the status bar, an announcement may be made, the electronic device may vibrate, or an indicator light may flash.

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

[0165] When using electronic devices, users pay more and more attention to creating an interface experience.

[0166] Currently, when a first interface is switched to a second interface, the first interface is directly switched to the second interface, resulting in poor coherence and a poor user experience.

[0167] For example, as shown in Figure 7, in the second interface switching configuration currently performed on the first interface, only the exit element on the first interface and the dynamic effect performed by the exit element during switching, and / or the input element on the second interface and the dynamic effect performed by the input element during switching are determined. In the switching process, to complete the switching from the first interface to the second interface, the exit element on the first interface executes the corresponding exit effect to exit, and the input element on the second interface executes the corresponding dynamic effect to enter.

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

[0169] From the above, it can be seen that the processing logic of current inter-interface conversion solutions is relatively simple, and only the dynamic effects of exit and entry 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 unsatisfactory. To solve this problem, the embodiments of the present application provide an inter-interface conversion method, device, and system for efficiently and flexibly implementing more coherent inter-interface conversion effects.

[0170] With reference to the accompanying drawings and application scenarios, the following describes in detail the method for performing inter-interface conversion based on the single-shot effect provided in the embodiments of the present application.

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

[0172] 4, it can be seen that the application framework layer mainly includes a configuration module, a parsing module, and an execution module. Therefore, in this embodiment of the present application, when the inter-interface conversion is performed based on the application framework, it can be seen that there may be three phases, namely, a configuration phase, a parsing phase, and an execution phase, as shown in FIG.

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

[0174] Phase 1: Configuration Phase: Phase 1 mainly refers to performing parameter configuration for scenarios and elements in the transformation 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, see FIG.

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

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

[0178] Then, in an optional manner in this embodiment of the present application, a device that configures the interface-to-interface conversion solution for the conversion object (e.g., a processor in the application-side device or a processor in the platform-side device) 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 located at different nodes in the transformation 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 claiming document (Application No. 202010943693.3). The transition scenario shown in FIG. 11 of the present application is equivalent to the sharing scenario shown in FIG. 10 of the priority claiming 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 claiming document (Application No. 202010943693.3).

[0180] As shown in Figure 12, the application-side device determines the element type and dynamic effect format based on the command triggered by the user. The element types include a shared element, an end element, and an input element. The end element shown in Figure 12 of the present application is equivalent to the end element shown in Figure 11 of the priority claiming document (Application No. 202010943693.3). The shared element shown in Figure 12 of the present application is equivalent to the successive element shown in Figure 11 of the priority claiming document (Application No. 202010943693.3). The input element shown in Figure 12 of the present application is equivalent to the input element shown in Figure 11 of the priority claiming document (Application No. 202010943693.3). Furthermore, as shown in FIG. 13 , a device configured to perform inter-interface transformation solution composition on a transformation object determines the classification of elements in each transformation scenario, i.e., 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, based on a selection command triggered by a user, and determines corresponding dynamic effects when the elements are transformed. 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 claiming 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 claiming document (Application No. 202010943693.3). All end elements shown in FIG. 13 of the present application are equivalent to all end elements shown in FIG. 12 of the priority claiming document (Application No. 202010943693.3). All input elements shown in Figure 13 of the present application are equivalent to all input elements shown in Figure 12 of the priority document (Application No. 202010943693.3).

[0181] It should be noted that in this embodiment of the present application, a device configured to perform inter-interface transformation solution composition on a transformation object can further divide element types based on the container the element is located in. For example, assume that container 1 is determined to be a shared container. It can be understood that all elements in container 1 are shared elements.

[0182] Additionally, in an optional manner of this embodiment of the present application, a device configured to perform inter-interface transformation solution composition on a transformation object may 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 transformation type is used as an example to briefly explain some parameters related to elements in the transformation object in this embodiment of the present application.

[0184] Parameters associated with an element in this embodiment of the present application may include name, motion duration, control ID, dynamic effect, dynamic effect delay, interface (exit and / or entry) duration, and the like.

[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 types, and any configuration parameters that can be applied to the elements in this embodiment of the present application fall within the protection scope of this embodiment of the present application. For example, if multiple dynamic effects are set for an element, the configured parameters may further include the interval duration of 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 an interface transformation for a selected transformation object are succinctly listed in tabular form.

[0187] [Table 1]

[0188] From the contents of Table 1, it can be seen that in this embodiment of the present application, when an inter-interface transformation solution is configured for a transformation object, the name of the transformation object on which the inter-interface transformation needs to be performed needs to be determined first. Then, the end element, shared element, input element of the transformation object are determined, the end dynamic effect, end duration, end dynamic effect delay, etc. for the end element are determined, the input dynamic effect, input duration, input dynamic effect delay, etc. for the input element are determined, and the shared dynamic effect, shared duration, shared dynamic effect delay, etc. for the shared element are determined.

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

[0190] For example, assume that container 1 contains three elements: element 1, element 2, and element 3. If container 1 is set as a shared element, all elements contained in container 1 become shared elements.

[0191] Furthermore, when a shared dynamic effect is configured for container 1, a dynamic effect may be configured individually 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 effect configured for Shared Element 2 and Shared Element 3 is gradient. In this case, in the inter-interface conversion process, Shared Element 1 executes the flipping dynamic effect. Shared Element 2 and Shared Element 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 inter-interface conversion process, the gradient dynamic effect is uniformly executed by Shared Elements 1 to 3 in Container 1.

[0193] In this embodiment of the present application, when a transformation is performed between multiple interfaces, the intermediate interface through which the transformation is performed may be considered a transition interface (which may 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 inter-interface conversion process, the total conversion time T1 in this embodiment of the present application is the sum of the end time T2, the sharing time T3, and the input time T4. When the end interface, the transition interface, and the input interface overlap in the inter-interface conversion process, the total conversion time T1 in this embodiment of the present application is less than the sum of the end time T2, the sharing time T3, and the input time T4.

[0195] Furthermore, the dynamic effect format in this embodiment of the present application can be of the following types: Including, but not limited to, explosion effects, displacement effects, scaling effects, cropping effects, rotation effects, and fade-out and fade-in effects.

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

[0197] The user can specify the user requirements, e.g. The attributes of the dynamic effect can be further set based on 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 effects solution configured in this embodiment of the present application.

[0199] [Table 2]

[0200] From the contents of Table 2, it can be seen that for the element named "AutoExplodeAnimCreator", the explosion dynamic effect is executed during exit and entry.

[0201] It should be noted that the transformation type is not limited in this embodiment of the present application. For example, the transformation type in this embodiment of the present application may alternatively be a ViewGroup transformation type, a Fragment transformation type, etc. The setting method of another transformation type is similar to that of the Activity transformation type. The main difference is that the control format is different, that is, the transformation setting is different. For a brief explanation, please refer to the above description of the Activity transformation type.

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

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

[0204] [Table 3]

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

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

[0207] For example, assume that an inter-interface transformation solution is configured for application A as shown in FIG. 14. The user determines, in a user-defined manner, the element corresponding to block 2 in application A as a shared element, the dynamic effect configured for the end element as a vanishing gradient, the dynamic effect configured for the shared element as an amplifying dynamic effect, and the dynamic effect configured for the input element as an emerging gradient. 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 claiming 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 claiming 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 claiming document (Application No. 202010943693.3). The end elements of Block 1 shown in Figure 14 of the present application are equivalent to the end elements of Block 1 shown in Figure 13 of the priority claim document (Application No. 202010943693.3). The shared elements of Block 2 shown in Figure 14 of the present application are equivalent to the shared elements of Block 2 shown in Figure 13 of the priority claim document (Application No. 202010943693.3). The input elements of Block 3 shown in Figure 14 of the present application are equivalent to the input elements of Block 3 shown in Figure 13 of the priority claim document (Application No. 202010943693.3).

[0208] When application A performs an interface-to-interface transformation, in this case, it is assumed that interface a in Figure 13 is the exit scenario of application A, interface b in Figure 13 is the transition scenario of application A, interface c in Figure 13 is the input scenario of application A, block 1 is the exit 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 and displays an amplifying dynamic effect, while block 1 used as an ending element fades out.

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

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

[0212] For example, as shown in Figure 15, if the size of the information container for displaying the end scenario is set to the size of dashed box 1 and the information container is displayed on the left border of the screen, the content of the end scenario will only be displayed within dashed box 1 in Figure 15. If the size of the information container for displaying the transition scenario is set to the size of dashed box 2 and the information container is displayed in the center of the screen, the content of the shared scenario will only be displayed within dashed box 2 in Figure 15.

[0213] Configuration method 2: Configured by pre-defined templates In an optional manner of this embodiment of the present application, multiple quick configuration templates can be set. Specifically, in the quick configuration template, the relevant configuration parameters of the elements are pre-set, and the user only needs to determine the name of the element. This implements quick configuration and effectively reduces the complexity of the configuration.

[0214] In an optional manner in this embodiment of the present application, after the user has determined the transformation object, the user can determine the elements that need to be composed by using the template by tapping the screen with a finger.

[0215] Specifically, after a user taps the screen with his / her finger, the mobile phone determines the name of the element or container displayed at the tapped screen position based on the tapped screen position, and binds the name of the element or container to the quick configuration template selected by the user, so that when the element or container performs inter-interface conversion, the configuration corresponding to the selected quick configuration module is performed.

[0216] For example, when a user configures an inter-interface conversion solution for application A, it is assumed that the current configuration interface is shown in Fig. 16(a), and the customized configuration and quick configuration are displayed on the current configuration interface. After the user taps on quick configuration with their finger, the current interface is shown in Fig. 16(b), and two quick configuration modules, namely, the above-mentioned quick configuration template 1 and quick configuration template 2, are displayed.

[0217] The relevant configuration in Express Configuration Template 1 is as follows: The exit dynamic effect is a translation from left to right, with a dynamic effect duration of 2 seconds. The entry dynamic effect is a translation from right to left, with a dynamic effect duration of 2 seconds. The shared element or shared container dynamic effect is an explosion, with a dynamic effect duration of 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-quarter the size of the interface, etc.

[0218] The relevant configuration in Rapid Configuration Module 2 is as follows: The exit dynamic effect is a gradient, and the dynamic effect duration is 2 seconds. The entry dynamic effect is a flipping, and the dynamic effect duration is 2 seconds. The shared element or shared container dynamic effect is a vibration, and the dynamic effect duration is 1.5 seconds. The center point of the vibration dynamic effect is the center point of the shared element or shared container, etc. In the process of selecting a quick configuration template, it is assumed that the user selects quick configuration template 1.

[0219] After determining the quick configuration template to be applied, the user only needs to determine the elements to which the template will be applied.

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

[0221] Therefore, when application A performs an interface conversion, as shown in Figures 17(a) to 17(h), it is assumed that interface a is the termination scenario of application A and interface b is the input scenario of application A. In the process of terminating interface a, interface a is translated from left to right for termination, with a dynamic effect duration of 2 seconds. In the process of terminating interface b, interface b is translated from right to left for input, with a dynamic effect duration of 2 seconds. The ship used as a shared element is always present, and the explosion dynamic effect is displayed at a quarter of the screen size by using the center point of the ship as the center point of the shared element.

[0222] Furthermore, after a user configures an inter-interface conversion solution for a conversion object by using the application framework provided in this embodiment of the present application, a configuration file for the inter-interface conversion solution may be generated, and the configuration file may be invoked when the conversion object subsequently performs an inter-interface conversion display.

[0223] It should be noted that in this embodiment of the present application, a method of combining a user-defined method and a pre-set template method may alternatively be used to configure an inter-interface conversion solution for a conversion object, etc. This is not limited in this embodiment of the present application.

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

[0225] Phase 2: Parsing Phase: Phase 2 mainly means that a device configured to parse the inter-interface transformation solution corresponding to the transformation object parses the inter-interface transformation solution obtained by the transformation object in the configuration phase to obtain information such as elements and element attributes configured for inter-interface transformation in the inter-interface transformation solution, and determines the effect of the inter-interface transformation solution on the transformation object.

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

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

[0228] First, in the parsing phase in this embodiment of the present application, a device configured to execute an inter-interface transformation solution for a transformation object determines the scenario type configured for the inter-interface transformation in the inter-interface transformation solution and the layout type corresponding to the scenario type by using the inter-interface transformation solution corresponding to the transformation 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, so that the transformation dynamic effect is extended based on the layout type, thus the compatibility is better and the adhesion is higher.

[0230] Additionally, a device configured to parse the inter-interface transformation solution corresponding to the transformation object determines a state of each transformed interface based on the inter-interface transformation solution.

[0231] It can be understood that a device for parsing an inter-interface transformation solution corresponding to a transformation object determines, based on the inter-interface transformation solution, elements included in the exit scenario and states corresponding to the elements, elements included in the transition scenario and states corresponding to the elements, and elements included in the input scenario and 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 type of the element, the dynamic effect duration and so on.

[0233] For example, assume the transformation object is a calendar application. The configuration files obtained by the calendar application in phase 1 and used for interface transformation are shown in Table 4.

[0234] [Table 4]

[0235] A device configured to parse the inter-interface transformation solution corresponding to the transformation object can determine, based on the contents of Table 4, that the ending dynamic effect in the ending scenario is a dynamic effect having a displacement of 20 pixels from left to right and a gradient of 2s, that the input dynamic effect in the input scenario is a dynamic effect having a displacement of 20 pixels from right to left and a gradient of 2s, and that the shared element is a year in the shared scenario, and in the interface transformation 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 the device configured to execute the inter-interface transformation solution corresponding to the transformation object displays the transformation effect configured in the inter-interface transformation solution based on the inter-interface transformation solution corresponding to the transformation object when an inter-interface transformation is executed on the transformation object.

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

[0238] For example, in this embodiment of the present application, when a user initiates a conversion, the platform-side device initiates the conversion in a one-tap manner based on various parameters in the inter-interface conversion solution corresponding to the conversion object obtained through syntax analysis, and displays the effect of performing inter-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 above description of Figures 11 and 12 and the contents of each module in the present application, it can be understood that the contents shown in Figure 27 in the priority document (Application No. 202010943693.3) can be obtained. The combination of Figures 9, 18, and 19 of the present application is equivalent to the contents shown in Figure 32 in the priority document (Application No. 202010943693.3).

[0241] Based on the above detailed description of the single-shot framework in the embodiment of the present application, an interface conversion method for an application-side device using the single-shot framework is provided. As shown in Figure 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 command 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, and the transition interface is an intermediate splicing interface from the first interface to the second interface.

[0244] It can be understood that in this embodiment of the present application, the first interface is an exit 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 an element configuration command triggered by a user.

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

[0247] For example, on the exit interface, at least one container and / or element is set as an exit element and at least one container and / or element is set as a shared element, and 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 scheme of this embodiment of the present application, the shared elements on the exit interface are the same as the shared elements 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 command 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 command triggered by a user, and the electronic device determines, based on the element configuration command triggered by the user, that the second element gradually changes to a third element on a transition interface, and the second element is partially identical to 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, based on a dynamic effect configuration command triggered by a user, a dynamic effect to be performed by an interface, a container, and / or an element in the process of switching from the first interface to the second interface.

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

[0255] Additionally, different dynamic effects can be specified for 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 applications. 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 the inter-interface conversion solution corresponding to the conversion object by performing the above-mentioned configuration operation. For specific implementation, please 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 inter-interface conversion solution corresponding to the conversion object to initiate the effect of inter-interface conversion.

[0259] Furthermore, in this embodiment of the present application, after the application-side device configures the inter-interface transformation solution corresponding to the transformation object, the application-side device can integrate the inter-interface transformation solution. Specifically, the application-side device encapsulates and stores the inter-interface transformation solution corresponding to the transformation object, so that when the inter-interface transformation is performed on the transformation object again, the inter-interface transformation effect of the transformation object is directly triggered to start.

[0260] It should be noted that the above-mentioned configuration steps do not constitute limitations on this embodiment of the present application. When the inter-interface conversion method in this embodiment of the present application is used to configure an inter-interface conversion solution, the steps performed can be flexibly adjusted based on actual circumstances. For example, when an inter-interface conversion solution is configured in this embodiment of the present application, the scenario type corresponding to the converted 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 aforementioned three types and can be further expanded.

[0261] Phase 3: Execution Phase: S2004: After detecting a first operation performed by a user on the electronic device, the application side device displays a first interface, where 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 displays a second interface after detecting a second operation performed by the user on the first 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 optional manner of this embodiment of the present 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 format of the second element on the transition interface gradually changes to the presentation format of the third element, and the second element is partially the same as the third element.

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

[0266] The solution for performing inter-interface conversion based on a single shot in this embodiment of the present 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. The solution is also applicable to different screen scenarios, such as full screen, split screen, and projection scenarios.

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

[0268] Application Example 1: A transition interface contains elements that exist in both a first interface and a second interface.

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

[0270] Conversion Type 1: Fragment conversion type In this embodiment of the present application, the inter-interface conversion solution based on the Fragment conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop to application conversion, etc., including but not limited to the following:

[0271] Case 1: In-application conversion: As shown in Figures 21(a) to 21(c), in this embodiment of the present application, an example of the effect of in-application transformation based on at least two Fragments is provided by using a calling 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 answer button, and the usage status of the calling application is determined based on the answer or hang-up command triggered by the user. For example, as shown in Table 5, the configuration files applied in this embodiment of the present application are as follows:

[0273] [Table 5]

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

[0275] When the calling application initiates the inter-interface conversion solution, if the user triggers a response command in the process of switching from the exit interface to the input interface, the response key is a shared element.

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

[0277] In this embodiment of the present application, after the answer key is used as a shared element and the dynamic effect transformation is performed, the presentation format of the answer key is similar to that of the hang-up key used as an end element, but it should be noted that the icon of the answer key is different from the icon of the hang-up key used as an end element on the switching interface.

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

[0279] Case 2: Application-to-application conversion: The following describes a method for performing inter-interface transformation based on the single-shot effect provided in this embodiment of the present application by using an example in which a user needs to switch to a message application when using a call application.

[0280] When a user configures an inter-interface transformation solution between a calling application and a messaging application, the answer button in the calling application is used as a shared element and is assumed to be continuously present in the transformation process.

[0281] For example, as shown in FIG. 22(a) and FIG. 22(b), when a user taps the message button on the call interface, the call application and the message application are triggered to perform interface transformation. After the call application jumps to the message application, the answer 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 the SMS message is displayed. After the SMS message is edited, the answer button is tapped, the answer button performs a rotation and shrink dynamic effect, and the call interface is displayed.

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

[0283] When a user configures an interface-to-interface transformation solution between the application desktop and the calling application, the answer button in the calling application is used as a shared element and is assumed to be continuously present in the transformation process.

[0284] For example, as shown in Figures 23(a) to 23(c), after a user taps the calling application icon on the application desktop, an interface transition between the application desktop and the calling application is triggered. In the process of the application desktop jumping to the calling application, the answer button is always present as a shared element, and a smooth downward dynamic effect is performed on the answer button. Then, the calling application interface is displayed.

[0285] Conversion Type 2: Activity Conversion Type In this embodiment of the present application, the inter-interface conversion solution based on the Activity conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop to application conversion, etc., including but not limited to the following:

[0286] Case 1: In-application conversion: As shown in Figures 24(a) to 24(d), an embodiment of the present application provides a first example of the effect of interface transformation based on at least two Activities by using a book application in an application market as an example. 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 exit interface and the input interface of the book application when the inter-interface conversion is performed are as shown in Figures 24(a) to 24(d). From the exit interface of the book application, it can be seen that the exit interface includes a title bar, a classification icon, and at least one book cover.

[0289] From the contents of Table 6, it can be seen that the book cover selected by the user is a shared element, and the shared element continues to exist during the interface conversion. The end elements are the title bar, the classification icon, and another book cover not selected by the user. During the interface conversion, a slide-down dynamic effect is performed. From the input interface of the book application, it can be seen that the content introduction, rating bar, function icons, etc. on the input interface are all input elements. During the interface conversion, a slide-up dynamic effect is performed.

[0290] Therefore, when the book application starts the inter-interface conversion solution, it is assumed that the book selected by the user is Book 4, as shown in Figures 24(a) to 24(d). Therefore, in the process of switching from the exit interface to the input interface, the exit interface is exited by sliding down, the icon of Book 4 is always present, and the input interface is entered by sliding up.

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

[0292] [Table 7]

[0293] When the inter-interface conversion is performed, it is assumed that the exit interface and the input interface of the gallery application are as shown in Figures 25(a) to 25(d). It can be seen from the exit interface of the gallery application that the exit interface includes a search bar, a function icon, at least one picture, etc.

[0294] From the contents of Table 7, it can be seen that the picture selected by the user is a shared element and continues to exist during the inter-interface conversion. The end elements include the search bar, the function icon, another picture not selected by the user, etc. During the inter-interface conversion, a left movement dynamic effect is executed. From the input interface of the gallery application, it can be seen that the function icon on the input interface, another picture not selected by the user, etc. are all input elements. During the inter-interface conversion, a center amplification dynamic effect is executed.

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

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

[0297] [Table 8]

[0298] When the conversion between interfaces is performed, it is assumed that the exit interface and input interface of the music application are as shown in Figures 26(a) to 26(g). From the scenarios shown in Figures 26(a) to 26(g), it can be seen that the exit scenario includes a classification icon, at least one cover, a function button, etc.

[0299] From the content of Table 8, it can be seen that the cover picture selected by the user is a shared element that continues to exist during the interface conversion, and the end element performs a scaling dynamic effect during the interface conversion. From the input scenario of a music application, it can be seen 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 performed.

[0300] Therefore, when the book application starts a single-shot interface conversion, the cover selected by the user is assumed to be the main cover, as shown in Figures 26(a) to 26(g). Therefore, in the process of switching from the exit interface to the input interface, the exit interface is closed via scaling, the main cover is always present, and the input interface is entered via sliding up.

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

[0302] Case 2: Application-to-application conversion: As shown in Figures 28(a) to 28(f), the following describes a method for performing inter-interface conversion based on the single-shot effect provided in this embodiment of the present application by using an example in which a user needs to switch to a gallery application when using a camera application.

[0303] When a user configures an inter-interface transformation solution between a camera application and a gallery application, the thumbnail button in the camera application is used as a shared element and is assumed to be continuously present in the transformation process.

[0304] For example, as shown in FIGS. 28(a) to 28(f), when a user taps the thumbnail button on the camera interface, an interface transition between the camera application and the gallery application is triggered. After the camera application jumps to the gallery application, the captured photo is displayed. In this case, the thumbnail button of the camera application continues to exist, the capture interface disappears, and the photo in the gallery appears. After the thumbnail button on the gallery interface is tapped, the thumbnail button continues to exist.

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

[0306] When a user configures an inter-interface conversion solution between the application desktop and the music application, the note element in the music application icon is used as a shared element, and the note element is assumed to exist continuously in the conversion process.

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

[0308] Transformation Type 3: ViewGroup Transformation Type In this embodiment of the present application, the inter-interface conversion solution based on the ViewGroup conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop-to-application conversion, etc., including but not limited to the following:

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

[0310] [Table 9]

[0311] When the inter-interface conversion is performed, it is assumed that the end interface and the input interface of the music application are as shown in Figures 30(a) to 30(f). Based on the contents of Table 9, it can be determined that 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, and in the inter-interface conversion process, the shared element presents an effect that vibrates from left to right with a vibration amplitude of 2 pixels.

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

[0313] Case 2: Application-to-application conversion: As shown in Figures 31(a) to 31(g), the following describes a method for performing inter-interface conversion based on the single-shot effect provided in this embodiment of the present application by using an example in which a user needs to switch to a camera application when using a shopping application.

[0314] When a user configures an inter-interface transformation solution between a shopping application and a camera application, the capture button in the shopping application is used as a shared element and is assumed to be continuously present in the transformation process.

[0315] For example, as shown in Figures 31(a) to 31(g), when a user taps the photo button on the shopping interface, an interface transition between the shopping application and the camera application is triggered. In the process of the shopping application jumping to the camera application, the photo button of the camera application continues to exist, the shopping interface fades out, and the camera interface fades in.

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

[0317] When a user configures an interface-to-interface transformation solution between the application desktop and the calendar application, the date element in the calendar application icon is used as a shared element and is assumed to be continuously present in the transformation process.

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

[0319] Application Example 2: When element 1 on a first interface is switched to a second interface by using at least one transition interface, element 1 gradually changes into element 2, and the similarity between element 2 and element 1 is higher than a similarity threshold.

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

[0321] Conversion Type 1: Fragment conversion type In this embodiment of the present application, the inter-interface conversion solution based on the Fragment conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop to application conversion, etc., including but not limited to the following:

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

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

[0324] For example, as shown in Figures 33(a) to 33(c), when a calling application initiates an interface conversion, in the process of switching from a first interface to a second interface, if a 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 a shared element, the presentation format of the shared element on the first interface is Element 1, the presentation format 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.

[0326] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 33(a) to 33(c), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is that the call is gradually picked up. This increases the interest and brings the user a more vivid interface switching experience.

[0327] In addition, an exit element on the first interface fades out. For example, the exit element is a hang-up key icon. A fade-out dynamic effect is performed during the interface switching. An input element on the second interface fades in. For example, the input elements are a hands-free icon and a keyboard icon. A fade-in dynamic effect is performed during the interface switching.

[0328] Case 2: Application-to-application conversion: The following describes a method for performing inter-interface transformation based on the single-shot effect provided in this embodiment of the present application by using an example in which a user needs to switch to a message application when using a call application.

[0329] When a user configures an inter-interface transformation solution between a calling application and a messaging application, the answer button in the calling application is used as a shared element and is assumed to be continuously present in the transformation process.

[0330] For example, as shown in Figures 34(a) to 34(c), when a user taps the 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 a first interface, and the message application interface can be understood as a second interface.

[0331] The presentation format of the shared element on the first interface is element 1, the presentation format 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.

[0332] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 34(a) to 34(c), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is that the call is gradually picked up. This increases the interest and brings the user a more vivid interface switching experience.

[0333] Additionally, an exit element on the first interface fades out. For example, the exit element is a lock icon. A fade-out dynamic effect is performed during the interface switching. An input element on the second interface fades in. For example, the input element is an SMS message editing interface represented by using a bubble window, and the interface is used to edit SMS messages.

[0334] Case 3: Desktop to Application Conversion: In the following, by using an example in which a user needs to switch from an application desktop to a calling application, a method for performing inter-interface transformation based on the single-shot effect provided in this embodiment of the present application is described.

[0335] When a user configures an interface-to-interface transformation solution between the application desktop and the calling application, the answer button in the calling application is used as a shared element and is assumed to be continuously present in the transformation process.

[0336] For example, as shown in Figures 35(a) to 35(c), after a user taps a calling application icon on an application desktop, an interface conversion between the application desktop and the calling application is triggered. In other words, the application desktop interface may be understood as a first interface, and the calling application interface may be understood as a second interface. The presentation format of the shared element on the first interface is Element 1, and the presentation format 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.

[0337] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 35(a) to 35(c), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is a gradually picked up call and a smooth downward moving dynamic effect is executed, which increases the fun and brings the user a more vivid interface switching experience.

[0338] Additionally, the exit element on the first interface fades out. For example, the exit element is an icon of another application. During the interface switching, a fade-out dynamic effect is performed. The input element on the second interface fades in to obtain the calling application interface.

[0339] Conversion Type 2: Activity Conversion Type In this embodiment of the present application, the inter-interface conversion solution based on the Activity conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop to application conversion, etc., including but not limited to the following:

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

[0341] For example, as shown in Figures 36(a) to 36(g), when a music application starts a single-shot transformation, 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, in the process of switching from the first interface to the second interface, the transition interface includes a shared element.

[0342] The presentation format of the shared element on the first interface is element 1, the presentation format 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.

[0343] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 36(a) to 36(g), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is a singer gradually lifting the microphone in his hand. This increases the fun and brings the user a more vivid interface switching experience.

[0344] In addition, the exit elements on the first interface execute a scaling dynamic effect to exit. For example, the exit elements are a category icon, at least one cover, a function button, etc. During interface switching, the scaling dynamic effect is executed to exit. The input elements on the second interface execute a slide-up dynamic effect to appear. For example, the input elements are a song list and a function icon, which fade in through a slide-up during interface switching.

[0345] Case 2: Application-to-application conversion: As shown in Figures 37(a) to 37(f), the following describes a method for performing inter-interface conversion based on the single-shot effect provided in this embodiment of the present application by using an example in which a user needs to switch to a gallery application when using a camera application.

[0346] When a user configures an inter-interface transformation solution between a camera application and a gallery application, the thumbnail button in the camera application is used as a shared element and is assumed to be continuously present in the transformation process.

[0347] For example, as shown in Figures 37(a) to 37(f), after a user taps a thumbnail icon in a camera application, an interface transformation between the camera application and the gallery application is triggered. In other words, the camera application can be understood as a first interface, and the gallery application interface can be understood as a second interface. The presentation format of the shared element on the first interface is Element 1, and the presentation format 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.

[0348] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 37(a) to 37(f), it can be seen 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, which increases the fun and brings the user a clearer interface switching experience.

[0349] Additionally, exit elements on the first interface fade out, and input elements on the second interface fade in. For example, after a camera application jumps to a gallery application to display a captured photo, the camera application's thumbnail button remains present, the capture interface disappears, and the photo in the gallery appears.

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

[0351] When a user configures an inter-interface conversion solution between the application desktop and the music application, the note element in the music application icon is used as a shared element and is assumed to be continuously present in the conversion process.

[0352] For example, as shown in Figures 38(a) to 38(f), after a user taps 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 format of the shared element on the first interface is Element 1, and the presentation format 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, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 38(a) to 38(f), it can be seen that in the process of gradual change from element 1 to element 2, the presented content gradually displays five line spectra on the music symbol, performing a smooth downward moving dynamic effect. This enhances the fun and brings the user a more vivid interface switching experience.

[0354] Additionally, the exit element on the first interface fades out. For example, the exit element is an icon of another application. During the interface switch, a fade-out dynamic effect is performed. The input element on the second interface fades in to acquire the music application interface.

[0355] Transformation Type 3: ViewGroup Transformation Type In this embodiment of the present application, the inter-interface conversion solution based on the ViewGroup conversion type can be further classified into several cases, such as inter-application conversion, intra-application conversion, and desktop-to-application conversion, etc., including but not limited to the following:

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

[0357] For example, as shown in Figures 39(a) to 39(f), when a calendar application starts inter-interface conversion, the icon of the month selected by the user is used as a shared element in the process of switching from the first interface to the second interface. 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 format of the shared element on the first interface is element 1, the presentation format 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.

[0359] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 39(a) to 39(f), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is the circular shadow of the August icon fading out. This increases the interest and brings the user a clearer interface switching experience.

[0360] Additionally, an end element on the first interface executes an amplifying dynamic effect to the end. For example, the end element is another month. During the interface transition, a scaling dynamic effect is executed to the end. An 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 the interface transition.

[0361] Case 2: Application-to-application conversion: As shown in Figures 40(a) to 40(g), the following describes a method for performing inter-interface conversion based on the single-shot effect provided in one embodiment of the present application by using an example in which a user needs to switch to a camera application when using a shopping application.

[0362] When a user configures an inter-interface transformation solution between a shopping application and a camera application, the capture button in the shopping application is used as a shared element and is assumed to be continuously present in the transformation process.

[0363] For example, as shown in Figures 40(a) to 40(g), after a user taps the photo icon in a 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 a first interface, and the camera application interface may be understood as a second interface. The presentation format of the shared element on the first interface is Element 1, and the presentation format 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.

[0364] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 40(a) to 40(g), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is the gradual extension of the camera lens. This increases the fun and brings the user a clearer interface switching experience.

[0365] In the process of the shopping application jumping to the camera application, the camera application's capture button remains active, the shopping interface fades out, and the camera interface fades in.

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

[0367] When a user configures an interface-to-interface transformation solution between the application desktop and the calendar application, the date element in the calendar application icon is used as a shared element and is assumed to be continuously present in the transformation process.

[0368] For example, as shown in Figures 41(a) to 41(f), after a user taps a calendar application icon on an application desktop, an interface conversion between the application desktop and the calendar application is triggered. In other words, the application desktop interface may be understood as a first interface, and the calendar application interface may be understood as a second interface. The presentation format of the shared element on the first interface is Element 1, and the presentation format 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.

[0369] Furthermore, in the process of switching from the first interface to the second interface, element 1 gradually changes to the presentation format of element 2. From Figures 41(a) to 41(f), it can be seen that in the process of element 1 gradually changing to element 2, the presented content is that the date element gradually displays a circular shadow, which increases the interest and brings the user a clearer interface switching experience.

[0370] In the process where an application desktop jumps to a calendar application, there is always a date that is used as a shared element.

[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, which 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, a user may need to perform split-screen operation on the mobile phone for reasons of operation convenience, etc. In this embodiment of the present application, in a split-screen operation scenario, the applications displayed on each screen can still implement the inter-interface conversion solution provided in the embodiment of the present application to reduce the user's visual jump width, increase the display interest, and improve the user experience.

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

[0374] In another example, as shown in Figure 43, it is assumed that the display interface of a mobile phone is divided into an upper layer and a lower layer, and the display interface of an application is suspended above 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 a user operates the gallery application on split-screen interface 1, the gallery application performs a corresponding conversion based on a preset inter-interface conversion solution. When a user operates the music application on split-screen interface 2, the music application performs a corresponding conversion based on a preset inter-interface conversion solution.

[0375] Preferably, the suspended application interface may be used as a shared element of the lowest layer application interface, so that when the lowest layer application interface is transformed, the suspended application interface is always present.

[0376] It should be noted that in this embodiment of the present application, in split-screen mode, interface conversion may be performed simultaneously for multiple screens based on corresponding inter-interface conversion solutions, and is not limited by conversion type or usage scenario. For example, 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 a system and an application. For details, please refer to the descriptions of Figures 20 to 41(f) in the embodiment of the present application.

[0377] Mode 2: Multi-screen collaboration mode When a user performs an operation on an application from time to time, screen switching may need to be performed. For example, when a user performs an operation on a gallery application by using a mobile phone to facilitate browsing, the mobile phone may be connected to a PC end, and 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 a user performs a multi-screen collaboration operation, 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, as shown in Figures 44(a) and 44(b). In other words, the operation of the mobile phone is changed to that of the PC side, and the display interface of the mobile phone is the same as that of the PC.

[0379] In another optional manner of this embodiment of the present application, when a 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 FIG. 45(a) and FIG. 45(b), the converted content and shared elements are displayed on the PC side, and the mobile phone side still keeps the display interface of the end interface.

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

[0382] For example, as shown in Figures 45(a) and 45(b), the PC side displays only the converted input interface and not the shared elements, while the mobile phone side displays the shared elements and the exit interface. In other words, in this case, the PC side is only used to enlarge and display the input interface, so that the user can see 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] It should be noted that in this embodiment of the present application, in the multi-screen collaboration mode, interface transformation may be performed simultaneously on multiple screens based on corresponding single-shot effects and is not limited by transformation type or usage scenario. For example, interface transformation may be performed based on different transformation types, such as Activity transformation type, ViewGroup transformation type, and Fragment transformation type, and may be performed within an application, between applications, or between the system and an application. For details, please refer to the descriptions of Figures 20 to 341 in the embodiment of the present application.

[0384] Based on the description of the implementation form, those skilled in the art can clearly understand that for the purpose of convenient and concise description, the division into the above-mentioned functional modules is used only as an example for explanation. During the application of the actual form, functions can be allocated 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 above-described functions. For the specific operation processes of the above-mentioned systems, devices, and units, please refer to the corresponding processes in the above-mentioned method embodiments, 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 exist physically alone, 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 this understanding, the technical solutions of the embodiments of the present application, or the portions contributing to the prior art, or all or part of the technical solutions, 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 perform all or part of the steps of the method described in the embodiments of the present application. The storage medium includes any medium that can store program code, such as a flash memory, a removable hard disk, a read-only memory, a random-access memory, a magnetic disk, or an optical disk.

[0387] The above description is merely a specific implementation of the embodiments of the present application and is not intended to limit the protection scope of the embodiments of the present application. Any modifications or substitutions 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. [Explanation of symbols]

[0388] 1 antenna 2 antennas 1100 Application side device 1100 Mobile Phone 1200 Platform Side Device 1210 processor 1220 memory 1230 transceiver 1240 Bus 100 mobile phones 110 processors 121 internal memory 130 USB interface 140 Charging Management Module 141 Charging Management Module 142 Battery 150 Mobile communication module 160 Wireless Communication Module 193 Camera 194 displays 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 Accelerometer 1180F Distance Sensor 1180G Optical Proximity 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. An interface conversion method applied to an electronic device, comprising: displaying, by the electronic device, a first interface 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, by the electronic device, at least one transition interface, and then displaying a second interface after detecting a second operation performed by the user on the first interface; Including, the second interface includes the second element and a third element, and the transition interface includes the second element; The method, wherein the second element does not include an element in the first interface, the transition interface, or a status bar on the second interface.

2. The step of displaying, by the electronic device, at least one transition interface and then displaying a second interface after detecting a second operation performed by the user on the first interface includes: fading out the first element on the first interface of the electronic device and fading in the third element on the second interface, allowing the second element to be continuously present on the first interface, the at least one transitional interface, and the second interface.

2. The method of claim 1, comprising:

3. executing, by the electronic device, dynamic effects corresponding to the interfaces and / or the elements in the process of switching from the first interface to the second interface based on the transformational dynamic effects configured for each interface or based on the transformational dynamic effects configured for the elements on the interfaces.

3. The method of claim 1 or 2, further comprising:

4. the first interface and the second interface are different display interfaces of a first application; or the first interface is a home screen, an interface adjacent to the home screen, or a left-most interface of the electronic device, 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.

4. The method of claim 1, further comprising:

5. An interface conversion method applied to an electronic device, comprising: determining, by the electronic device, an interface type based on an interface configuration command triggered by a user, the interface type including a first interface, at least one transition interface, and a second interface, the transition interface being an intermediate splicing interface from the first interface to the second interface; determining, by the electronic device, a first element and a second element on the first interface based on an element configuration command triggered by the user, and determining the second element and a third element on the second interface; Including, The transition interface includes the second element.

6. determining, by the electronic device, based on a dynamic effect configuration command triggered by the user, a dynamic effect to be executed by an interface and / or an element in the process of switching from the first interface to the second interface; 6. The method of claim 5, further comprising:

7. An interface conversion method applied to an electronic device, comprising: displaying, by the electronic device, a first interface 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, by the electronic device, at least one transition interface, and then displaying a second interface after detecting a second operation performed by the user on the first interface; Including, 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 the at least one transition interface, the presentation format of the second element on the transition interface gradually changes to the presentation format of the third element; The method, wherein the second element is partially the same as the third element.

8. The step of displaying, by the electronic device, at least one transition interface and then displaying a second interface after detecting a second operation performed by the user on the first interface includes: allowing the first element on the first interface of the electronic device to fade out, the fourth element on the second interface to fade in, and the second element on the transition interface to gradually change to the third element.

8. The method of claim 7, comprising:

9. executing, by the electronic device, dynamic effects corresponding to the interfaces and / or the elements in the process of switching from the first interface to the second interface based on the transformational dynamic effects configured for each interface or based on the transformational dynamic effects configured for the elements on the interfaces.

9. The method of claim 7 or 8, further comprising:

10. the first interface and the second interface are different display interfaces of a first application; or the first interface is a home screen, an interface adjacent to the home screen, or a left-most interface of the electronic device, 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.

10. The method of any one of claims 7 to 9, further comprising:

11. An interface conversion method applied to an electronic device, comprising: determining, by the electronic device, an interface type based on an interface configuration command triggered by a user, the interface type including a first interface, at least one transition interface, and a second interface, the transition interface being an intermediate splicing interface from the first interface to the second interface; determining, by the electronic device, 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 command triggered by the user; determining, by the electronic device, based on the element configuration command triggered by the user, that the second element gradually changes to the third element on the transition interface; Including, The method, wherein the second element is partially the same as the third element.

12. determining, by the electronic device, based on a dynamic effect configuration command triggered by the user, a dynamic effect to be executed by an interface and / or an element in the process of switching from the first interface to the second interface; 12. The method of claim 11, further comprising:

13. A method for inter-interface conversion, comprising: determining an interface to be transformed by the target application after receiving a user-triggered interface transformation instruction of the target application and shared elements included in the transformed interface; performing a conversion between corresponding interfaces based on the interface conversion instruction triggered by the user, wherein the shared elements on the converted interfaces are presented consecutively in an interface conversion process; A method comprising:

14. The conversion interface includes an exit interface and an input interface; or The conversion interface includes an exit interface, an input interface, and a shared interface; The method of claim 13 , wherein the ending interface is an initial interface during interface transformation, the input interface is a final interface during interface transformation, and the shared interface is an intermediate splicing interface during interface transformation.

15. determining an end element and / or an input element on the transformation interface, wherein the end element on the transformation interface disappears after the transformation interface is transformed, and the input element on the transformation interface appears after the transformation interface is transformed into the input interface; 15. The method of claim 13 or 14, further comprising:

16. Executing a corresponding dynamic effect in the transformation process based on the transformation dynamic effect configured for each interface on the transformation interface and / or based on the transformation dynamic effect configured for each element on the transformation interface.

16. The method of any one of claims 13 to 15, further comprising:

17. A method for inter-interface conversion, comprising: determining an interface type for conversion based on an interface conversion configuration command triggered by a user, the interface type including an end interface, an input interface, and a shared interface, the end interface referring to an initial interface during interface conversion, the input interface referring to a final interface during interface conversion, and the shared interface referring to an intermediate splicing interface during interface conversion; determining shared elements in an interface transformation process based on an element configuration command triggered by the user, the shared elements being elements that are presented consecutively in the interface transformation process; A method comprising:

18. determining an end element and / or an input element in an interface transformation process based on the element configuration command triggered by the user; further comprising 18. The method of claim 17, wherein the exit element on the transformation interface disappears after the exit interface is transformed, and the input element on the transformation interface appears after the exit interface is transformed into the input interface.

19. 1. An electronic device comprising: a display, one or more processors, and one or more memories; 17. An electronic device, wherein the one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, enable the electronic device to perform the method of any one of claims 1 to 4, the method of claim 5 or 6, the method of any one of claims 7 to 10, the method of claim 11 or 12, the method of any one of claims 13 to 16, or the method of claim 17 or 18.

20. 13. A computer-readable storage medium having stored thereon a computer program that, when executed on an electronic device, enables the electronic device to perform the method of any one of claims 1 to 4, the method of claim 5 or 6, the method of any one of claims 7 to 10, the method of claim 11 or 12, the method of any one of claims 13 to 16, or the method of claim 17 or 18.

21. 19. A graphical user interface system on an electronic device, the electronic device comprising: a display; one or more memories; and one or more processors, the one or more processors 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 a method according to any one of claims 1 to 18.

Images