Application program processing method and device, vehicle, electronic equipment and storage medium
By dynamically replacing the card view container in the vehicle's infotainment system, the problem of Activity destruction during full-screen application switching is solved, achieving seamless switching and a continuous user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-19
- Publication Date
- 2026-04-03
AI Technical Summary
In in-vehicle infotainment systems, when an application switches from a non-full-screen display to a full-screen display, existing technologies require destroying the Activity, resulting in the loss of application state and affecting the continuity of user experience.
By dynamically replacing the card view container, the projection state of the target application's Activity and the virtual display component ActivityView is maintained, achieving seamless switching between full-screen and non-full-screen displays and avoiding the destruction of the Activity.
It enables seamless switching between full-screen and non-full-screen displays, maintaining the continuity of application status and improving the user experience.
Smart Images
Figure CN121785699A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and more specifically, to methods, apparatus, vehicles, electronic devices, and storage media for processing applications. Background Technology
[0002] In the vehicle's infotainment system, non-full-screen application cards are used as containers within the horizontally scrollable application card list on the desktop, loading a virtual display component called ActivityView. By projecting the application's activity onto the ActivityView, non-full-screen display of the application is achieved.
[0003] When the user clicks the "Full Screen" button on the card, the screen mirroring relationship between the Activity and the ActivityView is first broken by calling the ActivityView's release method, then the application's Activity is destroyed, and finally startActivity is called to complete the full-screen display of the application.
[0004] However, since the previous Activity is destroyed, a new Activity needs to be restarted when startActivity is called, resulting in the loss of application state and affecting the continuity of user experience. Summary of the Invention
[0005] In view of this, the purpose of this application is to provide an application processing method, device, vehicle, electronic device and storage medium that can switch between full-screen display and non-full-screen display by dynamically replacing the view container where the card view container is located, without destroying the activity, so that the target application's activity and virtual display component ActivityView remain in the projection state throughout, avoiding loss of application state and ensuring the continuity of user experience.
[0006] In a first aspect, embodiments of this application provide a method for processing an application, the method comprising: In the card on the vehicle system desktop used for non-full-screen display of the target application, in response to the full-screen switching operation triggered by the vehicle system user, the first view container of the card is removed from the second view container of the application card list where the card is located; a virtual display component is added to the first view container, and the virtual display component maintains a projection relationship with the activity of the target application; The first view container is added to a third view container of full-screen size to display the target application in full-screen mode.
[0007] In one possible implementation, after adding the first view container to the third view container to display the target application in full screen, the method further includes: In response to a desktop return operation triggered by the vehicle infotainment user on the vehicle infotainment system desktop, the first view container is removed from the third view container; Add the first view container to the second view container; hide the third view container, and show the second view container after adding the first view container.
[0008] In one possible implementation, prior to the full-screen switching operation triggered by the vehicle infotainment system user, the method further includes: When the vehicle system desktop is started, the third view container and the second view container of the application card list are created in the vehicle system desktop in a default hidden state. When creating a corresponding view holder for the card in the application card list, a first view container for the card is created, and a second view container is used as the parent container of the first view container; Add the virtual display component to the first view container, and project the activity of the target application onto the virtual display component.
[0009] In one possible implementation, the method further includes: If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running; If the first running state of the vehicle system desktop is foreground running, then the second running state of the target application is determined according to the first loading state of the first view container and the second loading state of the third view container; the running state is used to indicate whether the vehicle system desktop or the target application is running in the foreground or in the background.
[0010] In one possible implementation, determining the second running state of the target application based on the first loading state of the first view container and the second loading state of the third view container includes: If the first loading state is loading complete or the second loading state is loading complete, then the second running state of the target application is running in the foreground.
[0011] In one possible implementation, determining the second running state of the target application based on the first loading state of the first view container and the second loading state of the third view container includes: If both the first loading state and the second loading state are not fully loaded, then the second running state of the target application is running in the background.
[0012] Secondly, embodiments of this application also provide an application processing apparatus, the apparatus comprising: The removal module is used to remove the first view container of the card used for non-full-screen display of the target application on the vehicle system desktop from the second view container of the application card list where the card is located in response to a full-screen switching operation triggered by the vehicle system user; a virtual display component is added to the first view container, and the virtual display component maintains a projection relationship with the activity of the target application; An add module is provided to add the first view container to a third view container of full-screen size for full-screen display of the target application.
[0013] In one possible implementation, the apparatus further includes an exit fullscreen module, which, after the first view container is added to the third view container to display the target application in fullscreen mode, is used to: In response to a desktop return operation triggered by the vehicle infotainment user on the vehicle infotainment system desktop, the first view container is removed from the third view container; Add the first view container to the second view container; hide the third view container, and show the second view container after adding the first view container.
[0014] In one possible implementation, the device further includes a desktop launch module, which, prior to the full-screen switching operation triggered by the vehicle infotainment system user, is configured to: When the vehicle system desktop is started, the third view container and the second view container of the application card list are created in the vehicle system desktop in a default hidden state. When creating a corresponding view holder for the card in the application card list, a first view container for the card is created, and a second view container is used as the parent container of the first view container; Add the virtual display component to the first view container, and project the activity of the target application onto the virtual display component.
[0015] In one possible implementation, the device further includes an operating status determination module, the operating status determination module being configured to: If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running; If the first running state of the vehicle system desktop is foreground running, then the second running state of the target application is determined according to the first loading state of the first view container and the second loading state of the third view container; the running state is used to indicate whether the vehicle system desktop or the target application is running in the foreground or in the background.
[0016] In one possible implementation, the running status determination module is specifically used to determine that if the first loading status is loading complete or the second loading status is loading complete, then the second running status of the target application is foreground running.
[0017] In one possible implementation, the running status determination module is specifically used to determine that if the first loading status is not fully loaded and the second loading status is not fully loaded, then the second running status of the target application is running in the background.
[0018] Thirdly, a vehicle including a processing device for an application as described in the second aspect.
[0019] Fourthly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the processing method of the application as described in any of the first aspects.
[0020] Fifthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the application processing method as described in any of the first aspects.
[0021] This application provides a method, apparatus, vehicle, electronic device, and storage medium for processing applications. The method includes: in response to a full-screen switching operation triggered by a vehicle system user, removing a first view container of a card used for non-full-screen display of a target application on the vehicle system desktop from a second view container of the application card list where the card is located; adding a virtual display component to the first view container, maintaining a projection relationship between the virtual display component and the activity of the target application; and adding the first view container to a third view container of full-screen size to display the target application in full screen. This application achieves the switching between full-screen and non-full-screen display by dynamically replacing the view container where the card view container is located, without destroying the activity, ensuring that the target application's activity and the virtual display component ActivityView remain in a projection state throughout, avoiding application state loss and ensuring user experience continuity. Attached Figure Description
[0022] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0023] Figure 1 A flowchart illustrating a processing method for an application provided in an embodiment of this application is shown; Figure 2 A schematic diagram of the in-vehicle infotainment system desktop provided in an embodiment of this application is shown; Figure 3 A schematic diagram of a full-screen display provided in an embodiment of this application is shown; Figure 4 A flowchart illustrating the desktop startup process provided in an embodiment of this application is shown; Figure 5 A flowchart illustrating the running status determination of an application provided in an embodiment of this application is shown; Figure 6 A schematic diagram of an application processing device provided in an embodiment of this application is shown; Figure 7 This application provides a schematic diagram of the structure of a vehicle according to an embodiment of the present application. Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation
[0024] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.
[0025] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0026] To enable those skilled in the art to utilize the content of this application, and in conjunction with the specific application scenario of "computer technology," the following embodiments are provided. For those skilled in the art, the general principles defined herein can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is primarily described within the "computer technology field," it should be understood that this is merely an exemplary embodiment.
[0027] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.
[0028] The following is a detailed description of an application processing method provided in an embodiment of this application.
[0029] Reference Figure 1 The diagram shown is a flowchart illustrating an application processing method according to an embodiment of this application. The exemplary steps of this embodiment are described below: S101. In the card for non-full-screen display of the target application on the vehicle system desktop, in response to the full-screen switching operation triggered by the vehicle system user, the first view container of the card is removed from the second view container of the application card list where the card is located.
[0030] In this embodiment, the vehicle infotainment system desktop system is the main interface displayed on the central control screen after the in-vehicle infotainment system is started. (Refer to...) Figure 2 The diagram shown is a schematic of the in-vehicle infotainment system desktop provided in this application embodiment. The desktop includes a horizontally swiping list of application cards. This list contains at least one card (interface design element / component) that is not displayed in full screen. The user can change the displayed card by swiping left or right; the remaining cards are "hidden" on the left and right sides of the screen and are not displayed. Each card can display a target application, such as... Figure 2The music player is displayed on cards that occupy 2 / 3 of the screen size. The target application displayed on each card can be specified by the vehicle's infotainment system user. A full-screen button is provided on the card, which the user can click to trigger a full-screen switching operation.
[0031] The first view container is the view container for the cards, and the second view container is the view container for the application card list.
[0032] Next, in response to the full-screen switching operation triggered by the vehicle's infotainment system user, the first view container of the card is removed from the second view container of the application card list where the card is located. A virtual display component ActivityView is added to the first view container, and the virtual display component maintains a projection relationship with the target application's Activity.
[0033] In this embodiment, the targetView (the first view container) is removed from its parent container, parentView, by using "parentView.removeView(targetView)". Before removal, the second view container of the application card list is the parent container of the first view container of the cards.
[0034] The removeView() method is a member method of ViewGroup. Its function is to remove the first view container from the second view container, severing their physical hierarchy. The first view container will disappear from the screen (because it loses the support of its parent container). The second view container will no longer manage the layout, drawing, and event dispatch of the first view container.
[0035] In Android, a view container is a view that can "hold" other views. A view is the smallest drawable unit of an Android interface, meaning all the content visible on the screen. In Android development, an Activity provides a user interface that allows users to interact with the target application. An ActivityView is the view component of an Activity, used to display the content of the user interface. Through Activity Views, developers can add various controls and layouts to build the user interface, such as buttons, text boxes, and images.
[0036] S102. Add the first view container to the third view container of full screen size to display the target application in full screen.
[0037] In this embodiment, the third view container is set to a visible state; the second view container is set to a hidden state; and then the first view container is added to the full-screen third view container. (See also...) Figure 3The image shown is a schematic diagram of a full-screen display provided in an embodiment of this application.
[0038] Here, the third-party view container is set to visible using "mFullscreenViewContainer.setVisibility(View.VISIBLE);". The core of View.VISIBLE is "the view is visible and can participate normally in the interface layout and interaction," and it is one of the fundamental constants controlling whether an Android view is displayed. setVisibility() is a core method provided by the View class in Android, used to dynamically set the visibility state of a view.
[0039] The first view container is added to a full-screen third view container using "mFullscreenViewContainer.addView(targetView)". Here, mFullscreenViewContainer is the third view container, addView() is the view addition operation, and targetView is the first view container. After this step, the first view container is displayed as a child container of the third view container within the space of the full-screen third view container.
[0040] Optionally, an application loading transition animation can be played while the third-view container is made visible to improve the user experience.
[0041] Furthermore, after adding the first view container to the third view container to display the target application in full screen, the method further includes: removing the first view container from the third view container in response to a desktop return operation triggered by the vehicle system user on the vehicle system desktop; adding the first view container to the second view container; and hiding the third view container and displaying the second view container after adding the first view container.
[0042] In summary, this application embodiment achieves the switching between full-screen and non-full-screen display by moving the view container of the card, without destroying the Activity, so that the Activity and ActivityView of the target application remain in the projection state throughout, avoiding the loss of application state and ensuring the continuity of user experience.
[0043] Additionally, refer to Figure 4 The diagram shown is a flowchart of desktop startup provided in an embodiment of this application. Specifically, before responding to a full-screen switching operation triggered by the vehicle system user, the method further includes: S401. When the vehicle infotainment system desktop starts, create a third-view container and a second-view container for the application card list in the vehicle infotainment system desktop.
[0044] In this embodiment of the application, when the vehicle system desktop is started, a full-screen third view container with a default hidden state and a second view container for horizontally swiping application card list are created in the layout of the vehicle system desktop.
[0045] Here, before responding to the full-screen switching operation triggered by the vehicle system user, this step pre-sets a third-view container with a full-screen size in a default hidden state on the vehicle system desktop. When the user triggers the full-screen switching operation, there is no need to create a full-screen view container again; the third-view container can be used directly, which improves the efficiency of subsequent full-screen switching.
[0046] S402. When creating a corresponding view holder for a card in the application card list, create a first view container for the card and use a second view container as the parent container of the first view container.
[0047] In this embodiment, when creating a corresponding ViewHolder for a card in the application card list that is not full-screen in size, a first view container for that card is created. A second view container is then used as the parent container of the first view container, so that the content within the first view container is displayed in a non-full-screen manner.
[0048] S403. Add a virtual display component to the first view container and project the activity of the target application onto the virtual display component.
[0049] In this embodiment of the application, a virtual display component ActivityView is added to the first view container, and the activity of the target application is projected onto the virtual display component to display the content of the target application in a non-full-screen manner.
[0050] Furthermore, when processing certain target events of the target application (such as message notification events and voice broadcast events), it is necessary to determine the foreground and background running states of the application. However, under the full-screen and non-full-screen display switching mechanism in this embodiment, it is no longer possible to determine the foreground and background running states of the application solely through the traditional onPause and onResume callbacks; it is also necessary to combine the first loading state of the first view container and the second loading state of the third view container. Specifically, refer to... Figure 5 The following is a flowchart illustrating the runtime status determination process of the application provided in this application: S501. If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running.
[0051] In this embodiment, the first running state of the vehicle system desktop is determined by onPause() and onResume(). If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running.
[0052] Among them, onPause() and onResume() are a pair of callbacks in the Android Activity lifecycle, used to tell the application whether the user can still see you.
[0053] S502. If the first running state of the vehicle system desktop is foreground running, then the second running state of the target application is determined based on the first loading state of the first view container and the second loading state of the third view container.
[0054] In this application embodiment, the specific process for determining the second running state of the target application is as follows: if the first loading state is loading complete or the second loading state is loading complete, then the second running state of the target application is foreground running; if the first loading state is not loading complete and the second loading state is not loading complete, then the second running state of the target application is background running.
[0055] Here, loading status includes "loading complete" and "loading incomplete"; "loading incomplete" includes "empty shell," "loading," "loading failed / unavailable," and "loading paused." "Loading complete" means the Activity has started, the canvas has been acquired, and the content has been correctly projected onto the ActivityView, making it visible and interactive for the user. "Empty shell" means the container has been inflated (the layout XML has been 'blown' into a real View tree in memory, no longer a static file on disk), but it hasn't contained any content yet, possibly only displaying a placeholder image or background color. "Loading" means the request has been triggered, but the screen hasn't been projected yet. "Loading failed / unavailable" means the application has crashed, refused screen projection, has insufficient permissions, or is out of memory. "Loading paused" means the container is still retained, but the Activity enters onPause (a lifecycle callback function triggered when the current page loses "foreground focus" but is not completely invisible), and the screen is frozen; the user can swipe away and then swipe back to reuse the view without reloading.
[0056] For example, when the target processing event of the target application is a message prompt event, if the second running state is in the foreground, the message text corresponding to the message prompt event will pop up on the vehicle system desktop; otherwise, it will not pop up.
[0057] For example, when the target processing event of the target application is a voice broadcast event, if the second running state is background running, the target application runs in the foreground and broadcasts the voice content corresponding to the voice broadcast event; if the second running state is foreground running, the voice content corresponding to the voice broadcast event is broadcast.
[0058] Based on the same inventive concept, this application also provides an application processing device corresponding to the application processing method. Since the principle of the device in this application for solving the problem is similar to the application processing method described above in this application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.
[0059] Reference Figure 6 The diagram shown is a schematic representation of an application processing apparatus provided in an embodiment of this application. The apparatus includes: The removal module 601 is used to remove the first view container of the card used for non-full-screen display of the target application on the desktop of the vehicle system from the second view container of the application card list where the card is located in response to a full-screen switching operation triggered by the vehicle system user; a virtual display component is added to the first view container, and the virtual display component maintains a projection relationship with the activity of the target application; Add module 602 is used to add the first view container to a third view container of full screen size to display the target application in full screen.
[0060] In one possible implementation, the device further includes a full-screen exit module 603, which, after the first view container is added to the third view container to display the target application in full screen, is used to: In response to a desktop return operation triggered by the vehicle infotainment user on the vehicle infotainment system desktop, the first view container is removed from the third view container; Add the first view container to the second view container; hide the third view container, and show the second view container after adding the first view container.
[0061] In one possible implementation, the device further includes a desktop launch module 604, which, prior to the full-screen switching operation triggered by the vehicle infotainment system user, is configured to: When the vehicle system desktop is started, the third view container and the second view container of the application card list are created in the vehicle system desktop in a default hidden state. When creating a corresponding view holder for the card in the application card list, a first view container for the card is created, and a second view container is used as the parent container of the first view container; Add the virtual display component to the first view container, and project the activity of the target application onto the virtual display component.
[0062] In one possible implementation, the device further includes an operating status determination module 605, the operating status determination module 605 being configured to: If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running; If the first running state of the vehicle system desktop is foreground running, then the second running state of the target application is determined according to the first loading state of the first view container and the second loading state of the third view container; the running state is used to indicate whether the vehicle system desktop or the target application is running in the foreground or in the background.
[0063] In one possible implementation, the running status determination module 605 is specifically used to determine that if the first loading status is loading complete or the second loading status is loading complete, then the second running status of the target application is foreground running.
[0064] In one possible implementation, the running status determination module 605 is specifically used to determine that if the first loading status is not completed and the second loading status is not completed, then the second running status of the target application is running in the background.
[0065] Here, this device completes the switching between full-screen and non-full-screen display by dynamically replacing the view container where the card view container is located, without destroying the activity. This keeps the target application's activity and the virtual display component ActivityView in a projection state throughout, avoiding application state loss and ensuring user experience continuity.
[0066] like Figure 7 As shown in the figure, an embodiment of this application provides a structural schematic diagram of a vehicle, which includes an application processing device.
[0067] like Figure 8As shown in the embodiment of this application, an electronic device 800 includes a processor 801, a memory 802, and a bus. The memory 802 stores machine-readable instructions executable by the processor 801. When the electronic device is running, the processor 801 communicates with the memory 802 via the bus, and the processor 801 executes the machine-readable instructions to perform the steps of the processing method of the application described above.
[0068] Specifically, the memory 802 and processor 801 mentioned above can be general-purpose memory and processor, without any specific limitations. When the processor 801 runs the computer program stored in the memory 802, it can execute the processing method of the application program mentioned above.
[0069] Corresponding to the processing method of the above application, this application embodiment also provides a computer-readable storage medium storing a computer program, which, when run by a processor, executes the steps of the processing method of the above application.
[0070] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.
[0071] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0072] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0073] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0074] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for processing an application, characterized in that, The method includes: In the card on the vehicle system desktop used for non-full-screen display of the target application, in response to the full-screen switching operation triggered by the vehicle system user, the first view container of the card is removed from the second view container of the application card list where the card is located; a virtual display component is added to the first view container, and the virtual display component maintains a projection relationship with the activity of the target application; The first view container is added to a third view container of full-screen size to display the target application in full-screen mode.
2. The application processing method according to claim 1, characterized in that, After adding the first view container to the third view container to display the target application in full screen, the method further includes: In response to a desktop return operation triggered by the vehicle infotainment user on the vehicle infotainment system desktop, the first view container is removed from the third view container; Add the first view container to the second view container; hide the third view container, and show the second view container after adding the first view container.
3. The application processing method according to claim 1, characterized in that, Prior to the full-screen switching operation triggered by the vehicle infotainment system user, the method further includes: When the vehicle system desktop is started, the third view container and the second view container of the application card list are created in the vehicle system desktop in a default hidden state. When creating a corresponding view holder for the card in the application card list, a first view container for the card is created, and a second view container is used as the parent container of the first view container; Add the virtual display component to the first view container and project the activity of the target application onto the virtual display component.
4. The application processing method according to claim 1, characterized in that, The method further includes: If the first running state of the vehicle system desktop is background running, then the second running state of the target application is background running; If the first running state of the vehicle system desktop is foreground running, then the second running state of the target application is determined according to the first loading state of the first view container and the second loading state of the third view container; the running state is used to indicate whether the vehicle system desktop or the target application is running in the foreground or in the background.
5. The application processing method according to claim 4, characterized in that, The step of determining the second running state of the target application based on the first loading state of the first view container and the second loading state of the third view container includes: If the first loading state is loading complete or the second loading state is loading complete, then the second running state of the target application is running in the foreground.
6. The application processing method according to claim 4, characterized in that, The step of determining the second running state of the target application based on the first loading state of the first view container and the second loading state of the third view container includes: If both the first loading state and the second loading state are not fully loaded, then the second running state of the target application is running in the background.
7. A processing apparatus for an application, characterized in that, The device includes: The removal module is used to remove the first view container of the card used for non-full-screen display of the target application on the vehicle system desktop from the second view container of the application card list where the card is located in response to a full-screen switching operation triggered by the vehicle system user; a virtual display component is added to the first view container, and the virtual display component maintains a projection relationship with the activity of the target application; An add module is provided to add the first view container to a third view container of full-screen size for full-screen display of the target application.
8. A vehicle, characterized in that, The vehicle includes the processing device for the application as described in claim 7.
9. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the processing method of the application as described in any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the processing method of the application program as described in any one of claims 1 to 6.