File management method and device and storage medium

Abstract

The invention provides a file management method and device and a storage medium. According to the method, the files frequently used by the user are added to the display card on the desktop for management, the user does not need to gradually search in the file management application according to the storage path and can directly click the corresponding file icon on the desktop to open the file which the user wants to view, convenience and rapidness are achieved, and the use experience of the user is greatly improved.

Description

File management method, device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on October 14, 2022, with application number 202211259598.7 and invention name “File Management Method, Device and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of information display technology, and in particular to a file management method, device and storage medium. Background Art

[0003] A file explorer is a resource management tool provided by the operating system. It allows you to view various files downloaded and stored by users on electronic devices, such as documents, images, audio and video data, etc.

[0004] However, when users view various files managed by the file explorer, they need to know the specific path of the file they want to view. For some files received through third-party applications, since their default paths are deep, such as multiple nested folders, users cannot quickly and accurately find the files they want to view.

[0005] Summary of the Invention

[0006] In order to solve the above technical problems, the present application provides a file management method, device and storage medium, which aim to reduce the complexity of operation and enable users to quickly and accurately find the files they want to view.

[0007] In a first aspect, the present application provides a file management method. The method includes: displaying a first interface; wherein the first interface includes a first card, the first card includes M file icons, each of the M file icons corresponds to a file in an electronic device, and M is a positive integer.

[0008] The first interface may be, for example, the desktop 10a mentioned below, and the first card may be, for example, the desktop cards 10a-1, 10a-2, 10a-3, 10a-4, etc. mentioned below.

[0009] The maximum value of M can be set according to business requirements, for example, 20 as mentioned below, that is, the first card can display file icons of up to 20 files.

[0010] Each file icon in the first card may display, for example, the file name, format, etc. of the corresponding file.

[0011] The types of files include, but are not limited to, documents, pictures, videos, audios, compressed packages, applications, etc. mentioned below.

[0012] Therefore, by displaying desktop cards for managing files on the desktop, and directly displaying shortcut entries to files that meet user needs in the desktop cards according to user needs, such as the file icons that establish shortcuts to files as mentioned above, users can search directly in the desktop cards and directly open the files they want to view. The entire search process is convenient and simple, which greatly improves the user experience.

[0013] According to the first aspect, the first interface is the desktop; displaying the first interface includes: in response to a first operation, displaying a desktop card setting entrance on the desktop; in response to a second operation acting on the desktop card setting entrance, displaying a desktop card setting interface, the setting interface including a desktop card entrance for managing files; in response to a third operation acting on the desktop card entrance for managing files, displaying a card form selection interface; in response to a fourth operation acting on the card form selection interface, adding a first card to the desktop according to the selected card form; in response to a fifth operation, adding a file to the first card, and displaying a file icon corresponding to the file in the first card.

[0014] The first operation is, for example, the two-finger pinching operation mentioned below, as shown in (1) in FIG8a .

[0015] Among them, the desktop card setting entrance is, for example, the “desktop card setting control” shown in (2) in FIG8a.

[0016] It is understandable that in actual applications, after the user makes a first operation on the desktop, the electronic device can respond to the first operation and also display wallpaper setting controls, switching effect setting controls, and desktop setting controls as described below.

[0017] The second operation is, for example, the click operation on the desktop card setting control mentioned below.

[0018] The setting interface is, for example, the interface shown in (3) of Figure 8a. As shown in (3) of Figure 8a, the setting interface may include a card entry for intelligent service recommendation (YOYO Suggestion), a card entry corresponding to the calendar application, a card entry corresponding to the weather application, and a desktop card entry for managing files (i.e., a desktop card entry for managing files in the file management application).

[0019] The third operation is, for example, a click operation on the desktop card entry corresponding to the file management application, as shown in (3) in FIG8a .

[0020] The card-format selection interface is exemplified by the interface 10c mentioned below.

[0021] The fourth operation is, for example, the following click operation on the control 10c-1 in the interface 10c.

[0022] Regarding the specific implementation details of selecting the card form of the first card in the card form selection interface and adding / creating the first card on the desktop, please refer to the following and will not be repeated here.

[0023] Among them, the fifth operation is, for example, the operation on the control 10f-3 displayed in the interface 10f below, or the operation on the file management application, or the direct operation on the first card. Please refer to the following for details and will not be repeated here.

[0024] Therefore, by operating on the desktop, adding the first card, and adding frequently used files to the first card, when viewing these files later, there is no need to access them step by step from the file management application according to the storage path. The files can be quickly found through the first card, and the operation is convenient and simple.

[0025] According to the first aspect, or any implementation method of the first aspect above, in response to the fifth operation, adding a file to the first card includes: displaying a file adding floating ball in the file preview interface, and the file adding floating ball is in a retracted state; in response to the sixth operation acting on the file adding floating ball, displaying the first navigation bar of the file adding floating ball, and the first navigation bar displays an adding entry for adding the file displayed in the file preview interface to the first card; in response to the seventh operation acting on the adding entry, adding the file displayed in the file preview interface to the first card, and retracting the first navigation bar, and the file adding floating ball is in a retracted state.

[0026] Among them, the file preview interface is such as the interface 10f-1 mentioned below, and the file adding floating ball in the retracted state is such as the style of the control 10f-3 shown in (3) in Figure 9a.

[0027] Among them, the sixth operation is, for example, the click operation performed on the control 10f-3 below, and the style of the file adding the floating ball to display the first navigation bar is, for example, the style of the control 10f-3 shown in (1) in Figure 9b.

[0028] The adding entry of the first card is, for example, the option of "add to desktop card" shown in (1) in FIG. 9b.

[0029] The sixth operation is, for example, the following click operation on the option “Add to desktop card”.

[0030] In response to the seventh operation on the option "Add to desktop card", the interface 10f may change as shown in (2) in FIG9b, and the first card may change as shown in (3) in FIG9b.

[0031] It is understandable that for this method of adding a file to the first card through the file adding floating ball in the third-party application, the fifth operation at least includes the sixth and seventh operations mentioned above. The specific implementation details are detailed below and will not be repeated here.

[0032] Therefore, by providing a file adding floating ball in the file preview interface that can be used to add files to the first card on the desktop, in the preview state, the file adding floating ball is in a retracted state, which does not affect the user's viewing of the file content. When the previewed file needs to be added to the first card for subsequent quick viewing, the file adding floating ball can be directly operated, which provides a better user experience.

[0033] According to the first aspect, or any implementation of the first aspect above, before adding the file displayed in the file preview interface to the first card, the method also includes: displaying a first prompt window, the first prompt window including a first option and a second option; when receiving an eighth operation acting on the first option, in response to the eighth operation, adding the file in the file preview interface to the first card, and canceling the display of the first prompt window; when receiving a ninth operation acting on the second option, in response to the ninth operation, creating a new card, adding the file in the file preview interface to the newly created card, and canceling the display of the first prompt window.

[0034] The first prompt window is, for example, the window 10f-4 mentioned below, the first option is, for example, the control 10f-41 mentioned below, and the second option is, for example, the control 10f-42 mentioned below.

[0035] The eighth operation is, for example, the operation of selecting control 10f-41 and clicking the "OK" button described below, and the ninth operation is, for example, the operation of selecting control 10f-42 and clicking the "OK" button described below. Details on adding files through the options provided in the first prompt window are described below and are not further elaborated here.

[0036] Thus, not only can files be added to an existing first card, but also a new card can be created according to user needs and files can be added to the new card, which can better adapt to different application scenarios.

[0037] According to the first aspect, or any implementation of the first aspect above, the method also includes: when the set time is reached and the seventh operation is not received, the first navigation bar is folded and the file addition floating ball is in a folded state; or, when the tenth operation acting on the file preview interface is received within the set time, the first navigation bar is folded and the file addition floating ball is in a folded state.

[0038] Therefore, when the user does not need to use the add entry in the first navigation bar of the file adding floating ball, the first navigation bar of the file adding floating ball is folded, so that the file adding floating ball is in a folded state, thereby minimizing the obstruction of the file content displayed in the file preview interface.

[0039] According to the first aspect, or any implementation of the first aspect above, in response to the fifth operation, adding a file to the first card includes: in response to the tenth operation acting on the file management application, displaying the second interface, the second interface is a page opened step by step according to the storage path, and the file to be added is displayed in the second interface; in response to the eleventh operation acting on the second interface, displaying the second navigation bar, the second navigation bar includes the third option; in response to the twelfth operation acting on the third option, displaying the first menu bar, the first menu bar includes the fourth option; after selecting the file to be added, in response to the thirteenth operation acting on the fourth option, adding the file to be added to the first card.

[0040] The tenth operation is, for example, the operation of opening a file management application as described below, and accessing the opening interface 10g step by step according to the storage path of the file 10.

[0041] Correspondingly, the second interface is, for example, the interface 10g.

[0042] The eleventh operation is, for example, an operation performed on the interface 10g below, such as a long press operation.

[0043] The third option is, for example, the “more option controls” shown in (2) in FIG. 10 a .

[0044] It is understandable that the second navigation bar may also include the following share controls, copy controls, move controls, delete controls, etc. The purpose of each control is detailed below and will not be repeated here.

[0045] The twelfth operation is, for example, a click operation on the "more options control".

[0046] Among them, the first menu bar, for example, in (3) in Figure 10a, a window including more options pops up in the interface 10g. In addition to the fourth option mentioned above (the "Add to Desktop" option shown in (3) in Figure 10a), the options included in it may also include a "Favorites" option, a "Rename" option, a "Details" option, a "Compress" option, a "Move to Safe" option, an "Open with other applications" option, etc.

[0047] The thirteenth operation is, for example, the click operation on the "Add to Desktop" option described below.

[0048] Therefore, by providing this file adding method, the user can add the files that have been stored locally to the first card, thereby facilitating subsequent use.

[0049] According to the first aspect, or any implementation of the first aspect above, the first card also includes a file adding entry; in response to the fifth operation, adding a file to the first card includes: in response to the fourteenth operation acting on the file adding entry, displaying the third interface, in which the file to be added and the fifth option are displayed; after selecting the file to be added, in response to the fifteenth operation acting on the fifth option, adding the file to be added to the first card.

[0050] The file adding entry included in the first card is, for example, the control 10a-13 shown in (2) in FIG11 .

[0051] It is understandable that in some implementations, the file adding entry may also be an area in the first card for displaying file icons.

[0052] The fourteenth operation is, for example, a click operation on the control 10a-13.

[0053] The third interface is, for example, the interface 10k shown in (1) of FIG. 12b , and the fifth option is, for example, the control 10k-2.

[0054] The fifteenth operation is, for example, a click operation on the control 10k-2.

[0055] Regarding how to use these two file adding entries to add files to the first card, please see below for details and will not be repeated here.

[0056] Thus, the user can directly operate the first card displayed on the desktop to directly jump to the third interface where files can be selected, and then select the files to be added and add them to the first card.

[0057] According to the first aspect, or any implementation method of the first aspect above, the first interface is a desktop, and a second card is displayed on the desktop, and the second card is a desktop card for managing files; displaying the first interface includes: in response to the sixteenth operation acting on the second card, displaying the second menu bar, and the second menu bar includes: more file management card options; in response to the seventeenth operation acting on the more file management card options, displaying the card form selection interface; in response to the eighteenth operation acting on the card form selection interface, adding a first card to the desktop according to the selected card form; in response to the nineteenth operation, adding a file to the first card, and displaying the file icon corresponding to the file in the first card.

[0058] The second card is, for example, the desktop card 10a-4 mentioned below.

[0059] Among them, the sixteenth operation is, for example, a click or long press operation on the desktop control 10a-4 as described below, and the displayed second menu bar may be the window 10a-5 shown in (2) in FIG8d.

[0060] It is understandable that the second menu bar may include not only more file management card options, but also the edit card options, remove options, etc. mentioned below.

[0061] The Remove option in the second menu bar can be used to remove the second card from the desktop; the Edit Card option in the second menu bar can be used to edit the source of the files managed in the second card. Its implementation method is similar to that of the first card. See below for details and will not be repeated here.

[0062] Among them, the seventeenth operation is, for example, a click operation on the more file management card option. After operating this option, you can directly jump to the card form selection interface, such as the interface 10c shown in (1) in Figure 8b.

[0063] The implementation of performing the eighteenth operation in interface 10c, adding the first card to the desktop, and adding a file to the first card in response to the nineteenth operation is similar to the fourth and fifth operations mentioned above and will not be repeated here. The specific implementation details can be found below.

[0064] Thus, the first card is created with the help of an existing card of the same type.

[0065] According to the first aspect, or any implementation of the first aspect above, usage scenarios of the files managed in the first card and usage scenarios of the files managed in the second card are different.

[0066] For example, the files managed in the first card are applicable to office scenarios, that is, they are usually files involved in work; the files managed in the second card may be applicable to game scenarios, such as the managed files are documents that record game accounts.

[0067] Therefore, by dividing the cards for managing files according to scenes, it is easier for users to find them.

[0068] According to the first aspect, or any implementation of the first aspect above, the usage location of the file managed in the first card is different from the usage location of the file managed in the second card.

[0069] For example, users may be accustomed to using different files at their company and residence. By managing the corresponding files separately using different locations, users can quickly find the files they need from the corresponding cards.

[0070] According to the first aspect, or any implementation of the first aspect above, the method also includes: in response to the twentieth operation acting on the first card, displaying a third menu bar, the third menu bar including a remove option and an edit option; in response to the twenty-first operation acting on the remove option, removing the first card from the desktop.

[0071] The twentieth operation is, for example, the following operation performed on the desktop card 10a-1 shown in (1) of FIG12a, such as a long press operation.

[0072] The third menu bar is, for example, the window 10i-1 shown in (2) of Figure 12a. It is understood that the third menu bar may include not only the above-mentioned remove option and edit option, but also more file management card setting options.

[0073] The twenty-first operation is, for example, the following click operation on the remove option in the window 10i-1.

[0074] Therefore, the third menu bar can be called out by operating the card to be deleted, and the entire card can be directly deleted through the remove option in the third menu bar, which is convenient and fast.

[0075] In addition, in actual applications, one or several files in the card can be deleted separately. The specific implementation method is detailed below and will not be repeated here.

[0076] According to the first aspect, or any implementation of the first aspect above, the method also includes: in response to the twenty-second operation acting on the editing option, displaying the first file source option and the second file source option; when receiving the operation on the first file source option, recommending M files from the folder selected by the user as the M files managed by the first card, or recommending M files from the N folders recommended by the system as the M files managed by the first card; when receiving the operation on the second file source option, using the M files selected by the user as the M files managed by the first card.

[0077] The twenty-second operation is, for example, an operation performed on the “Edit Card” setting option 10i-11 in the window 10i-1 as described below, such as a click operation.

[0078] Among them, the first file source option is, for example, the control 10j-11 corresponding to the "intelligent recommendation" method mentioned below, and the second file source option is, for example, the control 10j-12 corresponding to the "specified file" method mentioned below.

[0079] Details on operating the first file source option and the second file source option to implement file source settings and add files are described below and will not be repeated here.

[0080] According to the first aspect, or any implementation of the first aspect, the card size of the first card is fixed.

[0081] The size of the first card is a fixed size such as 2×2, 4×2, etc.

[0082] According to the first aspect, or any implementation of the first aspect, the card size of the first card is variable, and the maximum size of the first card is 4×2.

[0083] The variation form and variation range of the first card with variable size can be found below and will not be described in detail here.

[0084] According to the first aspect, or any implementation of the first aspect above, the method also includes: receiving a twenty-third operation on any file icon in the first card; in response to the twenty-third operation, switching from the first interface to the fourth interface, the fourth interface being a preview interface of the file corresponding to the clicked file icon.

[0085] The twenty-third operation is, for example, clicking on any file icon displayed in the first card.

[0086] The fourth interface is, for example, an interface for viewing the default application of the file corresponding to the file icon clicked by the user, and its form may be as shown in (3) in FIG. 9a .

[0087] According to the first aspect, or any implementation of the first aspect above, the method also includes: when the electronic device is in the lock screen interface and the screen is black and in standby mode, in response to the operation of lighting up the lock screen interface, lighting up the lock screen interface and displaying the first card in the lock screen interface.

[0088] Among them, the display form is shown in Figure 7, and the specific details are shown below, which will not be repeated here.

[0089] In a second aspect, the present application provides an electronic device. The electronic device includes: a memory and a processor, the memory and the processor being coupled; the memory storing program instructions, which, when executed by the processor, cause the electronic device to execute instructions of the method of the first aspect or any possible implementation of the first aspect.

[0090] The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0091] In a third aspect, the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0092] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0093] In a fourth aspect, the present application provides a computer program comprising instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0094] The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0095] In a fifth aspect, the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processing circuit executes the method of the first aspect or any possible implementation of the first aspect to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0096] The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] FIG1 is a schematic diagram of an interface for searching for files through a file management application;

[0098] FIG2 is a schematic diagram illustrating a hardware structure of an electronic device;

[0099] FIG3 is a schematic diagram illustrating a software structure of an electronic device;

[0100] FIG4a and FIG4b are schematic diagrams of interfaces in the form of a card, one of which is exemplarily shown, corresponding to a desktop card for file management added to the desktop of an electronic device;

[0101] 5a to 5c are second schematic diagrams of card-style interfaces of desktop cards corresponding to file management added to the desktop of an electronic device;

[0102] FIG6 is a third schematic diagram of an interface in the form of a card, which is exemplarily shown, corresponding to a desktop card for file management added to the desktop of an electronic device;

[0103] FIG7 is a schematic diagram showing an exemplary interface in the form of a card corresponding to a desktop card for file management displayed on a lock screen interface of an electronic device;

[0104] 8a to 8d are schematic diagrams of interfaces for exemplarily showing adding a desktop card corresponding to file management on the desktop of an electronic device;

[0105] 9a to 9c are one of the schematic diagrams of the interface for adding a file to a desktop card of file management;

[0106] 10a and 10b are two exemplary diagrams of interfaces for adding files to a desktop card of file management;

[0107] FIG11 is a third exemplary diagram of an interface for adding a file to a desktop card of file management;

[0108] FIG12a to FIG12c are one of the schematic diagrams of the interface of the desktop card for editing file management;

[0109] 13a and 13b are two exemplary diagrams of interfaces of desktop cards for editing file management;

[0110] FIG. 14 a and FIG. 14 b are schematic diagrams of interfaces for exemplarily showing deletion of files managed in a desktop card of file management. DETAILED DESCRIPTION

[0111] 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 part of the embodiments of this application, not all of them. 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.

[0112] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0113] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0114] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0115] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0116] Currently, electronic devices can receive and download various files such as documents, pictures, audio or video sent by other electronic devices through third-party apps such as instant messaging applications (APPs) and email apps. They can also download various files from the Internet through third-party apps such as browser apps and video apps. After these files are downloaded to the electronic device, they will be managed by the file explorer of the electronic device. In order to facilitate users to view the various files managed by the file explorer, a user-oriented file management APP is provided at the application layer of the electronic device. This allows users to view the various files managed by the file explorer through the file management APP.

[0117] Regarding how a user views files managed by a file explorer through a file management app, the following is an explanation with reference to FIG1 .

[0118] Specifically, if the user wants to find a file named "Document 1" received from an instant messaging APP, he needs to know the default file saving path of the instant messaging APP in the Android system, and then operate the electronic device, enter the file management APP and search according to the default saving path of the instant messaging APP in the Android system. Usually, files received by third-party APPs can be saved in the "My Phone" folder. Assuming that the default path for saving files by the instant messaging APP is Android>Data>com.tencent.mm>MicroMsg>Download, in some implementations, it can be searched directly through the file management APP on the desktop, and in other implementations, it can also be searched by finding the entrance of the file management APP through the settings APP.

[0119] For example, for the method of directly searching through the file management APP on the desktop, as shown in Figure 1, the user first clicks the icon of the file management APP on the desktop to enter the interface of the file management APP, then clicks the "My Phone" folder, and then accesses the directories Data>com.tencent.mm>MicroMsg>Download step by step (not all levels of directories are shown in Figure 1). In the Download folder, the user can see the icon of Document 1 (as shown in the dotted box in Figure 1), and then the user can operate on Document 1.

[0120] However, with this method, users need to know the save path of the file they want to view, and access the corresponding folders step by step according to the path to search. In actual use, since electronic devices receive and download a large number of files through different APPs, and in the Android system, the paths used by electronic devices to store received files are complex, and the save paths of files received by different APPs are not necessarily the same, files from third-party APPs are not easy to find after being saved locally on the electronic device. Since users usually do not understand the save path when storing files in the Android system, it is difficult to find the required files, resulting in difficulty in finding files and a low user experience.

[0121] In view of this, the present application provides a file management method, which aims to reduce the complexity of users' file search operations, so that users can quickly and accurately find the files they want to view.

[0122] In order to better understand the technical solutions provided by the embodiments of the present application, before describing the technical solutions of the embodiments of the present application, the hardware structure of the electronic device to which the embodiments of the present application are applicable is first described in conjunction with the accompanying drawings.

[0123] Regarding the electronic devices to which the file management method provided in the embodiments of the present application is applicable, for example, mobile phones, tablet computers, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc., they are not listed here one by one. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices. For ease of explanation, Figure 1 takes a mobile phone as an example for illustration.

[0124] 2 , the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0125] Exemplarily, in some implementations, the sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., which are not listed one by one here and are not limited in this application.

[0126] Specifically in the technical solution provided in the embodiment of the present application, the sensor module 180 needs to include at least a touch sensor and a pressure sensor.

[0127] The pressure sensor is used to sense pressure signals and convert them into electrical signals. In some implementations, the pressure sensor can be located on the display screen 194. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force is applied to the pressure sensor, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the electronic device 100 detects the touch operation intensity using the pressure sensor. The electronic device 100 can also calculate the touch location based on the detection signal from the pressure sensor. In some implementations, touch operations applied to the same touch location but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the icon of the aforementioned file management app, an instruction to open the file management app is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a card used to display a file selected by the user or recommended files, a window containing an option to edit the card is displayed.

[0128] Among them, the touch sensor is also called a "touch panel". The touch sensor can also be set on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event, for example, it can include touch event types such as sliding, clicking, and long pressing. Visual output related to the touch operation can be provided through the display screen 194. In other implementations, the touch sensor can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194. Specifically, in the technical solution provided in the embodiment of the present application, when the user touches or taps the touch screen, the touch sensor will monitor the user's operation behavior, and the electronic device 100 will receive data collected by the touch sensor in the touch screen, and will respond to the operation behavior, such as performing the operation of adding a file to the card on the desktop mentioned below.

[0129] In addition, it should be noted that the processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0130] It is understandable that the controller can be the nerve center and command center of the electronic device 100. In practical applications, the controller can generate operation control signals according to instruction operation codes and timing signals to complete the control of instruction fetching and execution.

[0131] Furthermore, it should be noted that processor 110 may also include a memory for storing instructions and data. In some implementations, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0132] For example, in some implementations, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0133] Continuing with FIG2 , illustratively, the charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 may receive charging input from the wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 may receive wireless charging input via a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device via the power management module 141.

[0134] Continuing to refer to Figure 2, illustratively, the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other implementations, the power management module 141 can also be set in the processor 110. In other implementations, the power management module 141 and the charging management module 140 can also be set in the same device.

[0135] 2 , illustratively, the wireless communication function of the electronic device 100 may be implemented through antenna 1 , antenna 2 , mobile communication module 150 , wireless communication module 160 , a modem processor, and a baseband processor.

[0136] It should be noted that antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other implementations, the antennas can be used in conjunction with tuning switches.

[0137] Continuing to refer to Figure 2, illustratively, the mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some implementations, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some implementations, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0138] In addition, it should be noted that the modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some implementations, the modem processor may be an independent device. In other implementations, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

[0139] Continuing to refer to Figure 2, illustratively, the wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0140] Specifically in the technical solution provided in the embodiments of the present application, the electronic device 100 can communicate with other electronic devices through the mobile communication module 150 or the wireless communication module 160, and then receive files sent by other electronic devices, or download files from a server.

[0141] It should also be noted that electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0142] Continuing to refer to Figure 2, illustratively, the display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some implementations, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1. Specifically, in the technical solution provided in the embodiments of the present application, a series of operations for the user to search for files can be implemented through the function controls displayed in the display screen 194.

[0143] In addition, it should be noted that the electronic device 100 can achieve the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0144] Furthermore, it should be noted that the ISP is used to process data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then transmitted to the ISP for processing and converted into an image visible to the naked eye. The ISP can also perform algorithmic optimization on image noise, brightness, and skin color. The ISP can also optimize parameters such as exposure and color temperature of the captured scene. In some implementations, the ISP can be located in camera 193.

[0145] In addition, it should be noted that the camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some implementations, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0146] Furthermore, it should be noted that the digital signal processor is used to process digital signals, and in addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0147] Furthermore, it should be noted that video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. This allows the electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0148] Continuing with FIG. 2 , the external memory interface 120 can be used, for example, to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored on the external memory card.

[0149] Continuing to refer to Figure 2, illustratively, the internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0150] Specifically in the technical solution provided in the embodiment of the present application, various files managed by the file explorer can be stored in the internal memory 121.

[0151] In addition, it should be noted that the electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0152] In addition, it should be noted that the audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some implementations, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0153] Continuing with FIG. 2 , illustratively, buttons 190 include a power button, a volume button, and the like. Buttons 190 may be mechanical buttons or touch buttons. Electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of electronic device 100.

[0154] Continuing to refer to Figure 2, illustratively, the motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, the motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0155] 2 , illustratively, the indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, and the like.

[0156] This concludes the introduction to the hardware structure of the electronic device 100. It should be understood that the electronic device 100 shown in FIG2 is merely an example. In a specific implementation, the electronic device 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have a different component configuration. The various components shown in FIG2 may be implemented in hardware, including one or more signal processing and / or application-specific integrated circuits, software, or a combination of hardware and software.

[0157] 2 , the software structure of the electronic device 100 is described below. Before describing the software structure of the electronic device 100 , the architecture that the software system of the electronic device 100 can adopt is first described.

[0158] Specifically, in actual applications, the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture.

[0159] In addition, it is understandable that the software systems used by current mainstream electronic devices include but are not limited to Windows systems, Android systems, and iOS systems. For ease of explanation, the embodiment of the present application takes the layered architecture Android system as an example to exemplify the software structure of the electronic device 100.

[0160] In addition, the file management solution provided in the subsequent embodiments of this application is also applicable to other systems in specific implementations.

[0161] See FIG3 , which is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.

[0162] As shown in Figure 3, the layered architecture of electronic device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other via software interfaces. In some implementations, the Android system is divided into four layers: from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0163] Among them, the application layer can include a series of application packages.

[0164] As shown in Figure 3, the application package may include applications such as desktop manager, file management, settings, music, and WLAN. These applications are not listed here one by one and are not limited in this application. Among them, the desktop manager is used to manage and display the icons of applications installed in the electronic device, as well as the cards for user management of user-selected files or automatically recommended files mentioned below, which do not have icons on the desktop; the file management APP is used to provide users with a way to view various files managed by the file explorer; the settings APP is used to provide various user operation entrances, such as the entrance to open the file management APP mentioned above.

[0165] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. In some implementations, these programming interfaces and programming frameworks can be described as functions.

[0166] As shown in Figure 3, the application framework layer may include functions such as the view system, content provider, resource manager / file resource manager, window manager, input manager, card service manager, etc., which are not listed here one by one and this application does not impose any restrictions on this.

[0167] The view system includes visual controls, such as controls for displaying text and images. The view system can be used to build applications. A display interface can consist of one or more views.

[0168] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0169] In actual applications, the resource manager and the file resource manager can be one, and Figure 3 takes the resource manager as an example. Specifically, the resource manager is used to provide various resources for the application, such as localized strings, icons, pictures, layout files, video files, etc.

[0170] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0171] The input manager is used to manage touch events and implement the dispatch of touch events.

[0172] The Card Service Manager receives and stores card information published by desktop applications (apps), such as the file names and paths described below. It also provides an interface for desktop applications to query card information. For example, it provides an interface for the desktop manager. When a user clicks the icon of a file within a card in the desktop manager, the file is directly found based on the name and path recorded in the card information and displayed through the corresponding app. The specific implementation details of this operation are detailed below and will not be repeated here.

[0173] Android Runtime includes core libraries and a virtual machine. Android Runtime is responsible for scheduling and management of the Android system.

[0174] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0175] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0176] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0177] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0178] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0179] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0180] It is understandable that the 2D graphics engine mentioned above is a drawing engine for 2D drawing.

[0181] Furthermore, it is understood that the kernel layer in the Android system is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, a sensor driver, a Wi-Fi driver, a Bluetooth driver, and the like. For example, the sensor driver can be used to output detection signals from a sensor (e.g., a touch sensor) to the view system, so that the view system displays the corresponding application interface in response to the detection signal.

[0182] This concludes the introduction to the software structure of the electronic device 100. It should be understood that the layers in the software structure shown in FIG3 and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, and this application does not impose any limitations thereon.

[0183] Taking the electronic device with the hardware structure shown in FIG2 and the software structure shown in FIG3 as an example, based on the file management method provided in the embodiment of the present application, a card for managing files (hereinafter referred to as a desktop card) can be displayed on the desktop of the electronic device. The desktop card displays files that meet the user's needs, such as the most recently received and downloaded files, or the most frequently used files, or the files with the longest usage time, or the files suitable for the current time period, or the files suitable for the current location, etc., which are not listed here one by one, and this embodiment does not limit this. In this way, the user can directly click the file icon of the corresponding file in the desktop card on the desktop to directly jump to the preview interface of the file corresponding to the clicked file icon, thereby greatly facilitating the user's viewing.

[0184] In order to better understand the file management method provided by this embodiment, the file management method provided by this embodiment is described below with reference to the accompanying drawings from the aspects of the card form, adding method, editing method, adding files to desktop cards, deleting files, etc.

[0185] The following describes, in conjunction with FIG. 4 a , FIG. 4 b , FIG. 5 a to FIG. 5 c , and FIG. 6 , exemplary implementations of desktop cards of various specifications and forms provided in the embodiments of the present application.

[0186] The first implementation method

[0187] As shown in (1) of FIG4a, an electronic device such as a mobile phone can display a desktop card 10a-1 on the desktop 10a. The desktop card 10a-1 is presented in a fixed-size 2×2 four-square grid format. Specifically, each row in the visible range only displays 2 file icons, and each column only displays 2 file icons.

[0188] Furthermore, in order to facilitate the user to quickly find more files through the desktop card 10a-1, when the size of the desktop card 10a-1 is fixed, the file icons that are not displayed in the visible range can be viewed through a sliding control. Continuing with FIG4a (1), the desktop card 10a-1 may include a control 10a-11 for displaying the number of files currently managed by the desktop card 10a-1, and a control 10a-12 for sliding the file icons displayed in the visible range.

[0189] Continuing to refer to (1) in FIG4a , for example, the desktop card 10a-1 currently manages 6 files, such as file 1.pptx, file 2.doc, file 3.txt, file 4.xls, file 5.xls, and file 6.xls. That is, the user can directly view these 6 files through the 6 file icons displayed in the desktop card 10a-1. For example, when the user clicks the file icon corresponding to file 1.pptx, the mobile phone will start a default or preset APP specifically for viewing PPTX format files in response to the user operation, and then the APP will access file 1.pptx and display the content in file 1.pptx.

[0190] Continuing to refer to (1) in FIG4a , for example, the current visible range of the desktop card 10a-1 can only display the file icons corresponding to the four files, namely, file 1.pptx, file 2.doc, file 3.txt, and file 4.xls. When the user wants to view file 5.xls, the control 10a-12 can be slid downward to display the file icon of file 5.xls within the visible range of the desktop card 10a-1, as shown in (2) in FIG4a . Correspondingly, if the user wants to view file 2.doc, the control 10a-12 can be slid upward to display the file icon of file 2.doc within the visible range of the desktop card 10a-1, as shown in (1) in FIG4a .

[0191] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0192] Furthermore, in some implementations, a fixed-size card format can also be a 4×2 eight-square grid format, such as the desktop card 10a-2 shown in FIG4b . The desktop card 10a-2 may include a control 10a-21 for displaying the number of files currently managed by the desktop card 10a-2, and a control 10a-22 for sliding the file icons displayed within the visible range. In this way, the file icons of eight frequently used files can be displayed within the visible range of the desktop card 10a-2, thereby minimizing the user's need to slide the control 10a-22, further reducing user operations.

[0193] It should be understood that the above two fixed-size card formats are merely examples for better understanding the technical solution of this embodiment and are not intended to be the sole limitation of this embodiment. In actual applications, appropriate desktop cards can be created based on the remaining space on the desktop 10a, or the user can set them based on personal preferences. This embodiment does not impose any restrictions on this.

[0194] In addition, the number of files that can be managed by a desktop card can also be a system default or set according to user usage habits. This embodiment does not limit this. This embodiment and the following embodiments take 20 as an example, that is, a desktop card can manage up to 20 files.

[0195] The second implementation method

[0196] As shown in FIG5a , an electronic device such as a mobile phone can display a desktop card 10a-3 on desktop 10a. The size of desktop card 10a-3 varies within a set range based on the number of managed files. For example, when only one file, file1.pptx, is managed, the visible area of ​​desktop card 10a-3 is 1×2. Desktop card 10a-3 can also display a control 10a-31 for the number of files currently managed by desktop card 10a-3, which is shown as one in FIG5a .

[0197] Exemplarily, in one implementation, the above-mentioned setting range is, for example, a maximum visible range of 2×2 (as shown in FIG4a ), a minimum visible range of 1×2 (as shown in FIG5a ), or a maximum visible range of 4×2 (as shown in FIG4b ), a minimum visible range of 1×2 (as shown in FIG5a ).

[0198] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0199] This embodiment takes the maximum visible range of 4×2 (as shown in Figure 4b) and the minimum visible range of 1×2 (as shown in Figure 5a) as an example. For example, when the user adds file 2.doc and file 3.txt to the desktop card 10a-3, the number displayed in the control 10a-31 changes to 3, and the card format of the desktop card 10-3 is presented in the 2×2 four-square format as shown in Figure 5b.

[0200] As shown in FIG5c , when the user subsequently adds files 4.xls, 5.xlst, and 6.xls to desktop card 10a-3, since the maximum visible area of ​​desktop card 10a-3 is 4×2, desktop card 10a-3 will also display a control 10a-32 for sliding the file icons displayed within the visible area. By sliding control 10a-32, the user can view file icons that are not currently displayed within the visible area. The operation of control 10a-32 is similar to that of control 10a-12 described above and will not be further described here.

[0201] The third implementation method

[0202] As shown in FIG6 , an electronic device such as a mobile phone can display a desktop card 10a-1 and a desktop card 10a-4 on a desktop 10a. The desktop cards 10a-1 and 10a-4 can be of the same or different card formats. FIG6 shows a four-square grid format of a fixed size of 2×2.

[0203] Continuing to refer to FIG6 , illustratively, in some implementations, the desktop card 10a-4 can be connected to the desktop card 10a-1, including a control 10a-41 for displaying the number of files currently managed by the desktop card 10a-4, and a control 10a-42 for sliding the file icons displayed within the visible range.

[0204] For example, in some implementations, the multiple desktop cards displayed in the desktop 10a can be divided according to the file type displayed, such as the file icons displayed in one desktop card are all file icons of files in TXT format, while the file icons displayed in another desktop card are all file icons of files in DOC format.

[0205] For example, in other implementations, the multiple desktop cards displayed on the desktop 10a can be divided according to the location of use. FIG6 shows the division according to location as an example. For example, desktop card 10a-1 manages files frequently used by the user at permanent location 1, and desktop card 10a-4 manages files frequently used by the user at permanent location 4. The files managed in the desktop cards corresponding to different permanent locations can be partially the same or completely different, and this embodiment does not impose any limitation on this.

[0206] Furthermore, it should be noted that, in actual applications, in order to reduce the occupied area of ​​the desktop 10a, the user's current location can be identified, and only the desktop cards corresponding to the location can be displayed on the desktop 10a. For example, when the user is in location 1, only the desktop card 10a-1 is displayed. Correspondingly, when the user is in location 2, only the desktop card 10a-4 is displayed.

[0207] For example, in other implementations, the above two classification methods can be combined. For example, if the user at the resident location 1 often views files in DOC format and TXT format, the desktop card 10a-1 can only manage files in DOC format that meet the set requirements, and the desktop card 10a-4 can only manage files in TXT format that meet the set requirements.

[0208] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0209] It should be noted that the above embodiment exemplifies three desktop card forms. It can be understood that the embodiments of the present application include but are not limited to the above three desktop card forms. In actual implementation, the embodiments of the present application can also support other card forms similar to the above three card forms, such as 3×2, etc., which can be determined based on actual usage requirements and are not limited by the embodiments of the present application.

[0210] The above-mentioned embodiments of the present application provide desktop cards of various specifications for users to choose from. Users can choose to add desktop cards that suit their usage habits to the desktop display according to their actual usage needs. The desktop cards provided in the embodiments of the present application present various files that have been recently used by the electronic device, or that have a usage frequency that meets the set requirements, or a usage duration that meets the set requirements, or that meet the current time period, or that meet the current location, and that are stored in different paths to the user, thereby providing users with a more intuitive and convenient form of file management.

[0211] For example, in some implementations, the display order of the file icons of the files managed by the desktop cards displayed on the desktop 10a and the positional relationship between the file icons may be fixed, such as being displayed in the order of addition.

[0212] For example, in other implementations, in order to better enhance the user experience, the order of file icons displayed in the desktop card can be dynamically adjusted based on the frequency, duration, location, etc. of use of the corresponding files. For example, when the user is at the permanent location 1, such as a company, the order of file icons displayed in the desktop card can be comprehensively adjusted based on multiple dimensions such as the frequency, duration, and time period of use of different files by the user over a period of time, such as 5 consecutive working days. For example, from 9 a.m. to 12 p.m. and from 2 p.m. to 6 p.m. on weekdays, when the user is at the permanent location 1, the desktop card 10a-1 mentioned above is displayed on the desktop 10a, and the frequency, duration, and time period of use are displayed within the default visible range of the desktop card 10a-1. The setting requires files 1.pptx, file 2.doc, file 3.txt, and file 4.xls. From 9:00 a.m. to 12:00 p.m. and from 2:00 p.m. to 6:00 p.m. on non-working days, when the user is at the permanent location 2, the above-mentioned desktop card 10a-4 is displayed on the desktop 10a, and files 21.pptx, file 22.doc, file 23.txt, file 24.xls, etc. whose usage frequency, usage time, and usage time period meet the setting requirements are displayed within the default visible range of the desktop card 10a-4.

[0213] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0214] In addition, it should be noted that when an electronic device such as a mobile phone is in the lock screen interface and the screen is black and in standby mode, after the user taps the screen or presses the power button to light up the screen, as shown in Figure 7, based on the file management method provided in the embodiment of the present application, a desktop card similar to the above-mentioned card form, such as desktop card 10b-1, can also be displayed on the lock screen interface 10b. Among them, the desktop card 10b-1 may include a control 10b-11 for displaying the number of files currently managed by the desktop card 10b-1, and a control 10b-12 for sliding the file icons displayed in the visible range.

[0215] As shown in Figure 7, it is exemplified that 9 files are managed in the desktop card 10b-1 displayed on the lock screen interface 10b. Within the current visible range, the visible file icons are the file icons corresponding to the four files file 1.pptx, file 2.doc, file 3.txt, and file 4.xls. If the user wants to view the remaining 5 files, the sliding control 10b-12 can be used to slide the file icons of the files that are not currently displayed into the visible range for the user to select.

[0216] It should be understood that the above description is only an example for better understanding the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment. The card format of the desktop card displayed on the lock screen interface 10b can be any of the above, which will not be repeated here.

[0217] The following describes an exemplary method for adding a desktop card provided in an embodiment of the present application with reference to FIG8a to FIG8d.

[0218] In the embodiments of this application, users can select a desktop card format that suits their usage habits based on their actual needs. Accordingly, the electronic device can display any of the above-described desktop cards on the desktop or lock screen interface based on the user's usage needs to facilitate the user's file search. This embodiment takes adding desktop cards to the desktop as an example.

[0219] Optionally, in an embodiment of the present application, when no card is displayed on the desktop, the user can select a desktop card from a variety of card formats preset by the system in various ways and add the selected desktop card to the desktop.

[0220] For example, in some implementations, the user can operate on the desktop homepage to call out the desktop card setting interface, and then the user can perform a card adding operation on the desktop card setting interface to add the card to the desktop.

[0221] As shown in (1) of FIG8a , an electronic device such as a mobile phone receives an operation (e.g., a two-finger pinch operation) performed by a user on the desktop 10a. As shown in (2) of FIG8a , the mobile phone displays multiple controls on the desktop 10a in response to the two-finger pinch operation, such as a wallpaper setting control, a desktop card setting control, a transition effect setting control, and a desktop setting control. Further, the mobile phone receives an operation (e.g., a click operation) performed by the user on the desktop card setting control. As shown in (3) of FIG8a , the mobile phone displays a setting interface for the desktop card in response to the click operation. The setting interface for the desktop card displays various types of cards, such as a YOYO suggestion card, a file management card, a calendar card, and a weather card. Of course, other possible cards may also be included.

[0222] When the mobile phone receives a user operation (e.g., a click operation) on a file management card, as shown in FIG8b (1), the mobile phone displays a file management card display interface 10c. As shown in FIG8b (1), the card display interface 10c displays different card formats. As shown in FIG8b (1), the current display is a four-square format with a fixed card size of 2×2, and supports the management of a maximum of 20 files (hereinafter referred to as card format 1).

[0223] Continuing with FIG8b (1), the card display interface 10c also displays an "Add to Desktop" control 10c-1. When the user clicks on the control 10c-1, the mobile phone responds to the user's click operation and adds a desktop card in the form of card 1 shown in FIG8b (1) to the desktop 10a, as shown in FIG8c. When the user adds the aforementioned six files, File 1.pptx, File 2.doc, File 3.txt, File 4.xls, File 5.xls, and File 6.xls, to the desktop card, the result is shown in FIG4a (1).

[0224] As shown in (1) to (3) in FIG. 8b , the card display interface 10c also displays controls 10c - 2 and 10c - 3 for switching the card format.

[0225] For example, in some implementations, the user can trigger the mobile phone to update the card display interface 10c to display cards of other forms or specifications by operating on the card display interface 10c (such as sliding a finger in the direction of the arrow, or clicking on the control 10c-2).

[0226] If the mobile phone receives a sliding operation as shown in (1) in FIG8b , the mobile phone can display a card in an eight-square grid format with a fixed size of 4×2 in the card display interface 10c, as shown in (2) in FIG8b , and supports a card that can manage up to 20 files (hereinafter referred to as card format 2). If the mobile phone receives a click operation on the control 10c-1 by the user, the mobile phone will add a desktop card of card format 2 as shown in (2) in FIG8b to the desktop 10a in response to the user's click operation. When the number of files added by the user to the desktop card is greater than or equal to 8, its format is as shown in FIG4b .

[0227] If the mobile phone receives a sliding operation as shown in (2) in FIG8b, the mobile phone displays a variable format in the card display interface 10c, as shown in (3) in FIG8b, and the maximum visible range is a 4×2 eight-square grid format, and a card format that supports the management of up to 20 files (hereinafter referred to as card format 3). If the mobile phone receives a click operation on the control 10c-1 by the user, the mobile phone will add a desktop card of card format 3 shown in (3) in FIG8b to the desktop 10a in response to the user's click operation. When the number of files added by the user to the desktop card is greater than or equal to 8, its format is as shown in FIG4b.

[0228] If the mobile phone receives a sliding operation from the user as shown in (3) in Figure 8b, the mobile phone can display a variable format in the card display interface 10c, and the maximum visible range is a four-square format of 2×2, and a card format that supports managing up to 20 files (hereinafter referred to as card format 4). If the mobile phone receives a click operation from the user on the control 10c-1, the mobile phone will add a desktop card of card format 4 to the desktop 10a in response to the user's click operation. When the user adds a file to the desktop card, the changes of the desktop card can be shown in Figures 5a to 5c.

[0229] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0230] Optionally, in this embodiment of the present application, the cards displayed in the file management card display interface 10c may be displayed in descending order of priority. For example, card form 1 has a higher priority than card form 2, which has a higher priority than card form 3, which has a higher priority than card form 4. It should be understood that the above description is merely an example for a better understanding of the technical solution of this embodiment and is not intended to be the sole limitation on this embodiment.

[0231] In addition, it should be noted that in other implementations, the user can operate on an electronic device, such as the negative first screen of a mobile phone, to call out the desktop card settings interface, and then the user can perform a card adding operation on the desktop card settings interface to add the card to the desktop.

[0232] In addition, it should be noted that in other implementations, the user can operate on the system settings interface of an electronic device, such as a mobile phone, to call out the settings interface of the desktop card, and then the user can perform the card adding operation on the settings interface of the desktop card to add the card to the desktop.

[0233] It is understood that the above illustrates a possible method for a user to add a desktop card when there is no desktop card on the desktop. It is understood that other possible implementation methods may exist. For example, when a desktop card is already displayed on the desktop, the user can operate on the existing desktop card to call up the desktop card settings interface, and then perform the new desktop card addition operation in the desktop card settings interface to add the new desktop card to the desktop. This method of creating / adding a desktop card on desktop 10a is shown in Figure 8d.

[0234] Refer to (1) in Figure 8d. For example, when the desktop 10a already has a desktop card 10a-4 of the file management type, if the user wants to add a desktop card of the file management type to the desktop 10a, the user can long press the desktop card 10a-4. After the mobile phone detects the user's long press operation on the desktop card 10a-4, in response to the long press operation, the interface 10h will be displayed as shown in (2) in Figure 8d.

[0235] Referring to (2) in FIG8d , illustratively, the interface 10h displays a desktop card 10a-4 and a window 10a-5. Window 10a-5 may include an “Edit Card” setting option for editing the desktop card 10a-4, a “More File Management Cards” setting option for creating / adding a new desktop card of the file management type, and a “Remove” setting option for removing / deleting the desktop card 10a-4.

[0236] It is understandable that when the user clicks the "More" "File Management" card setting option, the mobile phone will jump to the interface shown in Figure 8b in response to the click operation. The operation of adding a card through the card display interface 10c shown in Figure 8b can be seen above in detail and will not be repeated here.

[0237] The following is an illustrative description of various implementation methods for adding files to a desktop card provided in an embodiment of the present application, with reference to FIG. 9 a , FIG. 9 b , FIG. 10 a , FIG. 10 b , and FIG. 11 .

[0238] The first implementation method

[0239] As shown in (1) in FIG9a , when “Zhang San” sends a file named “File 10” in DOC format to the holder of an electronic device such as a mobile phone (hereinafter referred to as User A) through a third-party APP such as an instant messaging APP, User A operates the mobile phone, such as opening the third-party APP, and enters the chat interface 10d with “Zhang San”.

[0240] Referring to (1) in FIG9a , the chat interface 10d may include one or more controls, for example. These controls include, but are not limited to, a control 10d-1 for exiting the chat interface 10d, a control 10d-2 for setting and searching for information related to “Zhang San”, a control 10d-3 for displaying an avatar of “Zhang San”, and a control 10d-4 for displaying content sent by “Zhang San”, such as messages and files.

[0241] Exemplarily, in some implementations, when user A clicks control 10d-1, the mobile phone responds to the click operation and exits the chat interface with "Zhang San"; when user A clicks control 10d-2, the mobile phone responds to the click operation and jumps to an interface that may include options for searching historical chat content, setting do not disturb messages sent by "Zhang San", setting reminders for messages sent by "Zhang San", setting the chat background with "Zhang San", clearing chat records, etc., which are not listed one by one here, and this embodiment does not limit this; when user A clicks control 10d-3, the mobile phone responds to the operation behavior and jumps to a details interface about "Zhang San", which may include, for example, "Zhang San's" phone number, tag information, permission information, etc., which are not listed one by one here, and this embodiment does not limit this.

[0242] Continuing to refer to (1) in FIG9a, illustratively, when user A operates control 10d-4 (such as a long press operation or a click operation), the mobile phone responds to user A's operation behavior, as shown in (2) in FIG9a, and switches from chat interface 10d to interface 10e. Interface 10e may include one or more controls. These controls include, but are not limited to, control 10e-1 for exiting interface 10e, control 10e-2 for viewing more setting options, and control 10e-3 for receiving or saving files.

[0243] For example, in some implementations, when user A clicks on control 10e-1, the mobile phone responds to the click operation and exits interface 10e, that is, it returns to the chat interface 10d with "Zhang San"; when user A clicks on control 10e-2, the mobile phone responds to the click operation and may pop up a function window providing other setting options, which may include, for example, options to send to friends, favorites, etc., which are not listed one by one here, and this embodiment does not limit this.

[0244] In addition, the size of the file 10.doc currently to be received can also be displayed in the interface 10e, such as 30.21 KB as shown in (2) in FIG9a.

[0245] Continuing to refer to (2) in FIG9a, for example, when user A operates the control 10e-3, such as clicking, the mobile phone responds to the operation of user A, as shown in (3) in FIG9a. After saving the file 10.doc to the corresponding path of the third-party APP under the file management, a feasible method is to directly jump to the preview interface 10f provided by the third-party APP and display the content of the file 10.doc in the preview interface 10f.

[0246] It should be noted that in actual application, after clicking on the control 10e-3, the mobile phone responds to the click operation. In the process of downloading and saving the file 10.doc locally, a pop-up window can be displayed in the interface 10e to show the storage path of the file 10.doc, and it will automatically disappear after a set time, such as 3 seconds. In this way, it will not block the interface content and can also make it easier for user A to know the actual storage path of the file 10.doc, and then find the file 10.doc under the storage path.

[0247] In addition, it should be noted that in some implementations, when user A pre-sets the function of opening a file with another application, after saving file 10.doc to the corresponding path under the file management of the third-party app, the set application can be directly launched, and the application can display the contents of file 10.doc. This embodiment takes the example of directly jumping to the preview interface 10f provided by the third-party app and displaying the contents of file 10.doc in the preview interface 10f.

[0248] Continuing with (3) in FIG9a , the preview interface 10f exemplarily includes one or more controls. These controls include, but are not limited to, a control 10f-1 for exiting the preview interface 10f, a control 10f-2 for viewing more setting options, and a control 10f-3 for adding the file 10.doc to the desktop card.

[0249] For example, in some implementations, when user A clicks on control 10f-1, the mobile phone responds to the click operation and exits the preview interface 10f; when user A clicks on control 10f-2, the mobile phone responds to the click operation and may pop up a function window providing other setting options, which may include, for example, options to send to friends, collection options, etc., which are not listed one by one here, and this embodiment does not limit this.

[0250] In addition, it should be noted that the control 10f-3 displayed in the preview interface 10f shown in (3) of Figure 9a can be a floating ball in actual application. After the interface 10e switches to the preview interface 10f, it pops up automatically, and the initial state is the retracted state, that is, the style shown in (3) of Figure 9a. In this way, it will not disturb user A to view the content of file 10.doc. When the file 10.doc needs to be added to the desktop card, by operating the control 10f-3 (such as a long press operation or a click operation, etc.), the mobile phone responds to the operation behavior of user A, and the control 10f-3 will switch to the open state, such as the style shown in (1) of Figure 9b.

[0251] Referring to (1) in FIG9b , for example, when control f-3 is in the open state, it can provide an option to “add the current file, such as file 10.doc, to the desktop card.” When user A operates the “add to desktop card” option (such as a long press or click operation), the mobile phone responds to user A’s operation by calling the corresponding service, instance, or function / interface, obtaining the relevant information of file 10.doc from the storage path where file 10.doc is located, generating a corresponding file icon, and adding the file icon to the desktop card. At the same time, a shortcut is established between the file icon and the storage path of file 10.doc.

[0252] For example, in some implementations, after user A operates the "Add to desktop card" option, in order not to affect user A's continued browsing of the contents of file 10.doc in the preview interface 10f, the control 10f-3 can be changed from the open state shown in (1) in Figure 9b back to the collapsed state described in (2) in Figure 9b.

[0253] In addition, in order to inform user A whether the operation of adding file 10.doc to the desktop card is successful, after the mobile phone completes the above-mentioned process and adds file 10.doc to the desktop card, such as desktop card 10a-1 mentioned above, a prompt message indicating the successful addition can be popped up on the preview interface 10f, such as "Added to desktop card 10a-1" shown in (2) of Figure 9b. Accordingly, in order not to affect user A's continued browsing of the content of file 10.doc on the preview interface 10f, the pop-up prompt message can automatically disappear after a set time, such as 3 seconds.

[0254] Referring to FIG9b (3), for example, if user A has created / added a desktop card 10a-1 to desktop 10a, before adding file 10.doc to desktop card 10a-1, if no files have been added to desktop card 10a-1, that is, the number of managed files is 0, its style may be as shown in FIG8c. When user A operates the option of "add to desktop card", the mobile phone responds to the user operation and adds file 10.doc to desktop card 10a-1, and the style of desktop card 10a-1 may be as shown in FIG9b (3).

[0255] In addition, it should be noted that in actual applications, there may be a situation where no desktop card has been added to the desktop 10a, or user A wants to add the current file to other desktop cards. In order to better meet the usage needs of user A, when the control 10f-3 is in the open state shown in Figure 9c (1), after user A operates the "Add to desktop card" option, the mobile phone responds to the user operation behavior, as shown in Figure 9c (2), and a window 10f-4 may pop up on the preview interface 10f. The window 10f-4 may include one or more controls. These controls include but are not limited to a control 10f-41 for selecting to add the current file to an existing desktop card, a control 10f-42 for selecting to create a new desktop card and add the current file to the newly created desktop card, a control 10f-43 for defaulting to user A's selection and not popping up prompts in the future, and a "Cancel" button for canceling this selection and an "OK" button for confirming this selection. It should be noted that only one of the controls 10f-41 and 10f-42 can be selected at the same time.

[0256] For example, when control 10f-41 is in the selected state (as shown in (2) in FIG9c ), and controls 10f-42 and 10f-43 are in the unselected state (as shown in (2) in FIG9c ), if user A clicks the "OK" button, the mobile phone responds to this operation, window 10f-4 disappears, and file 10.doc is added to desktop card 10a-1 according to the above-mentioned process of adding file 10.doc to existing desktop card 10a-1. Accordingly, after file 10.doc is added to desktop card 10a-1, a prompt message will pop up on the preview interface 10f, and control 10f-3 will also be retracted, as shown in (3) in FIG9c .

[0257] For example, when control 10f-41 is in a selected state (the state shown in (2) in Figure 9c), and controls 10f-42 and 10f-43 are in an unselected state (the state shown in (2) in Figure 9c), if user A clicks the "OK" button, the mobile phone responds to the operation, window 10f-4 disappears, and the preview interface 10f returns to the style shown in (1) in Figure 9c.

[0258] In addition, it should be noted that if user A does not operate the "Add to desktop card" option when the control 10f-3 is in the open state, after a set time, such as 5s, or after the user clicks on other areas of the preview interface 10f, the control 10f-3 can change from the open state to the collapsed state.

[0259] It should also be noted that when the user exits preview interface 10f, control 10f-3 automatically displays. When the user opens another file, such as file 11.xls, a pop-up window appears on the preview interface corresponding to file 11.xls, indicating that control 10f-3 is used to add file 11.xls to the desktop card. In other words, the pop-up window for control 10f-3 on each preview interface corresponds to the file displayed on that preview interface.

[0260] In addition, it is understandable that if there are multiple desktop cards in the desktop 10a, such as at least 2, there can also be 2 controls 10f-41 provided in the window 10f-4 for selecting to add to the existing desktop cards, that is, one control 10f-41 corresponding to each desktop card. In this way, after the user presses the "OK" button, the mobile phone can add the file 10.doc to the corresponding desktop card.

[0261] For example, in other implementations, when user A selects control 10f-42 (such as the style of control 10f-41 shown in (2) of FIG9c ), and control 10f-41 and control 10f-43 are not selected, if user A clicks the "OK" button, the mobile phone, in response to this operation, can jump from the current interface to the interface shown in FIG8b and perform the operation of adding a desktop card to the desktop 10a. After the new desktop card is added to the desktop, the file 10.doc is added to the newly created desktop card according to the above-mentioned process of adding files to the desktop card. For the specific details of adding desktop cards and adding files to desktop cards, please refer to the above text and will not be repeated here.

[0262] For example, when user A selects control 10f-42 (the style of control 10f-41 shown in (2) in Figure 9c), and controls 10f-41 and 10f-43 are unselected, if user A clicks the "OK" button, the mobile phone responds to the operation, window 10f-4 disappears, and the preview interface 10f returns to the style shown in (1) in Figure 9c.

[0263] For example, in other implementations, when user A selects control 10f-1 or control 10f-2, control 10f-3 is also selected. If user A clicks the "OK" button, the mobile phone will respond to the operation and follow the above-mentioned processing flow of selecting control 10f-1 or control 10f-2 and then clicking the "OK" button, while recording user A's selection. When adding other files through the third-party APP later, after operating the "Add to desktop card" option in control 10f-3, the process of adding the file to the existing desktop card is executed directly according to the recorded content, or a new desktop card is created and added to the newly created desktop card, without the need to pop up window 10f-4 again in the preview interface f.

[0264] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0265] In this way, when user A wants to view the contents of file 10.doc later, he does not need to open the above-mentioned third-party APP again, find the chat history with "Zhang San", and then click control 10d-4. He also does not need to remember the storage path of file 10.doc, and then search for file 10.doc by opening the corresponding path step by step. He can directly operate the file icon corresponding to file 10.doc displayed in the desktop card, such as clicking. The mobile phone responds to the operation and can directly use the set application to open file 10.doc so that the user can view the contents of file 10.doc.

[0266] It should be understood that the above-mentioned method of adding a previewed file to a desktop card through the control 10f-3 provided in the preview interface of the third-party APP is merely an example listed to better understand the technical solution of this embodiment and is not the sole limitation of this embodiment. In actual applications, files can also be added to the desktop card through other methods, such as the second and third implementation methods described below. Specific details of the second and third implementation methods are detailed below.

[0267] In addition, it should be noted that in actual applications, in order to better meet the user's usage needs and improve the user experience, when the control f-3 is in the open state, it can also provide a sharing option, that is, a function option to share the current file with other users through other applications; and a save as option, that is, a function option to copy the current file from the default storage path and store it in the user-specified path, etc., which will not be listed one by one here, and this embodiment does not limit this.

[0268] For example, when user A clicks the Share option, a panel may pop up for the user to select an application for sharing the file; when user A clicks the Save As option, an interface may be switched to selecting a storage path. This embodiment does not limit the specific implementation of the above options.

[0269] The second implementation method

[0270] For example, in some implementations, the commonly used files stored in electronic devices such as mobile phones can also be accessed step by step through the file management APP, and then the commonly used files can be added to the desktop card on the desktop. Taking the storage path of file 10.doc as "My Phone>Android>Data>com.tencent.mm>MicroMsg>Download" as an example, if the user wants to add the file 10.doc under this path to the desktop card, as shown in Figure 1 and Figure 10a, the user can first click the icon of the file management APP on the desktop to enter the interface of the file management APP, then click the "My Phone" folder, and then access the directories Android>Data>com.tencent.mm>MicroMsg>Download step by step (not all the directories at each level are shown in Figure 1). In the Download folder, the user can see the icon of file 10.doc (as shown in (1) in Figure 10a), and then the user can operate on file 10.doc.

[0271] As shown in (1) of FIG10a, illustratively, in some implementations, the mobile phone receives an operation by the user on the icon corresponding to the file 10.doc (such as a click operation or a long press operation, etc.), and the mobile phone responds to the operation, as shown in (2) of FIG10a, and displays multiple controls about the file, such as a check box control corresponding to each file to facilitate the user's selection of the file, and also displays a share control, a copy control, a move control, a delete control, and more options controls, etc.

[0272] For example, in some implementations, when the user clicks on the share control, a share panel may pop up for the user to select an application for sharing the file; when the user clicks on the copy control, a copy of the selected file may be copied from the path, and then after opening other applications, the copied file may be added to the specified path through user operations such as long pressing; when the user clicks on the move control, an interface for selecting the folder to be moved to may be displayed for the user to select; when the user clicks on the operation control, the file selected by the check box may be deleted, wherein the check box corresponding to the file 10.doc shown in (2) in FIG10a is selected, and the check boxes corresponding to the file 1 and the picture 1 are unselected.

[0273] Continuing to refer to (2) in FIG10a, illustratively, when the user operates the more option control (such as a long press operation or a click operation, etc.), the mobile phone responds to the operation behavior, as shown in (3) in FIG10a, and a window including more options pops up in the interface 10g. Among them, the window may include one or more options. These options include but are not limited to the "Favorites" option, the "Rename" option, the "Details" option, the "Compress" option, the "Move to Safe" option, the "Add to Desktop" option, the "Open with Other Applications" option, etc., which are not listed here one by one, and this embodiment does not limit this.

[0274] Optionally, in response to the user's operation on the "Collect" option, the mobile phone can collect the files selected by the check box in the interface 10g, such as the file 10.doc shown in (3) in Figure 10a, to a folder under the specified path.

[0275] Optionally, in response to the user's operation on the "rename" option, the mobile phone may pop up a renaming interface so that the user can rename the selected file, such as the file name of file 10.doc.

[0276] Optionally, in response to the user's operation on the "Details" option, the mobile phone may pop up a details interface corresponding to the selected file. For example, the details interface may display the file format, file size, receiving time, etc. of the file, which are not listed one by one here and are not limited in this embodiment.

[0277] Optionally, in response to the user's operation on the "compression" option, the mobile phone may compress the selected file using a compression method supported by the mobile phone.

[0278] Optionally, in response to the user's operation on the "move to safe" option, the mobile phone can move the selected file into a folder with a set encryption key to ensure the security of the file.

[0279] Optionally, in response to the user's operation on the "Open with other applications" option, the mobile phone may pop up a panel for selecting other applications, so that the user can select an application installed on the mobile phone to open the selected file.

[0280] It should be understood that the above description is merely an example for better understanding the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment. This embodiment does not limit the specific content provided by each interface corresponding to the above function options and the triggering process.

[0281] Optionally, in response to the user's operation on the "Add to Desktop" option, the mobile phone may pop up a window 10g-1 in the interface 10g, as shown in (1) in Figure 10b. The functions and operations of the various controls and buttons in window 10g-1 are similar to those of window 10f-4 described above. The specific details can be found above and will not be repeated here.

[0282] In addition, it is understandable that in some implementations, the mobile phone may not pop up the window 10g-1 in response to the user's operation of the "Add to Desktop" option, as shown in (2) in Figure 10b, and directly add the selected file to the desktop card in the manner of adding files to the desktop card as described above, and after the addition is successful, a prompt is given on the interface 10g, such as "Added to desktop card 10a-1".

[0283] Accordingly, when no other files are added to the desktop card 10a-1, after the file 10.doc is added to the desktop card 10a-1 in this way, the style of the desktop card 10a-1 is shown in (3) of Figure 10b. In this way, when the user subsequently wants to view the file, there is no need to search for it in the file management app according to the path. The file to be viewed can be quickly opened directly through the desktop card 10a-1.

[0284] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0285] The third implementation method

[0286] For example, in some implementations, the user may also operate through a desktop card that has been added to the desktop 10a to add a file to the desktop card.

[0287] As shown in (1) in Figure 11, for example, in some implementations, each area in the desktop card that can display a file icon can be set to directly open a file management APP, such as a shortcut to the "File Management" interface in Figure 1. When the user clicks on any area in the desktop card 10a-1 for displaying a file icon, it can jump directly to the "File Management" interface in Figure 1, so that the user can find the corresponding file according to the storage path of the file to be added, and then select the file and add it to the desktop card 10a-1. In this way, when the user subsequently views the file, there is no need to search from the file management APP according to the path, and the file to be viewed can be quickly opened directly through the desktop card 10a-1.

[0288] It can be understood that for the adding method shown in (1) in Figure 11, if the locations where files can be added within the current visible range of the desktop card 10a-1 all display the file icons of the added files, the user can slide the control 10a-12 to find the area where the file icon is displayed to the user but the file icon is not yet displayed, and then operate it to add the file.

[0289] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0290] As shown in (2) in FIG11 , for example, in other implementations, in order to further reduce user operations, such as sliding the control 10a-12 and querying the clickable area to add files, a control 10a-13 for adding files can be fixed at a certain position of the desktop card 10a-1, such as the lower right corner of (2) in FIG11 . In this way, when the number of files managed by the desktop card 10a-1 has not reached its corresponding maximum number, such as 20, each time the user adds a file to the desktop card 10a-1, he can directly operate the control 10a-13 to directly jump to the "File Management" interface in FIG1 , and then select the appropriate file to add according to the above operation.

[0291] In addition, it should be noted that in some other implementations, after 20 files are added to the desktop card 10a-1 through the control 10a-13 shown in (2) of Figure 11, in order to avoid the user adding files to the desktop card 10a-1 again through the control 10a-13, and the number of files allowed to be added by the desktop card 10a-1 exceeds the limit, resulting in addition failure, the user repeating the operation, affecting the user experience, the control 10a-13 can be canceled when the number of files added to the desktop card 10a-1 reaches 20, as shown in (3) of Figure 11.

[0292] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0293] The following is an illustrative description of various implementation methods for editing desktop cards provided in the embodiments of the present application, with reference to Figures 12a to 12c, and Figures 13a and 13b.

[0294] It is understandable that the above-mentioned implementation method of adding files to the desktop card is that the user actively selects the files to be managed by the desktop card and adds them to the desktop card. In another implementation method, the files managed in the desktop card can also be automatically filtered out and added to the desktop card based on the user's historical usage habits, such as the frequency of use, duration of use, time period of use, and location of use of the files. In this way, the user does not need to select files one by one to add them. He only needs to set the file range and file type of the "smart recommendation" method by editing the entrance of the desktop card.

[0295] In addition, it should be noted that the editing of the desktop card in this embodiment specifically refers to setting the desktop card to start the process of automatically adding files.

[0296] For ease of understanding, this embodiment takes the setting entry provided by editing the desktop card as an example, which includes the "smart recommendation" method and the "specify file" method. Among them, the "smart recommendation" method means that after the user adds a desktop control to the desktop, the mobile phone can automatically filter out a set number of files that meet multi-dimensional requirements such as usage frequency, usage duration, usage time period, and usage location from multiple files in the specified directory, such as 20 files, and add them to the desktop card; the "specify file" method means that after the user adds a desktop control to the desktop, the mobile phone can independently select one or more files from a folder specified by the user as needed and add them to the desktop card.

[0297] The editing process of desktop cards using the "intelligent recommendation" method and the "specified file" method is explained below with reference to the accompanying drawings.

[0298] As shown in (1) of FIG12a, when the user operates the desktop card 10a-1, such as long pressing, the mobile phone responds to the operation, and an interface 10i pops up on the desktop 10a as shown in (2) of FIG12a. The interface 10i displays the desktop card 10a-1 and the window 10i-1.

[0299] Referring to (2) in Figure 12a, exemplarily, the window 10i-1 may include an "Edit Card" setting option 10i-11 for editing the desktop card 10a-1, a "More "File Management" Cards" setting option for creating / adding a new file management-type desktop card, and a "Remove" setting option for removing / deleting the desktop card 10a-1.

[0300] Optionally, when the user clicks the "More" "File Management" card setting option, the mobile phone will jump to the interface shown in Figure 8b in response to the click operation. The operation of adding a card through the card display interface 10c shown in Figure 8b can be seen above in detail and will not be repeated here.

[0301] Optionally, when the user clicks the "Remove" setting option, the mobile phone will remove the desktop card 10a-1 displayed on the desktop 10a from the desktop 10a in response to the click operation. It is understandable that if a file has been added to the desktop card 10a-1, the shortcut entry to the file managed by the desktop card 10a-1 will also be deleted. In other words, the user cannot directly find the file previously managed by the desktop card 10a-1 on the desktop and needs to use the file management app to search step by step according to the storage path.

[0302] Optionally, when the user clicks on the "Edit Card" setting option 10i-11, the mobile phone responds to the click operation and switches to the interface 10j as shown in (3) in Figure 12a. The interface 10j displays a window 10j-1 for selecting the above-mentioned "smart recommendation" mode or "specify file" mode.

[0303] Continuing to refer to (3) in FIG12a, illustratively, the window 10j-1 may include one or more controls, including but not limited to a control 10j-11 for selecting the "smart recommendation" mode and a control 10j-12 for selecting the "specified file" mode.

[0304] It is understandable that in some implementations, one of the above two methods can be set as the default method, such as in 13a (3) taking the "smart recommendation" method as the default method as an example. In this case, the window 10j-1 will also display the "Select Folder" entry 10j-13 corresponding to the "smart recommendation" method and the "File Type" entry 10j-14.

[0305] Exemplarily, when the user clicks on the "Select Folder" entry 10j-13, the mobile phone responds to the operation, as shown in (1) in Figure 12b, and enters the "My Files" interface 10k. The interface 10k includes one or more controls, including but not limited to a control 10k-1 for exiting the interface 10k, a control 10k-2 for saving the user's settings on the interface 10k, and a check box for selecting each folder.

[0306] As shown in (1) of FIG. 12b , the interface 10k includes three folders belonging to the first-level directory: "My Files," "My Phone," and "Favorites." These three folders can include several folders belonging to the second-level directory. In this embodiment, the files set in the "smart recommendation" mode are from the "My Files" folder.

[0307] Continuing to refer to (1) in FIG12b, for example, the file “My Files” includes four folders belonging to the second-level directory, namely “Font Library”, “Industry Survey”, “Seaside Photos”, and “Design Trends”, while the folder “Industry Survey” includes two files belonging to the third-level directory, namely “Operation Notes” and “Ancient Town Trip”.

[0308] For example, when the user selects the check boxes corresponding to the two folders "Font Library" and "Industry Survey", the mobile phone responds to the operation, as shown in (2) in Figure 12b, and the two folders "Running Notes" and "Ancient Town Trip" under the "Font Library" folder and the "Industry Survey" folder will be selected. If the user then clicks on the control 10k-2, the mobile phone responds to the user's operation, saves the information of the folder selected by the user, and returns to the interface 10j. At the same time, the area corresponding to the "Select Folder" entry 10j-3 in the interface 10j displays the number of folders selected by the user, as shown in (3) in Figure 12b.

[0309] It is understandable that in actual applications, if the user wants to set the source of the file to all files, the user can directly select the check box corresponding to "all files" to select all files displayed in the interface 10k and the folders included in these folders.

[0310] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0311] Continuing with (3) in FIG. 12b , illustratively, when the user clicks on the “File Type” entry 10j-14, the mobile phone responds to the operation, as shown in (1) in FIG. 12c , and enters the “File Type” interface 10m. The interface m includes one or more controls, including but not limited to a control 10m-1 for exiting the interface 10m, a control 10m-2 for saving the user’s settings in the interface 10m, and a checkbox for selecting the file type of files that are subsequently automatically added to the desktop card 10a-1.

[0312] As shown in (1) in FIG. 12b , for example, the interface 10m provides file types such as picture type, video type, document type, audio type, application type, and compressed package type. In some implementations, if the user only selects a few of the file types, the user can directly operate the check boxes corresponding to the file types to be selected, as shown in (2) in FIG. 12c , to select the picture type and document type; in other implementations, if the user does not limit the file types of the files added to the desktop card 10a-1, the user can directly select all the file types provided in the interface m through the check box corresponding to "All Types" displayed in the interface 10m.

[0313] Accordingly, after selecting the file type, the user can click on the control 10m-2. In response to the click operation, as shown in (3) in Figure 12c, the mobile phone will save the information of the file type selected by the user and return to the interface 10j. At the same time, the area corresponding to the "File Type" entry 10j-4 in the interface 10j displays the file type selected by the user, such as "Pictures, Documents" shown in (3) in Figure 12c.

[0314] It is understandable that the above-mentioned image types include but are not limited to JPG, PNG, BMP, GIF, RAW, etc.; video types include but are not limited to MP4, AVI, MOV, RMVB, MKV, etc.; document types include but are not limited to DOC, PPT / PPTX, XLS, TXT, PDF, EPUB, etc.; audio types include but are not limited to MP3, WAV, M4A, FLAC, AAC, etc.; applications include but are not limited to system APPs, such as settings, messages, calls, etc., as well as third-party APPs, such as instant messaging APPs, etc.; compressed packages include but are not limited to ZIP, RAR, 7Z, etc.

[0315] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0316] As shown in (1) of FIG13a, for example, when the user selects the "Specify File" mode, the "Select Folder" entry 10j-13 and the "File Type" entry 10j-14 corresponding to the "Smart Recommendation" mode are canceled, and the "Select File" entry 10j-5 corresponding to the "Specify File" mode is displayed. Since this mode allows the user to directly specify the file to be added, there is no need to provide an entry for setting the file type.

[0317] Continuing with FIG13a (1), illustratively, when the user clicks on the "Select File" entry 10j-5, the mobile phone responds to the operation, as shown in FIG13a (2), and enters the "My Files" interface 10k. The interface 10k includes one or more controls, including but not limited to a control 10k-1 for exiting the interface 10k, a control 10k-2 for saving the user's settings on the interface 10k, and a check box for selecting each folder.

[0318] As shown in (2) of FIG. 13a , the interface 10k includes, for example, three folders belonging to the first-level directory: “My Files,” “My Phone,” and “Favorites.” These three folders can each contain several folders belonging to the second-level directory. Each folder in the second-level directory can contain several folders belonging to the third-level directory, or can directly contain several files. In this embodiment, the specified file comes from the folder “Industry Survey” in “My Files.”

[0319] Continuing to refer to (2) in FIG13a, for example, the file “My Files” includes four folders belonging to the second-level directory, namely “Font Library”, “Industry Survey”, “Seaside Photos”, and “Design Trends”, while the folder “Industry Survey” includes two files belonging to the third-level directory, namely “Operation Notes” and “Ancient Town Trip”.

[0320] Continuing to refer to (2) in FIG13a, for example, the “Running Notes” folder includes a file in DOC format named “Running Notes 1”, and the “Ancient Town Trip” folder includes a file in DOC format named “Ancient Town Documents”.

[0321] For example, when the user selects the check boxes corresponding to the two files "Running Notes 1" and "Trip to the Ancient Town", the mobile phone responds to the operation, as shown in (1) in Figure 13b, and the two files "Running Notes 1" and "Trip to the Ancient Town" will be selected. If the user then clicks on the control 10k-2, the mobile phone responds to the user's operation, saves the information of the files selected by the user, and returns to the interface 10j. At the same time, the area corresponding to the "Select File" entry 10j-5 in the interface 10j displays the number of files selected by the user, as shown in (2) in Figure 13b.

[0322] It is understandable that in actual application, if the user wants to add all files in all folders displayed in the interface 10m to the desktop card 10a-1, he can directly select the check box corresponding to "All Files" to select all files in the folders displayed in the interface 10k.

[0323] It should be noted that for all the above-mentioned selected scenarios, if the number of files under all folders displayed in interface 10k does not exceed the maximum number allowed to be added by desktop card 10-1, these files can be directly added to desktop card 10a-1. If the number exceeds the maximum number allowed to be added by desktop card 10-1, a prompt message may pop up in interface 10k shown in (1) in Figure 13b, such as "Desktop card 10a-1 supports adding up to 10 files, please reselect".

[0324] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0325] Therefore, by providing an entry for editing cards and providing "smart recommendation" and "specified file" methods for users to choose from, it can better meet the user's actual usage scenarios and usage habits and improve the user experience.

[0326] The following describes various implementation methods for deleting files in desktop cards provided in the embodiments of the present application in combination with Figures 12a, 14a and 14b.

[0327] For example, in some implementations, the files managed in the desktop card can be deleted, for example, by deleting the entire desktop card to delete all the files managed by the desktop card. The specific implementation method is shown in Figure 12a. Please see the above description for details and will not be repeated here.

[0328] For example, in other implementations, the deletion of files managed in the desktop card may be, for example, the individual deletion of one or more files. This deletion method is described below with reference to FIG. 14 a and FIG. 14 b .

[0329] As shown in (1) of FIG. 14a , in one implementation, when a user operates (such as long pressing) a file icon corresponding to a file to be deleted in a desktop card 10a-1, such as file 1.pptx, the mobile phone responds to the operation, as shown in (2) of FIG. 14a , and a control 10a-14 for deleting the file icon may appear in the area where the file icon corresponding to file 1.pptx is located.

[0330] Referring to (2) in Figure 14a, for example, if the user clicks on the control 10a-14, the mobile phone responds to the operation, as shown in (3) in Figure 14a, and deletes the file icon corresponding to the file 1.pptx from the desktop card 10a-1, and moves the positions of the remaining file icons in sequence. The desktop card 10a-1 after the remaining file icons are moved is shown in (3) in Figure 14a.

[0331] In addition, it is understandable that in actual applications, when the positions of the remaining file icons are moved, the positional relationship of the remaining file icons may also be adjusted according to recent usage, and this embodiment does not impose any limitation on this.

[0332] Continuing to refer to (2) in FIG. 14a, for example, if the user operates other areas in the desktop card 10a-1 (such as a double-click operation), the mobile phone responds to the operation, as shown in (1) in FIG. 14a, and cancels the control 10a-14.

[0333] For example, in another implementation, when a user operates (e.g., long-presses) a file icon corresponding to a file to be deleted in desktop card 10a-1, such as file 1.pptx, the mobile phone responds to the operation, as shown in (1) in FIG14b , and a control 10a-14 for deleting the corresponding file icon appears in the area where the file icon corresponding to each file managed in desktop card 10a-1 is located. In this way, the user can delete multiple files in batches with one operation, without having to perform a specific operation on the file icon corresponding to each file to display the corresponding control 10a-14.

[0334] Continuing to refer to (1) in Figure 14b, for example, if the user clicks the control 10a-14 in the file icon area corresponding to file 1.pptx, the mobile phone responds to the operation, as shown in (2) in Figure 14b, deletes the file icon corresponding to file 1.pptx from the desktop card 10a-1, and moves the positions of the remaining file icons in sequence. The desktop card 10a-1 after the remaining file icons are moved is shown in (2) in Figure 14b.

[0335] Continuing to refer to (1) in Figure 14b, for example, if the user wants to continue deleting other files, then the corresponding file icon area control 10a-14 can be operated to delete the corresponding file icon; if the user wants to end the deletion operation, then other areas in the desktop card 10a-1 can be operated (such as double-clicking), and the mobile phone responds to the operation behavior, as shown in (3) in Figure 14b, and cancels the control 10a-14.

[0336] It is understandable that since the file icon in the desktop card 10a-1 is bound to the shortcut of the file, deleting the file icon can delete the file managed by the desktop card 10a-1.

[0337] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0338] In addition, it should be noted that in actual applications, in order to avoid gesture conflicts, when deleting files managed in the desktop card 10a-1 according to the method shown in Figures 14a and 14b, the long press operation performed can be an operation performed in the hot zone at a specified position in the desktop card.

[0339] It is understood that the so-called hot zone can be understood as a transparent element that can be placed on an area, such as any area in the desktop card 101-1, and interactive operations can be added to the element. Specifically, in this embodiment, a control 10a-14 for triggering the display of a file deletion can be added to the element. That is, after the user performs an operation in the hot zone, the phone will respond to the operation and display the file deletion control 10a-14, thereby avoiding gesture conflicts and ensuring user experience.

[0340] From the description of the above embodiments, it can be seen that the file management method provided by this embodiment displays a desktop card for managing files on the desktop, and directly displays a shortcut entry to the file that meets the user's usage needs in the desktop card according to user needs, such as the file icon that establishes a shortcut to the file as mentioned above, so that the user can directly search in the desktop card and directly open the file he wants to view. The entire search process is convenient and simple, which greatly improves the user experience.

[0341] Furthermore, it should be understood that the above embodiment uses desktop cards for file management as an example. In actual applications, the above file management method can also be applied to other applications. For example, for desktop cards for managing camera applications, calendar applications, etc., the process of adding desktop cards, setting file paths for desktop cards, and using desktop card functions can be found in the detailed description of the above embodiment and will not be repeated here.

[0342] In addition, it is understood that, in order to implement the above functions, the electronic device includes hardware and / or software modules that perform the corresponding functions. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0343] In addition, it should be noted that the file management methods provided in the above embodiments implemented by electronic devices in actual application scenarios can also be performed by a chip system included in the electronic device, wherein the chip system may include a processor. The chip system can be coupled to a memory so that when the chip system is running, it calls a computer program stored in the memory to implement the steps performed by the above electronic device. The processor in the chip system can be an application processor or a processor other than an application processor.

[0344] In addition, an embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the file management method in the above-mentioned embodiment.

[0345] In addition, an embodiment of the present application further provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes the above-mentioned related steps to implement the file management method in the above-mentioned embodiment.

[0346] In addition, an embodiment of the present application also provides a chip (which may also be a component or module), which may include one or more processing circuits and one or more transceiver pins; wherein the transceiver pins and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the above-mentioned related method steps to implement the file management method in the above-mentioned embodiment to control the receiving pin to receive signals, so as to control the sending pin to send signals.

[0347] In addition, it can be seen from the above description that the electronic device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0348] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A file management method, characterized in that: Display the first interface; The first interface includes a first card, the first card includes M file icons, each of the M file icons corresponds to a file in the electronic device, and M is a positive integer.

2. The method according to claim 1, characterized in that The first interface is a desktop; The displaying of the first interface includes: In response to a first operation, displaying a desktop card setting entry on the desktop; In response to a second operation on the desktop card setting entry, displaying a desktop card setting interface, the setting interface including a desktop card entry for managing files; In response to a third operation on the desktop card entry for managing files, displaying a card format selection interface; In response to a fourth operation on the card form selection interface, adding the first card on the desktop according to the selected card form; In response to the fifth operation, a file is added to the first card, and a file icon corresponding to the file is displayed in the first card.

3. The method according to claim 2, characterized in that In response to the fifth operation, adding a file to the first card includes: On the file preview interface, a file adding floating ball is displayed, and the file adding floating ball is in a retracted state; In response to a sixth operation on the file adding floating ball, a first navigation bar of the file adding floating ball is displayed, wherein the first navigation bar displays an adding entry for adding the file displayed on the file preview interface to the first card; In response to the seventh operation acting on the adding entry, the file displayed in the file preview interface is added to the first card, and the first navigation bar is retracted, and the file adding floating ball is in a retracted state.

4. The method according to claim 3, characterized in that Before adding the file displayed in the file preview interface to the first card, the method further includes: Displaying a first prompt window, wherein the first prompt window includes a first option and a second option; When an eighth operation acting on the first option is received, in response to the eighth operation, the file in the file preview interface is added to the first card, and the first prompt window is canceled; When a ninth operation acting on the second option is received, in response to the ninth operation, a new card is created, the files in the file preview interface are added to the newly created card, and the first prompt window is canceled.

5. The method according to claim 3, characterized in that The method further comprises: When the set time arrives and the seventh operation is not received, the first navigation bar is retracted, and the file adding floating ball is in a retracted state; or, When a tenth operation acting on the file preview interface is received within the set time, the first navigation bar is retracted, and the file adding floating ball is in a retracted state.

6. The method according to claim 2, characterized in that In response to the fifth operation, adding a file to the first card includes: In response to a tenth operation on the file management application, a second interface is displayed, wherein the second interface is a page opened step by step according to the storage path, and the file to be added is displayed in the second interface; In response to an eleventh operation performed on the second interface, displaying a second navigation bar, wherein the second navigation bar includes a third option; In response to a twelfth operation acting on the third option, displaying a first menu bar, wherein the first menu bar includes a fourth option; After the file to be added is selected, in response to a thirteenth operation acting on the fourth option, the file to be added is added to the first card.

7. The method according to claim 2, characterized in that The first card also includes a file adding entry; In response to the fifth operation, adding a file to the first card includes: In response to a fourteenth operation on the file adding entry, a third interface is displayed, wherein the third interface displays the file to be added and the fifth option; After the file to be added is selected, in response to a fifteenth operation acting on the fifth option, the file to be added is added to the first card.

8. The method according to claim 1, characterized in that The first interface is a desktop, a second card is displayed on the desktop, and the second card is a desktop card for managing files; The displaying of the first interface includes: In response to a sixteenth operation on the second card, a second menu bar is displayed, wherein the second menu bar includes: more file management card options; In response to a seventeenth operation on the more file management card option, displaying a card format selection interface; In response to an eighteenth operation on the card form selection interface, adding the first card on the desktop according to the selected card form; In response to the nineteenth operation, a file is added to the first card, and a file icon corresponding to the file is displayed in the first card.

9. The method according to claim 8, characterized in that The usage scenario of the files managed in the first card is different from the usage scenario of the files managed in the second card.

10. The method according to claim 8, characterized in that The usage location of the files managed in the first card is different from the usage location of the files managed in the second card.

11. The method according to claim 1, wherein The method further comprises: In response to a twentieth operation on the first card, displaying a third menu bar, the third menu bar including a remove option and an edit option; In response to a twenty-first operation acting on the remove option, the first card is removed from the desktop.

12. The method according to claim 11, characterized in that The method further comprises: In response to a twenty-second operation on the editing option, displaying a first file source option and a second file source option; When an operation is received on the first file source option, M files are recommended from the folder selected by the user as the M files managed by the first card, or M files are recommended from N folders recommended by the system as the M files managed by the first card; When an operation on the second file source option is received, the M files selected by the user are used as the M files managed by the first card.

13. The method according to claim 1, wherein The first card has a fixed card size.

14. The method according to claim 1, wherein The card size of the first card is variable, and the maximum size of the first card is 4×2.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: receiving a twenty-third operation on any file icon in the first card; In response to the twenty-third operation, the first interface is switched to the fourth interface, where the fourth interface is a preview interface of the file corresponding to the clicked file icon.

16. The method according to any one of claims 1 to 14, characterized in that The method further comprises: When the electronic device is in the lock screen interface and the screen is black and in standby mode, in response to an operation of lighting up the lock screen interface, the lock screen interface is lit and the first card is displayed in the lock screen interface.

17. An electronic device, characterized in that: The electronic device includes: a memory and a processor, the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the electronic device executes the file management method according to any one of claims 1 to 16.

18. A computer-readable storage medium, characterized in that The invention comprises a computer program, which, when executed on an electronic device, enables the electronic device to execute the file management method according to any one of claims 1 to 16.

Images