Customization of mobile applications using web-based technology

• US 9,740,670 B2
• Filed: 04/03/2015
• Issued: 08/22/2017
• Est. Priority Date: 12/17/2010
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Tseng, Erick, Fung, Philip, Sadan, Yariv
• Primary Examiner(s): Zuberi, Mohammed-Ibrahim
• Application Number:
  US14/678,917
• Publication Number:
  US 20150212990A1
• Time in Patent Office: 872 Days
• CPC Class Codes: G06F 3/04847 Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 40/103 Formatting, i.e. changing of presentation of documents automatic justification G06F40/189; automatic line break hyphenation G06F40/191
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/194 Calculation of difference between files
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

In one embodiment, receiving, at a first computing device from a second computing device, a request for a view of a user interface of a native application executing on the second computing device, wherein the view includes one or more first user interface components; determining, by the first computing device, a user agent type of the second computing device; selecting, by the first computing device, one or more second user-interface components to be included in the view based on the user agent type of the second computing device; generating, by the first computing device, code implementing a structured document that represents the view, wherein the structured document comprises the one or more first user-interface components and the one or more second user-interface components; and transmitting, from the first computing device to the second computing device, the code.

Claims

1. A method comprising:

by a server computing device, receiving from a client computing device a request for a view of a user interface of a native application executing on the client computing device, wherein the view includes one or more first user-interface components, and wherein the native application is an application installed locally on the client computing device;

by a server computing device, determining a user agent type of the client computing device;

by a server computing device, selecting one or more second user-interface components based on the user agent type of the client computing device, the one or more second user-interface components being associated with a native feature of the client computing device, the native feature comprising a hardware component native to the second-computing device;

by a server computing device, generating code implementing a structured document that represents the view, the structured document comprising the one or more first user-interface components and the one or more second user-interface components; and

by a server computing device, sending the code to the client computing device.

2. The method of claim 1, further comprising:

by a server computing device, receiving from the client computing device an application programming interface call to the server computing device, the call initiated by a user input to the client computing device through the one or more user-interface components; and

by a server computing device, sending to the client computing device a response to the call.

3. The method of claim 1, wherein each second user-interface component is associated with a customized uniform resource locator (URL) referring to the native feature.

4. The method of claim 1, wherein the code is in Hypertext Markup Language (HTML).

5. The method of claim 1, wherein the user agent type comprises an identification of the native application.

6. The method of claim 1, wherein the native feature comprises a sensor native to the client computing device.

7. The method of claim 1, wherein the native feature comprises an operating system executing on the client computing device.

8. One or more non-transitory computer-readable storage media embodying software that is operable when executed by a server computing device to:

receive from a client computing device a request for a view of a user interface of a native application executing on the client computing device, wherein the view includes one or more first user-interface components, and wherein the native application is an application installed locally on the client computing device;

determine a user agent type of the client computing device;

select one or more second user-interface components based on the user agent type of the client computing device, the one or more second user-interface components being associated with a native feature of the client computing device, the native feature comprising a hardware component native to the second-computing device;

generate code implementing a structured document that represents the view, the structured document comprising the one or more first user-interface components and the one or more second user-interface components; and

send the code to the client computing device.

9. The media of claim 8, wherein the software is further operable when executed to:

receive from the client computing device an application programming interface call to the server computing device, the call initiated by a user input to the client computing device through the one or more user-interface components; and

send to the client computing device a response to the call.

10. The media of claim 8, wherein each second user-interface component is associated with a customized uniform resource locator (URL) referring to the native feature.

11. The media of claim 8, wherein the code is in Hypertext Markup Language (HTML).

12. The media of claim 8, wherein the user agent type comprises an identification of the native application.

13. The media of claim 8, wherein the native feature comprises a sensor native to the client computing device.

14. The media of claim 8, wherein the native feature comprises an operating system executing on the client computing device.

15. A system comprising:

one or more non-transitory computer-readable storage media embodying instructions;

one or more processors coupled to the storage media and configured to execute the instructions to;

receive from a client computing device a request for a view of a user interface of a native application executing on the client computing device, wherein the view includes one or more first user-interface components, and wherein the native application is an application installed locally on the client computing device;

determine a user agent type of the client computing device;

select one or more second user-interface components based on the user agent type of the client computing device, the one or more second user-interface components being associated with a native feature of the client computing device, the native feature comprising a hardware component native to the second-computing device;

generate code implementing a structured document that represents the view, the structured document comprising the one or more first user-interface components and the one or more second user-interface components; and

send the code to the client computing device.

16. The system of claim 15, wherein the processors are further configured to execute the instructions to:

receive from the client computing device an application programming interface call to the server computing device, the call initiated by a user input to the client computing device through the one or more user-interface components; and

send to the client computing device a response to the call.

17. The system of claim 15, wherein each second user-interface component is associated with a customized uniform resource locator (URL) referring to the native feature.

18. The system of claim 15, wherein the code is in Hypertext Markup Language (HTML).

19. The system of claim 15, wherein the native feature comprises a sensor native to the client computing device.

20. The system of claim 15, wherein the native feature comprises an operating system executing on the client computing device.