Update application user interfaces on client devices

• US 9,823,917 B2
• Filed: 10/20/2011
• Issued: 11/21/2017
• Est. Priority Date: 10/20/2011
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Reiss, David Scott, Papakipos, Matthew Nicholas
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Kepnang, Gilles
• Application Number:
  US13/278,136
• Publication Number:
  US 20130104114A1
• Time in Patent Office: 2,224 Days
• Field of Search: 709203, 717121, 717168, 717178, 717170-172, 455418, 713200
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

In one embodiment, receiving a notice that a new version of a user interface of an application is available; storing information about the new version of the user interface; requesting permission from the application to update the user interface to the new version; and if the application grants the permission, then replacing an old version of the user interface of the application with the new version.

Claims

1. A method comprising:

by a computing device;

displaying a user interface for a running mobile application on the computing device, the user interface comprising one or more code files, each having a hashed value, and the mobile application having an application update policy;

receiving a message communicated over a network from a server, the message indicating that a new version of the user interface of the mobile application is available, and the new version of the user interface comprising one or more new code files;

storing, based on the received message, version information corresponding to the new version of the user interface for the mobile application, wherein the version information includes;

a timestamp specifying when the new version of the user interface is available,

a retrieval indicator confirming the new version is downloaded, and

one or more unique file paths associated with a respective new code file for the new version of the user interface;

based on the timestamp, downloading the one or more new code files from the server according to the unique file paths, wherein the one or more new code files are associated with the new version of the user interface;

calculating a new hashed value for each of the one or more new code files;

updating the version information by

     1) changing the retrieval indicator to reflect that the one or more new code files has been downloaded and

     2) adding the new hashed value for the new code file; and

for each new code file;

comparing the new hashed value with the hashed value of the running mobile application;

if the hashed values are the same, then forbidding the new code file from updating the user interface; and

if the hashed values are different, designating the new code file as applicable to update the user interface;

accessing the application update policy to determine conditions under which an update to the user interface of the mobile application is set to occur, wherein the conditions include performing the update upon reboot of the computing device or during an uninterrupted non-user input state of the mobile application;

applying, by an operating system of the computing device, an authority to override the application update policy; and

based on the conditions being true or the operating system override authority, updating the user interface with the designated new code files.

2. The method of claim 1, wherein the version information further comprises:

a unique version number associated with the new version, and a version manifest identifying one or more files included in the new version.

3. The method of claim 1, wherein the one or more new code files are downloaded using Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS).

4. The method of claim 1, wherein updating the user interface with the designated new code files comprises:

constructing a view;

attaching a code loader to the view; and

setting the code loader to load code implementing the new version of the user interface of the mobile application and display the new version of the user interface in the view as one or more web pages.

5. The method of claim 1, wherein:

the mobile application is a native application executing on the computing device; and

the user interface of the mobile application is implemented as one or more web pages.

6. The method of claim 1, wherein the computing device is a mobile device.

7. The method of claim 1, wherein the conditions specified by the mobile application update policy further include that the mobile application is not being displayed on a display of the computing device.

8. The method of claim 1, wherein the conditions specified by the mobile application update policy further include that the mobile application is not being executed by the computing device.

9. A system comprising:

a memory comprising instructions executable by one or more processors; and

the one or more processors coupled to the memory and operable to execute the instructions, the one or more processors being operable when executing the instructions to;

display a user interface for a running mobile application on a computing device including one or more of the processors, the user interface comprising one or more code files, each having a hashed value, and the mobile application having an application update policy;

receive a message communicated over a network from a server, the message indicating that a new version of a user interface of the mobile application is available, and the new version of the user interface comprising one or more new code files;

store, based on the received message, version information corresponding to the new version of the user interface for the mobile application, wherein the version information includes;

a timestamp specifying when the new version of the user interface is available,

a retrieval indicator confirming the new version is downloaded,

one or more unique file paths associated with a respective new code file for the new version of the user interface;

calculating a new hashed value for each of the one or more new code files;

update the version information by

     1) changing the retrieval indicator to reflect that the one or more new code files has been downloaded and

     2) adding new hashed value for the new code file; and

for each new code file;

compare the new hashed value with the hashed value of the running mobile application;

if the hashed values are the same, then forbid the new code file from updating the user interface; and

if the hashed values are different, designate the new code file as applicable to update the user interface;

access the application update policy to determine conditions under which an update to the user interface of the mobile application is set to occur, wherein the conditions include performing the update upon reboot of the computing device or during an uninterrupted non-user input state of the mobile application;

apply, by an operating system of the computing device, an authority to override the application update policy; and

based on conditions being true or the operating system override authority, update the user interface with the designated new code files.

10. The system of claim 9, wherein the version information further comprises:

a unique version number associated with the new version, and a version manifest identifying one or more files included in the new version.

11. The system of claim 9, wherein the one or more new code files are downloaded using Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS).

12. The system of claim 9, wherein updating the user interface with the designated new code files comprises:

constructing a view;

attaching a code loader to the view; and

setting the code loader to load code implementing the new version of the user interface of the mobile application and display the new version of the user interface in the view as one or more web pages.

13. The system of claim 9, wherein:

the mobile application is a native application executing on the computing device; and

the user interface of the mobile application is implemented as one or more web pages.

14. The system of claim 9, wherein the computing device is a mobile device.

15. The system of claim 9, wherein the conditions specified by the application update policy further include that the mobile application is not being displayed on a display of the computing device.

16. The system of claim 9, wherein the conditions specified by the application update policy further include that the mobile application is not being executed by the computing device.

17. One or more computer-readable non-transitory storage media embodying software operable when executed by a computer system to:

display a user interface for a running mobile application on a computing device associated with the computes system, the user interface comprising one or more code files, each having a hashed value, and the mobile application having an application update policy;

receive a message communicated over a network from a server, the message indicating that a new version of the user interface of the mobile application is available, and the new version of user interface comprising one or more new code files;

store, based on the received message, version information corresponding to the new version of the user interface for the mobile application, wherein the version information includes;

a timestamp specifying when the new version of the user interface is available,

a retrieval indicator confirming the new version is downloaded, and

one or more unique file paths associated with a respective new code file for the new version of the user interface;

based on the timestamp, download the one or more new code files from the server according to the unique file paths, wherein the one or more new code files are associated with the new version of the user interface;

calculate a new hashed value for each of the one or more new code files;

update the version information by

     1) changing the retrieval indicator to reflect that the one or more new code files has been downloaded and

     2) adding the new hashed value for the new code file; and

for each new code file;

compare the new hashed value with the hashed value of the running mobile application;

if the hashed values are the same, then forbid the new code file from updating the user interface; and

if the hashed values are different, designate the new code file as applicable to update the user interface;

access the application update policy to determine conditions under which an update to the user interface of the mobile application is set to occur, wherein the conditions include performing the update upon reboot of the computing device or during an uninterrupted non-user input state of the mobile application;

apply, by an operating system of the computing device, an authority to override the application update policy; and

based on the conditions being true or the operating system override authority, update the user interface with the designated new code files.

18. The media of claim 17, wherein the version information further comprises:

a unique version number associated with the new version, and a version manifest identifying one or more files included in the new version.

19. The media of claim 17, wherein the one or more new code files are downloaded using Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS).

20. The media of claim 17, wherein updating the user interface with the designated new code files comprises:

constructing a view;

attaching a code loader to the view; and

setting the code loader to load code implementing the new version of the user interface of the mobile application to display the new version of the user interface in the view as one or more web pages.

21. The media of claim 17, wherein:

the mobile application is a native application executing on the computing device; and

the user interface of the mobile application is implemented as one or more web pages.

22. The media of claim 17, wherein the computing device is a mobile device.

23. The media of claim 17, wherein the conditions specified by the application update policy further include that the mobile application is not being displayed on a display of the computing device.

24. The media of claim 17, wherein the conditions specified by the application update policy further include that the mobile application is not being executed by the computing device.