Abstract: Embodiments are directed to providing an indication of unseen email messages to a mobile device user, to establishing an unseen email message count and to maintaining a consistent unseen email message count across multiple mobile devices. In one scenario, a computer system receives subscription data that subscribes a user to email push notifications. The subscription data includes a token ID and a timestamp. The computer system determines that a new email message has arrived at the user's inbox and accesses the user's email inbox to determine the number of unseen email messages (which includes the number of email messages that have been received at the user's inbox and have not been seen since the time listed on the timestamp). The computer system also sends a push notification with the number of unseen email messages to each of the user's subscribed mobile devices.

Abstract: A meeting service with meeting time and location optimization is described. In some examples, organizer and attendee behaviors may be analyzed and used as contextual factors in computing ranking scores for potential meeting times. To optimize a meeting for the attendees (including the organizer), potential meeting times and locations may be ranked based on weighted coefficients for the factors that are used in ranking such as attendee schedules, preferences, meeting type, location attributes, attendee preferences for locations, and extraneous factors such as events and other happenings that may impact availability or access of attendees as well as meeting locations.

Abstract: Embodiments are directed to registering a device to receive notifications. In one scenario, a computer system receives a notification registration request from a computing device. The computer system generates a registration secret which includes identification information that uniquely identifies the computing device, and sends the generated registration secret including the information that uniquely identifies the computing device to a notification service. The computer system receives a hash value from the computing device, where the hash value is generated based on the identification information of the generated registration secret.

Abstract: Embodiments are directed to registering a device to receive notifications. In one scenario, a computer system receives a notification registration request from a computing device. The computer system generates a registration secret which includes identification information that uniquely identifies the computing device, and sends the generated registration secret including the information that uniquely identifies the computing device to a notification service. The computer system receives a hash value from the computing device, where the hash value is generated based on the identification information of the generated registration secret.

Abstract: Embodiments are directed to providing an indication of unseen email messages to a mobile device user, to establishing an unseen email message count and to maintaining a consistent unseen email message count across multiple mobile devices. In one scenario, a computer system receives subscription data that subscribes a user to email push notifications. The subscription data includes a token ID and a timestamp. The computer system determines that a new email message has arrived at the user's inbox and accesses the user's email inbox to determine the number of unseen email messages (which includes the number of email messages that have been received at the user's inbox and have not been seen since the time listed on the timestamp). The computer system also sends a push notification with the number of unseen email messages to each of the user's subscribed mobile devices.

Abstract: Embodiments are directed to providing an indication of unseen email messages to a mobile device user, to establishing an unseen email message count and to maintaining a consistent unseen email message count across multiple mobile devices. In one scenario, a computer system receives subscription data that subscribes a user to email push notifications. The subscription data includes a token ID and a timestamp. The computer system determines that a new email message has arrived at the user's inbox and accesses the user's email inbox to determine the number of unseen email messages (which includes the number of email messages that have been received at the user's inbox and have not been viewed or marked as read using another email client since the time listed on the timestamp). The computer system also sends a push notification with the number of unseen email messages to each of the user's subscribed mobile devices.

Abstract: Embodiments are directed to providing an indication of unseen email messages to a mobile device user, to establishing an unseen email message count and to maintaining a consistent unseen email message count across multiple mobile devices. In one scenario, a computer system receives subscription data that subscribes a user to email push notifications. The subscription data includes a token ID and a timestamp. The computer system determines that a new email message has arrived at the user's inbox and accesses the user's email inbox to determine the number of unseen email messages (which includes the number of email messages that have been received at the user's inbox and have not been viewed or marked as read using another email client since the time listed on the timestamp). The computer system also sends a push notification with the number of unseen email messages to each of the user's subscribed mobile devices.