Based on this embodiment of this application, in a desktop mode of a mobile phone, when an application that is being displayed on the mobile phone is started on the PC side, the application may continue to retain a state before switching, for example, a play record or a document reading position. In this way, continuity of switching an application from one screen to another screen can be implemented, to avoid restarting the application and affecting user experience.

FIG. 2(a)-1 to FIG. 2(b)-2 are schematic diagrams of another group of GUIs according to an embodiment of this application. FIG. 2(a)-1 to FIG. 2(b)-2 show a process in which a mobile phone switches a display screen of an application in a desktop mode.

With reference to FIG. 2(a)-1 and FIG. 2(a)-2, the GUIs show a display desktop 210 of a mobile phone 200a and a display interface 220 of a PC 200b.

The display desktop 210 of the mobile phone may include application icons of a plurality of applications installed on the mobile phone, such as Music, Email, Health, and AI life.

The display interface 220 of the PC may include a search box, an application bar, a display interface 230 of an APP 1 and a display interface 240) of an APP 1. The APP 1 may be a document application, and the display interface 230 and the display interface 240 may be two documents opened on the PC.

As shown in FIG. 2(a)-1 and FIG. 2(a)-2, the display interface 230 includes a title bar 230a and a content display section 230b. The title bar 230a may include a text “APP 1”, and controls that can control the display interface 230, such as a minimize control 231, a maximize control 232, and a close control 233. The content display section 230b may include a title section of a document 1 and a content section of the document 1.

Similarly, the display interface 240 includes a title bar 240a and a content display section 240b. The title bar 240a may include a text “APP 1”, and controls that can control the display interface 240, such as a minimize control 241, a maximize control 242, and a close control 243. The content display section 240b may include a title section of a document 2 and a content section of the document 2.

In this embodiment of this application, a user may first open the document 1 and then open the document 2, that is, a newly opened document is the document 2.

After the mobile phone detects an operation of tapping an application icon 211 of the APP 1 by the user, the mobile phone and the PC may display GUIs shown in FIG. 2(b)-1 and FIG. 2(b)-2.

It should be understood that, in this embodiment, when the display interface 230 and the display interface 240 of the APP 1 are opened on the PC 200b, the display interface 230 and the display interface 240 may be respectively located in different activity stacks (activity stack). For example, the display interface 230 is located in an activity stack 1, and the display interface 240 is located in an activity stack 2. The activity stack 1 may include a task 1, and the task 1 may include an activity 1 corresponding to the display interface 230. The activity stack 2 may include a task 2, and the task 2 may include an activity 2 corresponding to the display interface 240.

Because the user opens the display interface 230 and the display interface 240 at different times, for example, the user first opens the display interface 230 and then opens the display interface 240, levels corresponding to the activity stack 1 and the activity stack 2 are different. In other words, a level of the activity stack 1 is lower than a level of the activity stack 2, that is, a level of an activity stack corresponding to a newly opened display interface is higher. The level may be understood as a display sequence of the PC, that is, the PC displays an interface corresponding to an activity stack with a higher level.

In this embodiment of this application, because a screen of the PC is larger, a plurality of display interfaces of the APP 1 may be displayed. Although both the display interface 230 and the display interface 240 are displayed on the screen of the PC, the two display interfaces correspond to different levels.

In some possible embodiments, after the mobile phone detects the operation of tapping the application icon 211 of the APP 1 by the user, the mobile phone may migrate, from the PC to the mobile phone for display, a display interface corresponding to an activity stack with a higher level.

For example, a display interface newly opened by the user is the display interface 240, that is, a level of the activity stack 2 corresponding to the display interface 240 is higher. After detecting the operation of tapping the application icon 211 of the APP 1 by the user, the mobile phone may migrate content included in the activity stack 2 corresponding to the display interface 240 to a newly created activity stack 3 in the mobile phone. The content in the activity stack 2 may include a corresponding task and activity, so that the display interface 240 may be migrated to the mobile phone for display, thereby retaining the display interface 240, and avoiding a data loss caused by restart of the APP 1.

In some possible embodiments, after the mobile phone detects the operation of tapping the application icon 211 of the APP 1 by the user, the mobile phone may alternatively migrate display interfaces corresponding to a plurality of activity stacks of the APP 1 to the mobile phone for display:

For example, the mobile phone may migrate the display interface 230 and the display interface 240) to the mobile phone for display, for example, in a split-screen display mode or in a mode of preferably displaying the display interface 240 and displaying the display interface 230 after the display interface 240 is closed.

In some possible embodiments, after the mobile phone detects the operation of tapping the application icon 211 of the APP 1 by the user, the mobile phone may pop up a prompt box, and the user may select either of the display interface 230 and the display interface 240 to be migrated to the mobile phone for display.

Alternatively, the user may select the display interface 230 and the display interface 240 to be migrated to the mobile phone for display. In this way; the display interface 230 and the display interface 240) may be displayed in a split-screen mode in the mobile phone. In this case, both the display interface 230 and the display interface 240 may be displayed in a current interface of the mobile phone. Alternatively, the mobile phone may preferably display the display interface 240) corresponding to an activity stack with a higher level, and place the display interface 230 on a background. In other words, the mobile phone may display the display interface 230 after the display interface 240 is closed.

In some other embodiments, a display interface newly opened by the user is the display interface 240). After the mobile phone detects the operation of tapping the application icon 211 of the APP 1 by the user, the mobile phone may migrate the content included in the activity stack 2 corresponding to the display interface 240 to the mobile phone for display, that is, the mobile 35 phone does not need to create the activity stack 3.

With reference to FIG. 2(b)-1 and FIG. 2(b)-2, the GUIs show a display interface 250 of a mobile phone 200a and a display interface 260 of a PC 200b.

The display interface 250 of the mobile phone 200a may display content of a newly opened document, that is, content of a display interface 240b is displayed in the display interface 250, including a title section of a document 2 and a content section of the document 2.

The display interface 260 of the PC 200b includes a display interface 230.

It should be understood that, in this embodiment of this application, the PC may also open three or more documents of the APP 1. In this case, when the user starts the APP 1 on the mobile phone, the mobile phone may also display an interface of a newly opened document.

It should be understood that, in this embodiment of this application, the display interface 230 of the document 1 may retain an original position of the document 1 on a screen of the PC, or the display interface 230 of the document 1 may be moved to the middle of the screen of the PC for display, or the display interface 230 of the document 1 may be displayed on another position of the screen of the PC. This is not limited in this embodiment of this application.

Based on this embodiment of this application, when a plurality of interfaces of a same application are displayed on a PC, and the plurality of interfaces are displayed in a plurality of windows, for example, two or more documents, when the application is started on a mobile phone, an interface of a newly opened document is displayed on a screen of the mobile phone. In this technical solution, application restart is avoided, and continuity of switching an application from one screen to another screen can be implemented.

FIG. 3(a)-1 to FIG. 3(b)-2 are schematic diagrams of another group of GUIs according to an embodiment of this application. FIG. 3(a)-1 to FIG. 3(b)-2 show a process in which a mobile phone switches a display screen of an application in a desktop mode.

With reference to FIG. 3(a)-1 and FIG. 3(a)-2, the GUIs show a display interface 310 of a mobile phone 300a and a display interface 320 of a PC 300b.

The display interface 310 of the mobile phone 300a may be a home page display interface of an APP 1. The display interface 310 may include the APP 1, a search box, a function bar 310a, and the like, and an interface corresponding to “Recently opened” on the function bar. Content included in the interface corresponding to “Recently opened” may include a display area 311 and a display area 312. The display area 311 may include an icon of the APP 1, a title of a document 2, and some function controls such as “Favorites”. The display area 312 may include an icon of an APP 2, a title of a document 1, and some function controls such as “Favorites”.

The display interface 320 of the PC 300b may include a status bar, a search box, an application bar, and a display interface 330 and a display interface 340 of the APP 1. The status bar may include a signal indicator, a battery level, a time, and the like of the mobile phone. The APP 1 may be a document application, and the display interface 330 and the display interface 340 may be two documents opened on the PC.

The display interface 330 may include a title bar 330a and a content display section 330b. The title bar 330a may include a text “APP 1”, and controls that can control the display interface 330a, such as a minimize control 331, a maximize control 332, and a close control 333. The content display section 330b may include a title section of the document 1 and a content section of the document 1.

Similarly, the display interface 340) may include a title bar 340a and a content display section 340b. The title bar 340a may include a text “APP 1”, and controls that can control the display interface 340a, such as a minimize control 341, a maximize control 342, and a close control 343. The content display section 340b may include a title section of the document 2 and a content section of the document 2.

After the mobile phone 330a detects an operation of tapping the display area 312 by a user, the mobile phone 300a and the PC 300b may display GUIs shown in FIG. 3(b)-1 and FIG. 3(b)-2.

It should be understood that, in this embodiment, when the display interface 330 and the display interface 340 of the APP 1 are opened on the PC 300b, the display interface 330 and the display interface 340) may be respectively located in different activity stacks. For example, the display interface 330 is located in an activity stack 1, and the display interface 340 is located in an activity stack 2. The activity stack 1 may include a task 1, and the task 1 may include an activity 1 corresponding to the display interface 330. The activity stack 2 may include a task 2, and the task 2 may include an activity 2 corresponding to the display interface 340.

When the user taps the display area 312, the mobile phone may match, from windows that have been opened, a window displayed after the display area 312 is tapped. For example, the matching may be performed based on information such as a package name of a started application. UID of a started application, and an activity corresponding to a started application. When the matched window is the display interface 340, content in the activity stack 2 is migrated to a newly created activity stack 3 in the mobile phone, thereby retaining the display interface 340, and avoiding a data loss caused by restart of the APP 1.

In some other embodiments, the mobile phone may not need to create the new activity stack 3. In this case, when matching the display interface 340, the mobile phone directly migrates the display interface 340 to the mobile phone for display.

With reference to FIG. 3(b)-1 and FIG. 3(b)-2, the GUIs show a display interface 350 of a mobile phone 300a and a display interface 360 of a PC 300b.

Content displayed in the display interface 350 of the mobile phone 300a is the same as that displayed in the display interface 330b, that is, content of the display interface 330b is displayed on a screen of the mobile phone 300a, and includes a title section and a content section of a document 1.

The display interface 360 of the PC 300b includes a display interface 340.

It should be understood that the display interface 340 may retain an original position of the display interface 340 on a screen of the PC, or the display interface 340 may be moved to the middle of the screen of the PC for display, or the display interface 340 may be displayed on another position of the screen of the PC. This is not limited in this embodiment of this application.

In this embodiment of this application, when a plurality of interfaces of a same application are displayed on a PC, and the plurality of interfaces are displayed in a plurality of windows, for example, two or more documents, when the document is opened in an application interface of a mobile phone, a matched document interface is displayed on a screen of the mobile phone. In this technical solution, application restart is avoided, and continuity of switching an application from one screen to another screen can be implemented.

FIG. 4 is a schematic diagram of display interface switching in a display method according to an embodiment of this application. In this embodiment of this application, an activity stack (activity stack) 1 belongs to a mobile phone side, and an activity stack 2 also belongs to the mobile phone side. An example in which the mobile phone is in a desktop mode and is projected 20) to a PC is used for description.

With reference to (a) in FIG. 4, the activity stack 1 may include one or more tasks, and the task may include a plurality of activities 1 and activities 2.

In an Android system, most of content viewed by a user in an application is provided by an activity component. An application may include a plurality of activities. For example, after the user taps an icon of an application, an activity 1 is started, and a home page of the application is displayed in a display interface of an electronic device. After the user taps an element on the home page, it may be considered that an activity 2 is started, and the display interface of the electronic device is switched from the home page of the application to another interface. In other words, an interface corresponding to the activity 2 covers an interface corresponding to the activity 1, so that the user can view only a current display interface. The activity 2 is located at the top of an activity stack. To be specific, the interface corresponding to the activity 2 may be presented to the user, and some operations of the user may be directly received.

For example, with reference to FIG. 1(a)-1 and FIG. 1(a)-2, a display interface 110 of the mobile phone may be considered as an interface corresponding to the activity 2. Before the activity 2 is started, when the user taps an application icon of HUAWEI Video on a desktop of the mobile phone, it may be considered that the activity 1 is started. An interface corresponding to the activity 1 is a home page display interface of HUAWEI Video. In this case, the activity 1 is at the top of the activity stack. When the user taps a name of a TV series 1 or a corresponding card in the home page display interface, it may be considered that the activity 2 is started. In this case, the activity 2 is added to the activity stack, and the activity 2 is at the top of the activity stack, so that the mobile phone may display the corresponding display interface 110.

In this embodiment of this application, the mobile phone side starts an application and displays a display interface corresponding to the activity 2. When the user starts a same application on the PC side (for example, double-clicks an application icon of the application on the PC side), the mobile phone side creates an activity stack 2 for the application. In this case, the activity stack 2 may be an empty set. Then, the mobile phone side searches the mobile phone for information such as a package name, a user identity (user identification. UID), and an activity of a started application, to match an optimal window that meets a condition. In this embodiment, when the window matched by the mobile phone side, which is a window currently displayed by the mobile phone or a window in a background, is on the mobile phone, content in the activity stack 1 corresponding to the window is migrated to the activity stack 2, including a task and the activity 1 and the activity 2 included in the task.

With reference to (b) in FIG. 4, when the content in the activity stack 1 is migrated to the activity stack 2, the activity stack 1 is empty, and the activity stack 2 includes the task in the original activity stack 1, the activity 1 included in the task, and the activity 2 included in the task. In a corresponding interface of the PC, a window: displayed on the mobile phone, of the application is switched to the PC for display. In this case, the PC displays the window of the application and displays the display interface corresponding to the activity 2. In addition, a task and an activity sequence of the application are retained, that is, data of the application is retained, and the display interface corresponding to the activity 2 also becomes an interface focus of the PC interface. In other words, the display interface corresponding to the activity 2 may be directly presented to the user, and some operations of the user may be directly received.

In some embodiments, when the application supports a change of a display interface size (resize), the application may be displayed on a desktop of the PC in a form of a floating window: and a size of the floating window may be adjusted. In addition, interface elements in the display interface of the application may be displayed on the desktop of the PC after being re-arranged, that is, the interface element in the display interface may be adjusted as required, thereby improving user experience to some extent.

It should be understood that whether the application supports a change of a display interface size may be preset by a developer of the application. When developing the application, the developer of the application may write whether the application supports a change of a display interface size into source code of the application. In a possible implementation, in an electronic device using an Android system, whether an application supports a change of a display interface size is determined by determining whether the application supports resizing.

In a possible implementation, if code of the application declares that the display interface size of the application cannot be changed, the application is displayed in a full-screen form by default.

In some other embodiments, when the application does not support resizing, or a resizing effect is poor, the application may be displayed in a form of a floating window; but an interface layout of the window may change. For example, sizes or locations of some elements may change. In this case, the mobile phone may restart the current interface, that is, relaunch the display interface corresponding to the activity 2.

Therefore, when a display window of the application is switched from the mobile phone to the PC, the application is not restarted, but an original task and an original activity sequence are retained. In other words, in a process of switching the display window of the application, data of the application is not lost, that is, continuity of switching the application from one screen to another screen can be implemented, thereby improving user experience.

In some other embodiments, if the application does not support resizing or does not support moving to another screen for display, the mobile phone may restart the application, and display the window of the application on a screen of the PC.

In some other embodiments, if the window matched by the mobile phone is already opened on the PC, the window is displayed on a foreground and becomes a focus. In other words, the window may be directly presented to the user, and some operations of the user may be directly received.

It should be understood that, in this embodiment of this application, when the mobile phone establishes a connection relationship with the PC, pixels per inch (dots per inch. DPI) of the screen of the PC may be adapted to DPI of the mobile phone, that is, the DPI of the PC may be set to be the same as the DPI of the mobile phone. When the PC is in a keyboard-removed state or a touchscreen state, or a navigation state changes, a window management service (window manager service, WMS) in the mobile phone intercepts a message that is used for interface relaunching and that is sent by the system to the application, an operation of relaunching the current interface is not performed in the window of the application, thereby improving user experience.

For example, when the PC is in the keyboard-removed state or the touchscreen state, or the navigation state changes, an activity record in the mobile phone may detect a change of an activity, and determine, based on a manifest file of the application, whether to refresh an interface. When it is determined to refresh the interface, a message for interface refreshing may be sent to the application, and the WMS may intercept the message that is used for interface relaunching and that is sent by the activity record to the application, so that the application interface may not be relaunched.

In this embodiment of this application:

Keyboard-removed state: means that a keyboard of the PC changes from a connected state to a disconnected state, or the keyboard changes to a disconnected state and then to a connected state.

Touchscreen state: means that the application may be switched from a screen that can be touched for display to a screen that does not support touching for display.

Change of the navigation state: means that the PC supports an input operation performed by using a trackball or an arrow key. When the trackball or the arrow key changes, it may be considered that the navigation status changes.

It should be understood that in this embodiment of this application, the changes of the foregoing states of the electronic device are used as an example for description, but this shall not constitute any limitation on this application. In some other cases, when a system sends a message for relaunching an interface due to a change of another state of the electronic device, the WMS may still intercept the message for relaunching the interface. This technical solution also falls within the protection scope of this application.

FIG. 5 is a schematic flowchart of a display method according to an embodiment of this application. The method may be applied to a first electronic device and a second electronic device. An example in which the first electronic device is projected to the second electronic device is used. When the first electronic device establishes a connection relationship with the second electronic device, DPI of a screen of the second electronic device may be set to be the same as DPI of the first electronic device. As shown in FIG. 5, the method may include step 510 to step 550.

510: Detect an operation of starting a first application.

For example, with reference to FIG. 1(a)-1 and FIG. 1(a)-2, the second electronic device may be a PC 100b, the first application may be HUAWEI Video on a display desktop of the PC 100b, and the operation of starting the first application may be an operation of clicking an application icon 122 of HUAWEI Video by a user by using a mouse.

Step 510 may be performed by the first electronic device, that is, the first electronic device may detect the operation of starting the first application by the user.

It should be understood that the operation of starting the first application may be triggered on the first electronic device, or may be triggered on the second electronic device. This is not limited in this embodiment of this application.

520: Match a window of the first application in the first electronic device.

After the operation of starting the first application is detected, windows of applications that have been started in the first electronic device may be searched for a window that matches the first application. For example, the first electronic device may be searched for information such as a package name. UID, and an activity of a started application. In addition, the information may be compared with related information of the first application, so as to determine whether the first application has been started in the first electronic device. For example, when the first electronic device finds, in the applications that have been started, a package name that is the same as that of the first application, it may be determined that the first application has been started in the first electronic device.

530: Create an activity stack 2 in the first electronic device when it is determined that the matched window is in the first electronic device.

In this step, when it is determined that the window that matches the first application is in the first electronic device, an activity stack 2 may be created in the first electronic device, and an initial status of the activity stack 2 may be an empty set.

In some other embodiments, when it is determined that the window that matches the first application has been projected to the second electronic device, if the window is not on a foreground of the second electronic device, the matched window is moved to the foreground for display.

In some other embodiments, when it is determined that the window that matches the first application does not exist, that is, the first application was not executed before, a new window may be started in the first electronic device, and the new window is projected to the second electronic device for display.

In some other embodiments, if there is no optimally configured window, a second-matched window may be searched for based on affinity of the window.

In some other embodiments, when it is determined that the matched window is in the first electronic device, the first electronic device may not need to create the activity stack 2 but directly project the window to the second electronic device for display.

540: Migrate content of an activity stack 1 in which the window that matches the first application is located in the first electronic device to the activity stack 2.

In this step, the activity stack 1 includes an activity: a task, and the like corresponding to the window that matches the first application of the application. For example, with reference to FIG. 1(a)-1 and FIG. 1(a)-2, the first application may be HUAWEI Video, and a display interface corresponding to the window that matches the first application of the application may be the display interface 110 of HUAWEI Video in the mobile phone. In this case, the activity stack 1 may include a task, and the task includes an activity 1 corresponding to a home page display interface of HUAWEI Video and an activity 2 corresponding to the display interface 110. Then, the task in the activity stack 1, the activity 1 corresponding to the task, and the activity 2 corresponding to the task are migrated to the activity stack 2.

Optionally, when the content in the activity stack 1 is migrated to the activity stack 2, the first electronic device removes the activity stack 1.

550: Display, on the second electronic device, the matched window of the first application.

After the task in the activity stack 1, the activity 1 corresponding to the task, and the activity 2 corresponding to the task are migrated to the activity stack 2, the first electronic device sends data corresponding to content in the activity stack 2 to the second electronic device, and the matched window of the first application may be displayed on the screen of the second electronic device.

For example, if the first application is a video application, the first electronic device may transmit video data of the application to the second electronic device, and display, on the second electronic device, a window of the first application.

In some embodiments, to adapt to a window management requirement of the second electronic device, a size of the window of the first application may change. For example, the window of the first application is changed from being displayed in a full screen mode on the first electronic device to being displayed in a floating window form on the second electronic device, or being displayed in a full screen mode on the second electronic device. Alternatively, a title bar is added to the display interface corresponding to the window of the first application. The title bar may include a name of the first application, and function controls for controlling minimization, maximization, and closing of the window.

In some embodiments, when the first application supports resizing, the first application may be displayed on a desktop of the second electronic device in a form of a floating window; and a size of the floating window may be changed as the user performs adjustment. In addition, interface elements in the window of the first application may be re-arranged and then displayed on the desktop of the second electronic device, that is, the interface element in the window may be adjusted as required, thereby improving user experience to some extent.

In some embodiments, when the first application does not support resizing, or a resizing effect is poor, the first application may also be displayed in the form of a floating window; but an interface layout of the window may change. If the support effect is still poor, the first application loads the display interface by relaunching (relaunch) the display interface of the current window. In some embodiments, the first application may alternatively be displayed on the second electronic device in a full-screen form by default.

Based on this embodiment of this application, when the window of the application that has been started can be matched in the first electronic device after the application is started in the second electronic device, the window of the application may be migrated to the second electronic device for display, so as to ensure continuity of switching the application from the first electronic device to the second electronic device for display. Therefore, application restart can be avoided, thereby improving user experience.

It should be understood that a specific order of performing step 510 to step 550 is not limited in this embodiment of this application.

Optionally; the method may further include step 560.

560: Detect a state change of the second electronic device.

It should be understood that the state change in this step may include but is not limited to changes of the foregoing keyboard-removed state, touchscreen state, navigation state, and the like.

It should be understood that step 560 may be performed by the first electronic device.

Optionally, the method may further include step 570.

570: Intercept a message that is used for interface relaunching and that is sent to the first application due to a state change.

When the foregoing state changes, a system may send a message for relaunching an interface to the first application. In this case, a WMS in the first electronic device may intercept the message, so that the interface of the first application may not be relaunched.

It should be understood that step 570 may be performed after step 560, or may be performed before step 560. Step 570 may also be performed before or after any step between step 510 and step 550. This is not limited in this embodiment of this application.

This technical solution can avoid unnecessary interface relaunching caused by the foregoing state change, thereby improving user experience.

FIG. 6 is a schematic flowchart of a display method according to an embodiment of this application. The method may be applied to a first electronic device. An example in which the first electronic device is projected to a second electronic device is used for description. The method may include step 610 to step 630.

610: Detect, by the first electronic device, a first operation of starting a first application.

The first operation may be triggered on the second electronic device. With reference to FIG. 1(a)-1 and FIG. 1(a)-2, the first operation may be an operation of clicking the application icon 122 of HUAWEI Video by the user. Alternatively, the first operation may be triggered on the first electronic device.

620: Match, by the first electronic device, a window of the first application.

The first electronic device may match the window of the first application from windows of applications that have been started in the first electronic device.

In an embodiment, the first electronic device may match the window of the first application from the windows of the applications that have been started in the first electronic device based on first information.

The first information may include but is not limited to a package name of the started application, a user identity (UID) of the started application, and an activity corresponding to the started application.

It should be understood that the first electronic device may compare related information of the first application with content included in the first information. When the information can be matched, it may be understood that the first application has been started in the first electronic device. For example, if same content is matched from a window that has been started of the first electronic device based on a package name, an activity, and the like of the first application, it may be considered that the first application has been started in the first electronic device.

630: Migrate the window of the first application to the second electronic device for display, when the first electronic device determines that the matched window of the first application is located in the first electronic device.

The window of the first application may be displayed on the second electronic device in a form of a floating window: or may also be displayed on the second electronic device in a full-screen form.

In some embodiments, when the first application supports resizing, the first application may be displayed on a desktop of the second electronic device in a form of a floating window: and a size of the floating window may be changed as the user performs adjustment. In addition, interface elements in the window of the first application may be re-arranged and then displayed on the desktop of the second electronic device, that is, the interface element in the window may be adjusted as required, thereby improving user experience to some extent.

In some embodiments, when the first application does not support resizing, or a resizing effect is poor, the first application may also be displayed in the form of a floating window; but an interface layout of the window may change. If the support effect is still poor, the first application loads the display interface in a manner of relaunching.

In some other embodiments, when it is determined that the window that matches the first application does not exist, that is, the first application was not executed before, a new window may be started in the first electronic device, and the new window is projected to the second electronic device for display. In some other embodiments, if there is no optimally configured window, a second-matched window may be searched for based on affinity of the window.

In an embodiment of this application, after detecting an operation of starting the first application, the first electronic device matches a window of the first application in windows of applications that have been started. When determining that the matched window of the first application is in the first electronic device, the window of the first application is migrated to a second electronic device for display. In this technical solution, when an application is switched from a first electronic device to a second electronic device for display, data and a status of the application can be retained to avoid restarting the application.

Optionally: the migrating the window of the first application to the second electronic device for display includes: The first electronic device migrates content in a first activity stack corresponding to the window of the first application to a second activity stack. The first electronic device sends data of a window corresponding to the second activity stack to the second electronic device.

It should be understood that, with reference to (a) and (b) in FIG. 4, the first activity stack may be an activity stack 1, the second activity stack may be an activity stack 2, the second activity stack may be created by the first electronic device, and the second activity stack serves the second electronic device, so that a plurality of electronic devices can be managed by stack.

In an embodiment of this application, the first electronic device migrates the content in the first activity stack corresponding to the window of the first application to the second activity stack, so that a task and an activity record in the first activity stack can be retained, that is, data of the first application can be stored. In this way, when the first application is switched to the second electronic device for display, the data of the first application is not lost, thereby improving application continuity.

Optionally: the method may further include: The first electronic device removes the first activity stack. Therefore, system power consumption of the electronic device can be reduced.

Optionally: the window of the first application displayed on the second electronic device further includes a title bar, and the title bar includes at least an application name of the first application.

For example, with reference to FIG. 2(a)-1 and FIG. 2(a)-2, the second electronic device may be a PC 200b, and the first application may be an APP 1. In this case, a window or a display interface 230 of the APP 1 displayed by the PC 200b further includes a title bar 230a, and the title bar may include an application name of the APP 1. The title bar may further include some function controls, such as the control 231, the control 232, and the control 233.

Optionally, a size of the window of the first application displayed on the second electronic device is different from a size of the window displayed on the second electronic device.

For example, with reference to FIG. 2(a)-1 and FIG. 2(a)-2, the size of the window or the display interface 230 of the first application displayed on the PC 200b may be different from the size of the window or the display interface 230 of the first application displayed on the mobile phone 200a.

In another example, a size of the window of the first application displayed on the second electronic device may also be the same as a size of the window displayed on the second electronic device.

Optionally, the size of the window of the first application displayed on the second electronic device is adjustable.

In this technical solution, the user may adjust the size of the window of the first application as required, so that user experience can be effectively improved.

Optionally, the method further includes: placing the window of the first application on a foreground for display; when the first electronic device determines that the matched window of the first application is located in the second electronic device.

In this technical solution, when the window of the first application has been projected to the second electronic device, the window of the first application is displayed on the foreground.

Optionally, the method further includes: The first electronic device sets pixels per inch of a screen of the second electronic device to be the same as pixels per inch of a screen of the first electronic device.