Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. Content may be ranked and ordered within a module, and modules may be ranked and ordered with respect to each other. Inter-module ranking may be based on elements such as individual activity and the activity of the messaging service's user base, the value of the module to the messaging service, and offline models. Intra-module ranking may be defined by individual modules (e.g., based on recency, importance to user, affinity, etc.). Intra-module ranking may affect inter-module ranking, such as when individual content in a low-rated module is particularly exciting or pertinent (causing the entire module to receive a higher inter-module ranking).

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. After a number of recent or unread messages are shown in the inbox's initial interface, the messages end and are replaced with modules. A threshold may be defined for the number of recent/unread messages to display before transitioning to modules. The threshold may be determined dynamically based on a minimum and/or maximum number of messages to display. The determination may be based on the current time, whether there is an active conversation in a thread, whether there are unread messages in a thread, etc. The determination may vary from user to user based, for example, on whether the user is a relatively active user, and/or how the user has used the messaging application in the past.

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities that they might not otherwise be aware of (or inclined to use on a regular basis). After a number of recent or unread messages are shown in the inbox's initial interface, the messages end and are replaced with modules. Many different types of functionality may be the subject of the modules (e.g., a module for sharing local content such as photos from a photo album, a People/States module, Top Contacts, New Behavior, Live Videos, Events, Businesses, or Messaging Stickers). Once the available modules have been scrolled through, the interface may revert to more messages, such as less-recent or previously read threads from the original messages. Unread threads may also be collapsed in the top section of the inbox, or included in a module.

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities that they might not otherwise be aware of (or inclined to use on a regular basis). After a number of recent or unread messages are shown in the inbox's initial interface, the messages end and are replaced with modules. Many different types of functionality may be the subject of the modules (e.g., a module for sharing local content such as photos from a photo album, a People/States module, Top Contacts, New Behavior, Live Videos, Events, Businesses, or Messaging Stickers). Once the available modules have been scrolled through, the interface may revert to more messages, such as less-recent or previously read threads from the original messages. Unread threads may also be collapsed in the top section of the inbox, or included in a module.

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. After a number of recent or unread messages are shown in the inbox's initial interface, the messages end and are replaced with modules. A threshold may be defined for the number of recent/unread messages to display before transitioning to modules. The threshold may be determined dynamically based on a minimum and/or maximum number of messages to display. The determination may be based on the current time, whether there is an active conversation in a thread, whether there are unread messages in a thread, etc. The determination may vary from user to user based, for example, on whether the user is a relatively active user, and/or how the user has used the messaging application in the past.

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. After a number of recent or unread messages are shown in the inbox's initial interface, the messages end and are replaced with modules. In some embodiments, promotional material may be integrated into a module, or may be integrated as a module. For example, a new message thread may be created to indicate a store in which a discount is offered. The message may appear in a module, or may stand in the place of a module. The promotional material may be selected based on proximity. The messaging service may differentiate between sponsored materials advertising a product or service, and purely beneficial materials such as coupons.

Abstract: Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. Content may be ranked and ordered within a module, and modules may be ranked and ordered with respect to each other. Inter-module ranking may be based on elements such as individual activity and the activity of the messaging service's user base, the value of the module to the messaging service, and offline models. Intra-module ranking may be defined by individual modules (e.g., based on recency, importance to user, affinity, etc.). Intra-module ranking may affect inter-module ranking, such as when individual content in a low-rated module is particularly exciting or pertinent (causing the entire module to receive a higher inter-module ranking).

Abstract: A computing system and a user interface display requested data corresponding with a contact at a display device. The requested data includes contact information, communication histories, and files associated with the contact. The requested data is obtained from one or more contact information directories located locally and/or remotely from the computing system. The user interface also displays contact-centric tasks that may be engaged in between the user and the contact based upon the capabilities of the corresponding computing systems or that can be performed on a contact. Some of the contact information can be edited with an edit mode of the user interface. The contact may be a person, group, organization, or household.

Abstract: Participants in a chat session can control the archiving of chat messages in the chat session. Participants in a chat session send and receive a first set of chat messages, which are archived. A command to deactivate archiving is made by one of the participants. Messages in the chat session that are sent and received subsequent to the command to deactivate archiving are not archived. Archiving may be reactivated and messages subsequent to the command to reactivate archiving are archived.

Abstract: Email and chat messages may be displayed as part of the same conversation, in an integrated conversation view. The conversation view would include items corresponding to email messages that are part of the conversation and chat messages that are part of the conversation. A user may reply to an email message in the conversation by chat.

Abstract: A contact text box interface for resolving user input with contact information selected from contact directories and compared against usage patterns. Users are provided with a list of potentially relevant contacts from which a selection can be made. When a contact is selected, the corresponding and appropriate contact information is automatically provided to the application. Various criteria can be used to identify which contacts will be presented to the user and how they will be presented.

Abstract: A user is able to informatively control how contact information is provided to one or more applications through the use of a persona interface object, corresponding personas and contact information, and an information picker interface. The persona interface identifies available personas, each persona having different contact information. The user can select a persona to use in response to an applications request for information. The personas can be modified and developed through the information picker interface, which can also be used to inform the user about what information is being requested and how it will be used.

Abstract: Methods and systems present commands to a user within a software application program by determining the user's context within the application program and automatically presenting in a user interface commands that pertain to the user's current context. When the user's context changes, the context-sensitive commands are automatically removed from the user interface. In one implementation context blocks and context panes are employed to present the commands.