Auto-update is one of the killer features of Chrome. It is magical because it continuously updates the entire development platform imperceptibly and often. His support has influenced how we structure our development process. It was also one of the first features of Chrome. If we recall the history of the project long before it was publicly launched in 2008, the auto-update project was one of the first that we started working on. The idea was to give people an empty window with auto update. After they installed it, the empty window gradually turned into a browser. And today — five years after our auto-updater began updating a nearly empty window that could barely load web pages — now it’s a tool to provide an incredibly complex web technology platform on our users’s computers, which in turn allows developers web applications create an amazing new online experience. I have never seen such an efficient platform update mechanism before.
Chrome's auto-update system is deceptively simple. I say “deceptive” because it is completely invisible to users, but in fact it is supported by many complex technologies and processes. The key here is “completely invisible.” We have made numerous improvements to the auto update during Chrome development, including one major change when we dispersed the frequency of our releases from one quarter to one every six weeks. But from the user's point of view, Chrome is still ... Chrome.
I will focus on invisibility, because it is important:
Chrome auto update works silently in the background, never distracting you. If there is an update, it will download it and prepare it so that the next time you start the browser, it will be its latest version. Something like starting up Gmail is the latest version.
Source: https://habr.com/ru/post/127472/