Schedule management method and device

Abstract

This application provides a schedule management method and device that allows users to mark important schedules. Important schedules are displayed before ordinary schedules, allowing users to more intuitively see important schedules. Furthermore, for important schedules, the interface displaying the schedule will expand to display the important schedule information, that is, the interface displays more important schedule information than other schedules, allowing users to intuitively obtain more information about important schedules, thereby improving the user experience.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a schedule management method and device. Background Art

[0002] Schedule management applications on electronic devices allow users to create multiple schedules or access them from other applications. Different schedules have varying degrees of importance to users. For example, meetings involving important content are generally more important than regular meetings. Current schedule management applications fail to highlight important schedules, which can cause users to miss important ones. Summary of the Invention

[0003] In view of this, the present application provides a schedule management method and device to solve at least part of the above problems. The disclosed technical solutions are as follows:

[0004] In a first aspect, the present application provides a schedule management method, applied to an electronic device, comprising: displaying a first interface, the first interface including a first schedule card, the first schedule card including schedule information and a schedule priority, the schedule priority being none; in response to selecting an operation that sets the schedule priority to important, displaying a second interface, the second interface including a second schedule card, the schedule priority in the second schedule card being important, and the second schedule card containing more schedule information than the first schedule card. This solution allows users to manually mark important schedules, with the interface displaying more information about important schedules than other schedules, thereby facilitating users to intuitively obtain more information about important schedules and improving the user experience.

[0005] In a possible implementation of the first aspect, the schedule information includes a schedule title; the second schedule card also includes an important identifier, and the important identifier is located before the schedule title. In this way, the user can recognize that the schedule is an important schedule after seeing the important identifier in the schedule display area.

[0006] In one possible implementation of the first aspect, schedule priorities include None, Important, and Ignore. This solution incorporates Ignore into the priority level, and each interface displaying the schedule includes a priority setting item, making it easy for users to find the Ignore entry and facilitate user operation.

[0007] In a possible implementation of the first aspect, in response to the operation of selecting the schedule priority as important, a second interface is displayed, including: in response to the operation of clicking the schedule priority on the first schedule card, a priority setting option pop-up window is displayed on the first interface, and the priority setting option pop-up window includes a no level option, an important level option and an ignore option; in response to the operation of selecting the important level option on the priority setting option pop-up window, the second interface is displayed.

[0008] In a possible implementation of the first aspect, before displaying the first interface, the method further includes: displaying a third interface, the third interface including a first button for creating a new schedule; in response to an operation on the first button, displaying the first interface, the first interface also including a save button; in response to an operation selecting the schedule priority as important, displaying a second interface, including: in response to an operation on the schedule priority on the first interface, displaying a priority setting option pop-up window on the first interface, the priority setting option pop-up window including a no level option, an important level option, and an ignore option; in response to an operation selecting the important level option on the priority setting option pop-up window, displaying the first interface, and updating the schedule priority in the first interface to important; in response to an operation on the save button, displaying the second interface. It can be seen that the user can mark important schedules on the new schedule page, so that the user can mark important schedules when creating a new schedule.

[0009] In one possible implementation of the first aspect, the schedule information includes participants, and the method further includes: upon detecting that the schedule priority is important, obtaining the participants from all schedules containing the participant; selecting a preset number of participants from all schedule participants who meet preset conditions as recommended participants, the preset conditions including that the frequency of participation in important schedules is greater than a preset threshold; and generating a recommender list, the recommender list including the recommended participants. As can be seen, upon detecting an important schedule, participants meeting certain conditions can be selected from all schedule participants, combined with the participants in the important schedule, and recommended to the user as important participants. This allows the user to directly add important participants from the recommender list, reducing user operations and increasing the speed of adding important participants.

[0010] In one possible implementation of the first aspect, after generating the recommendation list, the method further includes: upon detecting a new important event, updating the recommended participants in the recommender list based on the participants of the new important event. This solution allows the recommender list to be updated based on updates to important events, so that the recommended participants in the recommender list are always important participants that the user is interested in.

[0011] In a possible implementation of the first aspect, the method further includes: displaying a first important participant interface, the first important participant interface including a recommender list, the recommender list including at least one participant item, the participant item including participant information and an add button; in response to an operation on the add button, displaying a second important participant interface, the second important participant interface including an important participant list, the important participant list including important participant items, each important participant item including an added participant and a remove button.

[0012] In one possible implementation of the first aspect, the first important participant interface further includes an "Add Other Participants" button. After displaying the first important participant interface, the method further includes: in response to an operation on the "Add Other Participants" button, displaying a first participant selection interface, the first participant selection interface including a list of first participants for all schedules; and in response to an operation on selecting any participant in the first participant list, displaying a third important participant interface, the third important participant interface including a list of important participants, the list of important participants including the selected participant. This allows users to add other participants as important participants in addition to those in the recommended participant list, thereby satisfying user needs.

[0013] In one possible implementation of the first aspect, the first schedule card further includes a participant setting item; after displaying the first interface, the method further includes: in response to an operation on the participant setting item, displaying a schedule participant interface, the schedule participant interface including a second participant list and an edit important participant button, the second participant list including all participants in the schedule included in the first schedule card; in response to an operation on the important participant button, displaying a second participant selection interface, the second participant selection interface including a participant selection list; in response to an operation on selecting a participant in the participant selection list, marking the selected important participant as an important participant and updating the important participant list. In this way, a user can directly set a participant as an important participant among the participants of a schedule, thereby meeting the user's needs.

[0014] In one possible implementation of the first aspect, after adding important participants, the method further includes: upon detecting that an important participant is among the participants of a non-important schedule, automatically marking the non-important schedule as an important schedule, where the non-important schedule has a priority of none. In this way, non-important schedules that include important participants can be automatically marked as important, eliminating the need for manual marking by the user, reducing user effort and improving the user experience.

[0015] In one possible implementation of the first aspect, after displaying the second interface, the method further includes: displaying a settings pop-up window, the settings pop-up window including displaying only important first setting items; and in response to operating the first setting items, displaying only important schedules in each interface displaying schedules. Thus, when there are many schedules, filtering and displaying important schedules can help users focus on important schedules and avoid missing important things.

[0016] In a possible implementation of the first aspect, after displaying the first interface, the method further includes: displaying a fourth interface in response to an operation on the first schedule card, the fourth interface including the schedule priority of the schedule in the first schedule card, and the schedule priority is none; after determining that the first prompt pop-up window has not been displayed, displaying the first prompt pop-up window on the fourth interface, the first prompt pop-up window including prompt information prompting the user to mark important schedules.

[0017] In a possible implementation of the first aspect, displaying a fourth interface in response to an operation on a first schedule card includes: displaying a fourth interface in response to a click operation on the first schedule card, the fourth interface displaying schedule details information of the schedule in the first schedule card, the schedule details information including a title, a start and end time, and a schedule priority, where the schedule priority is none; or, the first schedule card further includes a second button; displaying a fourth interface in response to an operation on the first schedule card includes: displaying a fourth interface in response to a click operation on the second button, the fourth interface including a third schedule card, the schedule displayed in the third schedule card being the same as the schedule displayed in the first schedule card, the schedule information displayed in the third schedule card being more than the schedule information displayed in the first schedule card, and the schedule priority in the third schedule card being none; or, displaying a fourth interface in response to an operation on the first schedule card includes: displaying a fourth interface in response to a long press operation on the first schedule card, the fourth interface including a fourth schedule card, the schedule displayed in the fourth schedule card being the same as the schedule displayed in the first schedule card, and the fourth schedule card being displayed in a pop-up window.

[0018] Secondly, the present application also provides another schedule management method and a desktop card setting item, wherein the schedule priority is set to important; in response to an operation on the desktop card setting item, a first desktop card for a first schedule is displayed on the desktop, and the first desktop card includes the number of days between the current date and the execution date of the first schedule. As can be seen, this solution can add a desktop card for an important schedule to the desktop, and the desktop card can display the number of days until the execution date of the important schedule, allowing the user to see the remaining deadline of the important schedule at a glance, further reminding the user to execute the important schedule or make adequate preparations for the important schedule.

[0019] In one possible implementation of the second aspect, before displaying the first interface, the method further includes: displaying a second interface, the second interface including a Create Schedule button; and in response to clicking the Create Schedule button, displaying the first interface. This solution allows the user to add a desktop card for a new schedule as soon as the user creates it, thus avoiding repeated user operations.

[0020] In a possible implementation of the second aspect, after displaying the first interface, the method further includes: in response to an operation on the desktop card setting item, and after detecting that the desktop card corresponding to the first schedule has been added, displaying a first pop-up window on the first interface, the first pop-up window including a cancel button, an confirm button, and information prompting the user whether to add the desktop card again; in response to the operation on the confirm button, adding a second desktop card for the first schedule, the second desktop card having the same content as the first desktop card. It can be seen that this solution supports users to repeatedly add desktop cards for a schedule, for example, adding desktop cards for the same schedule on different desktop pages, so that users can see the schedule on each desktop page, thereby improving the presentation rate of desktop cards and making it easier for users to pay attention to the schedule.

[0021] In a possible implementation of the second aspect, the method also includes: displaying a third interface, the third interface including a blank desktop card and a first button, the blank desktop card including an add schedule button; in response to the operation of the first button, displaying a blank desktop card on the desktop; in response to the operation of the add schedule button, displaying a schedule selection interface, the schedule selection interface including selectable schedules; in response to the operation of selecting a schedule in the schedule selection interface, displaying the desktop, the desktop including a third desktop card, the third desktop card including information of the selected schedule, and the number of days between the current date and the execution date of the selected schedule.

[0022] In a third aspect, the present application also provides an electronic device, which includes: one or more processors, a memory, and a touch screen; the memory is used to store program code; and the processor is used to run the program code, so that the electronic device implements the schedule management method of any one of the first and second aspects.

[0023] In a fourth aspect, the present application further provides a computer-readable storage medium having instructions stored thereon, which, when executed on an electronic device, enables the electronic device to implement the schedule management method of any one of the first and second aspects.

[0024] In a fifth aspect, the present application further provides a computer program product having an executable program stored thereon. When the computer program product is run on an electronic device, the schedule management method of any one of the first and second aspects is implemented in the electronic device.

[0025] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be realized in any single embodiment. On the contrary, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution or beneficial effect is included in at least one embodiment. Therefore, the description of a technical feature, technical solution or beneficial effect in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in the present embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that the embodiment can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects can also be identified in specific embodiments that do not embody all embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0027] Figure 1 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0028] Figure 2-1 This is a schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application;

[0029] Figure 2-2 This is a schematic diagram of another new schedule interface provided in an embodiment of the present application;

[0030] Figure 3 This is a schematic diagram of an interface of a schedule details view provided in an embodiment of the present application;

[0031] Figure 4 This is another interface diagram for manually marking important schedules provided in an embodiment of the present application;

[0032] Figure 5 This is another schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application;

[0033] Figure 6 This is a schematic diagram of another interface for manually marking important schedules provided in an embodiment of the present application;

[0034] Figure 7 This is a schematic diagram of an interface for a new function guide on important schedules provided by an embodiment of the present application;

[0035] Figure 8 This is a schematic diagram of a rule for determining important participants provided in an embodiment of the present application.

[0036] Figure 9 This is a schematic diagram of an interface for guiding new functions for important participants provided in an embodiment of the present application;

[0037] Figure 10 This is a schematic diagram of an interface for adding important participants provided in an embodiment of the present application;

[0038] Figure 11 This is a schematic diagram of an important participant interface provided by an embodiment of the present application;

[0039] Figure 12 This is another interface diagram for adding important participants provided in an embodiment of the present application;

[0040] Figure 13 This is another interface diagram for adding important participants provided in an embodiment of the present application;

[0041] Figure 14 This is a schematic diagram of automatically marking important schedules provided by an embodiment of the present application;

[0042] Figure 15 This is a schematic diagram of an interface for removing important participants provided in an embodiment of the present application;

[0043] Figure 16 is a schematic diagram of another important participant interface provided in an embodiment of the present application;

[0044] Figure 17 This is a schematic diagram of another important participant interface provided in an embodiment of the present application;

[0045] Figure 18 This is a schematic diagram of an interface for screening important schedules provided in an embodiment of the present application;

[0046] Figure 19 This is a schematic diagram of another interface for screening important schedules provided in an embodiment of the present application;

[0047] Figure 20 This is another schematic diagram of an interface for screening important schedules provided in an embodiment of the present application;

[0048] Figure 21 This is a schematic diagram of an interface for adding a schedule card to a desktop provided by an embodiment of the present application;

[0049] Figure 22 This is a schematic diagram of the display content of a schedule card provided in an embodiment of the present application;

[0050] Figure 23This is a schematic diagram of a schedule card format provided in an embodiment of the present application;

[0051] Figure 24 This is another interface diagram for adding a schedule card to the desktop provided by an embodiment of the present application;

[0052] Figure 25 This is another schematic diagram of an interface for adding a schedule card to the desktop provided by an embodiment of the present application;

[0053] Figure 26 This is a schematic diagram of an interface for selecting a schedule provided in an embodiment of the present application;

[0054] Figure 27 This is a schematic diagram of an interface for schedule card operation provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The terms "first", "second" and "third" in the specification, claims and drawings of this application are used to distinguish different objects rather than to limit a specific order.

[0056] 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.

[0057] Users can create multiple schedules with different time periods on the same date, for example, 8:00-9:00: Schedule 1, 10:00-11:00: Schedule 2, and 1:00-14:30: Schedule 3. Related art typically sorts schedules by their start time, limiting the number of schedules that can be displayed within the display interface. This schedule display method can cause important schedules to be placed at the back, requiring the user to manually scroll up to see important schedule information. Furthermore, the information displayed for different schedules is essentially the same, failing to highlight key information. For example, both the start and end times are displayed for a meeting schedule and a credit card repayment schedule. While a meeting schedule is more important to the user than a credit card repayment, the displayed schedule information fails to highlight its importance and does not provide more information about the meeting schedule. In other words, the displayed information and reminders for important and ordinary schedules are the same, leaving the user to subjectively determine which schedules are important, which can lead to missing important schedules.

[0058] To address the aforementioned technical issues, the inventors of this application have provided a schedule management method that allows users to mark important schedules. Important schedules are displayed before regular schedules, allowing users to more intuitively identify them. Furthermore, the interface displaying important schedules expands to display information about them, meaning that more information about important schedules is displayed on the interface than other schedules. This allows users to intuitively access more information about important schedules, improving the user experience.

[0059] Electronic devices to which the schedule management method provided in the embodiments of the present application can be applied may include mobile phones, tablet computers, desktop computers, laptop computers, notebook computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, smart watches, augmented reality (AR) devices, virtual reality (VR) devices, etc. It should be understood that the terminal devices involved in the embodiments of the present application only need to have the function of setting a schedule, and the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal devices.

[0060] Figure 1 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 1 As shown, the electronic device may include a processor 1 , a memory 2 , a display screen 3 , a touch sensor 4 , and a power management module 5 .

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

[0062] The processor 1 may include one or more processing units, and different processing units may be independent devices or integrated into one or more processors. For example, in an embodiment of the present application, the processor 1 may manage a schedule.

[0063] The memory 2 is used to store computer executable program codes and data, wherein the program codes include instructions. The processor 1 manages the schedule by executing the program instructions stored in the memory 2.

[0064] The display screen 3 is used to display images, videos, etc. The display screen can also display a series of graphical user interfaces (GUIs), which are the main screen of the electronic device. Generally speaking, the size of the display screen 3 of the electronic device is fixed, and only a limited number of controls can be displayed on the display screen 3 of the electronic device. A control is a GUI element, which is a software component included in an application. It controls all data processed by the application and the interactive operations on this data. Users can interact with the control through direct manipulation to read or edit relevant information of the application. Generally speaking, controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc.

[0065] Touch sensor 4, also known as a "touch control device," can be disposed on display screen 3. Touch sensor 4 and display screen 3 form a touch screen, also known as a "touch screen." Touch sensor 4 is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operations can be provided via display screen 3. In other embodiments, touch sensor 4 can also be disposed on the surface of the electronic device, in a location different from that of display screen 3.

[0066] The following describes an embodiment of the present application by taking a mobile phone as an example of an electronic device. The mobile phone has a function of setting a schedule, which can support a user to set a schedule reminder on a calendar application.

[0067] In addition, schedule management applications may include calendar applications and to-do list applications, and the embodiments of the present application may be applied to any application that can manage schedules. It should be understood that schedule management herein may include all schedule-related operations such as creating a new schedule, modifying the content of a schedule, and deleting a schedule, and the scope of schedule management is not limited in this application.

[0068] In an embodiment of the present application, a user can manually mark a new schedule as an important schedule, or manually mark an existing schedule as an important schedule.

[0069] The following is combined with Figure 2-1 Describes the process for users to manually mark important events when creating a new event.

[0070] Figure 2-1This is a schematic diagram of an interface for manually marking important schedules provided in an embodiment of the present application. This embodiment is explained by taking the example of creating a new schedule in a calendar application. It should be understood that new schedules can also be created in other schedule management applications, and this application does not limit this.

[0071] When the phone detects that the user clicks the calendar application icon, it can display Figure 2-1 The interface 10 shown in a is a month view interface of the calendar. The month view is used to display all dates of the entire month. In this example, all dates of the entire September are displayed. In the month view, the current date is highlighted by default. Of course, the interface can also highlight other dates selected by the user, such as the user can click on the digital icon indicating other dates to select the date. In one example, a specified date is highlighted by highlighting the mark, such as highlighting the mark as a circle 11 whose diameter is larger than the diameter of the digital icon. Figure 2-1 As shown in a, in this example, the current date is September 10, 2022.

[0072] Users can click on Figure 2-1 The icon 12 shown in a creates a new schedule for the currently highlighted date. In this example, the user clicks icon 12 to create a schedule for September 10, 2022. Of course, the user can also click Figure 2-1 Select another date by clicking another number icon shown in a, and further click icon 12 to create a schedule for the other date.

[0073] In one example, after the user clicks icon 12, the Figure 2-1 The new schedule interface shown in b is for the user to fill in the detailed information of the new schedule. Figure 2-1 As shown in FIG. 2 b , the new schedule interface includes a priority setting column 24 , a title setting column 21 , a location setting column 22 , a start and end time setting column 23 , and a reminder setting column 25 .

[0074] The priority setting column 24 includes a priority setting item 241. The user clicks the priority setting item 241 to set the priority of the newly created schedule and enters Figure 2-1 The interface 30 shown in c is as follows: Figure 2-1 As shown in Figure c, the interface displays a priority setting card 31, which displays all configurable levels, such as "Important," "Ignore," and "None." "Important" indicates that the schedule is important, i.e., the user's primary focus. "Ignore" indicates that the schedule can be ignored and the user does not need to pay attention to it. "None" indicates that the schedule does not need to be paid attention to but cannot be ignored.

[0075] For example, in one example, Figure 2-1 The interface 30 shown in c Figure 2-1b) adds a grayscale layer to the interface shown in FIG. 3, and further displays the priority setting card 31 on the upper layer of the grayscale layer. In this way, the priority setting card 31 can be highlighted, making the priority setting card 31 more eye-catching and making it easier for users to pay attention to the priority setting card 31. Of course, in other embodiments, it is also possible to directly Figure 2-1 The priority setting card 31 is directly displayed on the interface shown in b.

[0076] The user can select the selection button after any level to select that level. In one example, the selection button style of the priority level is a radio button, that is, the user can click the button in the unselected state to make it selected, and at the same time, the button that was originally in the selected state becomes unselected. For example, Figure 2-1 The selection button corresponding to the "Important" level in c is currently unselected. After the user clicks the button, it becomes selected. At the same time, the selection button corresponding to the "None" level changes from selected to unselected.

[0077] In addition, the priority setting card 31 may also be located at other locations on the interface 30. The embodiment of the present application does not limit the size, style, display position of the priority setting card, or the style of the selection button in the priority setting card.

[0078] In another exemplary embodiment, Figure 2-2 As shown, it shows another interface diagram of a new schedule interface provided by an embodiment of the present application. Figure 2-1 The difference between the new schedule interface shown in b is that Figure 2-2 The new schedule interface shown further includes a participant card 26 , which may include an inviter option 261 and a participant option 262 .

[0079] The user adds inviters to the schedule by operating the inviter option 261 . For example, when the schedule is an online meeting schedule, the user adds the meeting inviters through the inviter option.

[0080] The user can add other participants of the schedule by operating the participant option 262. In one example, after the user adds an inviter, the participant option can include the inviter by default.

[0081] In addition, the new schedule interface of this example may also include a meeting link bar 27. In one possible implementation, the meeting link bar may be reused with the location setting bar. For example, the user may click the location setting bar to paste the meeting link, or may enter the location of the schedule.

[0082] User in Figure 2-1 After selecting the "Important" level in the interface shown in c, jump to Figure 2-1 The interface shown in d is as follows Figure 2-1 As shown in d, the priority setting item 241 in the interface shows the "important" level. After the user fills in the other information in the new schedule interface, clicks the completion icon 40 to save the new schedule and jump to Figure 2-1 The month view interface 50 is shown in FIG.

[0083] Users can swipe up Figure 2-1 The area 13 showing the date in the month view interface shown in FIG. 1 is folded, that is, the date display area is formed by Figure 2-1 The 13 shown in a becomes as follows Figure 2-1 In the area 51 shown in FIG. 8 , the date display area 51 only displays the row containing the currently highlighted date, thereby increasing the area of ​​the schedule display area 52 below the date display area.

[0084] like Figure 2-1 As shown in FIGe , the schedule display area 52 is used to display all schedules that need to be reminded to the user under the currently highlighted date (September 10, 2022 in this example), including holidays, solar terms and other schedules. In this example, the display position of the holiday schedule is at the top of the schedule display area 52, that is, the display position of the holiday schedule is before other schedules. In other embodiments, the display position of the holiday schedule can be at the bottom of the schedule display area 52, that is, the display position of other schedules is before the holiday schedule. It should be understood that when the number of schedules under this date is large, they cannot all be displayed in the schedule display area 52, and the schedule display area 52 that is not displayed can be displayed by sliding the schedule display area 52 upward.

[0085] In the embodiment of the present application, for important schedules, the schedule information is expanded and displayed in the schedule display area 52 so that the user can directly obtain more information about the schedule. For non-important schedules, the schedule display is folded to save the display area of ​​the schedule display area. In this example, Figure 2-1 As shown in FIG. 5 , the important schedule of “design solution seminar” is expanded in card 56, while the non-important schedule (or ordinary schedule) of “train travel” is folded in card 57.

[0086] like Figure 2-1 As shown in FIG. 5 , the important schedule displayed by expanding the card 56 is a meeting schedule. The expanded schedule information may include a schedule title 53 , the schedule start and end time “8:00 am to 9:30 am”, the meeting inviter, participants, account, and priority 55 .

[0087] In one possible implementation, the title of an important schedule also includes an important identifier to indicate the importance of the schedule. In this example, the important identifier is "!". Of course, in other embodiments, the important identifier can also be other symbols, and this application does not limit this. Optionally, for online meetings, the expanded schedule information can also include a "Join Meeting" link button.

[0088] It can be seen that the user can view the important information of the schedule at a glance without performing any operation on the expanded card, thereby improving the efficiency of the user in obtaining detailed information of important schedules.

[0089] In addition, a folding button 54 may be included next to the schedule title in the card 56. The user can click the folding button 54 to change the schedule from an expanded display state to a folded display state. It is understood that in the folded display state, only very important information such as the schedule title, start and end time, etc. may be displayed. Figure 2-1 As shown in FIG. 5 , card 57 is in a collapsed state, displaying the schedule title, start and end times, and location, as well as an expand button 58. The user can click expand button 58 to expand the schedule from the collapsed state, thereby displaying more information about the "train trip" schedule, such as the seat number.

[0090] For important schedules, the schedule details are expanded by default in each scene. For example, Figure 2-1 In the schedule view interface 60 shown in FIG. 5 , the schedule display area 61 displays information about three schedules from top to bottom. The design proposal discussion is an important schedule, and its details are displayed expanded by default. The train trip and hotel check-in schedules are non-important schedules, and their information is displayed collapsed.

[0091] In one possible implementation, you can click Figure 2-1 The “Schedule” button 14 shown in a enters the schedule view interface 60 .

[0092] like Figure 2-1 As shown in FIG. 5 , “Ignore” is included in the priority card 31 as a priority of the schedule. That is, in this embodiment of the present application, “Ignore” is merged from more options in the schedule details interface to the priority of the schedule.

[0093] When the user clicks Figure 3 After the control 611 in the schedule details interface 610 shown in a, jump to Figure 3 The interface shown in b, and Figure 3The interface shown in b shows more tabs 612 on the schedule details interface 610, including share and delete options, that is, the more tabs 612 in the embodiment of the present application do not include the "Ignore" option. It should be noted that the user clicks Figure 2-1 After selecting the schedule titled "Design Solution Seminar" in e or f, enter the schedule details interface 610. It can be seen that after merging "Ignore" into the priority, the user can directly Figure 2-1 The priority setting item displayed on the interface shown in e or f sets the schedule to the "Ignore" level, shortening the user's path to the "Ignore" function, simplifying the user's operation, and improving the user experience.

[0094] Figure 2-1 The process shown here is for manually marking an event as important when creating a new event. You can also manually mark an existing event as important. For example, an existing event can be one that has already been created and has no priority assigned, or one that has been imported from another application.

[0095] Figure 4 This is another interface diagram of the process of marking important schedules provided by an embodiment of the present application. This embodiment takes the schedule information displayed in the monthly view interface of the calendar as an example to illustrate the process of manually marking an existing schedule as an important schedule.

[0096] like Figure 4 As shown in a, the current priority of the "Design Scheme Seminar" schedule in the expanded display state in the calendar month view interface 100 is "none", and the user can click button 101 (such as a drop-down menu button) to jump to Figure 4 The interface shown in b includes a priority menu 102. In this example, the priority menu 102 includes three levels: "Important", "Ignore", and "None". A grayscale layer is added above the row where the current priority (or selected level) is located, thereby highlighting the current level (or selected level) of the schedule. Figure 4 As shown in b, the current priority is "None" where the line is grayed out. The user can select the non-highlighted level in the priority menu 102. In this embodiment, the user can select the "Important" level to manually mark the schedule as important and jump to Figure 4 The interface shown in c.

[0097] contrast Figure 4 As can be seen from the interfaces shown in c and a, after marking the schedule of "Design Plan Seminar" as an important schedule, the priority setting item 104 of the schedule displays the "Important" level, and the title 105 of the schedule also includes an important identifier "!".

[0098] The embodiment of the present application also provides an interface diagram for manually marking an existing schedule as an important schedule in other scenarios. Figure 5 A schematic diagram of the interface for marking an event as important on the event details page is shown.

[0099] In one possible implementation, the user clicks Figure 2-1 The schedule card 56 in the e can jump to the following Figure 5 The schedule details interface 200 shown in a shows that the priority setting item 201 in the interface shows that the current priority is "none". The user can select other priorities by clicking button 202. After the user clicks button 202, the page will be redirected to Figure 5 The interface shown in b adds a grayscale layer on the upper layer of the schedule details interface 200, and further displays the priority setting card 203 on the upper layer of the grayscale layer. In this way, the priority setting card 203 can be made more eye-catching. Figure 2-1 The priority setting card 31 in the interface shown in c is the same and will not be described here. In this embodiment, the user clicks the button 204 corresponding to the "important" level in the priority setting card 203 to jump to Figure 5 In the schedule details interface shown in FIG. 3 , the priority item 205 in the interface shows that the current level is “important”, and the schedule title 206 includes an important identifier “!”.

[0100] See also Figure 6 , shows another interface schematic diagram for manually marking important schedules provided in an embodiment of the present application. This embodiment uses the schedule shortcut operation interface as an example to illustrate the process of manually marking important schedules.

[0101] In one possible implementation, the user can long press Figure 6 Schedule display card 301 in a enter Figure 6 The interface shown in b shows a pop-up window 302, which is used to display schedule information, such as schedule title, start and end time, priority options, etc. The priority options include the current level of the schedule and button 303. After the user clicks button 303, the user jumps to Figure 6 The interface shown in c also includes a priority menu 304 on the upper layer of the pop-up window 302. The user clicks the "Important" option in the priority menu 304 to jump to Figure 6 In the interface shown in d, the priority item 306 of the schedule displayed in the pop-up window 302 of the interface is "Important", and the schedule title 305 includes an important identifier "!".

[0102] The priority menu 304 in this embodiment is Figure 4 The priority menu 102 is the same as that shown in b, and will not be repeated here.

[0103] In addition, if Figure 6 In the interface shown in b, c, and d, the pop-up window 302 also includes a card 307 below, and the card 307 includes a "Share" and a "Delete" button. When the user clicks the "Share" button 308, it jumps to Figure 6 The sharing preview interface 401 shown in FIG. 4 includes a share button 403. Further, the user can forward the schedule information to others by clicking the share button 403. In addition, if the user clicks the "delete" button in the card 307, the schedule information is deleted from the calendar application.

[0104] When the user has not used the important schedule setting function, the schedule management application will prompt the user to set the schedules that are important to the user as important schedules. Figure 7 A schematic diagram of an interface for guiding a new function of setting important schedules provided in an embodiment of the present application is shown.

[0105] For example, Figure 7 As shown in a, the month view interface includes a card 70, which is in a folded display state, that is, only part of the schedule information is displayed, such as the title, start and end time and location.

[0106] In one scenario, if the user clicks the expand button 701 in the card 70, the page will be redirected to Figure 7 In the interface shown in b, card 70 is in an expanded state. In this state, a prompt pop-up window 72 may be displayed to guide the user to manually mark an event as important. In one example, the text in prompt pop-up window 72 may include "Mark important events to view more event information." In one example, prompt pop-up window 72 may be located above interface 90. In addition, when the user clicks anywhere on the interface except prompt pop-up window 72, prompt pop-up window 72 disappears.

[0107] In this example, the prompt pop-up window 72 is located above the priority item 73 , so that the user can intuitively know that the important schedule is marked by operating the priority item 73 .

[0108] In another scenario, if the user long presses Figure 7 Card 70 in a, jump to Figure 7 The quick operation interface 80 shown in c includes a schedule card 81. The schedule card 81 includes a prompt pop-up window 83 located above the priority item 82. The prompt pop-up window 83 is used to display a function to guide the user to manually mark important schedules.

[0109] In another scenario, if the user clicks (clicks) Figure 7 Card 70 in a, jump to Figure 7The schedule details interface 90 shown in d includes a card 91, which is used to display priority setting items. A prompt pop-up window 92 is displayed above the card 91. In addition, the prompt pop-up window 92 can be located in the upper layer of the interface 90.

[0110] Figure 7 Figures b, c, and d respectively show schematic diagrams of interfaces for displaying new function prompt pop-up windows in different scenarios. The functions of the prompt pop-up windows in different scenarios are the same, namely, guiding users to manually mark important schedules. The position, size, style, and displayed content of the prompt pop-up window can be adjusted according to different display scenarios, and this application does not limit this.

[0111] In addition, in a possible implementation, the above prompt pop-up window can be displayed only on the first interface touched, and no repeated prompts are given in other scenarios. For example, in response to the user's operation, the first interface entered is Figure 7 In the scenario shown in b, Figure 7 The prompt pop-up window 72 is displayed on the interface shown in b. Figure 7 When the scenes shown in c and d are executed, the prompt pop-up window will no longer be displayed.

[0112] In one possible implementation, participants who meet certain criteria (e.g., a participant's frequency of appearing in important schedules exceeding a preset threshold) can be selected from all schedule participants and recommended to the user as important schedule participants. Alternatively, users can automatically add important schedule participants. Once important schedule participants are identified, schedules containing them can be marked as important schedules, eliminating the need for users to manually mark them, further improving the user experience.

[0113] See also Figure 8 , showing a schematic diagram of a rule for determining important participants provided in an embodiment of the present application.

[0114] In one possible implementation, Figure 8 As shown, other participants are participants who have appeared in all schedules, including Y other participants in this example. Participants that meet the preset conditions are selected from these Y other participants as recommenders (that is, participants that the user may pay attention to). For example, the number of recommenders in this example can be X, where X < Y. In addition, the maximum value of X can be limited, such as X ≤ 5, that is, a maximum of 5 participants are recommended to the user. Furthermore, the user can select participants in the recommender list as important participants. Of course, the user can also directly select participants from other participants as important participants.

[0115] In the embodiment of the present application, the participants in the recommender list will be updated according to the user's operation of adding or deleting important participants.

[0116] In one embodiment of the present application, after the user uses the function of marking important schedules, the schedule management application will count all participants who have appeared in all important schedules and select participants who meet the preset conditions as recommenders. When the recommender list is not empty, the user is prompted to add important participants.

[0117] In other embodiments of the present application, when the schedule management application detects that all participants in the recommender list have been updated, the user may be prompted again to add new important participants.

[0118] See also Figure 9 , shows an interface diagram of a prompt box prompting a user to add important participants provided in an embodiment of the present application.

[0119] In one example, if Figure 9 As shown, a prompt box 702 is displayed on the month view interface 701 of the calendar application, which is used to guide the user to use the important participants function, in other words, prompt the user to add important participants to further improve the user experience. Furthermore, important schedules can be automatically marked based on the important participants added by the user.

[0120] In one example, if Figure 9 As shown, the prompt box 702 can be located between the date display area 705 and the schedule display area 706. In this example, the prompt box 702 can be located on the same layer as the date display area and the schedule display area. Of course, in other examples, the prompt box 702 can also be located on the upper layer of the layer where the date display area and the schedule display area are located, such as when the prompt box 702 is a pop-up window. For example, Figure 9 As shown, prompt box 702 includes text information for prompting the user, such as "Recommended important participants for you, smartly mark your schedule based on your important participants, don't miss important things." Of course, the text information displayed in prompt box 702 can also be other content, and this application does not limit this. In addition, prompt box 702 also includes an "Add Now" button 703 and a close button 704. After the user clicks the "Add Now" button 703, you can jump to the interface for adding important participants. After the user clicks the close button 704, the prompt box 702 is closed, that is, the prompt box 702 disappears.

[0121] The following will be combined Figure 10 Describes the process of adding key participants.

[0122] like Figure 10 As shown in a, after the user clicks the more button 800, more tabs 801 are displayed, and the more tabs 801 include a "settings" item 802. Further, after the user clicks the "settings" item 802, it jumps to Figure 10The interface 803 shown in b includes an important participant setting card 804. The user clicks the button 805 in the important participant setting card 804 to jump to Figure 10 The important participant interface shown in c.

[0123] like Figure 10 As shown in Figure c, the important participant interface includes a recommender list 806, which includes recommended participant setting items 807. For example, each participant setting item 807 includes the participant's information (such as name and account, etc.) and an "Add" button 808. After the user clicks the "Add" button 808, the participant is added to the important participant list. For example, in this example, after the user clicks the "Add" button in the participant items corresponding to the participants "Xiaomin" and "Long", it jumps to Figure 10 Interface 809 shown in d.

[0124] like Figure 10 As shown in FIG. d , interface 809 includes a list of key participants 810, which can be located above a list of recommenders 813. Key participant list 810 includes user-added participants "Xiaomin" and "Long." Each key participant setting item 811 includes the participant's information (such as name and account number) and a "Remove" button 812. The user can click "Remove" button 812 to delete the added key participant from the list of key participants.

[0125] In one embodiment of the present application, the number of important participants is not limited, that is, the number of participants in the important participant list is not limited.

[0126] like Figure 11 As shown in a, when the number of important participants in the important participant list is large, the window 901 displaying the important participant list cannot display all the important participants. In this case, a "more" button 902 will be displayed in the window 901. Click the "more" button 902 to jump to Figure 11 In the interface shown in b, a larger window 903 is used to display the list of important participants. It is understood that the user can change the important participants displayed in window 903 by sliding the page displayed in window 903 up or down. For example, when the important participant list in window 903 is slid up, the important participants after the important participant "Wind" in the figure can be displayed.

[0127] In addition, if Figure 11 As shown in FIG. 1 , the bottom of the window 903 includes a “fold” button 904. When the user clicks the “fold” button 904, the window 903 is closed. Figure 11 The interface shown in b jumps to Figure 11In the interface shown in a, after clicking the "Collapse" button 904, the window 903 displaying important participants is changed to a window 901 with a smaller display area.

[0128] In one application scenario, the important participant that the user wants to add is not included in the recommended participant list. In this case, you can select other participants as important participants through "Add other participants". Figure 12 , showing another interface schematic diagram for adding important participants provided in an embodiment of the present application.

[0129] like Figure 12 As shown in a, the important participant interface 1000 includes an "add other participants" button 1002. In this example, the button 1002 is located below the recommender list 1001. In other embodiments of the present application, the button 1002 can also be located in other positions, which is not limited by the present application. After the user clicks the button 1002, it jumps to Figure 12 b shows the interface 1003 for selecting participants.

[0130] like Figure 12 As shown in FIG. 1 , the interface 1003 is used to display a list of all participants. Each participant option in the list includes the participant's information and a selection button 1004. The user can click the selection button 1004 to select the participant. In this example, after the user clicks the selection button 1004 corresponding to the participant "Dannle", the user jumps to Figure 12 In the interface shown in c, the selection button 1004 corresponding to the participant "Dannle" in the interface becomes selected. In this example, "√" indicates selected. Of course, in other embodiments, "·" included in "○" can also be used to indicate selected.

[0131] like Figure 12 As shown in Figure c, the participant list selection interface 1003 includes a button 1006, a close button 1007, and a search box 1008. Button 1006 is a save button indicating completion. In this example, after the user selects the participant "Dannle" as an important participant, the user clicks button 1006 to save the current selection result, that is, to save the result of "Dannle" as an important participant. The user clicks Figure 12 After pressing button 1006, jump to Figure 12 If the user clicks the close button 1007, the interface 1003 is closed and the user can return to Figure 12 If there are many participants in the list of all participants, the user can enter at least part of the name or initials of the participant to be searched in the search box 1008 to search for the corresponding participant. Figure 12The bottom of the interface shown in c also includes a "Select All" button. After the user clicks the "Select All" button, all participants in the participant list are selected.

[0132] like Figure 12 As shown in d, it is the important participant interface 1009, Figure 10 d, interface 1009 includes a window 1010 for displaying important participants, and window 1010 is used to display information items of important participants and operation buttons, such as a "remove" button. The user clicks the "remove" button to delete the participant from the important participant list.

[0133] In addition, in an exemplary embodiment of the present application, participants are maintained in the dimension of their accounts, and the accounts of the same person in different applications will be regarded as different participants, such as Figure 12 As shown in b, the two participants are both named "AlisaLee", but have different accounts and are maintained as two different participants, i.e. Figure 12 1005 and 1012 in b correspond to two participants.

[0134] In another application scenario, an existing schedule includes participants, such as a meeting schedule, and the user can directly set the participants in the schedule as important participants.

[0135] Figure 13 This is another interface diagram for adding important participants provided in an embodiment of the present application.

[0136] Figure 13 The interface shown in a is a schedule details interface 1100, which includes a participant card 1101. The participant card 1101 includes all participants of the schedule. In addition, the card also includes a button 1102. After the user clicks the button 1102, it jumps to Figure 13 Participant interface 1104 shown in b.

[0137] like Figure 13 As shown in b, the participant interface 1104 includes information about all participants of the schedule. In this example, the schedule is an online meeting schedule. An online meeting usually includes an inviter and other participants. For example, the inviter is the person who created the online meeting. This person can invite other people to participate in the online meeting they created. In one embodiment of the present application, the inviter can be defaulted to an important participant, and an important identifier can be included in the participant item, for example, Figure 13 As shown in b, the inviter item 1106 includes the inviter's name "Xiaomin" and account information, and 11061 is an important identifier, which in this example is "VIP".

[0138] like Figure 13 As shown in b, the area shown in 1107 is other participants of the schedule. The user can slide this area up and down to update the participants displayed in the area. For example, if the user slides up, the participants currently displayed in the area will slide up, and at the same time, the participants below the participant "Long" will be displayed. Figure 13 The top of the interface 1104 shown in FIG. 1104 also includes a return button 1105. The user clicks the button 1105 to return to the Figure 13 The interface shown in a.

[0139] In one embodiment of the present application, Figure 13 The bottom of the participant interface 1104 shown in FIG. 1 also includes a button 1108 for “Edit Important Participants”. After the user clicks the button 1108, the user is redirected to the Figure 13 The interface 1112 for selecting participants is shown in c.

[0140] like Figure 13 As shown in FIG. 3 c , the interface 1112 for selecting a participant includes an area 1114 for displaying an inviter and an area 1115 for displaying other participants. Each participant display item in areas 1114 and 1115 includes a selection button 1113 .

[0141] In this embodiment of the present application, the inviter is considered a key participant by default. Therefore, selection button 1113 in the inviter's display item is selected by default. In this example, selection button 1113 in the inviter's display item is selected by default. Furthermore, if the user selects another participant, "Lee," as a key participant, selection button 1113 in that participant's display item becomes selected. In one example, the selection button can be "○" and the selected state can be "√." Of course, in other embodiments, the selected state can also be represented by other symbols, and similarly, the selection button can also be represented by other styles, and this application does not limit this.

[0142] like Figure 13 As shown in FIG. 3 , above the inviter display area, there is also an area 1109, which includes a completion button 1110 and a close button 1111, and may also include the number of selected important participants. After the user clicks the completion button 1110, it jumps to Figure 13 Click the close button 1111 to return to the interface shown in d Figure 13 The interface shown in b.

[0143] and Figure 13 Compared with the schedule details page interface shown in a, Figure 13The interface shown in Figure d is the schedule details page. In addition to the participant display item 1205, it also includes the key participant display item 1206. The participant display item 1205 is used to display all participants of the schedule. The key participant display item 1206 is used to display the key participants involved in the schedule. For example, in this example, the key participants are "Xiaomin" and "Lee."

[0144] In addition, the participant display item 1205 also includes a button 1209. The user clicks the button 1209 to jump to Figure 13 The participant interface shown in FIG. 1 includes an inviter display area 1201 and other participant display areas. The inviter display area 1201 is used to display the inviter involved in the schedule. The other participant display area is used to display the participants involved in the schedule other than the inviter. In one embodiment of the present application, the inviter display item includes an important identifier 1203 by default, such as "VIP", and the display item 1202 of the other participant "Lee" selected by the user also includes the important identifier 1203. In addition, Figure 13 In the interface shown in FIG. 1 , a return button 1204 is also included above the inviter display area. After the user clicks the return button 1204, the user is redirected to Figure 13 The interface shown in d is the schedule details page interface.

[0145] After the user edits the important participants, the schedule management application updates the important participant list. When it detects that an important participant is among the participants of a non-important schedule, it can automatically mark the non-important schedule as an important schedule. This process does not require manual operation by the user, further improving the user experience. For example, Figure 13 In the interface shown in FIG. d , the schedule title 1208 includes an important identifier, such as “!”, and the priority displayed in the priority option 1207 is “Important”.

[0146] Similarly, other view interfaces also include other view interfaces marked in the schedule, for example, Figure 14 The month view interface 1301 shown in FIG. 1 identifies that the participants of the non-important schedule of “Design Plan Discussion” include the important participant “Lee”, and automatically marks the non-important schedule as an important schedule. Figure 14 As shown, the schedule title 1302 in the interface includes an important identifier, and the priority display item shows that the priority of the schedule is “important.” This embodiment will not elaborate on the changes in other views after the schedule is automatically marked as important.

[0147] In addition, the aforementioned important schedule content also applies to schedules automatically marked as important, and will not be repeated here.

[0148] Figures 11 to 13This is a process of adding important participants provided in an embodiment of the present application. Conversely, important participants that have been added to the important participant list can be deleted.

[0149] See also Figure 15 , showing a schematic diagram of an interface for deleting important participants provided in an embodiment of the present application.

[0150] like Figure 15 As shown in a, the important participant interface 1400 includes an important participant list. Each participant display item in the list includes a "remove" button 1401. The user can delete the participant from the important participant list by clicking the "remove" button 1401.

[0151] In one possible implementation, the user clicks Figure 15 After clicking the "Remove" button 1401 shown in a, jump to Figure 15 The interface 1402 shown in b is Figure 15 A grayscale layer is added to the upper layer of the interface 1400 shown in a, and further, a prompt window 1403 is displayed on the upper layer of the grayscale layer, so that the prompt window 1403 can be highlighted, thereby guiding the user to view the content in the prompt box 1403.

[0152] like Figure 15 As shown in FIG. 14 , the prompt window 1403 may include information about the changes in the schedule status of the participant that may be caused by removing the important participant, as well as prompt information about the question of adding the participant again, as well as a “Cancel” button and a “Remove” button 1404. After the user clicks the “Cancel” button, the user returns to the Figure 15 The interface shown in a, the user clicks the "Remove" button and jumps to Figure 15 In this example, there is only one participant in the important participant list. When the user deletes this participant, the important participant list becomes empty. Figure 15 As shown in c, the important participant interface 1405 does not include an important participant list, but only displays a recommender list 1406.

[0153] In one application scenario, the recommender list does not contain any participants, that is, the recommender list is empty. Figure 16 As shown, in this scenario, when the user clicks Figure 16 After clicking the button 1601 in the important participant setting item in the interface 1600 shown in a, the recommender list is not displayed. Figure 16 The interface 1600 shown in a Figure 10 The setting items included in the interface 803 shown in b are the same, and the method of entering the interface is also the same, which will not be repeated here.

[0154] In one case, all schedules in the schedule management application are not important schedules, that is, no important schedules are included. In this case, the user clicks button 1601 and jumps to Figure 16 Interface 1603 shown in FIG. 16b includes a text prompt 1604 displaying the key participants, indicating the function and method for adding key participants. Furthermore, the interface includes a "Learn More" button 1605. Clicking "Learn More" takes the user to an interface detailing the "Key Participants" function, such as the "Key Participants" function in the "Game Tips" app.

[0155] In another case, the application for managing schedules includes important schedules. In this case, the user clicks button 1601 and jumps to Figure 16 The interface 1606 shown in c includes a text prompt message 1607 of "Follow important participants". The text prompt message is used to prompt the user to add important participants. The schedule containing important participants is defaulted as an important schedule prompt message. Figure 16 The interface shown in c also includes an "add other participants" button 1608. After the user clicks the "add other participants" button 1608, the user can jump to Figure 12 The interface shown in b. Figure 16 The interface is the same as that shown in b. Figure 16 The interface shown in c also includes a "Learn More" button.

[0156] It should be understood that in this embodiment, the user's operations of adding and deleting important participants will affect the participants in the recommender list.

[0157] In addition, if Figure 17 As shown in a, the important participant interface 1500 also includes a details button 1501. After the user clicks the details button 1501, it jumps to Figure 17 The interface 1502 shown in b is Figure 17 A grayscale layer is added to the upper layer of the interface shown in a, and a prompt window 1503 is further displayed on the upper layer of the grayscale layer. The prompt window 1503 is used to display information about important participant functions. In addition, the prompt window also includes a "Learn More" button 1504. The interface displayed after the user clicks the "Learn More" button 1504 is the same as the interface displayed after clicking Figure 16 The interface displayed after clicking the "Learn More" button in b and c is the same and will not be repeated here.

[0158] To make it easier for users to view important schedule information, you can also set it to display only important schedules. Figure 18 , shows a schematic diagram of an interface for screening important schedules provided in an embodiment of the present application.

[0159] like Figure 18 As shown in a, the month view interface 1700 of the calendar application includes a button 1701. After the user clicks the button 1701, the user jumps to Figure 18 In the interface shown in b, a setting item window 1702 is displayed on the upper layer of the month view interface 1700, which includes a "show only important" setting item 1703. After the user clicks the "show only important" setting item 1703, it jumps to Figure 18 Interface 1704 is shown in c.

[0160] like Figure 18 The interface 1700 shown in a includes important schedules and non-important schedules, such as train travel schedules, etc. Figure 18 The interface 1704 shown in c includes only important schedules and does not display non-important schedules. It should be noted that in this embodiment, the schedules for "Mid-Autumn Festival" and "Teacher's Day" are displayed by default. Of course, in other embodiments, it can also be set to not display holiday schedules and non-important schedules after selecting the "show only important" option, and only display important schedules. This application does not limit this.

[0161] also, Figure 18 The bottom of the interface shown in c also includes a prompt message 1705 that reads "Only important schedules are currently displayed" to remind the user that non-important schedules are not currently displayed on the interface. In other embodiments of the present application, the prompt message 1705 that reads "Only important schedules are currently displayed" may also be in other forms. For example, an identifier indicating the current filtering state may be displayed in a blank area of ​​the current interface or in an upper layer of the interface. The present application does not limit the identifier indicating the filtering state.

[0162] In another embodiment of the present application, the user can also restore the display of the entire schedule. Figure 18 As shown in c, after the user clicks button 1701, it jumps to Figure 18 The interface shown in d includes a setting item window 1707, and Figure 18 The difference between the setting item window 1702 shown in FIG. 17 is that the setting item window 1707 includes the "all schedules" setting item 1706, while the setting item window 1702 includes the "only important" setting item 1703. After the user clicks the "all schedules" setting item 1706, the user is redirected to Figure 18 The interface shown in a displays all schedules.

[0163] In one possible implementation, the content displayed on the setting items in the setting item windows 1702 and 1707 can be updated based on user operations. For example, if all schedules for a certain date are currently displayed in the view, the setting item in the setting item window may be "Show only important schedules." However, if the user clicks on the "Show only important schedules" setting item, the setting item in the setting item window changes to "All schedules."

[0164] In another possible implementation, the content displayed in the setting items in the setting item windows 1702 and 1707 remains fixed. For example, regardless of whether the current view displays only important schedules, the setting item window will display "Show only important / all schedules." This application does not limit the content style of the setting items displayed in the setting item window.

[0165] After the user sets the display to only show important schedules, other schedule display scenarios will be updated to show only important schedules.

[0166] See also Figure 19 , shows a schematic diagram of an interface of a schedule view provided in an embodiment of the present application, Figure 19 The a is a schedule view interface 1801, and the interface displays all schedules, for example, including important schedules 1802 and non-important schedules 1803 and 1804. After the user chooses to display only important schedules, the interface changes to Figure 19 The interface shown in b.

[0167] like Figure 19 As shown in Figure b, the schedule view interface 1805 only displays important schedules for each date, omitting non-important schedules. For example, area 1806 displays important schedules for September 10, while area 1807 displays important schedules for September 11. Furthermore, a prompt 1808 stating "Only important schedules are currently displayed" is included at the bottom of the interface.

[0168] See also Figure 20 , shows a schematic diagram of the interface of a schedule desktop card provided in an embodiment of the present application.

[0169] like Figure 20 As shown in a, desktop 1900 includes calendar card 1901, which includes schedules for the current date (September 10). If the current date includes multiple schedules, due to the limited display area of ​​calendar card 1901, not all schedules for that date can be displayed. For example, important schedules can be displayed first, and non-important schedules can be sorted by start and end time before being displayed.

[0170] For example, Figure 20 As shown in a, in this example, the calendar card 1901 includes an important schedule 1902 and a non-important schedule 1903. At the same time, the bottom of the calendar card 1901 also includes a prompt message 1904 of "There are 2 other schedules" to remind the user that there are schedules that have not been displayed on that day.

[0171] After the user chooses to display only important schedules, the calendar card 1901 changes to Figure 20 The display interface shown in b is as follows: Figure 20As shown in FIG. 1 , the calendar card 1901 only displays important schedules 1902 and does not display non-important schedules. In addition, the bottom of the calendar card 1901 can also display a prompt message 1905 stating that there are no other important schedules today.

[0172] In the embodiment of the present application, the desktop is also called a desktop application, a home screen, or a launcher, etc. For example, in the Android system, the desktop is also called a desktop launcher (Launcher). For the convenience of description, it is collectively referred to as the desktop in this article.

[0173] In another embodiment of the present application, the schedule management application further supports adding a single schedule card on the desktop, or called a schedule card.

[0174] In one scenario, when a user creates a new important schedule, he or she can add a schedule card for the schedule on the desktop. Figure 21 , shows a schematic diagram of an interface for adding a schedule card provided in an embodiment of the present application.

[0175] In one possible implementation, the function of adding a schedule card to the desktop can be provided only for important schedules. That is, only the display interface of important schedules has the function entry for adding a desktop card, while the interface of non-important schedules does not have the function entry for adding a desktop card. Of course, in other embodiments of the present application, schedule cards can be added to the desktop for all schedules, and this application does not limit this.

[0176] like Figure 21 As shown in a, after the user sets the priority setting item 2002 in the new schedule interface 2001 to "important", it jumps to Figure 21 The interface 2003 shown in b further includes an “add desktop card” setting item 2004, which includes a setting button 2005. Figure 21 The setting button 2005 shown in b is in an unopened state. After the user clicks the setting button 2005, it becomes an open state. Figure 21 The setting button 2005 shown in c is in the on state.

[0177] User clicks Figure 21 After pressing button 2006, jump to Figure 21 The interface shown in FIG. d includes an important schedule display area 2008. At the same time, the schedule card of the important schedule is added to the desktop. In addition, a prompt message 2009 stating "Schedule has been added to the desktop" is also included at the bottom of the interface. In an exemplary embodiment, the prompt message automatically disappears after being displayed for a preset period of time. Figure 21The interface shown in d also includes information 2007 indicating the date corresponding to the schedule. In this example, the schedule for September 9, 2022 is created on September 8, 2022, that is, tomorrow's schedule is created today.

[0178] like Figure 21 As shown in FIG. 5 , schedule card 2010 is a schedule card for a newly created important schedule, "Design Plan Discussion Meeting." Schedule card 2010 includes a countdown 2011 indicating the number of days from the current date to the schedule's execution date. In this example, the countdown is one day. Furthermore, the schedule card includes an area 2012 for displaying the schedule's execution date. In this example, the execution date is September 9, 2022.

[0179] See also Figure 22 , shows a schematic diagram of the calculation rules of countdown days and positive days provided by the embodiment of the present application. In the embodiment of the present application, countdown days refer to the number of days remaining from the current date to the execution date of the schedule.

[0180] For example, Figure 22 As shown, in this example, the schedule execution date is September 9, 2022, and the current date is September 8, 2022. Since the current date has not yet reached the schedule execution date, the schedule card displayed on September 8th displays the countdown to the schedule execution date. In an exemplary embodiment, the schedule card 2013 displayed on September 8th displays "1 day later" as the wedding anniversary and displays the execution date of the schedule, which is September 9, 2022.

[0181] When the current date is September 9, 2022, the current date is the schedule execution date. In an exemplary embodiment, the schedule card 2014 displayed on September 9, 2022 no longer displays the countdown days, but directly displays "Wedding Anniversary" and the execution date of the schedule, September 9, 2022.

[0182] If the current date is September 10, 2022, the current date has already exceeded the schedule execution date. In one exemplary embodiment, the schedule card 2015 displayed on September 10, 2022, may display that "1 day ago" was the wedding anniversary and may also display the schedule execution date, i.e., September 10, 2022. The content displayed on the schedule card can be adjusted according to actual needs and is not limited in this application.

[0183] also, Figure 21 The schedule card 2010 shown in FIG. 1 is only a specific example, and schedule cards of other styles and sizes may also be included. Figure 23 The following are schematic diagrams of three possible sizes of schedule cards. The size of schedule card 2016 is Figure 21The size of schedule card 2017 is twice that of schedule card 2016, and the size of schedule card 2018 is half that of schedule card 2016. Of course, in other embodiments of the present application, schedule cards of other sizes may also be included, and the present application does not limit this.

[0184] Previously combined Figure 21 The process of adding a schedule card on the desktop during the process of creating a new schedule is introduced. In other embodiments of the present application, a schedule card can also be added to the desktop for an existing schedule (such as a schedule that has been created or a schedule imported from other applications).

[0185] See also Figure 24 , shows another interface schematic diagram for adding a schedule card provided in an embodiment of the present application.

[0186] like Figure 24 As shown in a, the schedule details interface 2101 is the detailed information of the important schedule "Design Plan Seminar". The interface includes a desktop card setting item 2102. The desktop card setting item 2102 includes an "Add" button. The user can add the schedule card of the important schedule on the desktop by clicking the "Add" button.

[0187] In one case, the important event has not been added to the event card. In this case, the user clicks Figure 24 After clicking the "Add" button shown in a, jump to Figure 24 The desktop interface shown in b. Figure 24 As shown in FIG. 1 , the desktop interface includes a schedule card 2103 for an important schedule “design solution seminar”. The contents displayed on the schedule card 2103 are similar to those on FIG. Figure 22 The schedule cards shown are the same and will not be repeated here.

[0188] In another case, the important event has already been added to the event card. In this case, the user clicks Figure 24 After clicking the "Add" button shown in a, jump to Figure 24 The interface 2104 shown in c. Figure 24 As shown in c, the interface is Figure 24 A grayscale layer is added to the upper layer of the interface shown in a, and further, a prompt window 2105 is displayed on the upper layer of the grayscale layer. The prompt window 2105 includes a desktop card that reminds the user that the schedule has been added.

[0189] For example, in one example, prompt window 2105 may display a text message such as "The current schedule already has a desktop card. Do you want to add a duplicate?" In addition, prompt window 2105 may include a "Cancel" button and an "OK" button. If the user clicks the "Cancel" button, the process of adding a desktop card for the schedule is not executed. If the user clicks the "OK" button, the process of adding a desktop card for the schedule continues. In this case, at least two schedule cards corresponding to the schedule will appear on the desktop, and these at least two schedule cards will display the same content.

[0190] In the above-mentioned adding a desktop card when creating a new schedule, or adding a desktop card for an existing schedule, the schedule is first created and then the desktop card corresponding to the schedule is added. In another embodiment of the present application, a blank schedule card can also be added first, and then the schedule to be displayed on the blank schedule card can be selected.

[0191] See also Figure 25 , shows another interface schematic diagram for adding a schedule card provided in an embodiment of the present application.

[0192] In one possible implementation, Figure 25 As shown in a, the user can perform a two-finger pinch operation on the desktop 2200 to enter Figure 25 The interface shown in b is the desktop editing interface. The upper area of ​​the interface displays editable desktop pages 2201. You can change the currently displayed desktop page by swiping the desktop page left or right. The bottom area of ​​the interface displays operation options, such as wallpaper, calendar card 2202, transition effects, desktop settings, etc.

[0193] After the user clicks on the schedule card 2202, it jumps to Figure 25 The interface shown in c is a schedule card interface, which includes an area 2203 for displaying the style of the schedule card. For example, in this example, the style of the calendar card 2204 is currently displayed. The style of the currently displayed schedule card can be changed by sliding the area left and right. In addition, an "Add to Desktop" button 2205 is also included at the bottom of the schedule card interface. After the user clicks the "Add to Desktop" button 2205, it jumps to Figure 25 The interface shown in d.

[0194] After the user clicks the "Add to Desktop" button 2205, Figure 25 As shown in FIG. 4 , a schedule card 2206 added by the user is displayed on the desktop interface. The schedule card 2206 includes a button 2207 for adding a schedule. After the user clicks the button 2207 , the interface for selecting a schedule is jumped to.

[0195] In an exemplary embodiment, the interface for selecting a schedule includes three pages: "Holiday", "Schedule", and "Birthday". The user can select any one of the pages and add any one from the page to the schedule card. Figure 25 As shown in Figure 2, the "Schedule" page includes multiple schedules for multiple dates. For example, in this example, the "Schedule" page includes three schedules for September 9 and two schedules for September 10. The user can select any of the schedules and add it to the schedule card on the desktop. Each schedule item includes a selection button, which can have two display states: selected and unselected. In one example, button 2209 indicates the selected state, while button 2210 indicates the unselected state.

[0196] In one example, if Figure 26 As shown in a, it is a schematic diagram of the "Festival" page. Figure 26 b is a diagram of the "Birthday" page. Similar to the "Schedule" page, Figure 26 As shown in a of FIG, the “holiday” page 2301 includes multiple holiday options 2302, and each holiday option includes a selection button. Figure 26 As shown in b, the "Birthday" page 2303 includes multiple birthday options 2304, and each birthday option includes a selection button, which will not be repeated here.

[0197] In this example, after the user selects the "Design Workshop" schedule, they will be redirected to Figure 25 The interface shown in f, the schedule card 2211 shown in the interface is Figure 25 Compared with the blank card 2206 shown in FIG. d, the schedule information selected by the user is added, wherein the schedule card 2211 is Figure 22 The schedule information contained in the schedule cards shown is the same and will not be repeated here.

[0198] From the above process of adding schedule cards on the desktop, it can be seen that users can add important schedules to the schedule cards on the desktop. In this way, users do not need to open the schedule management application and can directly see the countdown or countdown of the schedule on the desktop, which reduces the user's operation of viewing important schedules, further improves the efficiency of users paying attention to important schedules, and avoids users missing important schedules.

[0199] In another embodiment of the present application, the user can also edit or remove the schedule card added on the desktop. In an exemplary embodiment, the user can edit or remove the schedule card by long pressing the schedule card on the desktop.

[0200] See also Figure 27 , shows a schematic diagram of an interface for operating a schedule card provided in an embodiment of the present application.

[0201] like Figure 27 As shown in a, the desktop interface includes a schedule card 2401. The user long presses the schedule card 2401 to jump to Figure 27 The interface shown in b, the interface also includes an operation tab 2402 below the schedule card 2401. In one example, the operation tab 2402 includes edit and remove. After the user clicks "Remove", it jumps to Figure 27 The interface shown in c is the desktop interface after the schedule card 2401 is deleted.

[0202] In another possible implementation, the user can edit the schedule in the schedule card 2401 by clicking "Edit" in the operation tab 2402, for example, changing the schedule information displayed on the schedule card. For example, in the original state, the schedule card 2401 adds the schedule of "Design Plan Seminar". Through the "Edit" operation, the schedule card can display the information of another schedule, which will not be repeated here.

[0203] It can be seen that the solution provided in this embodiment allows users to directly perform operations on schedule cards that have been added to the desktop, such as editing the schedule in the schedule card, or removing the schedule card, without the user having to enter the schedule management application to perform operations, which reduces the complexity of user operations and improves user experience.

[0204] In another embodiment of the present application, when a user modifies or deletes a schedule in a schedule management application, the content of the schedule card corresponding to the schedule is updated synchronously. For example, after a user deletes a schedule, the schedule card corresponding to the schedule can become a blank card, or the schedule card displaying the schedule can be directly deleted. For another example, after a user modifies the content of the schedule, the corresponding content of the schedule card corresponding to the schedule is updated synchronously.

[0205] For example, if the user deletes the "Design Workshop" schedule for September 9, 2022 in the Calendar application, in one example, Figure 27 The schedule card 2401 in a becomes a blank card, and the user can add other schedules to the schedule card 2401.

[0206] In another example, after deleting the "Design Solution Workshop" schedule on September 9, 2022 in the Calendar application, Figure 27 The schedule card 2401 in a is deleted synchronously.

[0207] It can be seen that the solution provided by this embodiment is that after the user operates a schedule in the schedule management application, the schedule card corresponding to the schedule is synchronously updated, that is, the schedule in the schedule management application and the content in the schedule card are automatically synchronized without the user's manual operation, thereby improving the user experience.

[0208] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0209] In the several embodiments provided in this embodiment, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

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

[0212] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment. The aforementioned storage medium includes: various media that can store program code, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

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

Claims

1. A schedule management method, characterized in that: Applied to electronic equipment, the method includes: Displaying a first interface, the first interface including a date display area and a schedule display area, the schedule display area including a first schedule card, the first schedule card including schedule information and schedule priority, the schedule priority being none; In response to an operation of clicking on a schedule priority on the first schedule card, a priority setting option pop-up window is displayed on the first interface, the priority setting option pop-up window including a no level option, an important level option, and an ignore option; In response to selecting the importance level option on the priority setting option pop-up window, a second interface is displayed, which includes a date display area and a second schedule card. The schedule priority in the second schedule card is important, and the second schedule card contains more schedule information than the first schedule card.

2. The method according to claim 1, characterized in that The schedule information includes a schedule title; the second schedule card also includes an important identifier, and the important identifier is located before the schedule title.

3. The method according to claim 1, characterized in that The schedule priorities include None, Important, and Ignore.

4. The method according to claim 1, wherein The displaying of the first interface includes: Displaying a third interface, the third interface including a date display area and a first button, the first button being used to create a new schedule; In response to the operation of the first button, a new schedule interface is displayed, wherein the new schedule interface includes a priority setting item and a save button, and the priority of the priority setting item is none; In response to an operation on the save button, the first interface is displayed.

5. The method according to any one of claims 1 to 4, characterized in that The schedule information includes participants, and the method further includes: When it is detected that the schedule priority is an important schedule, the participants in all schedules including the participants are obtained; Selecting a preset number of participants who meet preset conditions from among all participants of the schedule as recommended participants, wherein the preset conditions include that the frequency of participating in important schedules is greater than a preset threshold; A recommender list is generated, wherein the recommender list includes the recommendation participants.

6. The method according to claim 5, characterized in that After generating the recommendation list, the method further includes: When a new important schedule is detected, the recommended participants in the recommender list are updated based on the participants of the new important schedule.

7. The method according to claim 1, characterized in that The method further comprises: Displaying a first important participant interface, wherein the first important participant interface includes a recommender list, the recommender list includes at least one participant item, and the participant item includes participant information and an add button; In response to the operation of the add button, a second important participant interface is displayed, wherein the second important participant interface includes an important participant list, the important participant list includes important participant items, and each important participant item includes an added participant and a remove button.

8. The method according to claim 7, characterized in that The first important participant interface further includes a button for adding other participants; after displaying the first important participant interface, the method further includes: In response to the operation of the add other participants button, a first participant selection interface is displayed, wherein the first participant selection interface includes a first participant list of all schedules; In response to an operation of selecting any participant in the first participant list, a third important participant interface is displayed, wherein the third important participant interface includes an important participant list, and the important participant list includes the selected participant.

9. The method according to claim 1, characterized in that The first schedule card further includes a participant setting item; after displaying the first interface, the method further includes: In response to an operation on the participant setting item, displaying a schedule participant interface, the schedule participant interface including a second participant list and an edit important participant button, the second participant list including all participants in the schedule included in the first schedule card; In response to an operation on the important participant button, displaying a second participant selection interface, wherein the second participant selection interface includes a participant selection list; In response to an operation of selecting a participant in the participant selection list, the selected important participant is marked as an important participant, and the important participant list is updated.

10. The method according to any one of claims 7 to 9, characterized in that After adding the important participants, the method further includes: After detecting that an important participant is included in the participants of a non-important schedule, the non-important schedule is automatically marked as an important schedule. The non-important schedule is a schedule with a priority of none.

11. The method according to claim 1, wherein After displaying the second interface, the method further includes: Displaying a settings pop-up window, wherein the settings pop-up window includes displaying only the important first setting items; In response to the operation on the first setting item, only important schedules are displayed in each interface for displaying schedules.

12. The method according to claim 1, characterized in that The method further comprises: Displaying a fourth interface, the fourth interface including the schedule priority of the first schedule and desktop card setting items, the schedule priority being important; In response to an operation on the desktop card setting item, a first desktop card of the first schedule is displayed on the desktop, where the first desktop card includes the number of days between the current date and the execution date of the first schedule.

13. The method according to claim 12, characterized in that Displaying the fourth interface includes: Displaying a fifth interface, wherein the fifth interface includes a new schedule button; In response to an operation on the new schedule button, the fourth interface is displayed.

14. The method according to claim 12 or 13, characterized in that After displaying the fourth interface, the method further includes: In response to an operation on the desktop card setting item and after detecting that the first desktop card corresponding to the first schedule has been added, displaying a first pop-up window on the first interface, the first pop-up window including a cancel button, an confirm button, and information prompting the user whether to add the desktop card again; In response to an operation on the confirm button, a second desktop card of the first schedule is added, and the content of the second desktop card is the same as that of the first desktop card.

15. The method according to claim 12 or 13, characterized in that The method further comprises: Displaying a sixth interface, the sixth interface including a blank desktop card and a first button, the blank desktop card including an add schedule button; In response to an operation on the first button, displaying the blank desktop card on the desktop; In response to an operation on the add schedule button, displaying a schedule selection interface, the schedule selection interface including selectable schedules; In response to the operation of selecting a schedule in the schedule selection interface, a desktop is displayed, the desktop including a third desktop card, the third desktop card including information of the selected schedule and the number of days between the current date and the execution date of the selected schedule.

16. An electronic device, characterized in that: The electronic device includes: one or more processors, a memory and a touch screen; the memory is used to store program code; the processor is used to run the program code, so that the electronic device implements the schedule management method according to any one of claims 1 to 15.

17. A computer-readable storage medium, characterized in that Instructions are stored thereon, and when the instructions are executed on an electronic device, the electronic device executes the schedule management method according to any one of claims 1 to 15.

Images