Card display method and electronic device

Abstract

A card display method and an electronic device, which relate to the field of electronic devices, and can optimize the process of the electronic device displaying notification information of an application. The specific solution involves: in response to a service of a first application in an electronic device changing, the electronic device determining a first view of a first card of the first application (S1701); the electronic device creating, on the basis of the first view, a first embedded window layer corresponding to a second application (S1702); and in response to a first operation of switching to the second application, the electronic device displaying a first interface, wherein the first interface comprises an embedded window of the second application, and the embedded window of the second application displays the first embedded window layer, so as to display in the first interface the first card which comprises the first view (S1703).

Description

Card display method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on August 24, 2023, with application number 202311087384.0 and invention name “A card display method and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of electronic devices, and in particular to a card display method and electronic device. Background Art

[0003] Currently, electronic devices (such as mobile phones) usually display notification information of an application to users in the form of cards. The notification information can be notification information of applications with notification permission, such as text messages, itinerary information, taxi information, food delivery information, etc.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a card display method and electronic device, which can optimize the process of displaying notification information of an application on an electronic device.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a card display method, which is applied to an electronic device. The card display method may include: in response to a change in the business of a first application in the electronic device, the electronic device determines a first view of a first card of the first application; the electronic device creates a first embedded window layer corresponding to a second application based on the first view; in response to a first operation of switching to the second application, the electronic device displays a first interface, and the first interface includes an embedded window of the second application, wherein the first embedded window layer is displayed in the embedded window of the second application to display the first card including the first view in the first interface.

[0008] Based on the method described in the first aspect, when the business of a first application in an electronic device changes, in response to the business change of the first application, the electronic device can determine the first view of the first card of the first application and, based on the first view, create a first embedded window layer corresponding to the second application, so that the electronic device can embed the first embedded window layer into the embedded window of the second application. Thereafter, when the electronic device receives a first operation to switch to the second application, in response to the first operation, the electronic device can display the first interface corresponding to the second application. Since the first interface of the second application displayed by the electronic device includes the embedded window of the second application, the first embedded window layer embedded in the embedded window of the second application can be displayed while the electronic device displays the first interface corresponding to the second application, and thus the first card including the first view can be displayed in the first interface. That is, when the second application of the electronic device displays the first card, the first card can be displayed by displaying the embedded window of the second application instead of directly displaying the first card. In this way, the electronic device can determine the first view of the first card based on the business type of the first application, and then by displaying the first card including the first view on the first interface, the business status of the first application can be more effectively and intuitively displayed, providing a better user experience.

[0009] In combination with the first aspect, in another possible implementation, the above-mentioned card display method may further include: in response to a change in the business of the first application in the electronic device, the electronic device determines the second view of the first card of the first application, and the second view is different from the first view; the electronic device creates a second embedded window layer corresponding to the third application based on the second view; after the electronic device displays the first interface in response to the first operation of switching to the second application, the above-mentioned card display method may further include: in response to the second operation of switching to the third application, displaying the second interface, the second interface including the embedded window of the third application, wherein the second embedded window layer is displayed in the embedded window of the third application to display the first card including the second view in the second interface.

[0010] Based on this possible implementation, when the business of a first application in an electronic device changes, in response to the change in the business of the first application, the electronic device can determine the second view of the first card of the first application and, based on the second view, create a second embedded window layer corresponding to a third application. The electronic device can then embed the second embedded window layer into the embedded window of the third application. That is, when the business of the first application changes, the electronic device can determine the card views that can be displayed in each application based on the characteristics of each application. Furthermore, when the electronic device receives a second operation to switch to a third application, in response to the second operation, the electronic device's display interface can switch from the first interface corresponding to the second application to the second interface corresponding to the third application. Furthermore, because the electronic device displays the embedded window of the third application in the second interface of the third application, the electronic device's display interface simultaneously switches from the first card including the first view to the first card including the second view. That is, the electronic device can display first cards that are adapted to the characteristics of each application, thereby ensuring that the first cards displayed in different applications of the electronic device have good display effects.

[0011] In combination with the first aspect, in another possible implementation, the above-mentioned first view includes a progress bar, which is used to indicate the progress status of the business of the first application; the progress bar includes a first icon, a second icon, and a third icon, wherein the first icon is used to indicate the starting point of execution of the business of the first application, and the second icon is used to indicate the end point of execution of the business of the first application; the third icon is used to indicate that the progress status of the business of the first application has changed, and when the progress status of the business of the first application changes, the position of the third icon between the first icon and the second icon changes accordingly.

[0012] Based on this possible implementation method, the first view may include a progress bar for indicating the progress status of the business of the first application. In this way, when the electronic device displays the first card including the first view on the first interface, the progress status of the business of the first application can be more intuitively displayed through the progress bar in the first view, providing a better user experience.

[0013] In combination with the first aspect, in another possible implementation, the business stage of the above-mentioned first application includes a first business stage and a second business stage; the first view includes a segmented progress bar, which is used to indicate the progress status of the business of the first application in different business stages; the segmented progress bar includes a fourth icon, a fifth icon, a sixth icon and a seventh icon located between the fourth icon and the fifth icon; wherein, the fourth icon is used to indicate the execution starting point of the first business stage of the first application; the fifth icon is used to indicate the execution end point of the second business stage of the first application; the sixth icon is used to indicate the execution end point of the first business stage of the first application and the execution starting point of the second business stage of the first application; the seventh icon is used to indicate a change in the business progress of the second application, and when the progress of the business of the second application changes in the first business stage, the position of the seventh icon between the fourth icon and the sixth icon changes accordingly; or, when the progress of the business of the second application changes in the second business stage, the position of the seventh icon between the sixth icon and the fifth icon changes accordingly.

[0014] Based on this possible implementation method, the first view may include a segmented progress bar for indicating the progress status of the business of the first application at different business stages. In this way, when the electronic device displays the first card including the first view on the first interface, the segmented progress bar in the first view can more intuitively display the current business stage of the business of the first application and the progress status corresponding to the business stage, providing a better user experience.

[0015] In combination with the first aspect, in another possible implementation method, the above-mentioned electronic device determines the first view of the first card of the first application, which may include: the electronic device obtains the identification information of the second application; the electronic device determines the identification information of the first view based on the identification information of the second application; the electronic device determines the first view based on the identification information of the first view.

[0016] Based on this possible implementation method, the electronic device can pre-create a card view of the first card corresponding to each application. In this way, when the electronic device determines the first view, the electronic device can determine the identification information of the first view based on the identification information of the second application, and determine the first view based on the identification information of the first view, so that the card view can be quickly obtained, thereby improving the processing efficiency of the electronic device.

[0017] In combination with the first aspect, in another possible implementation method, before the above-mentioned electronic device determines the first view of the first card of the first application, the above-mentioned card display method may also include: the electronic device generates a placeholder view based on the card size information of the second application; the electronic device creates a placeholder embedded window layer corresponding to the placeholder view based on the placeholder view; the electronic device mounts the placeholder embedded window layer to the embedded window of the second application.

[0018] Based on this possible implementation method, before the electronic device determines the first view of the first card of the first application, the electronic device can generate a placeholder view based on the card size information of the second application, and create a placeholder embedded window layer corresponding to the placeholder view based on the placeholder view, so as to mount the placeholder embedded window layer in the embedded window of the second application. This can avoid the electronic device displaying cards of other applications other than the first application during the process of determining the card view of the first card of the first application.

[0019] In combination with the first aspect, in another possible implementation method, the above-mentioned electronic device creates a placeholder embedded window layer corresponding to the placeholder view based on the placeholder view, which may include: when a third embedded window layer is stored in the electronic device, obtaining status information of the third embedded window layer, wherein the third embedded window layer is an embedded window layer created based on the card view of the second card of the first application, and the progress status of the business of the first application indicated by the second card is different from that of the first card; when the status information indicates that the third embedded window layer is valid, updating the card view of the second card in the third embedded window layer to the placeholder view to obtain the placeholder embedded window layer.

[0020] Based on this possible implementation method, when a third embedded window layer is stored in the cache of an electronic device, the electronic device can update the card view of the second card in the third embedded window layer to a placeholder view to obtain a placeholder embedded window layer. This eliminates the need to recreate the placeholder embedded window layer, thereby improving the processing efficiency of the electronic device.

[0021] In combination with the first aspect, in another possible implementation method, the above-mentioned electronic device creates a first embedded window layer corresponding to the second application based on the first view, which may include: updating the placeholder view in the placeholder embedded window layer to the first view to obtain the first embedded window layer corresponding to the second application.

[0022] Based on this possible implementation method, the electronic device can update the placeholder view in the placeholder embedded window layer to the first view to obtain the first embedded window layer corresponding to the second application. This does not require recreating the first embedded window layer, which can improve the processing efficiency of the electronic device.

[0023] In combination with the first aspect, in another possible implementation, the display content corresponding to the second view is different from the display content corresponding to the first view, and / or the display size corresponding to the second view is different from the display size corresponding to the first view.

[0024] Based on this possible implementation, when the business of the first application changes, the electronic device can generate card views corresponding to each application based on the characteristics of different applications, wherein the display content and / or display size of the card views corresponding to different applications are different. In this way, the electronic device can generate first cards adapted to each application based on the characteristics of different applications, and then when the electronic device switches to any application, it can display the interface corresponding to the application, and display the first card including the card view corresponding to the application on the interface corresponding to the application, so as to ensure that the first cards displayed in different applications of the electronic device have good display effects.

[0025] In combination with the first aspect, in another possible implementation, the second application is a desktop, notification center, lock screen, screen off, negative one screen or banner notification; the third application is a desktop, notification center, lock screen, screen off, negative one screen or banner notification.

[0026] Based on this possible implementation method, when an application running in the foreground of an electronic device switches between the desktop, notification center, lock screen, screen off, negative one screen or banner notification, a first card including different card views can be displayed. This can ensure that the first card displayed on the desktop, notification center, lock screen, screen off, negative one screen or banner notification has a better display effect.

[0027] In combination with the first aspect, in another possible implementation, the display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes display height and display width; wherein, the second application is the desktop, the third application is the notification center, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

[0028] Based on this possible implementation method, when an application running in the foreground of an electronic device is switched from the desktop to the notification center, a first card including a second view can be displayed in the notification center, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. This can reduce the space occupied by the first card, so that the notification center of the electronic device can display more notification information cards. Users do not need to flip through all notification information cards to view them, which can improve the efficiency of human-computer interaction.

[0029] In combination with the first aspect, in another possible implementation, the display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes a display height and a display width; wherein, the second application is a desktop, the third application is a lock screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

[0030] Based on this possible implementation method, when an application running in the foreground of an electronic device switches from the desktop to the lock screen, a first card including a second view can be displayed in the notification center, and the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. This can reduce the space occupied by the first card, so that the lock screen of the electronic device can display more notification information cards. Users do not need to flip through all notification information cards to view them, which can improve the efficiency of human-computer interaction.

[0031] In combination with the first aspect, in another possible implementation, the display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes a display height and a display width; wherein, the second application is a lock screen, the third application is an off screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

[0032] Based on this possible implementation, since the display space of the screen-off interface of the electronic device is limited, when the application running in the foreground of the electronic device switches from the lock screen to the screen-off interface, a first card including a second view can be displayed on the screen-off interface, and the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. In this way, the display size of the first card can be reduced, and the space occupied by the first card can be minimized to the maximum extent, avoiding the card corresponding to the second application from being unable to be fully displayed. In addition, since the screen-off interface of the electronic device is in a constantly on state, displaying a smaller first card on the screen-off interface can reduce the power consumption of the electronic device.

[0033] In a second aspect, embodiments of the present application provide a card display device that can be applied to an electronic device and used to implement the method described in the first aspect. The functions of the card display device can be implemented through hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as a determination module, a creation module, and a display module.

[0034] The determination module may be configured to determine a first view of a first card of a first application in response to a change in a service of the first application in the electronic device.

[0035] The creation module can be used to create a first embedded window layer corresponding to the second application according to the first view.

[0036] The display module can be used to display a first interface in response to a first operation of switching to a second application, wherein the first interface includes an embedded window of the second application, wherein a first embedded window layer is displayed in the embedded window of the second application to display a first card including a first view in the first interface.

[0037] In a third aspect, an electronic device is provided that has the functionality to implement the method described in the first aspect. This functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functionality described above.

[0038] In a fourth aspect, an electronic device is provided, comprising: a processor and a memory; the memory is used to store computer-executable instructions, and when the electronic device is running, the processor executes the computer-executable instructions stored in the memory so that the electronic device executes a card display method as described in any one of the above-mentioned first aspects.

[0039] In a fifth aspect, an electronic device is provided, comprising: a processor; the processor is configured to be coupled to a memory, and after reading instructions in the memory, execute the card display method as described in any one of the above-mentioned first aspects according to the instructions.

[0040] In a sixth aspect, embodiments of the present application provide a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by an electronic device, the electronic device implements the card display method as described in the first aspect or any possible implementation of the first aspect.

[0041] In a seventh aspect, an embodiment of the present application provides a computer program product, comprising a computer-readable code. When the computer-readable code runs in an electronic device, the electronic device implements a card display method as described in any one of the first aspect or possible implementations of the first aspect.

[0042] In an eighth aspect, a device (for example, a chip system) is provided, which includes a processor for supporting an electronic device in implementing the functions described in the first aspect. In one possible design, the device also includes a memory for storing program instructions and data necessary for the electronic device. When the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0043] It should be understood that the beneficial effects of the second to eighth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of a software structure of an electronic device in the related art;

[0045] FIG2 is a schematic diagram of a scene in which an electronic device displays a card in the related art;

[0046] FIG3 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0047] FIG4 is a schematic diagram of a software structure of an electronic device provided in an embodiment of the present application;

[0048] FIG5 is a second schematic diagram of a software structure of an electronic device provided in an embodiment of the present application;

[0049] FIG6 is a third schematic diagram of a software structure of an electronic device provided in an embodiment of the present application;

[0050] FIG7 is a schematic diagram of a progress bar according to an embodiment of the present application;

[0051] FIG8 is a schematic diagram of one scenario of a card display method provided in an embodiment of the present application;

[0052] FIG9 is a second schematic diagram of a scene of a card display method provided in an embodiment of the present application;

[0053] FIG10 is a second schematic diagram of a progress bar provided in an embodiment of the present application;

[0054] FIG11 is a third schematic diagram of a scene of a card display method provided in an embodiment of the present application;

[0055] FIG12 is a fourth schematic diagram of a scene of a card display method provided in an embodiment of the present application;

[0056] FIG13 is a third schematic diagram of a progress bar provided in an embodiment of the present application;

[0057] FIG14 is a fifth schematic diagram of a scene of a card display method provided in an embodiment of the present application;

[0058] FIG15 is a sixth schematic diagram of a scene of a card display method provided in an embodiment of the present application;

[0059] FIG16 is a flow chart of a card display method according to an embodiment of the present application;

[0060] FIG17 is a second flow chart of a card display method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0062] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature specified as "first" or "second" may explicitly or implicitly include one or more of such features. Throughout this application, unless otherwise specified, "plurality" means two or more.

[0063] Currently, in order to more intuitively display the notification information corresponding to a certain application to the user, electronic devices (such as mobile phones, etc.) can display the notification information corresponding to the application (APP) to the user in the form of cards (or widgets, parts, components, etc.) on the display interface.

[0064] The application that displays notification information to the user in the form of a card can be an application in the electronic device that needs to publish notification information. The application can be an application that comes with the electronic device or a third-party application.

[0065] When an electronic device displays a card corresponding to an application, the electronic device may create a card corresponding to the application's notification information according to predefined native card elements, and display the card corresponding to the application's notification information. Native card elements are typically interface elements predefined based on the native Android card framework. That is, for any application, when an electronic device displays a card corresponding to the application, the card corresponding to the application may only include native card elements and cannot carry custom card elements of the application.

[0066] However, the native card elements supported by the native Android card framework are limited. For example, the native card elements supported by the native Android card framework include text elements and picture elements. Therefore, when an electronic device creates a card corresponding to the notification information of a certain application according to the native card elements, the electronic device can create a card including different text elements and picture elements according to the notification information of the application, and then display the notification information of the application to the user through the text elements and picture elements displayed on the card. However, the electronic device cannot create a card including custom card elements according to the notification information of the application, that is, the application of the electronic device cannot create different cards according to demand, and thus it is difficult to effectively and intuitively display the notification information of the application to the user.

[0067] The following describes a process in which an electronic device displays a card corresponding to notification information of an application program according to native card elements with reference to FIG. 1 .

[0068] As an example, let's take a mobile phone as an electronic device and a notification message from a ride-hailing app as an example. As shown in Figure 1, when the electronic device displays the card corresponding to the ride-hailing app's notification message, the ride-hailing app running on the electronic device creates a card (view) corresponding to the ride-hailing app's notification message based on native card elements. The card corresponding to the ride-hailing app's notification message is serialized according to pre-set rules to obtain the card data (view data) corresponding to the ride-hailing app's notification message.

[0069] The ride-hailing application running on the electronic device can send card data (view data) of a card (view) corresponding to the notification information of the ride-hailing application to the host application of the electronic device. The host application can be an application on the electronic device that can display cards, such as the electronic device's desktop, notification center, banner notification, lock screen, off screen, or negative one screen.

[0070] After receiving the card data of the card view corresponding to the notification information of the ride-hailing application, the host application of the electronic device creates and displays the card view corresponding to the notification information of the ride-hailing application based on the card data. The card view corresponding to the notification information of the ride-hailing application may only include native card elements (e.g., text elements and image elements) supported by the native Android card framework.

[0071] In addition, as shown in FIG1 , the taxi-hailing application of the electronic device can call predefined functions, such as a set text function and a set translation function. Correspondingly, the host application of the electronic device can also call predefined functions, such as a set text function and a set translation function. Specifically, the electronic device can pre-establish a correspondence between the set text function callable by the taxi-hailing application and the set text function callable by the host application, and pre-establish a correspondence between the set translation function callable by the taxi-hailing application and the set translation function callable by the host application.

[0072] In this way, the taxi-hailing application of the electronic device can call the taxi-hailing application's set text function to update the text elements in the card (view). When the taxi-hailing application of the electronic device calls the taxi-hailing application's set text function to update the text elements in the card (view), based on the pre-established correspondence, the set text function callable by the host application corresponding to the set text function of the taxi-hailing application can be first determined. Thus, the host application of the electronic device can call the set text function corresponding to the host application to update the text elements in the card (view).

[0073] Below, taking the example of a card corresponding to the notification information of a taxi-hailing application including text elements and picture elements, and a host application being the notification center of an electronic device, a schematic illustration of the update of the text elements included in the card corresponding to the notification information of the taxi-hailing application displayed on the electronic device is given in conjunction with Figure 2.

[0074] After the taxi-hailing application of the electronic device generates a taxi order, the taxi-hailing application of the electronic device will publish the taxi task and wait for the driver to accept the order. When the electronic device returns to the desktop after opening the application, as shown in (a) in Figure 2, the electronic device can display a card 11 corresponding to the taxi-hailing application in the notification center 10. Card 11 can be used to prompt the user that the taxi-hailing application has generated a taxi order and is waiting for the driver to accept the order. As shown in (a) in Figure 2, card 11 can include an icon 111 of the taxi-hailing application and a text 112 that reads "Waiting for the driver to accept the order."

[0075] Afterward, when the electronic device's ride-hailing application detects that the driver has accepted the order and is heading to the user's departure location according to the order, as shown in FIG2(b), the electronic device may display a card 12 corresponding to the ride-hailing application in the notification center 10. Card 12 may be used to notify the user that the driver has accepted the order and is heading to the departure location. As shown in FIG2(b), card 12 may include an icon 121 for the ride-hailing application and text 122 stating "Driver has accepted the order and is on his way."

[0076] Afterward, when the taxi-hailing application on the electronic device detects that the driver has arrived at the departure location, as shown in FIG2(c), the electronic device may display a card 13 corresponding to the taxi-hailing application in the notification center 10. Card 13 may be used to notify the user that the driver has arrived at the departure location and is waiting for the user to board the vehicle. As shown in FIG2(c), card 13 may include an icon 131 for the taxi-hailing application and text 132 that reads "Driver has arrived, please board the vehicle."

[0077] After the driver picks up the user and drives to the destination according to the ride order, as shown in FIG2(d), the electronic device may display a card 14 corresponding to the ride-hailing application in the notification center 10. Card 14 may be used to remind the user that the ride is now heading to the destination. As shown in FIG2(d), card 14 may include an icon 141 for the ride-hailing application and text 142 that reads "Driving to Destination."

[0078] That is, when the text elements included in the card corresponding to the taxi-hailing application are updated, the text elements included in the card corresponding to the taxi-hailing application displayed in the notification center of the electronic device are updated.

[0079] Of course, the taxi-hailing application of the electronic device can also call the taxi-hailing application's set translation function to update the display position of the card (view). When the taxi-hailing application of the electronic device calls the taxi-hailing application's set translation function to update the display position of the card (view), based on a pre-established correspondence, a set translation function callable by the host application corresponding to the taxi-hailing application's set translation function can be first determined. Thus, the host application of the electronic device can call the corresponding set translation function of the host application to update the display position of the card (view).

[0080] However, when an electronic device displays a card corresponding to a notification from a ride-hailing app, it can only display the card using native card elements supported by the native Android card framework. This method results in a relatively simple card style, making it difficult to intuitively and effectively present the ride-hailing app's notification information to the user.

[0081] From the above, it can be seen that in the relevant technology, electronic devices can only display cards corresponding to applications according to the native card elements supported by the native Android card framework, and cannot display cards including custom card elements according to the notification information of the application. The style of the displayed cards is relatively simple, and it is difficult to display the notification information of the application to the user intuitively and effectively, resulting in a low user experience.

[0082] In response to the above problems, an embodiment of the present application provides a card display method, which is applied to an electronic device. When the electronic device displays the notification information of an application in the form of a card, the application running on the electronic device can create a card view, and generate an embedded window layer corresponding to the card based on the card view, and send the embedded window layer corresponding to the card to the host application of the electronic device, so that the host application of the electronic device displays the embedded window layer corresponding to the card. That is, when the host application of the electronic device displays the notification information of the application in the form of a card, the host application of the electronic device displays its own embedded window layer instead of directly displaying the card view. Therefore, the application of the electronic device can create a card view including custom card elements according to demand, and generate an embedded window layer including custom card elements based on the card view, so that when the host application of the electronic device displays the notification information of the application, the host application of the electronic device can display a card view including different custom card elements, which can more effectively and intuitively display the notification information of the application to the user.

[0083] Furthermore, when an electronic device displays the card corresponding to an application, displaying the card corresponding to the application based on the embedded window layer can improve the speed of cross-process data transmission and realize real-time refresh of the card corresponding to the application, thereby ensuring the timeliness of the notification information of the application and providing a better user experience.

[0084] The card display method provided in the embodiment of the present application is described below.

[0085] The card display method provided in the embodiments of the present application can be applied to electronic devices. In some embodiments, the electronic devices can be mobile phones, tablet computers, handheld computers, personal computers (PCs), cellular phones, personal digital assistants (PDAs), wearable devices, and other electronic devices with application programs. The embodiments of the present application do not limit the specific form of the electronic devices.

[0086] For example, taking the electronic device as a mobile phone as an example, FIG3 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.

[0087] As shown in Figure 3, the electronic device may include a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, an antenna 1, an antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 370B, a microphone 370C, an earphone interface 370D, a sensor module 380, a button 390, a motor 391, an indicator 392, a camera 393, a display screen 394, and a subscriber identification module (SIM) card interface 395, etc. Among them, the sensor module 380 may include a pressure sensor 380A, a gyroscope sensor 380B, an air pressure sensor 380C, a magnetic sensor 380D, an acceleration sensor 380E, a distance sensor 380F, a proximity light sensor 380G, a fingerprint sensor 380H, a temperature sensor 380J, a touch sensor 380K, an ambient light sensor 380L, a bone conduction sensor 380M, etc.

[0088] It should be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0089] In an embodiment of the present application, the display screen 394 may be used to display the electronic device display interfaces of FIG. 8 , FIG. 9 , FIG. 11 , FIG. 12 , FIG. 14 , and FIG. 15 .

[0090] Of course, it is understood that FIG3 is merely an example of an electronic device in the form of a mobile phone. If the electronic device is a tablet computer, handheld computer, PC, PDA, wearable device (such as a smart watch, smart bracelet), or other device form factors, the structure of the electronic device may include fewer or more structures than shown in FIG3, and this is not limited here.

[0091] It is understandable that, generally speaking, the realization of electronic device functions requires not only hardware support but also software cooperation.

[0092] The software system of the electronic device can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the electronic device.

[0093] FIG4 is a block diagram of the software structure of the electronic device provided in an embodiment of the present application.

[0094] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: from top to bottom: the application layer, the application framework (FWK), the Android runtime and system libraries (also called the native layer), and the kernel layer.

[0095] In some examples, in order to implement the card display method provided in the embodiments of the present application, the application layer may also include a host application (such as the electronic device's desktop, negative one screen, notification center, banner notification, screen off, lock screen, etc.) and an application that provides a card. The application that provides a card is an application in the electronic device that can provide a card. It can be a third-party application, such as a travel application in the electronic device (such as a taxi application, a map application, etc.), a delivery application (such as a food delivery application, a courier application, etc.). The application that provides a card can also be an application of the system of the electronic device.

[0096] The card display method provided in the embodiment of the present application is schematically illustrated below in conjunction with Figure 5. It should be noted that the specific application mentioned in the embodiment of the present application is used as an example only to facilitate the description of the technical solution and does not limit the scope of the solution of the present application.

[0097] For example, taking the application that provides the card as a taxi-hailing application, as shown in Figure 5, the card display method provided in the embodiment of the present application includes the following process: when the electronic device displays the card corresponding to the notification information of the taxi-hailing application, the taxi-hailing application of the electronic device can generate an embedded window (i.e., SurfaceControlViewHost) layer corresponding to the card view (i.e., view) corresponding to the notification information of the taxi-hailing application based on the card view (i.e., view) corresponding to the notification information of the taxi-hailing application, and the embedded window layer includes a SurfaceControl layer.

[0098] Afterwards, the taxi-hailing application of the electronic device can encapsulate the embedded window layer corresponding to the card view, obtain the data packet of the embedded window layer corresponding to the card view (i.e., SurfacePackage), and transmit the data packet of the embedded window layer corresponding to the card view across processes to the host application of the electronic device.

[0099] After the host application of the electronic device receives the data packet of the embedded window layer corresponding to the card view, the host application of the electronic device can obtain the embedded window layer corresponding to the card view according to the data packet of the embedded window layer corresponding to the card view. The host application of the electronic device can mount (or embed) the embedded window layer corresponding to the card view on its own host layer (i.e., SurfaceView), that is, the host application of the electronic device can embed the SurfaceControl layer into its own host layer. In other words, the SurfaceControl layer actually embedded in the host layer of the host application of the electronic device and the SurfaceControl layer included in the embedded window layer generated by the taxi application of the electronic device are the same layer. In other words, the host layer of the host application of the electronic device and the embedded window layer of the taxi application of the electronic device both point to the high-performance rendering (graphic) layer (i.e., SurfaceControl layer). Therefore, the host application of the electronic device and the taxi application of the electronic device display the same object, that is, the host application of the electronic device can display the card corresponding to the notification information of the taxi application.

[0100] Furthermore, in combination with what is shown in Figure 5, since when the electronic device displays the card corresponding to the notification information of the taxi-hailing application, the host application of the electronic device displays the SurfaceControl layer embedded in its own host layer (that is, the embedded window layer generated by the taxi-hailing application), therefore, when the taxi-hailing application of the electronic device generates the embedded window layer, the taxi-hailing application of the electronic device can generate a card view including custom card elements, and based on the card view, generate an embedded window layer corresponding to the card view including custom card elements, so that the host application of the electronic device can display the embedded window layer corresponding to the card view including custom card elements, that is, the host application of the electronic device can display the taxi-hailing application card including custom card elements.

[0101] In addition, since the card view corresponding to the notification information of the taxi-hailing application running on the electronic device is created in the process of the taxi-hailing application. Therefore, when the notification information of the taxi-hailing application running on the electronic device changes (that is, the business of the taxi-hailing application changes), the taxi-hailing application can call the relevant function to adjust the card view corresponding to the notification information of the taxi-hailing application, and the SurfaceControl layer corresponding to the card view can be synchronously updated according to the adjusted card view, that is, the embedded window layer corresponding to the card view can be synchronously updated according to the adjusted card view. In addition, since the SurfaceControl layer actually embedded in the host layer of the host application of the electronic device and the SurfaceControl layer included in the embedded window layer generated by the taxi-hailing application of the electronic device are the same layer, the SurfaceControl layer displayed by the host application of the electronic device is also updated accordingly, that is, the card corresponding to the taxi-hailing application displayed by the host application of the electronic device is also updated accordingly.

[0102] In some examples, in order to implement the card display method provided in the embodiments of the present application, as shown in Figure 6, the application layer may also include a management plug-in corresponding to the application, specifically including a management plug-in corresponding to the application providing the card and a management plug-in corresponding to the host application.

[0103] The management plug-in corresponding to the application can be AAR (Android Archive) or JAR (Java Archive). In the embodiment of the present application, the specific type of the management plug-in corresponding to the application is not limited. In the embodiment of the present application, the management plug-in corresponding to the application is AAR as an example for illustration.

[0104] The AAR may include an AAR corresponding to the application providing the card and an AAR corresponding to the host application.

[0105] The AAR (also called a card kit) corresponding to the card-providing application can serve as a bridge for interaction between the card-providing application and the card management service of the electronic device. Specifically, the card kit can integrate relevant interfaces for card display, allowing the card-providing application to establish a communication connection with the card management service through the relevant interfaces integrated by the card kit, and then interact with the card management service through the card kit. In other words, the card-providing application does not need to understand the card management service of the electronic device; simply by calling the relevant interfaces provided by the card kit, it can implement functions such as card access, timed refresh, card caching, card retrieval, and card destruction.

[0106] It should be noted that CardKit can be integrated into any card-providing application on an electronic device. That is, any card-providing application on an electronic device can integrate CardKit. For example, a ride-hailing application on an electronic device can integrate CardKit. Another example is a food delivery application on an electronic device.

[0107] The AAR corresponding to the host application (also called the Host AAR) can serve as a bridge for interaction between the host application and the card management service of the electronic device. In other words, the Host AAR can integrate the relevant interfaces for card display, allowing the host application to establish a communication connection with the card management service through the relevant interfaces integrated by the Host AAR. In this way, the host application can quickly access the card management service through the Host AAR, helping the host application to implement functions such as host access, requesting to show / hide, obtaining the HostView (host view), resizing, and configuration changes.

[0108] It should be noted that the Host AAR can be integrated into the host application of the electronic device. That is, each host application of the electronic device can integrate the Host AAR. For example, the electronic device's desktop can integrate the Host AAR. Another example is that the electronic device's notification center can integrate the Host AAR. Another example is that the electronic device's negative first screen can integrate the Host AAR.

[0109] As shown in FIG6 , the application framework layer may further include a card display service (DisplayService), a card management service (LiveClipManagerService) and a system service (Service).

[0110] The card display service can be used as the initiator of instructions related to card display. The card display service is used to receive notifications from the decision-making center (i.e., the application that comes with the electronic device) related to controlling the host application to display cards. In response to the notifications related to controlling the host application to display cards, the card display service notifies the host application to display, hide, or destroy the card.

[0111] The card management service serves as a bridge between the card process and the host process. Specifically, it implements functions such as card lifecycle management, power consumption control, data caching, and exception recovery. The card management service can be used to obtain notifications related to card display from the host application and, using system services, send card display notifications to the card kit, instructing the card kit to retrieve the embedded window layer corresponding to the card view from the card-providing application. The card management service can also be used to establish a communication connection with the host AAR using system services and, through the host AAR, send the retrieved embedded window layer corresponding to the card view to the host application for display.

[0112] System services have the basic capabilities of Android native services, that is, system services can provide cross-process data transmission channels.

[0113] 6 , the card display method provided in the embodiment of the present application will be further illustrated by taking the application providing the card as a taxi-hailing application as an example.

[0114] As shown in FIG6 , a card display method provided by an embodiment of the present application may include S601 - S609 .

[0115] S601. Upon receiving a service notification sent by a taxi-hailing application of an electronic device, the card display service of the electronic device sends a card display notification to the host application of the electronic device.

[0116] Among them, service notifications are used to indicate changes in the service of the electronic device's ride-hailing application (such as a driver accepting an order), and card display notifications are used to instruct the host application to display the ride-hailing application card. The host application can include the electronic device's desktop, negative one screen, notification center, banner notification, screen off, lock screen, etc.

[0117] After the electronic device is turned on, the host application (desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) registers the business changes of the taxi application (not shown in the figure). When the business of the taxi application changes, the card display service sends a card display notification to these host applications to notify the host applications of the electronic device that the taxi application card needs to be displayed.

[0118] For example, after a user places a taxi order using a taxi application on an electronic device, when the service of the taxi application changes (such as a driver accepting an order), the taxi application can send a service notification to the card display service of the electronic device, that is, the taxi application notifies the card display service that the taxi application card currently needs to be displayed. After the card display service of the electronic device receives the service notification sent by the taxi application, it can send a card display notification to the host application of the electronic device (such as the desktop, negative one screen, notification center, banner notification, screen off, lock screen) to notify the host application of the electronic device that the taxi application card needs to be displayed. Therefore, when the electronic device switches to the desktop, the desktop of the electronic device can display the taxi application card. When the electronic device switches to the notification center, the notification center of the electronic device can display the taxi application card.

[0119] S602: The host application of the electronic device receives the card display notification and sends a first request to the Host AAR corresponding to the host application, where the first request is used to request the display of the taxi application card.

[0120] It should be noted that since the card display service of the electronic device can send a card display notification to all host applications of the electronic device that have registered taxi-hailing applications and whose business has changed, after each host application of all host applications of the electronic device that have registered taxi-hailing applications and whose business has changed receives the card display notification sent by the card display service, each host application can send a first request to the Host AAR corresponding to the host application.

[0121] S603. The Host AAR corresponding to the host application receives the first request and sends a second request to the card management service of the electronic device, where the second request is used to request display of the taxi application card.

[0122] After the Host AAR corresponding to the host application receives the first request, the Host AAR corresponding to the host application uses the system service of the electronic device to establish cross-process communication with the card management service of the electronic device, and sends a second request to the card management service of the electronic device to request the card management service of the electronic device to display the taxi application card.

[0123] It should be noted that, since each host application among all host applications with business changes registered for taxi-hailing applications can send a first request to the Host AAR corresponding to the host application after receiving the card display notification sent by the card display service, therefore, after the Host AAR corresponding to each host application receives the first request, the Host AAR corresponding to each host application can send a second request to the card management service of the electronic device.

[0124] S604. The card management service receives the second request and sends a third request to the card kit corresponding to the taxi-hailing application. The third request is used to request to obtain the embedded window layer corresponding to the taxi-hailing application card.

[0125] After the card management service of the electronic device receives the second request, the card management service can use the system service of the electronic device to establish cross-process communication with the card kit corresponding to the taxi-hailing application, and send a third request to the card kit corresponding to the taxi-hailing application to obtain the embedded window layer corresponding to the taxi-hailing application card from the card kit corresponding to the taxi-hailing application.

[0126] It should be noted that since the Host AAR corresponding to each host application can send a second request to the card management service of the electronic device, after the card management service receives the second request sent by the Host AAR corresponding to each host application, the card management service can send a third request to the card kit corresponding to the taxi application.

[0127] S605. The card kit corresponding to the taxi-hailing application receives the third request and sends a fourth request to the taxi-hailing application. The fourth request is used to request to obtain the card view corresponding to the taxi-hailing application card.

[0128] The fourth request includes a card view identifier (ie, a view id). The card view identifier can uniquely identify a card view in a card that can be displayed by the host application.

[0129] When a host application on an electronic device displays a card, the host application running in the foreground of the electronic device can change, so that a card view that is appropriate to the host application's display content can be displayed. In other words, for the same service of a ride-hailing app, when different host applications display the ride-hailing app card, the card views displayed by the different host applications will be different, and the card view identifiers of the different card views will be different.

[0130] For example, continuing with the example that the host application of the electronic device may include the desktop, notification center, lock screen, screen off, negative one screen, and banner notification, for the same service of the taxi application (such as the driver accepting an order), the view id of the card view of the taxi application card corresponding to the desktop is 1, the view id of the card view of the taxi application card corresponding to the notification center is 2, the view id of the card view of the taxi application card corresponding to the lock screen is 3, the view id of the card view of the taxi application card corresponding to the screen off is 4, the view id of the card view of the taxi application card corresponding to the negative one screen is 5, and the view id of the card view of the taxi application card corresponding to the banner notification is 6.

[0131] It should be noted that since the card management service can send a third request to the card kit corresponding to the taxi application after receiving the second request sent by the Host AAR corresponding to each host application, after the card kit corresponding to the taxi application receives the third request sent by the card management service when it receives the second request sent by the Host AAR corresponding to a host application, the card kit corresponding to the taxi application can send a fourth request to the taxi application, and the fourth request includes the card view identifier corresponding to the host application.

[0132] S606. The taxi application receives the fourth request, and obtains the card view corresponding to the taxi application card according to the card view identifier, and sends the card view corresponding to the taxi application card to the card kit corresponding to the taxi application.

[0133] S607. The card kit corresponding to the taxi application receives the card view corresponding to the taxi application card, and generates the embedded window layer corresponding to the taxi application card based on the card view corresponding to the taxi application card, and sends the embedded window layer corresponding to the taxi application card to the card management service.

[0134] After receiving the card view corresponding to the taxi application card, the card kit corresponding to the taxi application can generate an embedded window layer corresponding to the taxi application card based on the card view corresponding to the taxi application card. Furthermore, the card kit corresponding to the taxi application can encapsulate the embedded window layer corresponding to the taxi application card to obtain a data packet of the embedded window layer corresponding to the taxi application card, and send the data packet of the embedded window layer corresponding to the taxi application card to the card management service using the cross-process channel provided by the system service of the electronic device.

[0135] S608. The card management service receives the embedded window layer corresponding to the taxi-hailing application card, and sends the embedded window layer corresponding to the taxi-hailing application card to the Host AAR corresponding to the host application.

[0136] After the card management service of the electronic device receives the data packet of the embedded window layer corresponding to the taxi application card, the card management service uses the cross-process channel provided by the system service of the electronic device to send the data packet of the embedded window layer corresponding to the taxi application card to the Host AAR corresponding to the host application.

[0137] S609. The Host AAR corresponding to the host application receives the embedded window layer corresponding to the taxi-hailing application card, and sends the embedded window layer corresponding to the taxi-hailing application card to the host application.

[0138] The Host AAR corresponding to the host application can send a data packet of the embedded window layer corresponding to the taxi application card to the host application of the electronic device. After the host application of the electronic device receives the data packet of the embedded window layer corresponding to the taxi application card, it can mount the embedded window layer corresponding to the taxi application card on its own host layer (i.e., SurfaceView). Afterwards, when the electronic device runs the host application, the host application of the electronic device can display the embedded window layer corresponding to the taxi application card, that is, the host application of the electronic device displays the taxi application card.

[0139] Because when an electronic device displays a card corresponding to an application providing a card, the application providing a card running on the electronic device can create a card view, generate an embedded window layer corresponding to the card based on the card view, and send the embedded window layer corresponding to the card to the host application of the electronic device, so that the host application of the electronic device displays the embedded window layer corresponding to the card. That is, when the host application of the electronic device displays the card corresponding to the application providing a card, the host application of the electronic device displays the embedded window layer hanging below it, rather than directly displaying the card corresponding to the application providing the card. Therefore, the application of the electronic device can create a card view including custom card elements according to demand, and generate an embedded window layer including custom card elements based on the card view, so that when the host application of the electronic device displays notification information of the application, the host application of the electronic device can display a card view including different custom card elements.

[0140] In some examples, when the application providing the card is a travel application (such as a taxi application, a map application, etc.) or a delivery application (such as a food delivery application, a courier application, etc.), the custom card element can include a progress bar, which can be used to prompt the processing progress of the order of the travel application or the delivery application.

[0141] The progress bar will be schematically explained below with reference to FIG7 , taking a taxi application card displayed on the lock screen of an electronic device as an example.

[0142] After a ride-hailing app on an electronic device generates a ride-hailing order, the lock screen of the electronic device may display a ride-hailing app card. As shown in Figure 7, the ride-hailing app card 20 may include a progress bar 21. Progress bar 21 may be used to indicate the progress of the ride-hailing order. Progress bar 21 may include a first identifier 01 and a second identifier 02. First identifier 01 may indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), indicating the start of the ride-hailing order. Second identifier 02 may indicate the destination of the ride-hailing order, indicating the completion of the ride-hailing order. Progress bar 21 may also include a line 03 connecting first identifier 01 and second identifier 02. A vehicle identifier 04 displayed on line 03 indicates that a driver has accepted the order. Furthermore, after the driver accepts the order, the distance between vehicle identifier 04 and second identifier 02 indicates the proximity of the receiving vehicle to the destination of the ride-hailing order, indicating the progress of the ride-hailing order.

[0143] It should be noted that the first mark 01 and the second mark 02 can be located at the left and right ends of the progress bar 21, respectively. For example, as shown in FIG7 , the first mark 01 can be located at the left end of the progress bar 21, and the second mark 02 can be located at the right end of the progress bar 21. Of course, the first mark 01 can also be located at the right end of the progress bar 21, and the second mark 02 can also be located at the left end of the progress bar 21.

[0144] In addition, since the congestion conditions of the driving routes corresponding to the taxi orders are different, the colors of the connecting line 03 between the first identifier 01 and the second identifier 02 can be different, so that different colors can prompt the user of different congestion conditions. For example, the color of a certain section of the connecting line 03 between the first identifier 01 and the second identifier 02 can be red, and the red line segment can indicate that the driving section corresponding to the line segment is severely congested. For another example, the color of a certain section of the connecting line 03 between the first identifier 01 and the second identifier 02 can be yellow, and the yellow line segment can indicate that the driving section corresponding to the line segment is relatively congested. For another example, the color of a certain section of the connecting line between the first identifier 01 and the second identifier 02 can be green, and the green line segment can indicate that the driving section corresponding to the line segment is severely congested but relatively unobstructed.

[0145] 8 and 9 , the card display process of an embodiment of the present application is schematically illustrated by taking the case where the application providing the card is a taxi application, the host application is a lock screen, and the taxi application card includes a progress bar as an example.

[0146] For example, after a user opens a ride-hailing app on an electronic device, as shown in FIG8(a), the electronic device displays an interface 31 corresponding to the ride-hailing app. The ride-hailing app's interface 31 may include a departure location input box 32 and a destination input box 33. The user can enter the departure location and destination in the departure location input box 32 and the destination input box 33, respectively. After the electronic device receives the user's entry of the departure location and destination, as shown in FIG8(b), the electronic device displays a vehicle call interface 34. The vehicle call interface 34 may include a vehicle type selection control 35, a departure time selection control 36, a passenger number selection control 37, a payment method selection control 38, and a call control 39. The user can select the type of vehicle to receive the order using the vehicle type selection control 35, such as vehicle type A. The user can set the departure time using the departure time selection control 36, such as the current time. The user can set the number of passengers using the passenger number selection control 37, such as two passengers. The user can select a payment method using the payment method selection control 38, such as online payment. After selecting the vehicle, departure time, passenger number, and payment method, the user can click the call control 39. When the electronic device receives the user's trigger operation on the call control 39, in response, the taxi application of the electronic device generates a taxi order and publishes the taxi order to wait for the driver to accept the order.

[0147] When the electronic device's ride-hailing app detects that the driver has not yet accepted the order, as shown in FIG9(a), the electronic device may display a ride-hailing app card 41 on the lock screen 40. The ride-hailing app card 41 may include the ride-hailing app icon 411 and text 412 that reads "Waiting for driver to accept order." In conjunction with FIG9(a), the ride-hailing app card 41 may also include a progress bar 413. Progress bar 413 may include a first identifier 01, a second identifier 02, and a line 03 connecting the first and second identifiers 01 and 02. The first identifier 01 may indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), indicating that the ride-hailing order has begun. The second identifier 02 may indicate the destination of the ride-hailing order, indicating that the ride-hailing order has completed. At this point, no vehicle identifier is displayed on the line 03 connecting the first and second identifiers 01 and 02, reminding the user that the driver has not yet accepted the order.

[0148] When the electronic device's ride-hailing app detects that a driver has accepted a ride order, as shown in FIG9(b), the electronic device may display a ride-hailing app card 42 on the lock screen 40. The ride-hailing app card 42 may include a ride-hailing app icon 421 and text 422 stating "Driver has accepted the ride order." In conjunction with FIG9(b), the ride-hailing app card 42 may also include a progress bar 423. The progress bar 423 may include a first identifier 01, a second identifier 02, and a line 03 connecting the first and second identifiers 01 and 02. Compared to the progress bar 413 shown in FIG9(a), the progress bar 423 in the ride-hailing app card 42 may also include a vehicle identifier 04, located on the line 03 connecting the first and second identifiers 01 and 02, and adjacent to the first identifier 01. In other words, by displaying the vehicle identifier 04 on the line 03 connecting the first and second identifiers 01 and 02, adjacent to the first identifier 01, the driver is informed that the ride order has been accepted.

[0149] Afterward, the driver goes to the departure location to pick up the user. At this point, as shown in FIG9(c), the electronic device may display a ride-hailing application card 43 on the lock screen interface 40. Ride-hailing application card 43 may include a ride-hailing application icon 431, text 432 reading "License plate number XXX, arriving in about 2 minutes," and text 433 reading "Master Zhang, white." As shown in FIG9(c), ride-hailing application card 43 may also include a progress bar 434. Progress bar 434 may include a first identifier 01, a second identifier 02, a line 03 connecting the first and second identifiers 01 and 02, and a vehicle identifier 04 located on the line 03. Compared to the progress bar 423 shown in FIG9(b), the vehicle identifier 04 in progress bar 434 has moved a distance toward the second identifier 02, indicating that the receiving vehicle has traveled a certain distance. Specifically, the change in the distance between the vehicle identifier 04 and the second identifier 02 in progress bar 434 indicates that the receiving vehicle is heading toward the user's departure location. For example, the shorter the distance between the vehicle identifier 04 and the second identifier 02, the closer the order-receiving vehicle is to the user's departure location.

[0150] Afterward, when the electronic device's ride-hailing app detects the driver's arrival at the departure location, as shown in FIG9(d), the electronic device may display a ride-hailing app card 44 on the lock screen interface 40. The ride-hailing app card 44 may include a ride-hailing app icon 441, text 442 stating "Driver has arrived," and text 443 stating "Master Zhang, White." As shown in FIG9(d), the ride-hailing app card 44 may also include a progress bar 444. Progress bar 444 may include a first identifier 01, a second identifier 02, a line 03 connecting the first and second identifiers 01 and 02, and a vehicle identifier 04 located on the line 03. Compared to the progress bar 434 shown in FIG9(c), the vehicle identifier 04 in progress bar 444 continues to move a distance toward the second identifier 02, while its position remains unchanged. This indicates that the driver has arrived and that the user is urged to board the vehicle as soon as possible, based on the distance between the vehicle identifier 04 and the second identifier 02 and the movement of the vehicle identifier 04 in progress bar 444.

[0151] After the driver picks up the user and drives to the destination according to the ride order, as shown in FIG9(e), the electronic device may display a ride-hailing application card 45 on the lock screen interface 40. The ride-hailing application card 45 may include a ride-hailing application icon 451, text 452 reading "Driving to destination, approximately 20 minutes to arrive," and text 453 reading "Master Zhang, white." As shown in FIG9(e), the ride-hailing application card 45 may also include a progress bar 454. The progress bar 454 may include a first identifier 01, a second identifier 02, a line 03 connecting the first and second identifiers 01 and 02, and a vehicle identifier 04 located on the line 03. Compared to the progress bar 444 shown in FIG9(d), the vehicle identifier 04 in the progress bar 454 continues to move toward the second identifier 02, and the distance between the vehicle identifier 04 and the second identifier 02 gradually decreases. In other words, the gradually decreasing distance between the vehicle identifier 04 and the second identifier 02 in the progress bar 454 indicates that the receiving vehicle is heading toward the destination.

[0152] Afterwards, when the ride-hailing application detects that the user has arrived at the destination, as shown in FIG9(f), the electronic device may display a ride-hailing application card 46 on the lock screen interface 40. The ride-hailing application card 46 may include a ride-hailing application icon 461 and text 462 that reads "Arrived at destination." In conjunction with FIG9(f), the ride-hailing application card 46 may also include a progress bar 463. The progress bar 463 may include a first identifier 01, a second identifier 02, a line 03 connecting the first identifier 01 and the second identifier 02, and a vehicle identifier 04 located on the line 03 connecting the first identifier 01 and the second identifier 02. Compared to the ride-hailing application card 45 shown in FIG9(e), the vehicle identifier 04 in the progress bar 463 of the ride-hailing application card 46 has moved to the position of the second identifier 02, indicating that the order-receiving vehicle has arrived at the destination and the ride order has been completed.

[0153] That is to say, when the business of the taxi application changes (such as the processing progress of the taxi order changes), the progress bar included in the taxi application card displayed on the lock screen interface of the electronic device is updated synchronously.

[0154] In this example, a ride-hailing app running on an electronic device can generate a card view that includes a progress bar and send the embedded window layer corresponding to the card view that includes the progress bar to the host application. The host application on the electronic device can then display the embedded window layer corresponding to the card view that includes the progress bar. That is, the host application on the electronic device can display the ride-hailing app card that includes the progress bar. Furthermore, the progress bar can more intuitively and effectively display the progress of the ride-hailing order to the user, resulting in a better display effect. Furthermore, by updating the progress bar in real time based on the progress of the ride-hailing order, the timeliness of the ride-hailing app's notification information can be guaranteed, providing a better user experience.

[0155] In some examples, the progress bar can be a segmented progress bar. For example, continuing with the example of a ride-hailing application card displayed on the lock screen of an electronic device, the segmented progress bar described above is schematically illustrated. As shown in FIG10 , the ride-hailing application card 50 can include a segmented progress bar 51. The segmented progress bar 51 can be used to indicate the progress of the ride-hailing order. The segmented progress bar 51 can include a first marker 01, a second marker 02, and a third marker 05. The first marker 01 can be used to indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), that is, the first marker 01 can be used to indicate the start of the ride-hailing order. The second marker 02 can be used to indicate the destination of the ride-hailing order, that is, the second marker 02 can be used to indicate the completion of the ride-hailing order. The third marker 05 can be used to indicate the departure point of the user who placed the order. The third marker 03 is located between the first marker 01 and the second marker 02. The third marker 05 divides the connecting line between the first marker 01 and the second marker 02 into two segments, that is, the third marker 05 can divide the ride-hailing order processing process into two stages. That is to say, the first connecting line 06 between the first identifier 01 and the third identifier 05 can be used to indicate that the order-receiving vehicle is driving from the starting point to the departure point where the user is located. The second connecting line 07 between the third identifier 05 and the second identifier 02 can be used to indicate that the order-receiving vehicle is driving from the departure point where the user is located to the destination. As shown in Figure 10, the segmented progress bar 51 can also include a vehicle identifier 04. When the vehicle identifier 04 is on the first connecting line 06, it means that the order-receiving vehicle is driving from the starting point to the departure point where the user is located. When the vehicle identifier 04 is on the first connecting line 07, it means that the order-receiving vehicle has picked up the user and is driving from the departure point where the user is located to the destination.

[0156] It should be noted that the line type of the connecting line can indicate the current processing stage of the taxi order. For example, when the first connecting line 06 and the second connecting line 07 are both dotted lines, it indicates that the driver has not yet accepted the order. When the first connecting line 06 is a solid line and the second connecting line 07 is a dotted line, it indicates that the vehicle that accepts the order is driving from the starting point to the departure point where the user is located, that is, the current processing stage of the taxi order is the stage where the driver picks up the user, that is, the driver has not yet picked up the user and has not yet entered the stage where the driver sends the user to the destination. When the second connecting line 07 is a solid line, it indicates that the vehicle that accepts the order is driving from the departure point where the user is located to the destination, that is, the current processing stage of the taxi order enters the stage where the driver sends the user to the destination.

[0157] The first mark 01 and the second mark 02 can be located at the left and right ends of the segmented progress bar 51, respectively. For example, as shown in FIG10 , the first mark 01 can be located at the left end of the segmented progress bar 51, and the second mark 02 can be located at the right end of the segmented progress bar 51. Of course, the first mark 01 can also be located at the right end of the segmented progress bar 51, and the second mark 02 can also be located at the left end of the segmented progress bar 51.

[0158] In addition, since the congestion conditions of the driving routes corresponding to the taxi orders are different, the colors of the first connecting line 06 between the first logo 01 and the third logo 05 can be different, and the colors of the second connecting line 07 between the third logo 05 and the second logo 02 can also be different, so that different colors can prompt users of different congestion conditions.

[0159] 11 , the card display process of an embodiment of the present application is schematically illustrated by taking the case where the application providing the card is a taxi application, the host application is a lock screen, and the taxi application card includes a segmented progress bar.

[0160] After a user places a ride order using a ride-hailing app on an electronic device, if the ride-hailing app detects that the driver has not yet accepted the order, as shown in FIG11(a), the electronic device may display a ride-hailing app card 61 on the lock screen 60. The ride-hailing app card 61 may include a ride-hailing app icon 611 and text 612 that reads "Waiting for driver to accept order." As shown in FIG11(a), the ride-hailing app card 61 may also include a progress bar 613. Progress bar 613 may include a first marker 01, a second marker 02, and a third marker 05 located between the first and second markers 01 and 02. The first marker 01 may indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), indicating the start of the ride order. The second marker 02 may indicate the destination of the ride order, indicating the completion of the ride order. The third marker 05 may indicate the departure location of the user who placed the order. The segmented progress bar 613 also includes a first connecting line 06 between the first mark 01 and the third mark 05, and a second connecting line 07 between the third mark 05 and the second mark 02. At this time, the first connecting line 06 and the second connecting line 07 are both dotted lines, and the vehicle mark is not displayed on the first connecting line 06, to remind the user that the driver has not accepted the order yet.

[0161] Afterwards, when the taxi-hailing application of the electronic device detects that the driver has accepted the order, as shown in (b) of Figure 11, the electronic device may display a taxi-hailing application card 62 in the lock screen interface 60. The taxi-hailing application card 62 may include an icon 621 of the taxi-hailing application and a text 622 that reads "The driver has accepted the order." In conjunction with (b) of Figure 11, the taxi-hailing application card 62 may also include a segmented progress bar 623. The segmented progress bar 623 may include a first identifier 01, a second identifier 02, and a third identifier 05 located between the first identifier 01 and the second identifier 02. The segmented progress bar 613 also includes a first connecting line 06 between the first identifier 01 and the third identifier 05, a second connecting line 07 between the third identifier 05 and the second identifier 02, and a vehicle identifier 04. Compared with the segmented progress bar 613 shown in (a) in Figure 11, the first connecting line 06 is a solid line, and the vehicle identification 04 is located on the first connecting line 06. That is, by updating the line type of the first connecting line 06 from a dotted line to a solid line, and displaying the vehicle identification 04 on the first connecting line 06, the driver can be prompted that the order has been accepted and can accurately go to the departure point to pick up the user.

[0162] Afterwards, the driver drives to the departure location to pick up the user. At this time, as shown in (c) of Figure 11, the electronic device can display a taxi application card 63 in the lock screen interface 60. The taxi application card 63 may include an icon 631 of the taxi application, text 632 of "License plate number XXX·Arriving in about 2 minutes", and text 633 of "Master Zhang·White". In conjunction with (c) of Figure 11, the taxi application card 63 may also include a segmented progress bar 634. The segmented progress bar 634 may include a first identifier 01, a second identifier 02, and a third identifier 05 located between the first identifier 01 and the second identifier 02. The segmented progress bar 634 also includes a first connecting line 06 between the first identifier 01 and the third identifier 05, a second connecting line 07 between the third identifier 05 and the second identifier 02, and a vehicle identifier 04 located on the first connecting line 06. Compared with the segmented progress bar 623 shown in (b) of Figure 11, the vehicle identification 04 in the segmented progress bar 634 moves a distance toward the third identification 05 and is close to the third identification 05. That is, through the changes in the moving direction of the vehicle identification 04 in the segmented progress bar 634 and the distance between the vehicle identification 04 and the third identification 05, it can be prompted that the order vehicle is about to arrive at the departure place, and the user is requested to go to the departure place as soon as possible.

[0163] Afterwards, when the driver picks up the user and drives to the destination, as shown in (d) in Figure 11, the electronic device can display a taxi application card 64 in the lock screen interface 60. The taxi application card 64 may include an icon 641 of the taxi application, text 642 of "Driving to destination·Arriving in about 20 minutes", and text 643 of "Master Zhang·White". In conjunction with (d) in Figure 11, the taxi application card 64 may also include a segmented progress bar 644. The segmented progress bar 644 may include a first identifier 01, a second identifier 02, and a third identifier 05 located between the first identifier 01 and the second identifier 02. The segmented progress bar 644 also includes a first connecting line 06 between the first identifier 01 and the third identifier 05, a second connecting line 07 between the third identifier 05 and the second identifier 02, and a vehicle identifier 04. Compared with the segmented progress bar 634 shown in (c) of Figure 11, the second connecting line 07 in the segmented progress bar 644 is a solid line, and the vehicle identification 04 is located on the second connecting line 07, indicating that the order-receiving vehicle has picked up the user and is driving from the user's departure point to the destination. That is, by updating the line type of the second connecting line 07 from a dotted line to a solid line, and displaying the vehicle identification 04 on the second connecting line 07, it can be prompted that the driver has picked up the user and is heading to the destination.

[0164] Afterward, when the order-receiving vehicle arrives at the destination, as shown in FIG11(e), the electronic device may display a ride-hailing application card 65 on the lock screen interface 60. The ride-hailing application card 65 may include a ride-hailing application icon 651 and text 652 stating "Arrived at Destination." As shown in FIG11(e), the ride-hailing application card 65 may also include a segmented progress bar 653. Compared to the segmented progress bar 644 shown in FIG11(d), the segmented progress bar 653 includes a first identifier 01 and a second identifier 02, i.e., the segmented progress bar 653 does not include a third identifier. The segmented progress bar 653 may also include a solid line 03 connecting the first identifier 01 and the second identifier 02. This indicates that the order-receiving vehicle has arrived at the destination and the ride-hailing order has been completed by removing the third identifier and the vehicle identifier from the segmented progress bar 654 and displaying the line 03 connecting the first identifier 01 and the second identifier 02.

[0165] That is to say, when the business of the taxi application changes (the processing progress of the taxi order changes), the segmented progress bar included in the taxi application card displayed in the lock screen interface of the electronic device is updated synchronously.

[0166] In this example, the taxi-hailing application running on the electronic device can generate a card view including a segmented progress bar and send the embedded window layer corresponding to the card view including the segmented progress bar to the host application, so that the host application of the electronic device can display the embedded window layer corresponding to the card view including the segmented progress bar, that is, the host application of the electronic device can display the taxi-hailing application card including the segmented progress bar. Furthermore, the segmented progress bar can more intuitively and effectively display the processing progress of the taxi order to the user, with a better display effect. Furthermore, updating the segmented progress bar in real time according to the processing progress of the taxi order can ensure the timeliness of the notification information of the taxi-hailing application and provide a better user experience.

[0167] In some examples, when the application providing the card is a ride-hailing application, the ride-hailing application may include a first progress bar and a second progress bar. The first progress bar is used to indicate that the order-receiving vehicle drives from the starting point (i.e., the location of the order-receiving vehicle when the driver accepts the order) to the departure point where the user is located, and the second progress bar is used to indicate that the order-receiving vehicle drives from the departure point where the user is located to the destination.

[0168] 12 , we will continue to take the case where the application providing the card is a taxi application, the host application is a lock screen, and the taxi application card includes a first progress bar and a second progress bar as an example to schematically illustrate the card display process of an embodiment of the present application.

[0169] After a user places a ride order using a ride-hailing app on an electronic device, if the ride-hailing app detects that the driver has not yet accepted the order, as shown in FIG12(a), the electronic device may display a ride-hailing app card 71 on the lock screen 70. This card may include a ride-hailing app icon 711 and text 712 that reads "Waiting for driver to accept order." As shown in FIG12(a), the ride-hailing app card 71 may also include a first progress bar 713. The first progress bar 713 may include a first identifier 01, a third identifier 05, and a first connecting line 06 between the first and third identifiers 01 and 05. The first identifier 01 may indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), indicating the start of the ride order. The third identifier 05 may indicate the departure location of the user who placed the order. At this point, no vehicle identifier is displayed on the first connecting line 06 between the first and third identifiers 01 and 05, reminding the user that the driver has not yet accepted the order.

[0170] After a user places a ride order using a ride-hailing app on an electronic device, when the ride-hailing app detects that a driver has accepted the order, the electronic device may display a ride-hailing app card 72 on the lock screen 70, as shown in FIG12(b). The ride-hailing app card 72 may include a ride-hailing app icon 721 and text 722 stating "Driver has accepted the order." As shown in FIG12(b), the ride-hailing app card 72 may also include a first progress bar 723. The first progress bar 723 may include a first identifier 01, a third identifier 05, and a first connecting line 06 between the first and third identifiers 01 and 05. Compared to the first progress bar 713 shown in FIG12(a), the first progress bar 723 may also include a vehicle identifier 04 displayed on the first connecting line 06 between the first and third identifiers 01 and 05, with the vehicle identifier 04 positioned near the first identifier 01. This means that by displaying the vehicle identifier 04 near the first identifier 01 on the first connecting line 06 between the first and second identifiers 01 and 02, the driver is informed that the order has been accepted and is ready to travel to the departure location to pick up the user.

[0171] Afterward, the driver drives to the departure location to pick up the user. At this point, as shown in FIG12(c), the electronic device may display a ride-hailing application card 73 on the lock screen interface 70. The ride-hailing application card 73 may include a ride-hailing application icon 731, text 732 reading "License plate number XXX, arriving in about 2 minutes," and text 733 reading "Master Zhang, white." As shown in FIG12(c), the ride-hailing application card 73 may also include a first progress bar 734. The first progress bar 734 may include a first identifier 01, a third identifier 05, a first connecting line 06 between the first identifier 01 and the third identifier 05, and a vehicle identifier 04. Compared to the first progress bar 723 shown in FIG12(b), the vehicle identifier 04 in the first progress bar 734 moves a distance toward the third identifier 05, indicating that the receiving vehicle has traveled a distance toward the user's departure location. In other words, the change in the distance between the vehicle identifier 04 and the third identifier 05 in the first progress bar 734 indicates that the receiving vehicle is about to arrive at the departure location and that the user is urged to proceed to the departure location as soon as possible.

[0172] Afterward, when the driver arrives at the departure location, as shown in FIG12(d), the electronic device may display a ride-hailing application card 74 on the lock screen interface 70. The ride-hailing application card 74 may include a ride-hailing application icon 741, text 742 stating "Driver has arrived," and text 743 stating "Master Zhang, White." As shown in FIG12(d), the ride-hailing application card 74 may also include a first progress bar 744. The first progress bar 744 may include a first identifier 01, a third identifier 05, a first connecting line 06 between the first identifier 01 and the third identifier 05, and a vehicle identifier 04. Compared to the first progress bar 734 shown in FIG12(c), the vehicle identifier 04 in the first progress bar 744 moves to the location of the third identifier 05. This indicates that the driver has arrived at the departure location and is waiting for the user to board the vehicle, as indicated by the change in the distance between the vehicle identifier 04 and the third identifier 05 in the first progress bar 734.

[0173] Afterwards, when the driver picks up the user and drives to the destination, as shown in FIG12(e), the electronic device may display a ride-hailing application card 75 on the lock screen interface 70. The ride-hailing application card 75 may include a ride-hailing application icon 751, text 752 reading "Driving to destination, approximately 20 minutes to arrive," and text 753 reading "Master Zhang, white." As shown in FIG12(e), the ride-hailing application card 75 may also include a second progress bar 754. The second progress bar 754 may include a third identifier 05, a second identifier 02, a second connecting line 07 between the third identifier 05 and the second identifier 02, and a vehicle identifier 04 located on the second connecting line 07 between the third identifier 05 and the second identifier 02. Compared with the taxi application card 74 shown in (d) in Figure 12, the progress bar of the taxi application card 75 is updated to a second progress bar 754. The second progress bar is used to indicate that the vehicle receiving the order is driving from the user's departure point to the destination. That is to say, by updating the progress bar in the taxi application card 75 to the second progress bar 74 and displaying the vehicle logo 04 on the second progress bar 74, it can be prompted that the driver has picked up the user and is ready to drive to the destination.

[0174] Afterward, when the ride-hailing app detects that the user has arrived at the destination, as shown in FIG12(f), the electronic device may display a ride-hailing app card 76 on the lock screen interface 70. The ride-hailing app card 76 may include a ride-hailing app icon 761 and text 762 that reads "Arrived at Destination." As shown in FIG12(f), the ride-hailing app card 76 may also include a second progress bar 763. The second progress bar 763 may include a third identifier 05, a second identifier 02, a second connecting line 07 between the third identifier 05 and the second identifier 02, and a vehicle identifier 04 located on the second connecting line 07 between the third identifier 05 and the second identifier 02. Compared to the ride-hailing app card 75 shown in FIG12(e), the vehicle identifier 04 in the second progress bar 763 of the ride-hailing app card 76 has moved to the position of the second identifier 02, indicating that the ordering vehicle has arrived at the destination and the ride order has been completed.

[0175] That is to say, when the business of the taxi application changes (the processing progress of the taxi order changes), the progress bar included in the taxi application card displayed in the lock screen interface of the electronic device is updated synchronously.

[0176] In this example, a ride-hailing app running on an electronic device can generate a card view that includes a progress bar and send the embedded window layer corresponding to the card view that includes the progress bar to the host application. The host application on the electronic device can then display the embedded window layer corresponding to the card view that includes the progress bar. That is, the host application on the electronic device can display the ride-hailing app card that includes the progress bar. Furthermore, the progress bar can more intuitively and effectively display the progress of the ride-hailing order to the user, resulting in a better display effect. Furthermore, by updating the progress bar in real time based on the progress of the ride-hailing order, the timeliness of the ride-hailing app's notification information can be guaranteed, providing a better user experience.

[0177] In some examples, when the electronic device displays cards corresponding to other applications, it can also display a card including a progress bar. Taking the card of the food delivery application displayed on the lock screen of the electronic device as an example, the above-mentioned segmented progress bar is schematically explained.

[0178] As shown in Figure 13, the takeaway application card 80 may include a segmented progress bar 81. The segmented progress bar 81 can be used to prompt the user of the processing progress of the takeaway order. The segmented progress bar 81 may include a fourth identifier 08, a fifth identifier 09 and a sixth identifier 010. The fourth identifier 08 can be used to indicate the starting point (i.e., the location where the rider is when accepting the order), that is, the fourth identifier 08 can be used to indicate that the takeaway order has started to be executed. The fifth identifier 09 can be used to indicate the location of the user who placed the takeaway order, that is, the fifth identifier 09 can be used to indicate that the takeaway order has been completed. The sixth identifier 010 can be used to indicate the location of the merchant corresponding to the takeaway order. The sixth identifier 010 is located between the fourth identifier 08 and the fifth identifier 09. The sixth identifier 010 can divide the connecting line between the fourth identifier 08 and the fifth identifier 09 into two segments, that is, the sixth identifier 010 can divide the processing process of the takeaway order into two stages. That is to say, the third connecting line 011 between the fourth identifier 08 and the sixth identifier 010, the third connecting line 011 can be used to indicate the rider from the starting point to the location of the merchant, that is, the third connecting line 011 can be used to indicate the stage of the merchant accepting the order. The fourth connecting line 012 between the sixth identifier 010 and the fifth identifier 09, the fourth connecting line 012 can be used to indicate the rider from the location of the merchant to the user's location, that is, the fourth connecting line 012 can be used to indicate the stage of the rider delivering the order. As shown in Figure 13, the segmented progress bar 81 can also include a rider identifier 013. When the rider identifier 013 is on the third connecting line 011, it means that the rider is from the starting point to the location of the merchant, that is, the takeaway order is in the stage of the merchant accepting the order. When the rider identifier 013 is on the fourth connecting line 012, it means that the rider is from the location of the merchant to the user's location, that is, the takeaway order is in the stage of the rider delivering the order.

[0179] 14 , the card display process of an embodiment of the present application is schematically illustrated by taking the case where the application providing the card is a food delivery application, the host application is a notification center, and the food delivery application card includes a segmented progress bar as an example.

[0180] After a user places a takeout order using an electronic device's takeout app, when the electronic device's takeout app detects that the rider has not yet accepted the order, as shown in (a) of Figure 14, the electronic device may display a takeout app card 91 in the notification center 90. The takeout app card 91 may include an icon 911 of the takeout app and text 912 that reads "Waiting for the merchant to accept the order." In conjunction with (a) of Figure 14, the takeout app card 91 may also include a segmented progress bar 913. The segmented progress bar 913 may include a fourth identifier 08, a fifth identifier 09, and a sixth identifier 010 located between the fourth and fifth identifiers 08 and 09. The fourth identifier 08 may be used to indicate the starting point (i.e., the location of the rider when accepting the order), i.e., the fourth identifier 08 may be used to indicate the start of the takeout order. The fifth identifier 09 may be used to indicate the location of the user who placed the takeout order, i.e., the fifth identifier 09 may be used to indicate that the takeout order has been completed. The sixth identifier 010 may be used to indicate the location of the merchant corresponding to the takeout order. 14( a ), the segmented progress bar 913 further includes a third connecting line 011 between the fourth marker 08 and the sixth marker 010, and a fourth connecting line 012 between the sixth marker 010 and the fifth marker 09. At this point, the third connecting line 011 and the fourth connecting line 012 are both dashed lines to remind the user that the merchant has not yet accepted the order.

[0181] Afterwards, when the food delivery application of the electronic device detects that the merchant has accepted the order, as shown in (b) of Figure 14, the electronic device may display a food delivery application card 92 in the notification center 90. The food delivery application card 92 may include an icon 921 of the food delivery application, a text 922 that reads "The merchant has accepted the order," and a text 923 that reads "Estimated delivery at 12:42." As shown in (b) of Figure 14, the food delivery application card 92 may further include a segmented progress bar 924. The segmented progress bar 924 may include a fourth identifier 08, a fifth identifier 09, and a sixth identifier 010 located between the fourth identifier 08 and the fifth identifier 09. The segmented progress bar 924 also includes a third connecting line 011 between the fourth identifier 08 and the sixth identifier 010, and a fourth connecting line 012 between the sixth identifier 010 and the fifth identifier 09. Compared with the segmented progress bar 913 shown in (a) in Figure 14, the third connecting line 011 is a solid line and the fourth connecting line 012 is a dotted line. That is, by updating the line type of the third connecting line 011 from a dotted line to a solid line, it can be prompted that the merchant has accepted the order, is delivering the food accurately, and is waiting for the rider to accept the order.

[0182] Afterwards, when the rider accepts the order and goes to the merchant to pick up the order, as shown in (c) in Figure 14, the electronic device can display a takeaway application card 93 in the notification center 90. The takeaway application card 93 may include an icon 931 of the takeaway application, a text 932 that reads "The rider has accepted the order," and a text 933 that reads "1 kilometer away from the merchant, 1 minute to arrive." In conjunction with (c) in Figure 14, the takeaway application card 93 may further include a segmented progress bar 934. The segmented progress bar 934 may include a fourth identifier 08, a fifth identifier 09, and a sixth identifier 010 located between the fourth identifier 08 and the fifth identifier 09. The segmented progress bar 934 may further include a third connecting line 011 between the fourth identifier 08 and the sixth identifier 010, and a fourth connecting line 012 between the sixth identifier 010 and the fifth identifier 09. Compared with the segmented progress bar 924 shown in (b) of Figure 14, the segmented progress bar 934 can also include a rider logo 013 displayed on the third connecting line 011, that is, by displaying the rider logo 013 on the third connecting line 011 in the segmented progress bar 934, it can be prompted that the rider has accepted the order and is heading to the merchant to pick up the order.

[0183] Afterwards, when the rider picks up the takeaway from the merchant and delivers it to the user, as shown in (d) in Figure 14, the electronic device can display a takeaway application card 94 in the notification center 90. The takeaway application card 94 may include an icon 941 of the takeaway application, a text 942 that reads "The rider is delivering the food", and a text 943 that reads "602 meters away from you, expected to arrive in 8 minutes". In conjunction with (d) in Figure 14, the takeaway application card 94 may also include a segmented progress bar 944. The segmented progress bar 944 may include a fourth identifier 08, a fifth identifier 09, and a sixth identifier 010 located between the fourth identifier 08 and the fifth identifier 09. The segmented progress bar 944 also includes a third connecting line 011 between the fourth identifier 08 and the sixth identifier 010, a fourth connecting line 012 between the sixth identifier 010 and the fifth identifier 09, and a rider identifier 013. Compared with the segmented progress bar 934 shown in (c) in Figure 14, the third connecting line 011 and the fourth connecting line 012 are both solid lines, and the rider logo 013 is located on the fourth connecting line 012, indicating that the rider has picked up the takeaway from the merchant and is traveling from the merchant to the user's location. That is, the line type of the fourth connecting line 012 is updated from a dotted line to a solid line, and the rider logo 013 is displayed on the fourth connecting line 012, which indicates that the rider has picked up the takeaway from the merchant and is delivering the takeaway to the user.

[0184] Afterwards, when the rider has delivered the takeaway to the destination, as shown in (e) in FIG14 , the electronic device may display a takeaway application card 95 in the notification center 90. The takeaway application card 95 may include an icon 951 of the takeaway application, a text 952 that reads “Order delivered”, and a text 953 that reads “Welcome back again”. In conjunction with (e) in FIG14 , the takeaway application card 95 may further include a segmented progress bar 954. Compared to the segmented progress bar 944 shown in (d) in FIG14 , the segmented progress bar 954 may include the fourth identifier 08 and the fifth identifier 09, but not the sixth identifier. In addition, the segmented progress bar 954 can also include a connecting line 014 between the fourth identifier 08 and the fifth identifier 09, and the connecting line 014 between the fourth identifier 08 and the fifth identifier 09 is a solid line, that is, by canceling the display of the sixth identifier and the rider identifier in the segmented progress bar 954, and displaying the connecting line 014 between the fourth identifier 08 and the fifth identifier 09, it can be indicated that the takeaway has been delivered and the takeaway order has been completed.

[0185] That is, when the business of the food delivery application changes (the processing progress of the food delivery order changes), the segmented progress bar included in the food delivery application card displayed in the notification center of the electronic device is updated synchronously.

[0186] In this example, the food delivery application running on the electronic device can generate a card view including a segmented progress bar, and send the embedded window layer corresponding to the card view including the segmented progress bar to the host application, so that the host application of the electronic device can display the embedded window layer corresponding to the card view including the segmented progress bar, that is, the host application of the electronic device can display the food delivery application card including the segmented progress bar. Furthermore, the segmented progress bar can be used to more intuitively and effectively display the processing progress of the food delivery order to the user, with a better display effect. Furthermore, the real-time updating of the segmented progress bar according to the processing progress of the food delivery order can ensure the timeliness of the notification information of the food delivery application, and provide a better user experience.

[0187] It should be noted that when a host application of an electronic device displays a card, the host application running in the foreground of the electronic device may change. For different host applications, the content to be displayed on the interface of the electronic device is different. Therefore, it is possible to display appropriate cards based on the display content of the host application. In other words, when different host applications display cards corresponding to the application providing the card, the display method of the card corresponding to the application providing the card is different. The display method of the card corresponding to the application providing the card may include at least one of the display content, display size, and display position.

[0188] 15 , the card display process of an embodiment of the present application is schematically illustrated by taking the application that provides the card as a taxi-hailing application as an example.

[0189] When a user needs to take a taxi, they can use the taxi application on the electronic device to place an order. Afterwards, when the electronic device displays the desktop, when the service of the taxi application changes (such as the driver accepts the order), as shown in (a) of Figure 15, a taxi application card 111 can be displayed at the top of the desktop 110 of the electronic device. The taxi application card 111 can be used to prompt the driver that the order has been accepted. As shown in (a) of Figure 15, the taxi application card 111 can include the taxi application icon 112, the text "License plate number XXX·Arriving in about 2 minutes" 113, and the text "Master Zhang·White" 114. The taxi application card 111 can also include a call control 115, which can be used to contact the driver who accepted the order. The display height of the taxi application card 111 is h1, and the display width of the taxi application card 111 is d1.

[0190] After the electronic device's desktop 110 displays a ride-hailing application card 111, when the user pulls down from the top status bar of the display screen, the electronic device displays a notification center 120 in response, as shown in FIG15(b). The ride-hailing application card 121 is also displayed in the notification center 120. As shown in FIG15(b), the ride-hailing application card 121 may include a ride-hailing application icon 122, text 123 reading "License plate number XXX, arriving in about 2 minutes," and text 124 reading "Master Zhang, white." Compared to the ride-hailing application card 111 shown in FIG15(a), the ride-hailing application card 121 may also include a progress bar 125. The progress bar 125 can more intuitively inform the user of the progress of the ride order. Furthermore, the display height of the ride-hailing application card 121 is h2, and the display width of the ride-hailing application card 121 is d2. The display height h2 of the ride-hailing application card 121 is less than the display height h1 of the ride-hailing application card 111. The display width d2 of the taxi application card 121 can be equal to the display width d1 of the taxi application card 111. Thus, when the host application running in the foreground of the electronic device switches from the desktop to the notification center, the display size of the taxi application card can be reduced, thereby reducing the space occupied by the taxi application card and allowing the electronic device to display more other notification information cards. This allows the user to view more notification information cards without having to scroll through them, thereby improving the efficiency of human-computer interaction.

[0191] After the electronic device's desktop 110 displays a ride-hailing application card 111, the electronic device enters a lock screen state when it receives a user's lock screen operation (e.g., pressing the lock screen button). While the electronic device is in the lock screen state, in response to a user's touch operation on the electronic device's display, the electronic device displays a lock screen interface 130, as shown in FIG15(c). The ride-hailing application card 131 is also displayed on the lock screen interface 130. As shown in FIG15(c), the ride-hailing application card 131 may include a ride-hailing application icon 132, text 133 reading "License plate number XXX, arriving in about 2 minutes," and text 134 reading "Master Zhang, white." Compared to the ride-hailing application card 111 shown in FIG15(a) and the ride-hailing application card 121 shown in FIG15(b), the ride-hailing application card 131 may also include a progress bar 135. The progress bar 135 can more intuitively inform the user of the progress of the ride order. Furthermore, the display height of the ride-hailing application card 131 is h3, and the display width of the ride-hailing application card 131 is d3. The display height h3 of the ride-hailing application card 131 is less than the display height h2 of the ride-hailing application card 121. The display width d3 of the ride-hailing application card 131 can be equal to the display width d1 of the ride-hailing application card 111. Furthermore, the ride-hailing application card 131 is located at the bottom of the lock screen interface 130, while the ride-hailing application card 111 is located at the top of the desktop 110. This means that the display position of the ride-hailing application card 131 is different from that of the ride-hailing application card 111. As can be seen, when the host application running in the foreground of the electronic device switches from the desktop to the lock screen, the display size of the ride-hailing application card can be reduced, reducing the space occupied by the ride-hailing application card. This allows the electronic device to display more other notification information cards, allowing the user to view more notification information cards without having to scroll through them, thereby improving the efficiency of human-computer interaction.

[0192] After the electronic device displays the ride-hailing application card 111 on its desktop 110, when the electronic device receives a lock screen operation from the user (e.g., pressing the lock screen button), the electronic device displays an always on display (AOD) interface 140, as shown in FIG15(d), and displays the ride-hailing application card 141 on the AOD interface 140. Compared to the ride-hailing application card 111 shown in FIG15(a), the ride-hailing application card 141 is a card capsule. When the electronic device receives a touch operation (e.g., a slide operation) from the user on the ride-hailing application card 141 (i.e., the card capsule), the electronic device opens the ride-hailing application. Furthermore, due to the limited space available on the electronic device's off-screen interface, the display height h4 of the ride-hailing application card 141 (i.e., card capsule) is smaller than the display height h1 of the ride-hailing application card 111, and the display width d3 of the ride-hailing application card 141 (i.e., card capsule) is smaller than the display width d1 of the ride-hailing application card 111. This minimizes the space occupied by the ride-hailing application card when the host application running in the foreground of the electronic device switches to the off-screen interface, preventing the ride-hailing application card from being incompletely displayed. Furthermore, as shown in FIG15 (d), due to the smaller display size of the ride-hailing application card 141 (i.e., card capsule), the ride-hailing application card 141 (i.e., card capsule) can include some information related to the ride-hailing order (e.g., the ride-hailing application icon 142 and the text "License Plate Number XXX" 143). This allows users to obtain some information about the ride-hailing application without opening the ride-hailing application, making it more convenient to use.

[0193] In this example, when a host application on an electronic device displays a card, the card display method can be different for different host applications, ensuring that the cards displayed in different host applications have a good display effect. Furthermore, the content information carried by the card can be set with emphasis based on the content to be displayed by different host applications and user usage habits to achieve the purpose of notifying the user, improve the efficiency of human-computer interaction, and thus enhance the user experience.

[0194] The methods in the following embodiments can all be implemented in an electronic device having the above hardware structure or software structure.

[0195] Since after the electronic device is turned on, the host application (desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) registers the business changes of the taxi application (not shown in the figure), therefore, when the business changes of the taxi application occur, the electronic device can generate a card view of the taxi application card corresponding to each host application in all host applications that have registered the business changes of the taxi application, and when a host application is running in the foreground of the electronic device, the card view of the taxi application card corresponding to the host application is displayed, that is, the taxi application card corresponding to the host application is displayed.

[0196] The following describes a card display method provided in an embodiment of the present application in detail, taking the card providing application as a taxi-hailing application and the host application as a first host application as an example, in conjunction with Figure 16. Figure 16 is a schematic flow chart of a card display method provided in an embodiment of the present application. As shown in Figure 16, the card display method may include the following steps S1601-S1630.

[0197] S1601. The taxi application generates a taxi order.

[0198] In some examples, a ride-hailing application on an electronic device may receive an order from a user and, in response to the order, generate a ride order. Specifically, when a user places a ride order using the ride-hailing application on an electronic device, the user may launch the ride-hailing application and perform a corresponding order operation on the ride-hailing application. This means that the ride-hailing application on the electronic device may receive the user's order operation. The ride-hailing application on the electronic device then generates a ride order in response to the user's order operation.

[0199] The above-mentioned order placement operation may include one operation or multiple operations.

[0200] For example, when the order placement operation includes multiple operations, the order placement operation may include an operation for inputting information related to the taxi order and an operation for triggering the generation of the taxi order. For example, the operation for inputting information related to the taxi order may include an operation for inputting departure location information, destination information, departure time information, and vehicle type information. The operation for triggering the generation of the taxi order may be a click on an order placement control. For example, the order placement control may be the call control 39 shown in FIG8( b ).

[0201] S1602. The taxi-hailing application sends the card UUID and card instance information to the decision-making center.

[0202] After the taxi application generates a taxi order, the taxi application can generate card instance information (i.e., cardInstanceId) corresponding to the taxi order. After the taxi application of the electronic device generates the cardInstanceId corresponding to the taxi order, the taxi application can send the cardInstanceId corresponding to the taxi order to the decision-making center.

[0203] The card instance information can be used to indicate a taxi order generated by a taxi application, that is, a unique card instance information is generated for each taxi order.

[0204] For example, when a user places two taxi orders (e.g., Order A and Order B) using a taxi app, card instance information 1 corresponding to Order A and card instance information 2 corresponding to Order B may be generated. If the processing progress of Order A changes, the taxi app can determine, based on card instance information 1, that the taxi app card to be displayed on the electronic device is the taxi app card corresponding to Order A. If the processing progress of Order B changes, the taxi app can determine, based on card instance information 2, that the taxi app card to be displayed on the electronic device is the taxi app card corresponding to Order B.

[0205] In addition, after the taxi application of the electronic device generates a taxi order, when the processing progress of the taxi order changes (such as the driver accepts the order), the taxi application can generate a card UUID and send the card UUID to the decision-making center of the electronic device to notify the decision-making center that the taxi application card corresponding to the card UUID (that is, the card corresponding to the notification information of the taxi application) needs to be displayed.

[0206] The card UUID can be used to uniquely identify a set of cards corresponding to the ride-hailing application's business (i.e., the processing progress of a ride order). In other words, when the processing progress of a ride order changes, the ride-hailing application sends the card UUID to the decision-making center.

[0207] Specifically, when the host application of the electronic device displays a card, the host application running in the foreground of the electronic device may change. For different host applications, the content to be displayed on the interface of the electronic device is different. That is to say, for the same service of the taxi application (such as the driver accepting an order), the taxi application cards displayed in different host applications of the electronic device are different. Therefore, the card UUID can be used to uniquely identify a group of cards corresponding to a service of the taxi application, that is, the desktop of the electronic device corresponds to the taxi application card, the lock screen of the electronic device corresponds to the taxi application card, the notification center of the electronic device corresponds to the taxi application card, the banner notification (or status bar) of the electronic device corresponds to the taxi application card, the screen off of the electronic device corresponds to the taxi application card, and the negative one screen of the electronic device corresponds to the taxi application card.

[0208] For example, after a taxi-hailing application on an electronic device generates a taxi order, the application will publish the taxi task and wait for the driver to accept the order. After the driver accepts the order, the application can generate a card UUID (such as a8146578-c7b1-4a19-92eb-f91ae4542779) that identifies a set of cards indicating that the driver has accepted the order, and send the card UUID to the decision-making center of the electronic device to notify the decision-making center that it needs to display the card indicating that the driver has accepted the order.

[0209] S1603. The decision-making center sends a card creation notification to the card display service. The card creation notification includes the card UUID and cardInstanceId. The card creation notification is used to instruct the card display service to create a taxi application card.

[0210] After the decision-making center of the electronic device receives the card UUID sent by the taxi application, the decision-making center can obtain the AppClipInfo (such as the package name of the taxi application, etc.) corresponding to the business of the taxi application based on the card UUID. The decision-making center can determine whether the taxi application has the card display permission based on the AppClipInfo. For example, the decision-making center can compare the package name of the taxi application with the white list stored in the electronic device. When the package name of the taxi application is in the white list stored in the electronic device, it is determined that the taxi application has the card display permission. After the decision-making center determines that the taxi application has the card display permission, the decision-making center can determine that the taxi application is an application that meets the emergency conditions, and then the decision-making center can send a card creation notification to the card display service to notify the card display service to create a taxi application card (that is, the card corresponding to the notification information of the taxi application).

[0211] It should be noted that applications that meet emergency conditions may be pre-set applications. Pre-set applications may include applications related to time information (such as taxi-hailing applications, food delivery applications, map applications, and express delivery applications), applications related to property information (such as payment applications, financial applications, etc.), and applications related to personal safety information (such as motion monitoring applications, emergency call applications, etc.).

[0212] S1604. The card display service sends a card display notification to the first host application of the electronic device. The card display notification may include a card UUID and a cardInstanceId. The card display notification is used to notify the first host application of the electronic device to display the taxi application card.

[0213] The card UUID can be obtained from a ride-hailing application. Specifically, after the ride-hailing application on the electronic device generates a ride order, when the processing progress of the ride-hailing application changes, the ride-hailing application generates and sends the card UUID to the decision-making center of the electronic device. After receiving the card UUID, the decision-making center sends a card creation notification carrying the card UUID to the card display service of the electronic device.

[0214] The cardInstanceId can be obtained from the taxi application. Specifically, after the taxi application of the electronic device generates a taxi order, the taxi application generates the cardInstanceId corresponding to the taxi order. After the taxi application of the electronic device generates the cardInstanceId corresponding to the taxi order, the taxi application can send the cardInstanceId corresponding to the taxi order to the decision-making center. After the decision-making center receives the cardInstanceId, the decision-making center can send a card creation notification carrying the cardInstanceId to the card display service of the electronic device, and then the card display service can send a card display notification carrying the cardInstanceId to the first host application of the electronic device.

[0215] In one example, after the electronic device is turned on, the host application (desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) can register the business changes of the taxi application (not shown in the figure). When the business changes of the taxi application, the card display service sends a card display notification to these host applications to notify the host applications of the electronic device that the taxi application card currently needs to be displayed. After each host application of the electronic device receives the card display notification sent by the card display service, each host application of the electronic device can send a card display notification to the Host AAR corresponding to the host application to notify the Host AAR corresponding to the host application that the taxi application card currently needs to be displayed.

[0216] The above registration process can also be performed at other times, for example, when the electronic device installs a taxi-hailing application or when the electronic device updates the taxi-hailing application. This application does not limit this.

[0217] That is to say, after the card display service of the electronic device receives the card creation notification sent by the decision-making center, the card display service can send card display notifications to the host applications of the business changes of the above-mentioned registered taxi-hailing application respectively. The host applications of the business changes of the above-mentioned registered taxi-hailing application include the above-mentioned first host application, that is, the first host application can be any one of the desktop, negative one screen, notification center, banner notification, screen off or lock screen. It should be noted that the specific implementation process of the card display service sending card display notifications to multiple host applications of the business changes of the registered taxi-hailing application can be illustrated by taking S1604 (that is, the specific implementation process of the card display service sending card display notifications to the first host application) as an example.

[0218] S1605: The first host application sends a card display notification to the Host AAR corresponding to the first host application. The card display notification may include a card UUID and a cardInstanceId.

[0219] After the first host application receives the card display notification sent by the card display service, the first host application can send a card display notification to the Host AAR corresponding to the first host application to notify the Host AAR corresponding to the first host application that the taxi application card currently needs to be displayed.

[0220] It should be noted that, after the card display service of the electronic device receives the card creation notification sent by the decision-making center, the card display service can send card display notifications to all host applications of the business changes of all registered taxi-hailing applications. Therefore, after each host application of the business changes of all registered taxi-hailing applications receives the card display notification sent by the card display service, each host application can send a card display notification to the Host AAR corresponding to the host application. The specific implementation process of each host application sending a card display notification to the Host AAR corresponding to the host application can be illustrated by taking S1605 (i.e., the specific implementation process of the first host application sending a card display notification to the Host AAR corresponding to the first host application) as an example.

[0221] S1606. The Host AAR corresponding to the first host application sends the card UUID, cardInstanceId, hostinfo corresponding to the first host application, and size corresponding to the first host application to the card management service.

[0222] After the Host AAR corresponding to the first host application receives the card UUID and cardInstanceId sent by the first host application, the Host AAR corresponding to the first host application may send the card UUID and cardInstanceId to the card management service.

[0223] The identification information corresponding to the first host application (i.e., hostinfo) and the card size information corresponding to the first host application (i.e., size) can be pre-generated by the first host application. For example, after the electronic device is turned on, the first host application can register the service change of the taxi-hailing application. After the first host application registers the service change of the taxi-hailing application, the first host application can generate the hostinfo corresponding to the first host application and the size corresponding to the first host application, and send the hostinfo corresponding to the first host application and the size corresponding to the first host application to the card management service through the Host AAR corresponding to the first host application.

[0224] Before introducing the hostinfo corresponding to the first host application, the hostinfo of the host application is first explained.

[0225] The hostinfo of the host application may include a host identifier (ie, host id) corresponding to the host application and a card view identifier (ie, view id) corresponding to the host application.

[0226] The host identifier may be used to uniquely identify a host application of the electronic device, that is, different host applications of the electronic device correspond to different host identifiers.

[0227] For example, taking the host applications of an electronic device including the desktop, notification center, lock screen, screen off, negative one screen, and banner notification as an example, the host id corresponding to the desktop is 1, the host id corresponding to the notification center is 2, the host id corresponding to the lock screen is 3, the host id corresponding to the screen off is 4, the host id corresponding to the negative one screen is 5, and the host id corresponding to the banner notification is 6.

[0228] The card view identifier can uniquely identify the card view (ie, view) corresponding to the card to be displayed by the host application.

[0229] For example, continuing to take the example of the host applications of the electronic device including the desktop, notification center, lock screen, screen off, negative one screen, and banner notification, for the same service of the taxi application (such as the driver accepting an order), the view id of the card view of the taxi application card corresponding to the desktop is 1, the view id of the card view of the taxi application card corresponding to the notification center is 2, the view id of the card view of the taxi application card corresponding to the lock screen is 3, the view id of the card view of the taxi application card corresponding to the screen off is 4, the view id of the card view of the taxi application card corresponding to the negative one screen is 5, and the view id of the card view of the taxi application card corresponding to the banner notification is 6.

[0230] It should be noted that because different host applications have different card view identifiers for the same ride-hailing application card, when the host application of the electronic device displays the ride-hailing application card, the electronic device can determine the view ID corresponding to the host application based on the host ID corresponding to the host application, and then obtain the card view of the ride-hailing application card from the ride-hailing application based on the view ID corresponding to the host application.

[0231] The hostinfo corresponding to the first host application is described below.

[0232] The hostinfo of the first host application may include a host id corresponding to the first host application and a view id corresponding to the first host application.

[0233] The host ID corresponding to the first host application can be used to uniquely identify the first host application. For example, if the first host application is the desktop, the host ID corresponding to the first host application is 1. For another example, if the first host application is the notification center, the host ID corresponding to the first host application is 2.

[0234] The view id corresponding to the first host application is the identification information of the card view corresponding to the card to be displayed by the first host application. For example, if the first host application is the desktop, the view id corresponding to the first host application is 1. For another example, if the first host application is the notification center, the view id corresponding to the first host application is 2.

[0235] The host application's card size information can be the size information of the card view corresponding to the card allowed to be displayed by the host application, that is, the size information of the card view generated by the application that provides the card (such as a ride-hailing application). The host application's card size information can include display height and display width.

[0236] The card size information corresponding to the first host application is the size information of the card view corresponding to the card allowed to be displayed by the first host application. For example, if the first host application is the desktop, the card size information corresponding to the first host application may include display height h1 and display width d1. For another example, if the first host application is the screen off, the card size information corresponding to the first host application may include display height h4 and display width d4, where display height h4 is smaller than display height h1, and display width d4 is smaller than display width d1.

[0237] It should be noted that, since each host application in the host application (such as the desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) of the business change of the registered taxi application can send a card display notification to the Host AAR corresponding to the host application, therefore, after the Host AAR corresponding to each host application receives the card display notification, the Host AAR corresponding to each host application can send the card UUID, cardInstanceId, hostinfo corresponding to the host application and size corresponding to the host application to the card management service. Among them, the specific implementation process of each host application sending the card UUID, cardInstanceId, hostinfo corresponding to the host application and size corresponding to the host application to the card management service can be illustrated by taking S1606 (i.e. the specific implementation process of the Host AAR corresponding to the first host application sending the card UUID, cardInstanceId, hostinfo corresponding to the first host application and size corresponding to the first host application to the card management service) as an example.

[0238] S1607. The card management service obtains the AppClipInfo corresponding to the taxi-hailing application's service based on the card UUID.

[0239] The AppClipInfo corresponding to the business of the taxi-hailing application may include the package name of the taxi-hailing application, the class name of the specific implementation corresponding to the business of the taxi-hailing application, etc.

[0240] Specifically, after the card management service of the electronic device receives the card UUID sent by the Host AAR corresponding to the first host application, the card management service can obtain the AppClipInfo corresponding to the service of the taxi application according to the card UUID through the package manager service (PMS).

[0241] Because the card UUID can be used to uniquely identify a set of cards corresponding to the taxi application's services (i.e., the processing progress of taxi orders), the card management service can obtain the AppClipInfo corresponding to the taxi application's services based on the card UUID. Based on this AppClipInfo, the card kit corresponding to the taxi application can then determine and call the card kit corresponding to the taxi application. The card kit corresponding to the taxi application can then determine the Taxi Provider corresponding to the taxi application's services based on this AppClipInfo. The card kit corresponding to the taxi application can then obtain the card view corresponding to the taxi application card from the Taxi Provider corresponding to the taxi application's services.

[0242] S1608. The card management service sends AppClipInfo, cardInstanceId, hostinfo corresponding to the first host application, and size corresponding to the first host application to the card kit corresponding to the taxi application.

[0243] After the card management service obtains the AppClipInfo corresponding to the business of the taxi-hailing application based on the card UUID, the card management service can determine the card kit corresponding to the taxi-hailing application based on the AppClipInfo corresponding to the business of the taxi-hailing application, and send the AppClipInfo, cardInstanceId, hostinfo corresponding to the first host application, and size corresponding to the first host application corresponding to the business of the taxi-hailing application to the card kit corresponding to the taxi-hailing application.

[0244] It should be noted that, due to the host applications (such as desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) of the business changes of the registered taxi application, each host application can send the card UUID, cardInstanceId, hostinfo corresponding to the host application and the size corresponding to the host application to the card management service. Therefore, after the card management service receives the card UUID, cardInstanceId, hostinfo corresponding to the host application and the size corresponding to the host application sent by any host application, the card management service can obtain AppClipInfo according to the card UUID. After the card management service obtains AppClipInfo according to the card UUID, the card management service determines and sends the AppClipInfo, cardInstanceId, hostinfo corresponding to the host application and the size corresponding to the host application to the card kit corresponding to the taxi application based on the AppClipInfo.

[0245] In an embodiment of the present application, after the card kit corresponding to the taxi application receives the AppClipInfo, cardInstanceId, hostinfo corresponding to the first host application, and size corresponding to the first host application sent by the card management service, the card kit corresponding to the taxi application can determine the Taxi Provider corresponding to the taxi application's business based on the AppClipInfo, and then the card kit corresponding to the taxi application can obtain the card view corresponding to the taxi application card from the Taxi Provider corresponding to the taxi application's business. After the card kit corresponding to the taxi application obtains the card view corresponding to the taxi application card, the card kit corresponding to the taxi application can generate an embedded window layer corresponding to the taxi application card based on the card view corresponding to the taxi application card. After the card kit corresponding to the taxi application generates the embedded window layer corresponding to the taxi application card, the card kit corresponding to the taxi application can send the embedded window layer corresponding to the taxi application card to the first host application, so that the first host application displays the embedded window layer corresponding to the taxi application card, that is, the first host application displays the taxi application card.

[0246] In some examples, in order to avoid the first host application of the electronic device displaying cards of other applications during the process in which the card kit corresponding to the taxi application obtains the card view corresponding to the taxi application card from TaxiProvider and generates the embedded window layer corresponding to the taxi application card based on the card view, before the card kit corresponding to the taxi application obtains the card view corresponding to the taxi application card from TaxiProvider, the card kit corresponding to the taxi application can generate an embedded window layer (i.e., a placeholder embedded window layer) for placeholder without adding the card view corresponding to the taxi application card, and send the placeholder embedded window layer to the Host AAR corresponding to the first host application, so that the Host AAR corresponding to the first host application adds a placeholder view in the placeholder embedded window layer, and then the Host AAR corresponding to the first host application can send the placeholder embedded window layer with the placeholder view added to the first host application, so that the first host application can mount the placeholder embedded window layer with the placeholder view added to the host layer of the first host application itself for placeholder.

[0247] Specifically, for the specific implementation process of the card kit corresponding to the taxi-hailing application generating a placeholder embedded window layer, see S1609-S1615.

[0248] In some examples, when a data packet of an embedded window layer corresponding to a created taxi application card exists in the cache of the electronic device, when the card kit corresponding to the taxi application creates a placeholder embedded window layer, the card kit corresponding to the taxi application can obtain status information of the data packet (i.e., SurfacePackage) of the embedded window layer corresponding to the created taxi application card. When the status information indicates that the data packet of the embedded window layer corresponding to the created taxi application card is valid, the card kit corresponding to the taxi application can use the embedded window layer corresponding to the created taxi application card as a placeholder embedded window layer (i.e., an embedded window layer for a placeholder card view to which the taxi application card is not added).

[0249] Specifically, the card kit corresponding to the taxi-hailing application can use the embedded window layer corresponding to the created taxi-hailing application card as a placeholder embedded window layer. For the specific implementation process, see S1609-S1611.

[0250] When the status information indicates that the data packet of the embedded window layer corresponding to the created taxi application card is invalid, the card kit corresponding to the taxi application can create a placeholder embedded window layer (that is, an embedded window layer for the card view corresponding to the taxi application card that is not added and is used as a placeholder).

[0251] In some examples, when there is no data packet of the embedded window layer corresponding to the created taxi application card in the cache of the electronic device, the card kit corresponding to the taxi application can create a placeholder embedded window layer.

[0252] Specifically, for the specific implementation process of the card kit corresponding to the taxi application creating a placeholder embedded window layer, see S1612-S1615.

[0253] The following is a schematic illustration of the specific implementation process of generating a placeholder embedded window layer by the card kit corresponding to the taxi-hailing application.

[0254] S1609. The card kit corresponding to the taxi-hailing application obtains the data packet of the embedded window layer corresponding to the created taxi-hailing application card.

[0255] The card kit corresponding to the taxi application can obtain the data packet of the embedded window layer corresponding to the created taxi application card from the cache of the electronic device, and determine the status information of the data packet of the embedded window layer corresponding to the created taxi application card.

[0256] S1610. When the status information indicates that the data packet of the embedded window layer corresponding to the created taxi-hailing application card is valid, the card kit corresponding to the taxi-hailing application calls back the OnSurfacePackageChanged function.

[0257] When the status information indicates that the data packet of the embedded window layer corresponding to the created taxi application card is valid, the card kit corresponding to the taxi application can return the data packet of the embedded window layer corresponding to the created taxi application card to the card management service by calling back the OnSurfacePackageChanged function.

[0258] Exemplarily, when the return value of the status information of the data packet (i.e., SurfacePackage) of the embedded window layer corresponding to the created taxi application card is the first value (such as 1), the card kit corresponding to the taxi application determines that the data packet (i.e., SurfacePackage) of the embedded window layer corresponding to the created taxi application card is valid.

[0259] S1611. The card management service calls back the OnSurfacePackageChanged function.

[0260] The card management service can return the data packet of the embedded window layer corresponding to the created taxi application card to the Host AAR corresponding to the first host application of the electronic device by calling back the OnSurfacePackageChanged function. After receiving the data packet of the embedded window layer corresponding to the created taxi application card, the Host AAR corresponding to the first host application can obtain the embedded window layer corresponding to the created taxi application card based on the data packet of the embedded window layer corresponding to the created taxi application card, and use the embedded window layer corresponding to the created taxi application card as a placeholder embedded window layer. After obtaining the placeholder embedded window layer, the Host AAR corresponding to the first host application can add a placeholder view in the placeholder embedded window layer. That is, after S1611, execute S1616.

[0261] In some examples, if the status information indicates that the data packet of the embedded window layer corresponding to the created ride-hailing application card is invalid, the card kit corresponding to the ride-hailing application can create a placeholder embedded window layer and return the data packet of the placeholder embedded window layer to the host AAR corresponding to the first host application, so that the host AAR corresponding to the first host application adds a placeholder view to the placeholder embedded window layer. In other words, if the status information indicates that the data packet of the embedded window layer corresponding to the created ride-hailing application card is invalid, S1612-S1615 are executed.

[0262] Exemplarily, when the return value of the status information of the data packet of the embedded window layer corresponding to the created taxi application card is a second value (such as 0), the card kit corresponding to the taxi application determines that the data packet of the embedded window layer corresponding to the created taxi application card is invalid.

[0263] S1612. The card kit corresponding to the taxi-hailing application creates a placeholder embedded window layer.

[0264] S1613. The card kit corresponding to the taxi-hailing application creates a monitoring event. The monitoring event is used to monitor whether the placeholder embedded window layer is created.

[0265] S1614. When the placeholder embedded window layer is created, the card kit corresponding to the taxi-hailing application calls back the OnSurfacePackageCreated function.

[0266] When the placeholder embedded window layer is created, the card kit corresponding to the taxi-hailing application can return the data packet of the placeholder embedded window layer to the card management service by calling back the OnSurfacePackageCreated function.

[0267] S1615. The card management service calls back the OnSurfacePackageCreated function.

[0268] The card management service can return the data packet of the placeholder embedded window layer to the Host AAR corresponding to the first host application by calling back the OnSurfacePackageCreated function, so that the Host AAR corresponding to the first host application adds a placeholder view in the placeholder embedded window layer.

[0269] After the Host AAR corresponding to the first host application receives the placeholder embedded window layer sent by the card management service, the Host AAR corresponding to the first host application can create a placeholder view and add the placeholder view to the placeholder embedded window layer. Then, the Host AAR corresponding to the first host application can send the placeholder embedded window layer with the placeholder view added to the first host application, so that the first host application can mount the placeholder embedded window layer with the placeholder view added to the host layer of the first host application itself for placeholding. Specifically, for the specific implementation process of the Host AAR corresponding to the first host application creating a placeholder view and adding the placeholder view to the placeholder embedded window layer, please refer to S1616-S1618.

[0270] S1616. The Host AAR corresponding to the first host application creates a placeholder view according to the card size information (ie, size) corresponding to the first host application.

[0271] The Host AAR corresponding to the first host application can create a placeholder view based on the card size information of the first host application. For example, the placeholder view can be a reusable DynamicCardHostView object.

[0272] S1617. The Host AAR corresponding to the first host application adds the placeholder view to the placeholder embedded window layer.

[0273] After the Host AAR corresponding to the first host application receives the data packet of the placeholder embedded window layer sent by the card management service, the Host AAR corresponding to the first host application can obtain the placeholder embedded window layer based on the data packet of the placeholder embedded window layer. After the Host AAR corresponding to the first host application creates the placeholder view, the first host application calls back the onCardViewCreated{cardInstanceId,view} function to add the placeholder view (i.e., the DynamicCardHostView object) to the placeholder embedded window layer.

[0274] In some examples, after the Host AAR corresponding to the first host application receives a data packet of the embedded window layer corresponding to the created taxi application card, the Host AAR corresponding to the first host application obtains the embedded window layer corresponding to the created taxi application card based on the data packet of the embedded window layer corresponding to the created taxi application card. After the Host AAR corresponding to the first host application creates a placeholder view, the Host AAR corresponding to the first host application can call the onCardViewCreated{cardInstanceId,view} function to update the card view in the embedded window layer corresponding to the created taxi application card to the placeholder view. Afterwards, the Host AAR corresponding to the first host application sends the embedded window layer with the placeholder view added to the first host application, so that the first host application mounts the placeholder embedded window layer with the placeholder view added to the host layer corresponding to the first host application.

[0275] In some examples, after the Host AAR corresponding to the first host application receives a data packet of the placeholder embedded window layer, the Host AAR corresponding to the first host application obtains the placeholder embedded window layer based on the data packet of the placeholder embedded window layer. After the Host AAR corresponding to the first host application creates a placeholder view, the Host AAR corresponding to the first host application can call the onCardViewCreated{cardInstanceId,view} function to add a placeholder view to the placeholder embedded window layer. Afterwards, the Host AAR corresponding to the first host application can send the placeholder embedded window layer with the added placeholder view to the first host application, so that the first host application mounts the placeholder embedded window layer with the added placeholder view to the host layer corresponding to the first host application.

[0276] S1618. The Host AAR corresponding to the first host application sends the placeholder embedded window layer with the placeholder view added to the first host application, so that the first host application mounts the placeholder embedded window layer with the placeholder view added to the host layer corresponding to the first host application.

[0277] After the first host application receives the placeholder embedded window layer with the placeholder view added sent by the Host AAR corresponding to the first host application, the first host application mounts the placeholder embedded window layer with the placeholder view added to the host layer corresponding to the first host application, that is, the first host application embeds the placeholder view into the window of the first host application.

[0278] It should be noted that, after the card management service receives the card UUID, card instance information, identification information corresponding to the host application, and card size information corresponding to the host application sent by any host application, the card management service can obtain AppClipInfo according to the card UUID. After the card management service obtains AppClipInfo according to the card UUID, the card management service determines and sends the AppClipInfo, card instance information, identification information corresponding to the host application, and card size information corresponding to the host application to the card kit corresponding to the taxi application based on the AppClipInfo. That is to say, the card kit corresponding to the taxi application can obtain the card view (i.e., view) corresponding to the taxi application card corresponding to each host application in the host application for which the taxi application's business has been changed from TaxiProvider. Therefore, before the card kit corresponding to the taxi application can obtain the card view (i.e., view) corresponding to the taxi application card corresponding to each host application in the host application for which the taxi application's business has been changed from TaxiProvider, each host application can mount the placeholder embedded window layer that adds the placeholder view to the host layer of the first host application itself for placeholder. Among them, the specific implementation process of each host application adding a placeholder embedded window layer of a placeholder view and mounting it to the host layer of the first host application itself for placeholding can be illustrated by taking S1609-S1618 (that is, the first host application adds a placeholder embedded window layer of a placeholder view and mounts it to the host layer of the first host application itself for placeholding) as an example.

[0279] S1619. The card kit corresponding to the taxi application determines the Taxi Provider corresponding to the service of the taxi application based on the AppClipInfo, and sends the cardInstanceId to the Taxi Provider corresponding to the service of the taxi application.

[0280] After the card kit corresponding to the taxi application receives the AppClipInfo, cardInstanceId, and hostinfo corresponding to the first host application corresponding to the business of the taxi application, the card kit corresponding to the taxi application can determine the Taxi Provider corresponding to the business of the taxi application based on the AppClipInfo, and send a binding service request to the Taxi Provider corresponding to the business of the taxi application.

[0281] After the Taxi Provider corresponding to the taxi app's business receives a service binding request from the card kit corresponding to the taxi app, the Taxi Provider corresponding to the taxi app's business performs initialization operations. After the Taxi Provider corresponding to the taxi app's business performs initialization operations, the Taxi Provider corresponding to the taxi app's business can bind services with the card kit corresponding to the taxi app, that is, the Taxi Provider corresponding to the taxi app's business and the card kit corresponding to the taxi app establish a communication connection. After the Taxi Provider corresponding to the taxi app's business and the card kit corresponding to the taxi app bind services, the Taxi Provider corresponding to the taxi app's business can send a notification to the card kit corresponding to the taxi app that the binding service has been successfully created.

[0282] After the card kit corresponding to the taxi application receives the notification of successful creation of the binding service sent by the Taxi Provider corresponding to the business of the taxi application, the card kit corresponding to the taxi application can send the cardInstanceId corresponding to the business of the taxi application to the Taxi Provider corresponding to the business of the taxi application, so that the Taxi Provider corresponding to the business of the taxi application determines the taxi order corresponding to the taxi application card to be displayed according to the cardInstanceId, and obtains the card view of the taxi application card corresponding to the taxi order according to the hostinfo corresponding to the first host application, that is, the Taxi Provider corresponding to the business of the taxi application obtains the card view of the taxi application card corresponding to the first host application according to the hostinfo corresponding to the first host application.

[0283] A taxi-hailing app can include multiple Taxi Providers. Each Taxi Provider corresponds to a specific service (i.e., the processing progress of taxi orders). The Taxi Provider can be used to generate card views corresponding to the service (e.g., driver acceptance). It should be noted that the Taxi Provider corresponding to the service can be integrated into the taxi-hailing app.

[0284] It should be noted that, when the card kit corresponding to the taxi application uses the embedded window layer corresponding to the created taxi application card as a placeholder embedded window layer, S1619 can be executed before S1609, and S1619 can also be executed at the same time as S1609. There is no specific limitation on the execution order of S1619 and S1609.

[0285] Also, when the card kit corresponding to the taxi-hailing application creates a placeholder embedded window layer, S1619 can be executed before S1612, or S1619 can be executed simultaneously with S1612. There is no specific limitation on the execution order of S1619 and S1612.

[0286] S1620. The Taxi Provider corresponding to the business of the taxi application determines the taxi order corresponding to the taxi application card to be displayed according to the cardInstanceId corresponding to the business of the taxi application.

[0287] For example, when a user places two taxi orders (e.g., Order A and Order B) using a taxi app, card instance information 1 corresponding to Order A and card instance information 2 corresponding to Order B may be generated. The Taxi Provider corresponding to the taxi app's business (i.e., the processing progress of the taxi orders) may determine, based on card instance information 1, that the taxi app card to be displayed is the taxi app card corresponding to Order A. The Taxi Provider corresponding to the taxi app's business (i.e., the processing progress of the taxi orders) may determine, based on card instance information 2, that the taxi app card to be displayed is the taxi app card corresponding to Order B.

[0288] S1621. The card kit corresponding to the taxi-hailing application calls the getview(hostinfo) function to send the hostinfo corresponding to the first host application to the Taxi Provider corresponding to the service of the taxi-hailing application.

[0289] After the Taxi Provider corresponding to the business of the taxi application determines the taxi order corresponding to the taxi application card to be displayed based on the cardInstanceId corresponding to the business of the taxi application, the card kit corresponding to the taxi application can send the hostinfo corresponding to the first host application to the Taxi Provider corresponding to the business of the taxi application, that is, the card kit corresponding to the taxi application can send the view id corresponding to the first host application to the Taxi Provider corresponding to the business of the taxi application.

[0290] It should be noted that after the card management service receives the card UUID, card instance information, identification information corresponding to the host application and card size information corresponding to the host application sent by any host application, the card management service can obtain AppClipInfo based on the card UUID, and send the AppClipInfo, card instance information, identification information corresponding to the host application and card size information corresponding to the host application to the card kit corresponding to the taxi application. Therefore, after the card kit corresponding to the taxi application receives the AppClipInfo, card instance information and identification information corresponding to the host application, the card kit corresponding to the taxi application can determine the Taxi Provider corresponding to the business of the taxi application based on AppClipInfo, and send the card instance information and identification information corresponding to the host application to the Taxi Provider corresponding to the business of the taxi application.

[0291] S1622. The Taxi Provider corresponding to the taxi-hailing application's service creates a card view of the taxi-hailing application card corresponding to the first host application based on the hostinfo corresponding to the first host application.

[0292] After the Taxi Provider corresponding to the business of the taxi application receives the hostinfo corresponding to the first host application sent by the card kit corresponding to the taxi application, the Taxi Provider corresponding to the business of the taxi application can determine the view id corresponding to the first host application based on the hostinfo corresponding to the first host application, and obtain the card view of the taxi application card corresponding to the first host application based on the view id corresponding to the first host application. The card view of the taxi application card is the card view of the taxi application card corresponding to the target taxi order. The card view of the taxi application card can be used to indicate changes in the business of the taxi application, that is, to indicate the processing progress of the target order. Among them, the target taxi order is the taxi order determined based on the cardInstanceId corresponding to the business of the taxi application.

[0293] For example, continuing with the example of an electronic device with host applications including the desktop, notification center, lock screen, off-screen, negative one screen, and banner notifications, for the same service of a taxi-hailing application (e.g., driver accepting an order), when the first host application is the desktop, the card view corresponding to the first host application is identified as 1. The Taxi Provider corresponding to the taxi-hailing application's service can, based on card view identifier 1, obtain the card view of the taxi-hailing application card corresponding to the desktop. When the first host application is the notification center, the card view corresponding to the first host application is identified as 2. The Taxi Provider corresponding to the taxi-hailing application's service can, based on card view identifier 2, obtain the card view of the taxi-hailing application card corresponding to the notification center. When the first host application is the lock screen, the card view corresponding to the first host application is identified as 3. The Taxi Provider corresponding to the taxi-hailing application's service can, based on card view identifier 3, obtain the card view of the taxi-hailing application card corresponding to the lock screen. When the first host application is the off-screen, the card view corresponding to the first host application is identified as 4. The Taxi Provider corresponding to the taxi-hailing application's service can, based on card view identifier 4, obtain the card view of the taxi-hailing application card corresponding to the off-screen. When the first host application is the negative one screen, the card view identifier corresponding to the first host application is 5. The Taxi Provider corresponding to the taxi application's service can obtain the card view of the taxi application card corresponding to the negative one screen based on the card view identifier 5. When the first host application is a banner notification, the card view identifier corresponding to the first host application is 6. The Taxi Provider corresponding to the taxi application's service can obtain the card view of the taxi application card corresponding to the banner notification based on the card view identifier 6.

[0294] It should be noted that, since the card kit corresponding to the taxi-hailing application can send the hostinfo corresponding to each host application in the host application that registers the business changes of the taxi-hailing application to the Taxi Provider corresponding to the business of the taxi-hailing application, the card kit corresponding to the taxi-hailing application can determine the view id corresponding to each host application based on the hostinfo corresponding to each host application in the host application that registers the business changes of the taxi-hailing application, and obtain the card view corresponding to each host application based on the view id corresponding to each host application.

[0295] Among them, for different host applications, the content to be displayed on the corresponding interface of the host application is different. Therefore, for the same business of the taxi application, when different host applications display the taxi application card, the card views of the taxi application card displayed by different host applications are different.

[0296] For example, the card views of the taxi-hailing application card displayed by different host applications are different, which may mean that the card contents of the card views of the taxi-hailing application card displayed by different host applications are different.

[0297] For example, taking the example of a host application of an electronic device that may include the desktop, notification center, lock screen, off screen, negative one screen, and banner notification, for the same service of a taxi-hailing application (e.g., driver accepting an order), as shown in (a) of FIG15 , the desktop 110 of the electronic device may display a taxi-hailing application card 111. The taxi-hailing application card 111 may include a taxi-hailing application icon 112, text 113 of "License plate number XXX, arriving in about 2 minutes", text 114 of "Master Zhang, white", and a call control 115.

[0298] As shown in FIG15( b ), the notification center 120 of the electronic device may display a ride-hailing application card 121. This ride-hailing application card 121 may include a ride-hailing application icon 122, text 123 reading "License plate number XXX, arriving in about 2 minutes," and text 124 reading "Master Zhang, white." Compared to the ride-hailing application card 111 shown in FIG15( a ), this card also includes a progress bar 125.

[0299] As shown in FIG15( c ), the lock screen interface 130 of the electronic device may display a ride-hailing application card 131. This ride-hailing application card 131 may include a ride-hailing application icon 132, text 133 reading "License plate number XXX, arriving in about 2 minutes," and text 134 reading "Master Zhang, white." Compared to the ride-hailing application card 111 shown in FIG15( a ), this card also includes a progress bar 135.

[0300] As shown in Figure 15(d), the electronic device's screen-off interface 140 may display a ride-hailing app card 141. Compared to the ride-hailing app card 111 shown in Figure 15(a), the ride-hailing app card 141 is a card capsule. The ride-hailing app card 141 (i.e., card capsule) may include some information related to the ride-hailing order (e.g., the ride-hailing app icon 142 and text 143 reading "License Plate Number XXX").

[0301] It should be noted that the above progress bar may be a segmented progress bar.

[0302] For example, the card views of the taxi-hailing application card displayed by different host applications are different, which may mean that the card sizes of the card views of the taxi-hailing application card displayed by different host applications are different.

[0303] For example, continuing with the example of an electronic device where the host application may include the desktop, notification center, lock screen, screen off, negative one screen, and banner notification, for the same service of a taxi-hailing application (e.g., driver accepting orders), as shown in (a) of FIG15 , the desktop 110 of the electronic device may display a taxi-hailing application card 111. The display height of the taxi-hailing application card 111 is h1, and the display width of the taxi-hailing application card 111 is d1.

[0304] As shown in FIG15( b ), the notification center 120 of the electronic device may display a ride-hailing application card 121. The ride-hailing application card 121 has a display height of h2 and a display width of d2. The display height h2 of the ride-hailing application card 121 is smaller than the display height h1 of the ride-hailing application card 111.

[0305] As shown in FIG15( c ), the lock screen interface 130 of the electronic device may display a ride-hailing application card 131. The display height of the ride-hailing application card 131 is h3, and the display width of the ride-hailing application card 131 is d3. The display height h3 of the ride-hailing application card 131 is less than the display height h2 of the ride-hailing application card 121.

[0306] As shown in FIG15( d ), the screen-off interface 140 of the electronic device may display a ride-hailing application card 141. The display height of the ride-hailing application card 141 is h4, and the display width of the ride-hailing application card 141 is d4. The display height h4 of the ride-hailing application card 141 is less than the display height h2 of the ride-hailing application card 111, and the display width d4 of the ride-hailing application card 141 is less than the display width d1 of the ride-hailing application card 111.

[0307] That is to say, for the same service of the taxi application (such as the driver accepting orders), the taxi application cards displayed on the desktop, notification center, lock screen interface, and screen-off interface of the electronic device are different, that is, the card views (i.e., views) of the taxi application cards displayed by different host applications are different, that is, the card view identifiers of the card views of the taxi application cards corresponding to different host applications are different.

[0308] In an embodiment of the present application, before obtaining the card view of the taxi application card corresponding to the first host application according to the card view identifier corresponding to the first host application, the Taxi Provider corresponding to the taxi application business can generate a card view of the taxi application card corresponding to the first host application according to the card size information and taxi business data corresponding to the first host application.

[0309] S1623. The Taxi Provider corresponding to the business of the taxi application sends a card view of the taxi application card corresponding to the first host application to the card kit corresponding to the taxi application.

[0310] It should be noted that, since the Taxi Provider corresponding to the business of the taxi-hailing application can determine the view id corresponding to each host application based on the hostinfo corresponding to each host application in the host application that registers the business changes of the taxi-hailing application, and obtain the card view corresponding to each host application based on the view id corresponding to each host application, the Taxi Provider corresponding to the business of the taxi-hailing application can send the card views corresponding to each host application in the host application that registers the business changes of the taxi-hailing application to the card kit corresponding to the taxi-hailing application.

[0311] S1624. The card kit corresponding to the taxi-hailing application adds the card view of the taxi-hailing application card corresponding to the first host application to the embedded window layer.

[0312] After the card kit corresponding to the ride-hailing application receives the card view of the ride-hailing application card corresponding to the first host application, the card kit corresponding to the ride-hailing application can add the card view of the ride-hailing application card corresponding to the first host application to the embedded window layer (i.e., SurfaceControlViewHost or ViewHost). In other words, the card kit corresponding to the ride-hailing application generates an embedded window layer corresponding to the ride-hailing application card based on the card view of the ride-hailing application card corresponding to the first host application.

[0313] Among them, in some examples, the embedded window layer can be the embedded window layer corresponding to the created taxi application card obtained in the above-mentioned S1609, that is, the card kit corresponding to the taxi application can add the card view of the taxi application card corresponding to the first host application to the embedded window layer, and it can be that the card kit corresponding to the taxi application can update the card view in the embedded window layer corresponding to the created taxi application card to the card view of the taxi application card corresponding to the first host application.

[0314] In some examples, the embedded window layer can be a placeholder embedded window layer created by the card kit corresponding to the taxi-hailing application in S1612, that is, the card kit corresponding to the taxi-hailing application can add the card view of the taxi-hailing application card corresponding to the first host application to the embedded window layer, or the card kit corresponding to the taxi-hailing application can add the card view of the taxi-hailing application card corresponding to the first host application to the placeholder embedded window layer.

[0315] It should be noted that, since the Taxi Provider corresponding to the business of the taxi application can send the card views corresponding to each host application in the host application that registers the business changes of the taxi application to the card kit corresponding to the taxi application, the card kit corresponding to the taxi application can add the card views of the taxi application cards corresponding to each host application to the embedded window layer, that is, the card kit corresponding to the taxi application can generate the embedded window layer corresponding to the taxi application cards corresponding to each host application based on the card views of the taxi application cards corresponding to each host application.

[0316] S1625. The card kit corresponding to the taxi-hailing application calls back the onSurfaceViewRendered function.

[0317] The card kit corresponding to the taxi application monitors whether the embedded window layer corresponding to the taxi application card has been rendered. That is, the card kit corresponding to the taxi application monitors whether the card view in the placeholder embedded window layer has been updated to the card view of the taxi application card corresponding to the first host application. After the card kit corresponding to the taxi application monitors that the embedded window layer corresponding to the taxi application card has been rendered, the card kit corresponding to the taxi application can call back the onSurfaceViewRendered function to notify the card management service that the embedded window layer corresponding to the taxi application card has been rendered.

[0318] S1626. The card management service calls back the onSurfaceViewRendered function.

[0319] The card management service of the electronic device calls back the onSurfaceViewRendered function to notify the Host AAR corresponding to the first host application that the embedded window layer corresponding to the taxi application card is rendered.

[0320] S1627. The Host AAR corresponding to the first host application calls back the onSurfaceViewRendered function.

[0321] The Host AAR corresponding to the first host application calls back the onSurfaceViewRendered function to notify the first host application that the embedded window layer corresponding to the taxi application card is rendered.

[0322] S1628. The first host application updates the placeholder view added in the placeholder embedded window layer to the card view of the taxi-hailing application card corresponding to the first host application.

[0323] After the Host AAR corresponding to the first host application calls back the onSurfaceViewRendered function, the first host application updates the placeholder view added in the placeholder embedded window layer to the card view of the taxi application card corresponding to the first host application, that is, the first host application removes the placeholder corresponding to the placeholder view in the embedded window layer mounted (or embedded) in the host layer corresponding to the first host application, and adds the card view of the taxi application card corresponding to the first host application in the embedded window layer mounted in the host layer corresponding to the first host application, that is, the first host application updates the placeholder view in the embedded window layer mounted in the host layer corresponding to the first host application to the card view of the taxi application card corresponding to the first host application.

[0324] It should be noted that, since the card kit corresponding to the taxi application generates the embedded window layer corresponding to the taxi application card corresponding to each host application based on the card view of the taxi application card corresponding to each host application, each host application can update the placeholder view in the embedded window layer of the host layer corresponding to the host application to the card view of the taxi application card corresponding to the host application. The specific implementation process of each host application being able to update the placeholder view in the embedded window layer of the host layer corresponding to the host application to the card view of the taxi application card corresponding to the host application can be illustrated by taking S1628 (i.e., the specific implementation process of the first host application updating the placeholder view added in the placeholder embedded window layer to the card view of the taxi application card corresponding to the first host application) as an example.

[0325] S1629: The first host application receives a switching operation input by the user.

[0326] The switching operation can be used to open the first host application of the electronic device. For example, if the first host application is the desktop, the switching operation can be a user swiping up from the bottom of the display screen of the electronic device. For another example, if the first host application is the notification center, the switching operation can be a user pulling down from the status bar at the top of the display screen. For another example, if the first host application is the lock screen, the switching operation can be a user clicking on the display screen of the electronic device when the electronic device is in the lock screen state.

[0327] S1630. In response to the switching operation, the first host application displays an interface corresponding to the first host application, where the interface corresponding to the first host application includes a taxi-hailing application card corresponding to the first host application.

[0328] Since the first host application will be mounted to the embedded window layer of the host layer corresponding to the first host application, which includes the card view of the taxi application card corresponding to the first host application, in response to the switching operation, the first host application displays the interface corresponding to the first host application, and displays the card view of the taxi application card corresponding to the first host application in the interface corresponding to the first host application, that is, the interface corresponding to the first host application includes the taxi application card corresponding to the first host application.

[0329] For example, taking the desktop as the first host application, in response to the switching operation, a taxi application card 111 can be displayed at the top of the desktop 110 of the electronic device. The taxi application card 111 can be used to prompt the driver that the order has been accepted. In conjunction with (a) in Figure 15, the taxi application card 111 can include an icon 112 of the taxi application, text 113 of "License plate number XXX·Arrived in about 2 minutes", and text 114 of "Master Zhang·White". The taxi application card 111 can also include a call control 115, which can be used to contact the driver who accepted the order. Among them, the display height of the taxi application card 111 is h1, and the display width of the taxi application card 111 is d1.

[0330] For another example, taking the first host application as the notification center, when the electronic device receives a lock screen operation from the user (e.g., pressing the lock screen button), the electronic device displays a screen-off interface 140, and displays a ride-hailing application card 141 on the screen-off interface 140, as shown in (d) in FIG15 . The ride-hailing application card 141 is a card capsule. When the electronic device receives a touch operation (e.g., a slide operation) from the user on the ride-hailing application card 141 (i.e., the card capsule), the electronic device opens the ride-hailing application. Furthermore, the display height h4 of the ride-hailing application card 141 is less than the display height h1 of the ride-hailing application card 111, and the display width d3 of the ride-hailing application card 141 is less than the display width d1 of the ride-hailing application card 111.

[0331] It should be noted that, since the host application (desktop, negative one screen, notification center, banner notification, screen off and lock screen, etc.) registers the business changes of the taxi application after the electronic device is turned on, when the business changes of the taxi application occur, the electronic device can generate a card view of the taxi application card corresponding to each host application in all host applications that have registered the business changes of the taxi application, and when a host application is running in the foreground of the electronic device, the card view of the taxi application card corresponding to the host application is displayed, that is, the taxi application card corresponding to the host application is displayed. The above example is illustrated by taking the first host application (such as the desktop) as an example, that is, each host application in all host applications that have registered the business changes of the taxi application can execute the above S1604-S1628.

[0332] According to the solution of the present application, when an electronic device displays an application's notification information in the form of a card, the application running on the electronic device can create a card view, generate an embedded window layer corresponding to the card based on the card view, and send the embedded window layer corresponding to the card to the host application of the electronic device, so that the host application of the electronic device displays the embedded window layer corresponding to the card. That is, when the host application of the electronic device displays the application's notification information in the form of a card, the host application of the electronic device displays its own embedded window layer, rather than directly displaying the card view. Therefore, the application of the electronic device can create a card view including custom card elements according to demand, and generate an embedded window layer including custom card elements based on the card view, so that when the host application of the electronic device displays the application's notification information, the host application of the electronic device can display a card view including different custom card elements, which can more effectively and intuitively display the application's notification information to the user.

[0333] Furthermore, when an electronic device displays the card corresponding to an application, displaying the card corresponding to the application based on the embedded window layer can improve the speed of cross-process data transmission and realize real-time refresh of the card corresponding to the application, thereby ensuring the timeliness of the notification information of the application and providing a better user experience.

[0334] For ease of understanding, the card display method provided by the embodiment of the present application is described below with reference to FIG17. As shown in FIG17, the card display method may include the following S1701-S1703.

[0335] S1701: In response to a change in the service of a first application in an electronic device, the electronic device determines a first view of a first card of the first application.

[0336] In the embodiments of the present application, the electronic device may include multiple applications, such as a first application. In some examples, the first application may be a travel application (such as a taxi application, a map application, etc.) or a delivery application (such as a food delivery application, a courier application, etc.). The specific type of the first application is not limited in the embodiments of the present application. For example, the first application may be the card-providing application shown in FIG6 above.

[0337] The electronic device may also include a second application. The second application may be an application that registers business changes of the first application included in the electronic device. That is, when the business of the first application changes, the second application may display the first card of the first application. In some examples, the second application may be a desktop, a notification center, a lock screen, an off screen, a negative one screen, or a banner notification. Exemplarily, the above-mentioned second application may be the host application in the above-mentioned S601-S609. Exemplarily, the above-mentioned second application may also be the above-mentioned S1604-S1608, or the above-mentioned S1616-S1618, or the above-mentioned S1621-S1630, the first host application.

[0338] The first card may be a card corresponding to the first application, that is, the first card may be used to indicate a service change of the first application. For example, taking the first application as a taxi-hailing application, the first card may be the taxi-hailing application card in S606-S609 or S1623-S1624.

[0339] In an embodiment of the present application, when the first card is displayed by different applications of an electronic device (such as the desktop, notification center, lock screen, screen off, negative one screen, or banner notification), the card view of the first card can be adjusted according to the display content of the application of the electronic device. That is to say, for the same business of the first application, the card views of the first card displayed by different applications of the electronic device can be different. Based on this, in response to changes in the business of the first application in the electronic device, the electronic device can determine multiple card views of the first card of the first application, wherein the multiple card views respectively correspond to different applications included in the electronic device (such as the desktop, notification center, lock screen, screen off, negative one screen, or banner notification).

[0340] The first view may be a card view of the first card that can be displayed by the second application program. The first view may be the card view in S604-S607 or S1622-S1623.

[0341] In some examples, the first view may include a custom card element, which may be a progress bar or a segmented progress bar.

[0342] Exemplarily, the first view includes a progress bar, which can be used to indicate the progress status of the business of the first application. The progress bar may include a first icon, a second icon, and a third icon, wherein the first icon can be used to indicate the execution starting point of the business of the first application, and the second icon can be used to indicate the execution end point of the business of the first application; the third icon is used to indicate that the progress status of the business of the first application has changed, and when the progress status of the business of the first application changes, the position of the third icon between the first icon and the second icon changes accordingly. In this way, when the electronic device displays the first card including the first view on the first interface, the progress status of the business of the first application can be more intuitively displayed through the progress bar in the first view, and the user experience is better.

[0343] For example, taking the first application as a taxi application, the first icon can be used to indicate the starting point (i.e., the location of the order-receiving vehicle when the driver accepts the order), that is, the first icon can be used to indicate the execution starting point of the taxi order. The second icon can be used to indicate the destination of the taxi order, that is, the second icon can be used to indicate the execution end point of the taxi order. Specifically, the progress bar can be the progress bar 21 shown in Figure 7 above. The first icon can be the first identifier 01 shown in Figure 7 above. The second icon can be the second identifier 02 shown in Figure 7 above. The third icon can be the vehicle identifier 04 shown in Figure 7 above.

[0344] Exemplarily, the business phases of the first application include a first business phase and a second business phase; the first view includes a segmented progress bar, which is used to indicate the progress status of the business of the first application in different business phases.

[0345] The segmented progress bar may include a fourth icon, a fifth icon, a sixth icon located between the fourth and fifth icons, and a seventh icon. The fourth icon may be used to indicate the starting point of the first business phase of the first application. The fifth icon may be used to indicate the end point of the second business phase of the first application. The sixth icon may be used to indicate the end point of the first business phase of the first application and the starting point of the second business phase of the first application.

[0346] The seventh icon can be used to indicate that the business progress of the second application has changed, and when the progress of the business of the second application changes in the first business stage, the position of the seventh icon between the fourth icon and the sixth icon changes accordingly; or, when the progress of the business of the second application changes in the second business stage, the position of the seventh icon between the sixth icon and the fifth icon changes accordingly.

[0347] In this way, when the electronic device displays the first card including the first view on the first interface, the segmented progress bar in the first view can more intuitively display the current business stage of the first application and the progress status corresponding to the business stage, providing a better user experience.

[0348] For example, taking the first application as a taxi-hailing application, the fourth icon can be used to indicate the starting point (i.e., the location of the receiving vehicle when the driver accepts the order), that is, the fourth icon can be used to indicate the starting point of the taxi order. The fifth icon can be used to indicate the destination of the taxi order, that is, the fifth icon can be used to indicate the end point of the taxi order. The sixth icon can be used to indicate the departure point of the user who placed the order. The sixth icon is located between the fourth and fifth icons. The sixth icon can divide the connecting line between the fourth and fifth icons into two sections. That is, the sixth icon can divide the taxi order processing process into two stages, namely the first business stage and the second business stage. When the seventh icon is located between the fourth and sixth icons, it indicates that the receiving vehicle is traveling from the starting point to the user's departure point. When the seventh icon is located between the sixth and fifth icons, it indicates that the receiving vehicle has picked up the user and is traveling from the user's departure point to the destination.

[0349] Specifically, the segmented progress bar may be the segmented progress bar 51 shown in FIG10 . The fourth icon may be the first identifier 01 shown in FIG10 . The fifth icon may be the second identifier 02 shown in FIG10 . The sixth icon may be the third identifier 03 shown in FIG10 . The seventh icon may be the vehicle identifier 04 shown in FIG10 .

[0350] In some examples, the electronic device determines the first view of the first card of the first application, which may include: the electronic device determines the first view of the first card of the first application based on the card size information corresponding to the second application and the business data of the first application.

[0351] In some examples, the electronic device determines the first view of the first card of the first application, which may include: the electronic device obtains identification information of the second application; the electronic device determines the identification information of the first view based on the identification information of the second application; and the electronic device determines the first view based on the identification information of the first view.

[0352] For example, the identification information of the second application may be the host identification (i.e., host id) of the host application in S1622. The identification information of the first view may be the card view identification (i.e., view id) in S606 or S1622.

[0353] In this example, the electronic device can pre-create a card view of the first card corresponding to each application. In this way, when the electronic device determines the first view, the electronic device can determine the identification information of the first view based on the identification information of the second application, and determine the first view based on the identification information of the first view, so that the card view can be quickly obtained, thereby improving the processing efficiency of the electronic device.

[0354] Specifically, the specific implementation of the electronic device determining the first view of the first card of the first application in the above example can refer to the above S606, or the specific implementation in the above S1622, which will not be repeated in the embodiments of the present application.

[0355] In some embodiments, in order to avoid the electronic device displaying cards of other applications other than the first application during the process of determining the card view of the first card of the first application, before the electronic device determines the card view of the first card of the first application, the electronic device can create a placeholder embedded window layer corresponding to the placeholder view, and mount the placeholder embedded window layer to the embedded window of the second application for placeholder.

[0356] In some examples, before the electronic device determines the first view of the first card of the first application, the card display method may also include: the electronic device generates a placeholder view based on the card size information of the second application; the electronic device creates a placeholder embedded window layer corresponding to the placeholder view based on the placeholder view; and the electronic device mounts the placeholder embedded window layer to the embedded window of the second application.

[0357] The card size information of the second application may be the size information of the card view of the card allowed to be displayed by the second application. For example, the card size information of the second application may include a display height and a display width.

[0358] Exemplarily, the placeholder view may be a reusable DynamicCardHostView object.

[0359] Specifically, for the specific implementation of how the electronic device generates the placeholder view based on the card size information of the second application in the above example, reference can be made to the specific implementation in S1616 above, which will not be repeated in the embodiments of the present application.

[0360] In some examples, an electronic device creates a placeholder embedded window layer corresponding to a placeholder view based on the placeholder view, which may include: when a third embedded window layer is stored in the electronic device, obtaining status information of the third embedded window layer; when the status information indicates that the third embedded window layer is valid, updating the card view of the second card in the third embedded window layer to the placeholder view to obtain the placeholder embedded window layer.

[0361] The third embedded window layer is an embedded window layer created based on the card view of the second card of the first application. The progress status of the business of the first application indicated by the second card is different from that indicated by the first card. For example, continuing to take the first application as a taxi application as an example, the third embedded window layer can be the embedded window layer corresponding to the taxi application card created in S1609-S1611 above.

[0362] The status information of the third embedded window layer can be used to indicate whether the third embedded window layer is valid, that is, the status information of the third embedded window layer can be used to indicate whether the data packet corresponding to the third embedded window layer is valid. Exemplarily, when the status information of the third embedded window layer is a first value (such as 1), the data packet corresponding to the third embedded window layer is valid, that is, the third embedded window layer is valid. When the status information of the third embedded window layer is a second value (such as 0), the data packet corresponding to the third embedded window layer is invalid, that is, the third embedded window layer is invalid.

[0363] Specifically, in the above example, when a third embedded window layer is stored in the electronic device, the status information of the third embedded window layer is obtained; when the status information indicates that the third embedded window layer is valid, the card view of the second card in the third embedded window layer is updated to a placeholder view to obtain a specific implementation method of the placeholder embedded window layer. You can refer to the specific implementation methods in S1609-S1611 above, which will not be repeated in the embodiments of the present application.

[0364] In some examples, the electronic device creates a placeholder embedded window layer corresponding to the placeholder view based on the placeholder view, which may include: when the third embedded window layer is not stored in the electronic device or the status information of the third embedded window layer indicates that the third embedded window layer is invalid, the electronic device creates a placeholder embedded window layer based on the placeholder view.

[0365] Specifically, for the specific implementation of how the electronic device creates a placeholder embedded window layer based on the placeholder view in the above example, reference can be made to the specific implementation in S1612-S1615 above, which will not be repeated in the embodiments of the present application.

[0366] S1702: The electronic device creates a first embedded window layer corresponding to the second application program based on the first view.

[0367] After the electronic device determines the first view of the first card of the first application, the electronic device can create a first embedded window layer corresponding to the second application based on the first view. The electronic device can embed the first embedded window layer into the embedded window of the second application (i.e., the host layer of the second application), so that when the electronic device displays the first interface corresponding to the second application, the embedded window of the second application can be displayed, and then the first embedded window layer embedded in the embedded window of the second application can be displayed, that is, the first card including the first view is displayed in the first interface.

[0368] The first embedded window layer may be a layer capable of embedding an embedded window of the second application. For example, the first embedded window layer may be the embedded window layer in S607 or S1624.

[0369] In some examples, the electronic device creating a first embedded window layer corresponding to the second application based on the first view may include: updating the placeholder view in the placeholder embedded window layer to the first view to obtain the first embedded window layer corresponding to the second application. This eliminates the need to recreate the first embedded window layer, which can improve processing efficiency of the electronic device.

[0370] Specifically, the specific implementation method of the electronic device in the above example creating the first embedded window layer corresponding to the second application based on the first view can refer to the above S607 or the specific implementation method in the above S1624, which will not be repeated in the embodiments of the present application.

[0371] S1703. In response to the first operation of switching to the second application, the electronic device displays a first interface, wherein the first interface includes an embedded window of the second application, wherein a first embedded window layer is displayed in the embedded window of the second application to display a first card including a first view in the first interface.

[0372] Among them, the above-mentioned first operation can be an operation for opening the second application of the electronic device. For example, if the second application is a desktop, the first operation can be an upward sliding operation of the user at the bottom of the display screen of the electronic device. For another example, if the second application is a notification center, the first operation can be a pull-down operation of the user on the top status bar of the display screen. For another example, if the second application is a lock screen, the first operation can be a click operation of the user on the display screen of the electronic device when the electronic device is in the lock screen state. Exemplarily, the first operation can be the switching operation in the above-mentioned S1629. The first interface can be the display interface corresponding to the second application.

[0373] After the electronic device creates a first embedded window layer corresponding to the second application based on the first view, the electronic device can embed the first embedded window layer into the embedded window of the second application. Thereafter, when the electronic device receives a first operation to switch to the second application, in response to the first operation, the electronic device can display the first interface corresponding to the second application, and the first interface can include the embedded window of the second application. In this way, while displaying the first interface corresponding to the second application, the electronic device can display the first card including the first view in the first interface.

[0374] Specifically, for the specific implementation of the electronic device displaying the first interface in response to the first operation of switching to the second application in the above example, reference can be made to the specific implementation in S1630 above, which will not be repeated in the embodiments of the present application.

[0375] In some examples, the card display method may also include: in response to a change in the business of a first application in an electronic device, the electronic device determines a second view of the first card of the first application, and the second view is different from the first view; the electronic device creates a second embedded window layer corresponding to a third application based on the second view.

[0376] In an embodiment of the present application, the electronic device may further include a third application. The third application may also be an application that registers a business change of the first application included in the electronic device. That is to say, when the business of the first application changes, the third application may also display the first card of the first application. In some examples, the third application may be a desktop, a notification center, a lock screen, an off screen, a negative one screen, or a banner notification. Exemplarily, the above-mentioned second application may be the host application in the above-mentioned S601-S609. Exemplarily, the above-mentioned second application may also be the above-mentioned S1604-S1608, or the above-mentioned S1616-S1618, or the above-mentioned S1621-S1630, the first host application.

[0377] It should be noted that the third application can be different from the second application. For example, if the second application is the desktop, the third application can be the notification center. If the second application is the desktop, the third application can be the lock screen. If the second application is the lock screen, the third application can be the screen off. If the second application is the desktop, the third application can be the screen off.

[0378] The second view may be a card view of the first card that can be displayed by the third application. The second view may be the card view in S604-S607, or S1622-S1623.

[0379] In some examples, the electronic device determines the second view of the first card of the first application, which may include: the electronic device determines the second view of the first card of the first application based on the card size information corresponding to the third application and the business data of the first application.

[0380] In some examples, the electronic device determines the second view of the first card of the first application, which may include: the electronic device obtains identification information of a third application; the electronic device determines identification information of the second view based on the identification information of the third application; and the electronic device determines the second view based on the identification information of the second view.

[0381] For example, the identification information of the third application may be the host identification (i.e., host id) of the host application in S1622. The identification information of the second view may be the card view identification (i.e., view id) in S606 or S1622.

[0382] Specifically, the specific implementation of the electronic device determining the second view of the first card of the first application in the above example can also refer to the above S606, or the specific implementation in the above S1622, which will not be repeated in the embodiments of the present application.

[0383] Exemplarily, the second embedded window layer may be a layer capable of embedding an embedded window of a third application. Exemplarily, the second embedded window layer may be the embedded window layer in S607 or S1624.

[0384] In some examples, the electronic device creates a second embedded window layer corresponding to the third application based on the second view, which may include: updating the placeholder view in the placeholder embedded window layer to the second view to obtain the second embedded window layer corresponding to the third application.

[0385] Specifically, the specific implementation method of the electronic device in the above example creating the second embedded window layer corresponding to the third application based on the second view can refer to the above S607 or the specific implementation method in the above S1624, which will not be repeated in the embodiments of the present application.

[0386] After the electronic device creates a second embedded window layer corresponding to the third application based on the second view, the electronic device can embed the second embedded window layer in the embedded window of the third application (that is, the host layer of the third application). In this way, when the electronic device displays the second interface corresponding to the third application, the embedded window of the third application can be displayed, and then the second embedded window layer embedded in the embedded window of the third application can be displayed, that is, the first card including the second view is displayed in the second interface.

[0387] In some examples, the second view is different from the first view, and the display content corresponding to the second view is different from the display content corresponding to the first view.

[0388] In some examples, the second view is different from the first view, and the display size corresponding to the second view is different from the display size corresponding to the first view. The display size may include a display height and a display width.

[0389] For example, the second application is the desktop, the third application is the notification center, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. In this way, when the application running in the foreground of the electronic device switches from the desktop to the notification center, the first card including the second view can be displayed in the notification center, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. This can reduce the space occupied by the first card, allowing the notification center of the electronic device to display more notification information cards. The user can view all notification information cards without flipping through them, which can improve the efficiency of human-computer interaction.

[0390] For example, the second application is the desktop, the third application is the lock screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. In this way, when the application running in the foreground of the electronic device switches from the desktop to the lock screen, the first card including the second view can be displayed in the notification center, and the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. This can reduce the space occupied by the first card, so that the lock screen of the electronic device can display more notification information cards. The user can view all notification information cards without flipping through them, which can improve the efficiency of human-computer interaction.

[0391] Exemplarily, the second application is the lock screen, the third application is the off-screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. In this example, since the display space of the off-screen interface of the electronic device is limited, when the application running in the foreground of the electronic device switches from the lock screen to the off-screen, the first card including the second view can be displayed on the off-screen interface, and the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view. In this way, the display size of the first card can be reduced, and the space occupied by the first card can be minimized to avoid the card corresponding to the second application from being unable to be fully displayed. In addition, since the off-screen interface of the electronic device is in a constantly on state, displaying a smaller first card on the off-screen interface can reduce the power consumption of the electronic device.

[0392] It should be noted that the display size corresponding to the first view may be the card size information of the second application, and the display size corresponding to the second view may be the card size information of the third application.

[0393] In some examples, the second view is different from the first view, and the display content corresponding to the second view is different from the display content corresponding to the first view, and the display size corresponding to the second view is different from the display size corresponding to the first view.

[0394] In this example, when the business of the first application changes, the electronic device can generate card views corresponding to each application based on the characteristics of different applications, wherein the display content and / or display size of the card views corresponding to different applications are different. In this way, the electronic device can generate first cards adapted to each application based on the characteristics of different applications, and then when the electronic device switches to any application, it can display the interface corresponding to the application and display the first card including the card view corresponding to the application on the interface corresponding to the application. This ensures that the first cards displayed in different applications of the electronic device have good display effects.

[0395] In some examples, after the electronic device displays a first interface in response to a first operation of switching to a second application, the card display method may also include: in response to a second operation of switching to a third application, the electronic device displays a second interface, the second interface including an embedded window of the third application, wherein a second embedded window layer is displayed in the embedded window of the third application to display the first card including the second view in the second interface.

[0396] The above-mentioned second operation may be an operation for opening a third application of the electronic device. For example, if the third application is a desktop, the second operation may be an upward sliding operation of the user at the bottom of the display screen of the electronic device. For another example, if the third application is a notification center, the second operation may be a downward pulling operation of the user at the top status bar of the display screen. For another example, if the third application is a lock screen, the second operation may be a click operation of the user on the display screen of the electronic device when the electronic device is in the lock screen state. Exemplarily, the second operation may be the switching operation in S1629 above. The second interface may be a display interface corresponding to the third application.

[0397] After the electronic device displays the first interface, when the electronic device receives a second operation to switch to a third application, in response to the second operation, the electronic device can display a second interface corresponding to the third application. The second interface may include an embedded window of the third application. In this way, the electronic device switches from displaying the first interface corresponding to the second application to the second interface corresponding to the third application, and can display a first card including a second view in the second interface.

[0398] Specifically, for the specific implementation of the electronic device displaying the second interface in response to the second operation of switching to the third application in the above example, reference can be made to the specific implementation in S1630 above, which will not be repeated in the embodiments of the present application.

[0399] In this example, when the business of a first application on an electronic device changes, in response to the change in the business of the first application, the electronic device can determine the second view of the first card of the first application and, based on the second view, create a second embedded window layer corresponding to a third application. The electronic device can then embed the second embedded window layer into the embedded window of the third application. In other words, when the business of the first application changes, the electronic device can determine the card views that can be displayed in each application based on the characteristics of each application. Furthermore, when the electronic device receives a second operation to switch to the third application, in response to the second operation, the electronic device's display interface can switch from the first interface corresponding to the second application to the second interface corresponding to the third application. Furthermore, because the electronic device displays the embedded window of the third application in the second interface of the third application, the electronic device's display interface simultaneously switches from the first card including the first view to the first card including the second view. In other words, the electronic device can display first cards that are adapted to the characteristics of each application, thereby ensuring that the first cards displayed in different applications on the electronic device have good display effects.

[0400] In the solution of the present application, when the business of a first application in an electronic device changes, in response to the business change of the first application, the electronic device can determine the first view of the first card of the first application and, based on the first view, create a first embedded window layer corresponding to the second application, so that the electronic device can embed the first embedded window layer into the embedded window of the second application. Subsequently, when the electronic device receives a first operation to switch to the second application, in response to the first operation, the electronic device can display the first interface corresponding to the second application. Since the first interface of the second application displayed by the electronic device includes the embedded window of the second application, the first embedded window layer embedded in the embedded window of the second application can be displayed while the electronic device displays the first interface corresponding to the second application, and thus the first card including the first view can be displayed in the first interface. In other words, when the second application of the electronic device displays the first card, the first card can be displayed by displaying the embedded window of the second application instead of directly displaying the first card. In this way, the electronic device can determine the first view of the first card based on the business type of the first application, and then by displaying the first card including the first view on the first interface, the business status of the first application can be more effectively and intuitively displayed, providing a better user experience.

[0401] It should be understood that the division of units or modules (hereinafter referred to as units) in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or physically separated. Furthermore, the units in the device may be implemented entirely in the form of software called through processing elements; entirely in the form of hardware; or partially in the form of software called through processing elements, and partially in the form of hardware.

[0402] For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device for implementation. In addition, it can also be stored in a memory in the form of a program, and called by a certain processing element of the device to execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software called by the processing element.

[0403] In one example, the units in the above apparatus may be one or more integrated circuits configured to implement the above method, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.

[0404] For another example, when the units in the device can be implemented in the form of a processing element scheduling program, the processing element can be a general-purpose processor, such as a CPU or other processor that can call programs. For another example, these units can be integrated together and implemented in the form of a system on a chip (SOC).

[0405] In one implementation, the units implementing the corresponding steps of the above methods in the apparatus described above may be implemented in the form of a processing element scheduling program. For example, the apparatus may include a processing element and a storage element, with the processing element invoking a program stored in the storage element to execute the method described in the above method embodiments. The storage element may be a storage element on the same chip as the processing element, i.e., an on-chip storage element.

[0406] In another implementation, the program for executing the above method may be stored in a memory element on a different chip from the processing element, i.e., an off-chip memory element. In this case, the processing element calls or loads the program from the off-chip memory element onto the on-chip memory element to call and execute the method described in the above method embodiment.

[0407] For example, embodiments of the present application may also provide a device, such as an electronic device, which may include a processor and a memory for storing instructions executable by the processor. When the processor is configured to execute the instructions, the electronic device implements the card display method described in the aforementioned embodiments. The memory may be located within or outside the electronic device. The processor may include one or more processors.

[0408] In another implementation, the unit of the apparatus implementing each step of the above method may be configured as one or more processing elements, which may be provided on the corresponding electronic device. The processing elements may be integrated circuits, such as one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of these integrated circuits. These integrated circuits may be integrated together to form a chip.

[0409] For example, embodiments of the present application further provide a chip that can be used in the aforementioned electronic device. The chip includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via circuits; the processors receive and execute computer instructions from the electronic device's memory via the interface circuits to implement the methods described in the aforementioned method embodiments.

[0410] An embodiment of the present application also provides a computer program product, including computer instructions executed by the above-mentioned electronic device.

[0411] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0412] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, 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 devices or units, which can be electrical, mechanical or other forms.

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

[0414] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0415] 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 readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, such as a program. The software product is stored in a program product, such as a computer-readable storage medium, including a number of instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0416] For example, an embodiment of the present application may further provide a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by an electronic device, the electronic device implements the card display method described in the aforementioned method embodiment.

[0417] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A card display method, characterized in that: Applied to electronic equipment, the method comprises: In response to a change in the service of a first application in the electronic device, the electronic device determines a first view of a first card of the first application; The electronic device creates a first embedded window layer corresponding to the second application according to the first view; In response to a first operation of switching to the second application, the electronic device displays a first interface, wherein the first interface includes an embedded window of the second application, wherein the first embedded window layer is displayed in the embedded window of the second application to display the first card including the first view in the first interface.

2. The method according to claim 1, characterized in that The method further comprises: In response to a change in the service of a first application in the electronic device, the electronic device determines a second view of a first card of the first application, the second view being different from the first view; The electronic device creates a second embedded window layer corresponding to the third application according to the second view; After the electronic device displays the first interface in response to the first operation of switching to the second application, the method further includes: In response to a second operation of switching to the third application, a second interface is displayed, wherein the second interface includes an embedded window of the third application, wherein the second embedded window layer is displayed in the embedded window of the third application to display the first card including the second view in the second interface.

3. The method according to claim 1, characterized in that The first view includes a progress bar, and the progress bar is used to indicate the progress status of the service of the first application; The progress bar includes a first icon, a second icon, and a third icon, wherein the first icon is used to indicate the execution start point of the service of the first application, and the second icon is used to indicate the execution end point of the service of the first application; The third icon is used to indicate that the progress status of the service of the first application program has changed, and when the progress status of the service of the first application program has changed, the position of the third icon between the first icon and the second icon has changed accordingly.

4. The method according to claim 1, characterized in that The service phase of the first application includes a first service phase and a second service phase; the first view includes a segmented progress bar, and the segmented progress bar is used to indicate the progress status of the service of the first application in different service phases; The segmented progress bar includes a fourth icon, a fifth icon, a sixth icon and a seventh icon located between the fourth icon and the fifth icon; wherein the fourth icon is used to indicate the execution starting point of the first business phase of the first application; the fifth icon is used to indicate the execution end point of the second business phase of the first application; the sixth icon is used to indicate the execution end point of the first business phase of the first application and the execution starting point of the second business phase of the first application; The seventh icon is used to indicate that the business progress of the second application has changed, and when the progress of the business of the second application changes in the first business stage, the position of the seventh icon between the fourth icon and the sixth icon changes accordingly; or, when the progress of the business of the second application changes in the second business stage, the position of the seventh icon between the sixth icon and the fifth icon changes accordingly.

5. The method according to claim 1, characterized in that The electronic device determines a first view of a first card of the first application, including: The electronic device obtains identification information of the second application; The electronic device determines identification information of the first view according to identification information of the second application program; The electronic device determines the first view according to the identification information of the first view.

6. The method according to claim 1, characterized in that Before the electronic device determines the first view of the first card of the first application, the method further includes: The electronic device generates a placeholder view according to the card size information of the second application; The electronic device creates a placeholder embedded window layer corresponding to the placeholder view according to the placeholder view; The electronic device mounts the placeholder embedded window layer to the embedded window of the second application.

7. The method according to claim 6, characterized in that The electronic device creates, according to the placeholder view, a placeholder embedded window layer corresponding to the placeholder view, including: In a case where a third embedded window layer is stored in the electronic device, obtaining status information of the third embedded window layer, wherein the third embedded window layer is an embedded window layer created according to a card view of a second card of the first application, and the progress status of the business of the first application indicated by the second card is different from that indicated by the first card; When the status information indicates that the third embedded window layer is valid, the card view of the second card in the third embedded window layer is updated to the placeholder view to obtain the placeholder embedded window layer.

8. The method according to claim 6, characterized in that The electronic device creates a first embedded window layer corresponding to the second application according to the first view, including: The placeholder view in the placeholder embedded window layer is updated to the first view to obtain a first embedded window layer corresponding to the second application.

9. The method according to claim 2, characterized in that: The display content corresponding to the second view is different from the display content corresponding to the first view, and / or the display size corresponding to the second view is different from the display size corresponding to the first view.

10. The method according to claim 2, characterized in that The second application is a desktop, notification center, lock screen, off screen, negative one screen or banner notification; The third application is a desktop, notification center, lock screen, screen off, negative one screen or banner notification.

11. The method according to claim 10, characterized in that The display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes a display height and a display width; The second application is the desktop, the third application is the notification center, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

12. The method according to claim 10, characterized in that The display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes a display height and a display width; Among them, the second application is the desktop, the third application is the lock screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

13. The method according to claim 10, characterized in that The display size corresponding to the second view is different from the display size corresponding to the first view, and the display size includes a display height and a display width; Among them, the second application is the lock screen, the third application is the off screen, the display width corresponding to the second view is smaller than the display width corresponding to the first view, and the display height corresponding to the second view is smaller than the display height corresponding to the first view.

14. An electronic device, characterized in that: The electronic device comprises a processor and a memory for storing instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the method as claimed in any one of claims 1 to 13.

15. A computer-readable storage medium having computer program instructions stored thereon; characterized in that: When the computer program instructions are executed by an electronic device, the electronic device implements the method according to any one of claims 1 to 13.

Images