Abstract: A method performed by a computing system includes generating a to-do list user interface comprising a user actuatable list element corresponding to a particular entry on a to-do list associated with a user, and a user input mechanism actuatable to perform a to-do list management function comprising at least one of adding a new entry on the to-do list, deleting an existing entry on the to-do list, and modifying an existing entry on the to-do list. The method includes generating an agenda associated with the user, the agenda comprising an agenda item having an associated time period, and detecting a flick gesture on the user actuatable list element on the to-do list user interface, and adding, based on the detected flick gesture, an agenda item to the agenda associated with the user, the added agenda item corresponding to the particular entry on the to-do list.

Abstract: A method performed by a computing system includes generating a to-do list user interface comprising a user actuatable list element corresponding to a particular entry on a to-do list associated with a user, and a user input mechanism actuatable to perform a to-do list management function comprising at least one of adding a new entry on the to-do list, deleting an existing entry on the to-do list, and modifying an existing entry on the to-do list. The method includes generating an agenda associated with the user, the agenda comprising an agenda item having an associated time period, and detecting a flick gesture on the user actuatable list element on the to-do list user interface, and adding, based on the detected flick gesture, an agenda item to the agenda associated with the user, the added agenda item corresponding to the particular entry on the to-do list.

Abstract: A to-do list management system surfaces a user interface with a user input mechanism that displays a user actuatable element for each item on a user's to-do list. It senses a flick gesture and automatically moves a to-do list item to the user's agenda. It can also sense a user input gesture and automatically remove an agenda item from the user's agenda, and place it on the user's to-do list.

Abstract: A to-do list management system surfaces a user interface with a user input mechanism that displays a user actuatable element for each item on a user's to-do list. It senses a flick gesture and automatically moves a to-do list item to the user's agenda. It can also sense a user input gesture and automatically remove an agenda item from the user's agenda, and place it on the user's to-do list.

Abstract: Techniques described herein provide mechanisms for generating contextually-aware scheduling exceptions. In some configurations, when a scheduling conflict is detected, the techniques disclosed herein can utilize contextual data from a number of resources to determine if a scheduling exception can be made. The contextual data can include preferences, such as preferences of a service provider or a customer, that define criteria and/or goals. The techniques disclosed herein prioritize customers based on the contextual data and provide different scheduling options for customers and other entities based on a priority associated with individual customers. When there is a conflict between two or more calendar events, a scheduling exception can be made for some customers and a scheduling conflict can be made for other customers depending on one or more priorities associated with the customers.

Abstract: Techniques provide a contextually-aware resource manager. In response to one or more events, such as the creation or modification of a calendar event, one or more contextually-aware recommendations are generated and displayed to a user. For example, a recommendation can include the names of service providers, the names of customers, time slots for one or more calendar events, and notifications of one or more conditions. The recommendation can be based on data defining a level of eligibility for service providers and customers. The level of eligibility can be determined by a wide range of contextual data, including but not limited to traffic data, payment data, location data, map data, preference data, scheduling data, workload data, work history data, status data, skill set data, or weather data. The techniques assist user interaction with a computing device, and among other benefits, saves computing resources and reduce the number of inadvertent user entries.

Abstract: Techniques described herein provide contextually-aware insights into calendar events. Generally described, the techniques disclosed herein can analyze a wide variety of contextual data including, but not limited to, weather data, traffic data, location data, performance data, preference data, and scheduling data, to generate salient insights that can be automatically displayed and/or communicated to a user. Insights related to one or more calendar events may be generated in response to a discovery of a predetermined condition. A predetermined condition may be detected at the time an appointment is made or at a later time when contextual data indicates a change in one or more conditions. An insight can include a text description, an image, a graphical indicator, a generated voice, and any other suitable form of communication describing useful information regarding one or more calendar events. An insight can include ranked list of recommendations can also be displayed.