Automatically updating applications on a client's device without interrupting the user's experience

• US 9,032,383 B2
• Filed: 09/27/2012
• Issued: 05/12/2015
• Est. Priority Date: 02/29/2012
• Status: Active Grant

• Current Assignee: Zesty.ai, Inc.
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: D'Aurelio, Ryan James, Leece, Mark John Sawrey, Berrett, Douglas Duane
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): FINKLEY, RESHAUN
• Application Number:
  US13/629,149
• Publication Number:
  US 20130227539A1
• Time in Patent Office: 957 Days
• Field of Search: 717/169
• US Class Current: 717/169
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 3/041 Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
• CPC Class Codes: G06F 3/048 Interaction techniques based on graphical user interfaces [GUI]
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/137 Hierarchical processing, e.g. outlines
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching

Abstract

Portions of an application can be delivered through a network without having to download the entire application. When an application is installed, HTML, CSS and JavaScripts® or other User Interface (UI) files can be copied into local cache. A version number can also be stored with this code, so that when the application is launched, a web service checks the latest version on a server computer. If the latest version differs from the cached version, then an update is needed. New UI files can then be downloaded to the local cache. The local cache can be a folder that is used by the application, wherein the folder is stored on a hard drive of the client device. Binaries associated with the application can be stored in a different folder.

Claims

1. A method of updating a client device, comprising:

providing application files in a first install directory on the client device;

upon launching of an application using the application files, automatically checking to determine whether updates are available for the application;

if updates are available, determining whether the updates are for binary files or for text-based files;

if the updates are for binary files of the application, then requesting user permission to download the updates;

if the updates are for text-based files, then copying updated application files to a second updates directory on the client device, different than the install directory without user permission so that updates of binary files of the application are treated differently than text-based files of the application; and

executing the application using at least the updates located in the second updates directory, while ignoring an older version of the updated application files that remain in the install directory during execution of the application.

2. The method of claim 1, wherein the updates are text-based files that are interpreted at runtime.

3. The method of claim 2, wherein the text-based files include one or more of the following file types:

HTML files, script files, CSS files.

4. The method of claim 1, wherein the updated files are user interface files.

5. The method of claim 1, wherein automatically checking to determine whether updates are available includes storing a version number attribute on the client device that is associated with a stored version of the application, downloading a current version of the application from a server computer and comparing the stored version to the current version.

6. The method of claim 5, wherein if the stored version and the current version are different, determining that updates are available.

7. The method of claim 5, wherein the version number is associated with application files in the second updates directory and the first install directory.

8. The method of claim 1, wherein the application itself installs the updates to the second updates directory and the application does not have authorization to store files in the first install directory.

9. The method of claim 2, wherein updating the text-based files includes updating all text-based files that are used for user interface elements if any text-based file needs to be updated.

10. One or more computer-readable nonvolatile storage media storing instructions thereon for executing a method, the method comprising:

installing an application onto a client device in an install directory, including first user interface portions of the application;

downloading, from a server computer, updated user interface portions of the application to the client device that represent updates to the first user interface portions, wherein the application can automatically initiate the updates without requiring user authorization, whereas other portions of the application require user authorization to initiate the updates;

storing the updated user interface portions in a local directory that is different than the install directory, while maintaining the first user interface portions of the application in the install directory; and

launching the application using the updated user interface portions while ignoring the first user interface portions.

11. The method of claim 10, wherein the user interface portions are downloaded by the application itself.

12. The method of claim 10, wherein the application includes a check version procedure that compares server-side application files to either application files in the install directory or application files in the local directory.

13. The method of claim 10, wherein the updated user interface portions include only text files that have changed.

14. The method of claim 10, wherein the updated user interface portions include all of the text files regardless of whether they changed or not.

15. The method of claim 10, further including checking a web service on startup to determine if new user interface updates are available.

16. The method of claim 10, wherein the user interface updates are for HTML, CSS and/or script files.

17. A method of displaying user interface elements on a client device, comprising:

in response to a first launch of an application after an update, deleting text-based files from a local store directory and copying text-based files from an install directory to the local store directory;

downloading one or more current version numbers for the text-based files from a server computer;

comparing the one or more current version numbers to installed version numbers of the text-based files stored in the local store directory;

if the current version numbers do not match the installed version numbers, downloading at least the text-based files that do not match without acquiring authorization from a user;

storing the text-based files in the local store directory, while maintaining an older version of the text-based files in the install directory;

downloading one or more current version numbers for binary files from the server computer;

comparing the one or more current version numbers for the binary files to installed version numbers for the binary files;

if the current version numbers for the binary files do not match the installed version numbers, requesting authorization from the user to download the binary files; and

launching the application using at least one file from the install directory and the text-based files in the local store directory.

18. The method of claim 17, further including downloading all of the text-based files if even one version number does not match.

19. The method of claim 17, further including launching a redirection page when launching the application that uses files from the local store directory if they are present, and uses files from the install directory if they are not in the local store directory.