Abstract: In accordance with some embodiments, a method is performed at an invitee device with one or more processors, non-transitory memory, an input device, and a display. The method includes receiving, from an organizer, an invitation for a calendar event. The method includes displaying, on the display, a calendar user interface including a first graphical representation of the calendar event displayed at location of the calendar user interface corresponding to a time of the calendar event. The method includes detecting, via the input device, a proposed new time input indicative of a proposed new time for the calendar event. In response to detecting the proposed new time input, the method includes displaying a second graphical representation of the calendar event at a location of the calendar user interface corresponding to the proposed new time and sending a notification to the organizer including an indication of the proposed new time.

Abstract: One or more user accounts can be linked together to form a group of linked user accounts. A shared calendar can be assigned to a group of linked user accounts. A shared calendar can be a unique calendar assigned to the group of linked user accounts that can be accessed by each member of the group of linked user accounts to schedule appointments, reminders, etc. A shared task list can be assigned to a group of linked user accounts and accessed by each member of the group of linked user accounts. Members of the group of linked user accounts can add tasks to the shared task list that can then be viewed by the other members of the group of linked user accounts. This can allow a family to add tasks to the shared task list that can then be completed by other members of the family.

Abstract: In accordance with some embodiments, a method is performed at an invitee device with one or more processors, non-transitory memory, an input device, and a display. The method includes receiving, from an organizer, an invitation for a calendar event. The method includes displaying, on the display, a calendar user interface including a first graphical representation of the calendar event displayed at location of the calendar user interface corresponding to a time of the calendar event. The method includes detecting, via the input device, a proposed new time input indicative of a proposed new time for the calendar event. In response to detecting the proposed new time input, the method includes displaying a second graphical representation of the calendar event at a location of the calendar user interface corresponding to the proposed new time and sending a notification to the organizer including an indication of the proposed new time.

Abstract: One or more user accounts can be linked together to form a group of linked user accounts. A shared calendar can be assigned to a group of linked user accounts. A shared calendar can be a unique calendar assigned to the group of linked user accounts that can be accessed by each member of the group of linked user accounts to schedule appointments, reminders, etc. A shared task list can be assigned to a group of linked user accounts and accessed by each member of the group of linked user accounts. Members of the group of linked user accounts can add tasks to the shared task list that can then be viewed by the other members of the group of linked user accounts. This can allow a family to add tasks to the shared task list that can then be completed by other members of the family.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.

Abstract: A text input is received in a calendar context. The text input is processed with a context-neutral extraction process to generate a first set of elements and with a calendar-specific extraction process to generate a second set of elements. A calendar event is created from the first set of elements and the second set of elements and displayed on a display device without confirming the elements of the calendar event with a user.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.

Abstract: The calendaring techniques and systems described herein enable a user to more easily resolve conflicts for attendees to an event by visually indicating available time slots for all attendees in a calendar window or in a timeline window separate from the calendar window. The first available time slot may be automatically selected or the user may select an available slot to reschedule the event. In another aspect, inspector windows are displayed within a calendar window to show summary or details for an event. An inspector window can also be displayed when a change to an event is detected. In yet another aspect, calendars for multiple accounts accessible by a user are merged into a single calendar view.