Abstract: A method for providing messaging-related information to a mobile device is discussed. The method includes receiving from the mobile device a request for messaging-related information, using the request to identify a device-type indication for the mobile device, identifying one or more presentation parameters for presenting the messaging-related content properly on the mobile device, and transmitting the messaging-related content to the mobile device in a format corresponding to the one or more parameters.

Abstract: Methods for implementing an auto-complete feature for contact entry on mobile devices are described. In some embodiments, a mobile device downloads from a server a number of contacts associated with a user, wherein the number of contacts is a subset of contacts in a contact list of the user. Upon receiving a partial contact entry from the user that includes a string of one or more characters, the mobile device identifies contacts from the downloaded contacts matching the partial entry. The mobile device displays no more than a preset number of matching contacts on the display of the mobile device at any one time, in a particular order, with an option for the user to display and fetch for more matching contacts. Other embodiments are also described.

Abstract: A social networking system aggregates content related to the media events that have aired or are currently airing from a variety of sources, such as the entity broadcasting the media event and users that author content items referencing the media events. The social networking system generates multiple event interfaces that allow users of the social networking system to consume content, both user authored content and content curated from external sources, related to a media event. The interfaces include both content items that have a high correlation with the media events and visual representations of the user response to media event. Further, the interfaces include interface elements that allow users to easily navigate and interact with the information being presented as well as provide additional content related to the media events.

Abstract: Systems, methods, and computer readable storage mediums for providing message services from a server are described. In some embodiments, a server stores an attachment associated with a communication. The server sends the communication to a client device, with a representation of the attachment type that includes an indication of the attachment's native file type. The server receives a request from the client device to view the attachment in the client device. The server retrieves the attachment in response to the request and transcodes the attachment from the attachment's native file type to a viewable file type configured to display in the client device. The viewable file type is determined by the server based on metadata received from the client device. The server transmits at least a portion of the attachment in the viewable file type to the client device for display. Other embodiments are also described.

Abstract: Systems and methods for implementing a card-based user interface for thread-based communications on mobile devices are described. In some embodiments, in response to activation of an application, a mobile device receives data that represents a set of threaded conversations, where the data includes a representation header for each threaded conversation in the set of threaded conversations. The mobile device then displays a list of the representation headers for the set of threaded conversations. In response to an activation of the representation header corresponding to a particular threaded conversation in the set of the threaded conversations, the mobile device displays in a first expanded card, text associated with a most recent message in the particular threaded conversation, and in a collapsed card, a representation of previously read messages in the particular threaded conversation. Other embodiments are also described.

Abstract: Informational items are displayed in a scrollable area of a message display. The informational items may be any number of type of items (e.g., RSS feeds, new items, images, application tips, and so on). A user is provided the ability to scroll forward and backward through the informational items. A user may choose the informational item (e.g., by clicking) and more detailed information about the informational item is presented to the user. Depending on the display view of the message application (e.g., InBox, conversation), different informational item types will have different probabilities of display. A user may customize the types of informational items to be displayed.

Abstract: A method for providing messaging-related information to a mobile device is discussed. The method includes receiving from the mobile device a request for messaging-related information, using the request to identify a device-type indication for the mobile device, identifying one or more presentation parameters for presenting the messaging-related content properly on the mobile device, and transmitting the messaging-related content to the mobile device in a format corresponding to the one or more parameters.

Abstract: Systems, methods, and computer readable storage mediums for providing message services from a server are described. In some embodiments, a server stores an attachment associated with a communication. The server sends the communication to a client device, with a representation of the attachment type that includes an indication of the attachment's native file type. The server receives a request from the client device to view the attachment in the client device. The server retrieves the attachment in response to the request and transcodes the attachment from the attachment's native file type to a viewable file type configured to display in the client device. The viewable file type is determined by the server based on metadata received from the client device. The server transmits at least a portion of the attachment in the viewable file type to the client device for display. Other embodiments are also described.

Abstract: Methods for implementing an auto-complete feature for contact entry on mobile devices are described. In some embodiments, a mobile device downloads from a server a number of contacts associated with a user, wherein the number of contacts is a subset of contacts in a contact list of the user. Upon receiving a partial contact entry from the user that includes a string of one or more characters, the mobile device identifies contacts from the downloaded contacts matching the partial entry. The mobile device displays no more than a preset number of matching contacts on the display of the mobile device at any one time, in a particular order, with an option for the user to display and fetch for more matching contacts. Other embodiments are also described.

Abstract: Systems and methods for downloading customized applications from a server are described. In some embodiments, a server receives a request from a client device to download an application. The server identifies a type of the client device and a user characteristic. In response to the request, the server obtains a customized environment file associated with the user characteristic for the application, where the customized environment file defines an interface appearance of the application. The server sends to the client device, the customized environment file and the application appropriate for the type of the client device, such that the customized environment file gives the application running on the client device an appearance associated with the user characteristics. Other embodiments are also described.

Abstract: Methods for simulating icon popout on memory constrained devices are described. In some embodiments, the client device displays a message status icon where the message status icon represents a first message status of the respective message. In response to a user action, the status of the respective action changes and the visual appearance of the message status icon varies such that the displayed message status icon represents a second message status of the respective message, to identify a status change of the respective message. The message status icon comprises a fixed image having a display background with at least one property that can be varied to achieve the changes in the visual appearance of the message status icon. Other embodiments are also described.

Abstract: Systems and methods to provide a user-interface graphic are implemented on a client system having one or more processors and memory to store programs. The method includes, while executing a browser application on the client system, displaying a page on a display of the client system; displaying the user-interface graphic over the page at a first position relative to the page. The method further includes receiving a request to scroll the page, responding to the request by scrolling the page, and in response to detecting an end of the scrolling, displaying the user-interface graphic at a second position relative to the page.

Abstract: A method for providing messaging-related information to a mobile device is discussed. The method includes receiving from the mobile device a request for messaging-related information, using the request to identify a device-type indication for the mobile device, identifying one or more presentation parameters for presenting the messaging-related content properly on the mobile device, and transmitting the messaging-related content to the mobile device in a format corresponding to the one or more parameters.

Abstract: Informational items are displayed in a scrollable area of a message display. The informational items may be any number of type of items (e.g., RSS feeds, new items, images, application tips, and so on). A user is provided the ability to scroll forward and backward through the informational items. A user may choose the informational item (e.g., by clicking) and more detailed information about the informational item is presented to the user. Depending on the display view of the message application (e.g., InBox, conversation), different informational item types will have different probabilities of display. A user may customize the types of informational items to be displayed.

Abstract: Informational items are displayed in a scrollable area of a message display. The informational items may be any number of type of items (e.g., RSS feeds, new items, images, application tips, and so on). A user is provided the ability to scroll forward and backward through the informational items. A user may choose the informational item (e.g., by clicking) and more detailed information about the informational item is presented to the user. Depending on the display view of the message application (e.g., InBox, conversation), different informational item types will have different probabilities of display. A user may customize the types of informational items to be displayed.