Seamless transition method and device of application interface, storage medium and electronic equipment

By taking screenshots of the interface in the application and playing transition animations, the jitter problem during dynamic interface transitions is solved, and a jitter-free page transition is achieved, which improves the user experience.

CN118916104APending Publication Date: 2024-11-08SHENZHEN BREO TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311375676.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-10-19
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In applications, the interface jitters due to the zoom of view controls during dynamic interface transitions, which affects the user experience. The existing technology has not effectively solved this problem.

Method used

By detecting the transition instructions, the interface screenshot of the first dynamic interface is taken and played to the second dynamic interface in the form of a transition animation, avoiding the view component from constantly scaling when adapting to the size, and achieving a jitter-free page transition.

Benefits of technology

The page transition effect without jitter is realized, which improves the user experience and solves the problem of screen jitter during dynamic interface transitions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916104A_ABST
    Figure CN118916104A_ABST
Patent Text Reader

Abstract

The invention provides a seamless transition method and device for an application interface, a storage medium and electronic equipment, and the method comprises the steps that a transition instruction is detected on a first dynamic interface of an application program, and the transition instruction is used for indicating transition from the first dynamic interface of the application program to a second dynamic interface of the application program; in response to the transition instruction, intercepting an interface screenshot of the first dynamic interface of a view component, and playing a transition animation between the first dynamic interface and the second dynamic interface by adopting the interface screenshot; and after the transition animation is played, displaying the second dynamic interface on the current interface of the application program. Through the embodiment of the invention, the view component is prevented from being continuously zoomed during transition adaptive size, a jitter-free page transition special effect is realized, and the technical problem of picture jitter during transition between two dynamic interfaces in related technologies is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of sensors, and in particular to a method and device for seamlessly transitioning an application interface, a storage medium, and an electronic device. Background Art

[0002] In the related technology, in the interface of the application, for example, pulling down on Taobao to enter the second floor, pulling down on the JD homepage to enter a new page, and pulling down on the WeChat homepage to enter the mini program, all push to the next interface, and need to execute the transition between the two interfaces.

[0003] In the related technology, a view control is used in an APP to load a dynamic interface on the home page. Since the dynamic interface needs to change in real time, during the transition and adaptation switching process, in order to adapt to the different UI sizes, the view control is enlarged or reduced, which will cause the h5 content to be updated in real time, resulting in jitter, affecting the smoothness of the interface transition and poor user experience.

[0004] With respect to the above-mentioned problems existing in the related technologies, no efficient and accurate solutions have been found yet. Summary of the invention

[0005] The present invention provides a method and device for seamless transition of an application interface, a storage medium, and an electronic device to solve the above-mentioned technical problems existing in the related art.

[0006] According to one embodiment of the present invention, a method for seamless transition of an application interface is provided, comprising: detecting a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to indicate a transition from the first dynamic interface of the application to a second dynamic interface of the application; in response to the transition instruction, capturing an interface screenshot of the first dynamic interface of a view component, and using the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface; and after the transition animation is played, displaying the second dynamic interface on the current interface of the application.

[0007] Optionally, detecting a transition instruction in the first dynamic interface of the application includes at least one of the following: detecting a click instruction for a specified interface element in the first dynamic interface of the application, and generating a first transition instruction based on the click instruction, wherein the first dynamic interface includes the specified interface element; detecting a specified operation in the first dynamic interface of the application, and triggering generation of a second transition instruction based on the specified operation.

[0008] Optionally, using the interface screenshot to play the transition animation between the first dynamic interface and the second dynamic interface includes: searching for the parent view of the view component, wherein the child view of the parent view includes the view component; setting the child view currently displayed under the parent view as the interface screenshot; determining the display size of the second dynamic interface; taking the initial size of the interface screenshot as the starting size and the display size as the ending size, scaling the interface screenshot at a preset playback rate until the current size of the interface screenshot is scaled to the ending size, and the transition animation playback is completed.

[0009] Optionally, setting the sub-view currently displayed under the parent view as the interface screenshot includes: adding the interface screenshot as a sub-view of the parent view; setting the properties of the view component to a hidden state, and setting the properties of the interface screenshot to a displayed state.

[0010] Optionally, displaying the second dynamic interface on the current interface of the application includes: reading rendering parameters of the second dynamic interface; and controlling the view component to display the second dynamic interface on the current interface of the application using the rendering parameters.

[0011] Optionally, controlling the view component to use the rendering parameters to display the second dynamic interface on the current interface of the application includes: hiding the interface screenshot on the current interface of the application and displaying the view component; controlling the view component to use the rendering parameters to display the second dynamic interface.

[0012] Optionally, the first dynamic interface includes a first element set, and the second dynamic interface includes a second element set, and the second element set includes a number of display elements in the first element set.

[0013] According to another embodiment of the present invention, a seamless transition device for an application interface is provided, comprising: a detection module, used to detect a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to indicate a transition from the first dynamic interface of the application to a second dynamic interface of the application; a transition module, used to respond to the transition instruction, capture an interface screenshot of the first dynamic interface of a view component, and use the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface; and a display module, used to display the second dynamic interface on the current interface of the application after the transition animation is played.

[0014] Optionally, the detection module includes at least one of the following: a first detection unit, used to detect a click instruction for a specified interface element in the first dynamic interface of the application, and generate a first transition instruction based on the click instruction, wherein the first dynamic interface includes the specified interface element; a second detection unit, used to detect a specified operation in the first dynamic interface of the application, and trigger generation of a second transition instruction based on the specified operation.

[0015] Optionally, the transition module includes: a searching unit for searching for a parent view of the view component, wherein the child view of the parent view includes the view component; a setting unit for setting the child view currently displayed under the parent view as the interface screenshot; a determining unit for determining the display size of the second dynamic interface; and a playing unit for scaling the interface screenshot at a preset playback rate with the initial size of the interface screenshot as the starting size and the display size as the ending size until the current size of the interface screenshot is scaled to the ending size and the transition animation is played.

[0016] Optionally, the setting unit includes: an adding sub-unit, used to add the interface screenshot as a sub-view of the parent view; a setting sub-unit, used to set the properties of the view component to a hidden state, and set the properties of the interface screenshot to a displayed state.

[0017] Optionally, the display module includes: a reading unit, used to read rendering parameters of the second dynamic interface; and a control unit, used to control the view component to use the rendering parameters to display the second dynamic interface on the current interface of the application.

[0018] Optionally, the control unit includes: a processing subunit, used to hide the interface screenshot in the current interface of the application and display the view component; and a display subunit, used to control the view component to display the second dynamic interface using the rendering parameters.

[0019] Optionally, the first dynamic interface includes a first element set, and the second dynamic interface includes a second element set, and the second element set includes a number of display elements in the first element set.

[0020] According to yet another embodiment of the present invention, a storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above-mentioned device embodiments when running.

[0021] According to another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above-mentioned device embodiments.

[0022] Through the embodiments of the present invention, a transition instruction is detected in the first dynamic interface of the application, wherein the transition instruction is used to indicate a transition from the first dynamic interface of the application to the second dynamic interface of the application. In response to the transition instruction, an interface screenshot of the first dynamic interface of the view component is captured, and the interface screenshot is used to play the transition animation between the first dynamic interface and the second dynamic interface. After the transition animation is played, the second dynamic interface is displayed on the current interface of the application. By using the interface screenshot of the dynamic interface to play the transition animation, continuous scaling of the view component when the transition adapts to the size is avoided, a jitter-free page transition special effect is achieved, and the technical problem of screen jitter when transitioning between two dynamic interfaces in the related technology is solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0024] Figure 1 is a hardware structure block diagram of a mobile phone according to an embodiment of the present invention;

[0025] Figure 2 is a flow chart of a method for seamless transition of an application interface according to an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of a first dynamic interface and a second dynamic interface in an embodiment of the present invention;

[0027] Figure 4 is an implementation flow chart of an embodiment of the present invention;

[0028] Figure 5 The present invention is a structural block diagram of a seamless transition device for an application interface according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only embodiments of a part of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present application. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Example 1

[0032] The method embodiment provided in the first embodiment of the present application can be executed in a mobile phone, a computer, a tablet, a health device, a massager or a similar display device. Taking running on a mobile phone as an example, Figure 1 FIG. 1 is a hardware structure diagram of a mobile phone according to an embodiment of the present invention. Figure 1 As shown, the mobile phone may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Optionally, the mobile phone may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the mobile phone. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0033] The memory 104 can be used to store mobile phone programs, for example, software programs and modules of application software, such as a mobile phone program corresponding to a seamless transition method of an application interface in an embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the mobile phone program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile phone via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0034] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile phone. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0035] In this embodiment, a method for seamless transition of an application interface is provided. Figure 2 is a flow chart of a method for seamless transition of an application interface according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0036] Step S202, detecting a transition instruction in a first dynamic interface of the application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application;

[0037] The first dynamic interface and the second dynamic interface of this embodiment are interfaces of view components that load small windows (window views) in a parent view (such as the main interface of an application). Optionally, the interfaces (first dynamic interface and second dynamic interface) of this embodiment can be display interfaces of health devices, control interfaces of remotely controlled health devices, or meridian introduction interfaces. Health devices can be neck massagers, massage chairs, neck mask guns, moxibustion devices, etc. The second dynamic interface can be larger than the display size of the first dynamic interface.

[0038] Optionally, the transition instruction can be an instruction triggered by a touch gesture, such as an instruction triggered by a selection operation, a click operation, a pull-down operation, etc., or it can be an instruction triggered by a non-touch gesture, such as an air operation gesture.

[0039] In one example, the first dynamic interface includes a first element set, the second dynamic interface includes a second element set, and the second element set includes several display elements in the first element set. For example, the first dynamic interface includes 3 display elements, namely a, b, and c, and the second dynamic interface includes 4 display elements, namely a, d, e, and f. Both the first dynamic interface and the second dynamic interface include display element a.

[0040] Figure 3It is a schematic diagram of the first dynamic interface and the second dynamic interface in an embodiment of the present invention. The first dynamic interface is a thumbnail human meridian model diagram. The view component is used to load the 3D human meridian model in the upper right corner of the application homepage. The second dynamic interface is a complete human meridian model diagram, including the meridian flow on the human body model and the meridian data at the bottom. The display size of the second dynamic interface is the full-screen size.

[0041] Step S204, responding to the transition instruction, capturing a screenshot of the first dynamic interface of the view component, and using the screenshot to play a transition animation between the first dynamic interface and the second dynamic interface;

[0042] In an application scenario of this embodiment, there is a human body model on the home page, and the display interface of the human body model is the first dynamic interface, which is displayed synchronously with the home page of the app. If you pull down or click to trigger the transition instruction, the interface is pushed down, and the human body model slowly enlarges and transitions to the complete interface of the human body model (the second dynamic interface), thereby realizing the transition special effect.

[0043] Optionally, the view component may be a component such as WKWebview that can implement page display on a terminal.

[0044] During the transition process, a screenshot of the first dynamic interface is used to create and play the transition animation to avoid page jitter caused by the view component constantly updating the H5 content in real time when adapting to the display size of the second dynamic interface.

[0045] Step S206, after the transition animation is played, the second dynamic interface is displayed on the current interface of the application.

[0046] Through the above steps, a transition instruction is detected in the first dynamic interface of the application, wherein the transition instruction is used to indicate a transition from the first dynamic interface of the application to the second dynamic interface of the application. In response to the transition instruction, an interface screenshot of the first dynamic interface of the view component is captured, and the interface screenshot is used to play the transition animation between the first dynamic interface and the second dynamic interface. After the transition animation is played, the second dynamic interface is displayed on the current interface of the application. By using the interface screenshot of the dynamic interface to play the transition animation, the continuous scaling of the view component when the transition adapts to the size is avoided, a jitter-free page transition effect is achieved, and the technical problem of screen jitter when transitioning between two dynamic interfaces in the related technology is solved.

[0047] In one implementation of the present embodiment, detecting a transition instruction in the first dynamic interface of the application may be, but is not limited to: detecting a click instruction for a specified interface element in the first dynamic interface of the application, and generating a first transition instruction based on the click instruction, wherein the first dynamic interface includes the specified interface element; detecting a specified operation in the first dynamic interface of the application, and triggering generation of a second transition instruction based on the specified operation.

[0048] Optionally, the specified operation may be, but is not limited to, a pull-down operation, a pull-up operation, a left swipe operation, a right swipe operation, etc.

[0049] In an implementation scenario of this embodiment, using interface screenshots to play the transition animation between the first dynamic interface and the second dynamic interface includes:

[0050] S11, searching for a parent view of the view component, wherein the child view of the parent view includes the view component;

[0051] Optionally, the parent view of the view component can be the home view (home page view). The view component is mounted on the home view. When the application is started and the home view is opened, its child view is loaded synchronously, that is, the view of the view component is loaded.

[0052] S12, setting the subview currently displayed under the parent view as the interface screenshot;

[0053] In one example, setting the subview currently displayed under the parent view as an interface screenshot includes: adding the interface screenshot as a subview of the parent view; setting the properties of the view component to a hidden state, and setting the properties of the interface screenshot to a displayed state.

[0054] The subview in this embodiment can be set to display and hide two states. In the hidden state, the corresponding subview is not displayed on the screen UI, and in the displayed state, the corresponding subview is displayed on the screen UI. By adding the interface screenshot to the same parent view as the view component and displaying it, and setting the properties of the view component to the hidden state, after the transition animation ends, the properties of the interface screenshot are set to the hidden state, and the properties of the view component are set to the displayed state, flexible switching between the two subviews can be achieved.

[0055] S13, determining a display size of the second dynamic interface;

[0056] S14, taking the initial size of the interface screenshot as the starting size and the display size as the ending size, scaling the interface screenshot according to a preset playback rate until the current size of the interface screenshot is scaled to the ending size, and the transition animation playback is completed.

[0057] In an example, the initial size of the interface screenshot is 1*1, and the display size of the second dynamic interface is 6*6. Taking the preset playback rate of 1 frame / minute / second as an example, the playback time of the transition animation is 1 second (1 second = 10 minutes and seconds). Then, the size of the display frame of the view component needs to be enlarged from 1*1 to 6*6 within 1 second, and 10 frames of interface screenshots with different zoom sizes need to be played, namely 1.5*1.5, 2*2, 2.5*2.5, 3*3, 3.5*3.5, 4*4, 4.5*4.5, 5*5, 5.5*5.5, and 6*6. When the 6*6 interface screenshot is played, the transition animation is completed, and the 6*6 interface screenshot is switched to the second dynamic interface of 6*6 to complete the interface transition.

[0058] In this embodiment, displaying the second dynamic interface on the current interface of the application includes: reading rendering parameters of the second dynamic interface; and controlling the view component to display the second dynamic interface on the current interface of the application using the rendering parameters.

[0059] Optionally, the rendering parameters of the second dynamic interface are related to the rendering parameters of the first dynamic interface. When the first dynamic interface is displayed, the rendering parameters of some display elements are in a hidden state, so only some display elements can be displayed. When the second dynamic interface needs to be displayed, the display elements in the hidden state in the first dynamic interface are updated to a displayed state to obtain the rendering parameters of the second dynamic interface, thereby avoiding re-reading the rendering parameters and reducing data transmission time.

[0060] Optionally, controlling the view component to use rendering parameters to display the second dynamic interface on the current interface of the application includes: hiding the interface screenshot on the current interface of the application and displaying the view component; controlling the view component to use rendering parameters to display the second dynamic interface.

[0061] The interface screenshot and view component in this embodiment are two sub-views of the same level under the same parent view. The sub-view can be set to display and hide. In the hidden state, the corresponding sub-view is not displayed on the screen UI. In the displayed state, the corresponding sub-view is displayed on the screen UI. By adding the interface screenshot to the same parent view as the view component and displaying it, and setting the properties of the view component to the hidden state, after the transition animation ends, the properties of the interface screenshot are set to the hidden state, and the properties of the view component are set to the displayed state, flexible switching between the two sub-views can be achieved.

[0062] Figure 4It is an implementation flow chart of an embodiment of the present invention. In the APP of the iOS operating system, the WKWebview control is used to load the 3D human meridian model (the first dynamic interface) in the upper right corner of the homepage, and the human body model is dynamic and rotates at all times. Since the model needs to be changed from small to large, during the adaptation switching process, the human meridian model will shake in the related technology, and the user experience is poor. Now in order to solve this problem, the solution of this embodiment is to capture the current WKWebview screen when the transition animation starts to play when the transition is released or clicked, and then the screenshot is added to the same parent view and displayed, and the WKWebview attribute is set to hidden at the same time. After the transition animation is played, the screenshot attribute is hidden, and the WKWebview attribute is set to display state to achieve flexible switching, so that the model shaking problem during the transition process is solved.

[0063] By adopting the solution of this embodiment, a new transition effect is created to handle the jitter effect caused by zooming in and out of the view component. The first dynamic interface displayed on the homepage, with the transition effect, seamlessly transitions to the second dynamic interface, achieving a good user experience. For applications on operating systems such as iOS, when the small window loaded on the web needs to be adapted to zoom in and out, a solution to jitter is provided.

[0064] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0065] Example 2

[0066] In this embodiment, a seamless transition device for an application interface is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" may be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0067] Figure 5 is a structural block diagram of a seamless transition device for an application interface according to an embodiment of the present invention. Figure 5 As shown, the device comprises:

[0068] A detection module 50, configured to detect a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application;

[0069] A transition module 52, configured to respond to the transition instruction, capture an interface screenshot of the first dynamic interface of the view component, and use the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface;

[0070] The display module 54 is used to display the second dynamic interface on the current interface of the application after the transition animation is played.

[0071] Optionally, the detection module includes at least one of the following: a first detection unit, used to detect a click instruction for a specified interface element in the first dynamic interface of the application, and generate a first transition instruction based on the click instruction, wherein the first dynamic interface includes the specified interface element; a second detection unit, used to detect a specified operation in the first dynamic interface of the application, and trigger generation of a second transition instruction based on the specified operation.

[0072] Optionally, the transition module includes: a searching unit for searching for a parent view of the view component, wherein the child view of the parent view includes the view component; a setting unit for setting the child view currently displayed under the parent view as the interface screenshot; a determining unit for determining the display size of the second dynamic interface; and a playing unit for scaling the interface screenshot at a preset playback rate with the initial size of the interface screenshot as the starting size and the display size as the ending size until the current size of the interface screenshot is scaled to the ending size and the transition animation is played.

[0073] Optionally, the setting unit includes: an adding sub-unit, used to add the interface screenshot as a sub-view of the parent view; a setting sub-unit, used to set the properties of the view component to a hidden state, and set the properties of the interface screenshot to a displayed state.

[0074] Optionally, the display module includes: a reading unit, used to read rendering parameters of the second dynamic interface; and a control unit, used to control the view component to use the rendering parameters to display the second dynamic interface on the current interface of the application.

[0075] Optionally, the control unit includes: a processing subunit, used to hide the interface screenshot in the current interface of the application and display the view component; and a display subunit, used to control the view component to display the second dynamic interface using the rendering parameters.

[0076] Optionally, the first dynamic interface includes a first element set, and the second dynamic interface includes a second element set, and the second element set includes a number of display elements in the first element set.

[0077] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0078] Example 3

[0079] An embodiment of the present invention further provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0080] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0081] S1, detecting a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application;

[0082] S2, responding to the transition instruction, capturing an interface screenshot of the first dynamic interface of the view component, and using the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface;

[0083] S3, after the transition animation is played, display the second dynamic interface on the current interface of the application.

[0084] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0085] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0086] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0087] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0088] S1, detecting a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application;

[0089] S2, responding to the transition instruction, capturing an interface screenshot of the first dynamic interface of the view component, and using the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface;

[0090] S3, after the transition animation is played, display the second dynamic interface on the current interface of the application.

[0091] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0092] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0093] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0094] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0096] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0097] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0098] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for seamless transition of an application interface, characterized in that: include: Detecting a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application; In response to the transition instruction, capturing an interface screenshot of the first dynamic interface of the view component, and using the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface; After the transition animation is played, the second dynamic interface is displayed on the current interface of the application.

2. The method according to claim 1, characterized in that Detecting a transition instruction in the first dynamic interface of the application includes at least one of the following: Detecting a click instruction for a designated interface element in a first dynamic interface of the application program, and generating a first transition instruction based on the click instruction, wherein the first dynamic interface includes the designated interface element; A designated operation is detected in a first dynamic interface of the application program, and a second transition instruction is triggered to be generated based on the designated operation.

3. The method according to claim 1, characterized in that Using the interface screenshot to play the transition animation between the first dynamic interface and the second dynamic interface includes: Finding a parent view of the view component, wherein a child view of the parent view includes the view component; Setting the subview currently displayed under the parent view as the interface screenshot; Determining a display size of the second dynamic interface; The initial size of the interface screenshot is used as the starting size, the display size is used as the ending size, and the interface screenshot is scaled according to a preset playback rate until the current size of the interface screenshot is scaled to the ending size, and the transition animation playback is completed.

4. The method according to claim 3, characterized in that Setting the subview currently displayed under the parent view as the interface screenshot includes: Add the interface screenshot as a subview of the parent view; The property of the view component is set to a hidden state, and the property of the interface screenshot is set to a displayed state.

5. The method according to claim 1, characterized in that Displaying the second dynamic interface on the current interface of the application includes: Reading rendering parameters of the second dynamic interface; The view component is controlled to use the rendering parameters to display the second dynamic interface on the current interface of the application.

6. The method according to claim 5, characterized in that Controlling the view component to display the second dynamic interface on the current interface of the application using the rendering parameters includes: Hide the interface screenshot in the current interface of the application and display the view component; Control the view component to display the second dynamic interface using the rendering parameters.

7. The method according to any one of claims 1 to 6, characterized in that: The first dynamic interface includes a first element set, and the second dynamic interface includes a second element set, and the second element set includes a number of display elements in the first element set.

8. A seamless transition device for an application interface, characterized in that: include: A detection module, used to detect a transition instruction in a first dynamic interface of an application, wherein the transition instruction is used to instruct a transition from the first dynamic interface of the application to a second dynamic interface of the application; A transition module, configured to respond to the transition instruction, capture an interface screenshot of the first dynamic interface of the view component, and use the interface screenshot to play a transition animation between the first dynamic interface and the second dynamic interface; A display module is used to display the second dynamic interface on the current interface of the application after the transition animation is played.

9. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 7.