Systems and methods for supporting downloadable applications on a portable client device

• US 9,497,147 B2
• Filed: 01/17/2014
• Issued: 11/15/2016
• Est. Priority Date: 11/02/2007
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Shih, Jimmy, Beust, Cdric, McKinley, Joanne, Phillips, Derek, Nicolaou, Alex, Shamis, Zhanna
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US14/158,716
• Publication Number:
  US 20140136640A1
• Time in Patent Office: 1,033 Days
• Field of Search: 709/206, 709/207
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

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.

Claims

1. A method comprising:

at a server having one or more processors and a memory storing programs executed by the one or more processors;

storing an attachment associated with a communication;

sending, to a client device, the communication but not the attachment, wherein the communication includes a graphical representation of the attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

receiving a request from the client device to view the attachment at the client device;

responsive to receiving the request, retrieving the attachment and converting the attachment from the native file type to a viewable file type configured for display at the client device, wherein the viewable file type is determined by the server based on metadata received from the client device; and

transmitting at least a portion of the attachment in the viewable file type to the client device for display.

2. The method of claim 1, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

3. The method of claim 1, wherein the viewable file type is determined by a user of the client device.

4. A system comprising:

one or more processors;

a memory coupled to the one or more processors; and

one or more programs, stored in the memory, configured for execution by the one or more processors to;

store an attachment associated with a communication;

send, to a client device, the communication but not the attachment, wherein the communication includes a graphical representation of the attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

receive a request from the client device to view the attachment at the client device;

responsive to receiving the request, retrieve the attachment and converting the attachment from the native file type to a viewable file type configured for display at the client device, wherein the viewable file type is determined based on metadata received from the client device; and

transmit at least a portion of the attachment in the viewable file type to the client device for display.

5. The system of claim 4, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

6. The system of claim 4, wherein the viewable file type is determined by a user of the client device.

7. A non-transitory computer readable storage medium storing one or more programs configured for execution by a server to:

store an attachment associated with a communication;

send, to a client device, the communication but not the attachment, wherein the communication includes a graphical representation of the attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

receive a request from the client device to view the attachment at the client device;

responsive to receiving the request, retrieve the attachment and converting the attachment from the native file type to a viewable file type configured for display at the client device, wherein the viewable file type is determined based on metadata received from the client device; and

transmit at least a portion of the attachment in the viewable file type to the client device for display.

8. The non-transitory computer readable storage medium of claim 7, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

9. The non-transitory computer readable storage medium of claim 7, wherein the viewable file type is determined by a user of the client device.

10. A method comprising:

at a client device having one or more processors and a memory storing programs executed by the one or more processors;

receiving a communication that includes a graphical representation of an attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

sending a request to a server to view the attachment in a viewable file type that is configured for display at the client device;

responsive to sending the request, receiving at least a portion of the attachment in the viewable file type configured for display at the client device; and

outputting, for display, at least the portion of the attachment in the viewable file type.

11. The method of claim 10, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

12. The method of claim 10, further comprising:

receiving a user selection of the viewable file type.

13. The method of claim 10, wherein the request includes metadata indicating the viewable file type.

14. A client device comprising:

one or more processors;

a memory coupled to the one or more processors; and

one or more programs, stored in the memory, configured for execution by the one or more processors to;

receive a communication that includes a graphical representation of an attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

send a request to a server to view the attachment in a viewable file type that is configured for display at the client device;

responsive to sending the request, receive at least a portion of the attachment in the viewable file type configured for display at the client device; and

output, for display, at least the portion of the attachment in the viewable file type.

15. The client of claim 14, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

16. The client of claim 14, wherein the one or more programs are further configured for execution by the one or more processors to:

receive a user selection of the viewable file type.

17. The client of claim 14, wherein the request includes metadata indicating the viewable file type.

18. A non-transitory computer readable storage medium storing one or more programs configured for execution by a client device to:

receive a communication that includes a graphical representation of an attachment, wherein the graphical representation indicates a native file type of the attachment, and wherein the native file type comprises a file format that is not viewable at the client device;

send a request to a server to view the attachment in a viewable file type that is configured for display at the client device;

responsive to sending the request, receive at least a portion of the attachment in the viewable file type configured for display at the client device; and

output, for display, at least the portion of the attachment in the viewable file type.

19. The non-transitory computer readable storage medium of claim 18, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

20. The non-transitory computer readable storage medium of claim 18, wherein the one or more programs are further configured for execution by the client device to:

receive a user selection of the viewable file type.

21. The non-transitory computer readable storage medium of claim 18, wherein the request includes metadata indicating the viewable file type.