Installed applications will re-use the same underlying appcache mechanisms we have in Gecko already. To update an installed application, we'll check its manifest against the master copy on the installation server (if a data connection of the right kind is available), and if the copy on the server is newer, we'll attempt to pull down an atomic update. If not all elements in the update are fetched, it aborts. If successful, the resources in cache are updated, and the next time the app is opened, the newer version will pop up automatically.
Fabrice, we were looking for an owner here and you were suggested. If that's incorrect, feel free to re-assign to someone more appropriate or nobody. Thanks.
Removing blocking because meta. Removed a blocking- dependent bug.
Removing assignee & qacontact as this has become a tracking bug.
Closing as we are basically finished for v1, outside of some post v1 work at this point.
For watching progress post v1, watch bug 863032 instead.