|Written in||C, C++|
|Working state||Preinstalled on Chromebooks, Chromeboxes, Chromebits, Chromebase|
|Initial release||June 15, 2011|
|Latest release||70.0.3538.76 (October 26, 2018) [±]|
|Update method||Rolling release|
|Platforms||x86, ARMv7, x64|
|Kernel type||Monolithic (Linux kernel)|
|Default user interface||WIMP-based [web browser] windows|
|License||Google Chrome OS Terms of Service|
Chrome OS is an operating system designed by Google that is based on the Linux kernel and uses the Google Chrome web browser as its principal user interface. As a result, Chrome OS primarily supports web applications.
Google announced the project in July 2009, conceiving it as an operating system in which both applications and user data reside in the cloud: hence Chrome OS primarily runs web applications. Source code and a public demo came that November. The first Chrome OS laptop, known as a Chromebook, arrived in May 2011. Initial Chromebook shipments from Samsung and Acer occurred in July 2011.
Chrome OS has an integrated media player and file manager. It supports Chrome Apps, which resemble native applications, as well as remote access to the desktop. Android applications started to become available for the operating system in 2014, and in 2016, access to Android apps in the entire Google Play Store was introduced on supported Chrome OS devices. Reception was initially skeptical, with some observers arguing that a browser running on any operating system was functionally equivalent. As more Chrome OS machines have entered the market, the operating system is now seldom evaluated apart from the hardware that runs it.
Chrome OS is only available pre-installed on hardware from Google manufacturing partners. An open source equivalent, Chromium OS, can be compiled from downloaded source code. Early on, Google provided design goals for Chrome OS, but has not otherwise released a technical description.
- 1 Supported applications
- 2 Open source
- 3 History
- 4 Applications
- 5 Design
- 6 Reception
- 7 See also
- 8 References
- 9 External links
In September 2014, Google launched App Runtime for Chrome (beta), which allows certain ported Android applications to run on Chrome OS. Runtime was launched with four Android applications: Duolingo, Evernote, Sight Words, and Vine.
Chrome OS is partially developed under the open source Chromium OS project. As with other open source projects, developers can modify the code from Chromium OS and build their own versions, whereas Chrome OS code is only supported by Google and its partners and only runs on hardware designed for the purpose. Unlike Chromium OS, Chrome OS is automatically updated to the latest version.
Google announced Chrome OS on July 7, 2009, describing it as an operating system in which both applications and user data reside in the cloud. To ascertain marketing requirements, the company relied on informal metrics, including monitoring the usage patterns of some 200 Chrome OS machines used by Google employees. Developers also noted their own usage patterns. Matthew Papakipos, former engineering director for the Chrome OS project, put three machines in his house and found himself logging in for brief sessions: to make a single search query or send a short email.
At a November 19, 2009, news conference, Sundar Pichai, at the time Google's vice president overseeing Chrome, demonstrated an early version of the operating system. He previewed a desktop which looked very similar to the Chrome browser, and in addition to the regular browser tabs, also had application tabs, which take less space and can be pinned for easier access. At the conference, the operating system booted up in seven seconds, a time Google said it would work to reduce.
Also on November 19, 2009, Chris Kenyon, vice president of OEM services at Canonical Ltd, announced that Canonical was under contract to contribute engineering resources to the project with the intent to build on existing open source components and tools where feasible.
The launch date for retail hardware featuring Chrome OS was delayed from late 2010 to June 15, 2011.
Laptops running Chrome OS are known collectively as "Chromebooks". The first was the CR-48, a reference hardware design that Google gave to testers and reviewers beginning in December 2010. Retail machines followed in May 2011. A year later, in May 2012, a desktop design marketed as a "Chromebox" was released by Samsung. In March 2015 a partnership with AOPEN was announced and the first commercial Chromebox was developed.
In early 2014, LG Electronics introduced the first device belonging to the new all-in-one form factor called "Chromebase". Chromebase devices are essentially Chromebox hardware inside a monitor with built-in camera, microphone and speakers.
The Chromebit is an HDMI dongle running Chrome OS. When placed in an HDMI slot on a television set or computer monitor, the device turns that display into a personal computer. The device was announced in March 2015 and shipped that November.
Chrome OS supports dual-monitor setups, on devices with a video-out port.
In April 2012, Google made the first update to Chrome OS's user interface since the operating system had launched, introducing a hardware-accelerated window manager called "Aura" along with a conventional taskbar. The additions marked a departure from the operating system's original concept of a single browser with tabs and gave Chrome OS the look and feel of a more conventional desktop operating system. "In a way, this almost feels as if Google is admitting defeat here", wrote Frederic Lardinois on TechCrunch. He argued that Google had traded its original version of simplicity for greater functionality. "That’s not necessarily a bad thing, though, and may just help Chrome OS gain more mainstream acceptance as new users will surely find it to be a more familiar experience."
Relationship to Android
Google's offering two open source operating systems, Android and Chrome OS, has drawn some criticism and market confusion, as both are client-based and overlap in functionality. Steve Ballmer, Microsoft CEO at the time, accused Google of not being able to make up its mind. Steven Levy wrote that "the dissonance between the two systems was apparent" at Google I/O 2011. The event featured a daily press conference in which each team leader, Android's Andy Rubin and Chrome's Sundar Pichai, "unconvincingly tried to explain why the systems weren't competitive." Google co-founder Sergey Brin addressed the question by saying that owning two promising operating systems was "a problem that most companies would love to face". Brin suggested that the two operating systems "will likely converge over time." The speculation over convergence increased in March 2013 when Chrome OS chief Pichai replaced Rubin as the senior vice president in charge of Android, thereby putting Pichai in charge of both.
The relationship between Android and Chrome OS became more substantial at Google I/O 2014, where developers demonstrated native Android software running on Chrome OS through a Native Client based runtime. In October 2015, The Wall Street Journal reported that Chrome OS would be folded into Android so that a single OS would result by 2017. The resulting OS will be Android, but it will be expanded to run on laptops. Google responded that while the company has "been working on ways to bring together the best of both operating systems, there's no plan to phase out Chrome OS."
Integrated media player, file manager
Google integrates a media player into both Chrome OS and the Chrome browser, enabling users to play back MP3s, view JPEGs, and handle other multimedia files while offline. It supports DRM videos.
Chrome OS also includes an integrated file manager, resembling those found on other operating systems, with the ability to display directories and the files they contain from both Google Drive and local storage, as well as to preview and manage file contents using a variety of Web applications, including Google Docs and Box. Since January 2015, Chrome OS can also integrate additional storage sources into the file manager, relying on installed extensions that use the File System Provider API.
At Google I/O 2014, a proof of concept showing Android applications, including Flipboard, running on Chrome OS was presented. In September 2014, Google introduced a beta version of the App Runtime for Chrome (ARC), which allows selected Android applications to be used on Chrome OS, using a Native Client-based environment that provides the platforms necessary to run Android software. Android applications do not require any modifications to run on Chrome OS, but may be modified to better support a mouse and keyboard environment. At its introduction, Chrome OS support was only available for selected Android applications.
In 2016, Google introduced the ability to run Android apps on supported Chrome OS devices, with access to the entire Google Play Store. The previous Native Client-based solution was dropped in favor of a container containing Android's frameworks and dependencies (initially based on Android 6.0), which allows Android apps to have direct access to the Chrome OS platform, and allow the OS to interact with Android contracts such as sharing. Engineering director Zelidrag Hornung explained that ARC had been scrapped due to its limitations, including its incompatibility with the Android Native Development Toolkit (NDK), and that it was unable to pass Google's own compatibility test suite.
Custom Linux applications can be installed inside LXC virtual machines on some chromebook models, via the "Linux Apps" entry in the settings menu, or the vmc command in crosh. The feature is part of project Crostini, a Chrome OS initiative to provide a polished UI experience to run both command line and graphical Linux applications. It was noticed in the Chromium OS source code in early 2018. Early parts of Crostini were made available for the Google Pixelbook via the dev channel in February as part of Chrome OS version 66, and it was enabled by default via the beta channel for testing on a variety of chromebooks in August with version 69.
Remote application access and virtual desktop access
In June 2010, Google software engineer Gary Kačmarčík wrote that Chrome OS will access remote applications through a technology unofficially called "Chromoting", which would resemble Microsoft's Remote Desktop Connection. The name has since been changed to "Chrome Remote Desktop", and is like "running an application via Remote Desktop Services or by first connecting to a host machine by using RDP or VNC". Initial roll-outs of Chrome OS laptops (Chromebooks) indicate an interest in enabling users to access virtual desktops.
Early in the project, Google provided publicly many details of the Chrome OS's design goals and direction, although the company has not followed up with a technical description of the completed operating system.
Design goals for Chrome OS's user interface included using minimal screen space by combining applications and standard Web pages into a single tab strip, rather than separating the two. Designers considered a reduced window management scheme that would operate only in full-screen mode. Secondary tasks would be handled with "panels": floating windows that dock to the bottom of the screen for tasks like chat and music players. Split screens were also under consideration for viewing two pieces of content side-by-side. Chrome OS would follow the Chrome browser's practice of leveraging HTML5's offline modes, background processing, and notifications. Designers proposed using search and pinned tabs as a way to quickly locate and access applications.
New window manager and graphics engine
On April 10, 2012, a new build of Chrome OS offered a choice between the original full-screen window interface and overlapping, re-sizable windows, such as found on Microsoft Windows and Apple's macOS. The feature was implemented through the Ash window manager, which runs atop the Aura hardware-accelerated graphics engine. The April 2012 upgrade also included the ability to display smaller, overlapping browser windows, each with its own translucent tabs, browser tabs that can be "torn" and dragged to new positions or merged with another tab strip, and a mouse-enabled shortcut list across the bottom of the screen. One icon on the task bar shows a list of installed applications and bookmarks. Writing in CNET, Stephen Shankland argued that with overlapping windows, "Google is anchoring itself into the past" as both iOS and Microsoft's Metro interface are largely or entirely full-screen. Even so, "Chrome OS already is different enough that it's best to preserve any familiarity that can be preserved".
In preliminary design documents for the Chromium OS open source project, Google described a three-tier architecture: firmware, browser and window manager, and system-level software and userland services.
- The firmware contributes to fast boot time by not probing for hardware, such as floppy disk drives, that are no longer common on computers, especially netbooks. The firmware also contributes to security by verifying each step in the boot process and incorporating system recovery.
- System-level software includes the Linux kernel that has been patched to improve boot performance. Userland software has been trimmed to essentials, with management by Upstart, which can launch services in parallel, re-spawn crashed jobs, and defer services in the interest of faster booting.
- The window manager handles user interaction with multiple client windows much like other X window managers.
Chrome OS is initially intended for secondary devices like netbooks, not as a user's primary PC, and will run on hardware incorporating an x86 or ARM-based processor. While Chrome OS will support hard disk drives, Google has requested that its hardware partners use solid-state drives "for performance and reliability reasons" as well as the lower capacity requirements inherent in an operating system that accesses applications and most user data on remote servers. In November 2009 Matthew Papakipos, engineering director for the Chrome OS claimed that the Chrome OS consumes one-sixtieth as much drive space as Windows 7.
Google Cloud Print is a Google service that helps any application on any device to print on supported printers. While the cloud provides virtually any connected device with information access, the task of "developing and maintaining print subsystems for every combination of hardware and operating system—from desktops to netbooks to mobile devices—simply isn't feasible." The cloud service requires installation of a piece of software called proxy, as part of the Chrome OS. The proxy registers the printer with the service, manages the print jobs, provides the printer driver functionality, and gives status alerts for each job.
In 2016, Google included "Native CUPS Support" in Chrome OS as an experimental feature that may eventually become an official feature. With CUPS support turned on, it becomes possible to use most USB printers even if they do not support Google Cloud Print.
Chrome OS was designed with the intention of storing user documents and files on remote servers. Both Chrome OS and the Chrome browser may introduce difficulties to end users when handling specific file types offline; for example, when opening an image or document residing on a local storage device, it may be unclear whether and which specific Web application should be automatically opened for viewing, or the handling should be performed by a traditional application acting as a preview utility. Matthew Papakipos, Chrome OS engineering director, noted in 2010 that Windows developers have faced the same fundamental problem: "Quicktime is fighting with Windows Media Player, which is fighting with Chrome.":3
In March 2010, Google software security engineer Will Drewry discussed Chrome OS security. Drewry described Chrome OS as a "hardened" operating system featuring auto-updating and sandbox features that will reduce malware exposure. He said that Chrome OS netbooks will be shipped with Trusted Platform Module (TPM), and include both a "trusted bootpath" and a physical switch under the battery compartment that actuates a developer mode. That mode drops some specialized security functions but increases developer flexibility. Drewry also emphasized that the open source nature of the operating system will contribute greatly to its security by allowing constant developer feedback.
At a December 2010 press conference, Google claimed that Chrome OS would be the most secure consumer operating system due in part to a verified boot ability, in which the initial boot code, stored in read-only memory, checks for system compromises.
Chrome OS includes the Chrome Shell, or "crosh", which documents minimal functionality such as ping and SSH at crosh start-up. In the older Chrome OS versions originally in Acer C710 no bash-like shell abilities were provided. In the later Chromebooks such as Acer C720, bash is available from crosh, where the entire Linux filesystem can be found and explored.
In developer mode, a full-featured bash shell (which is supposed to be used for development purposes) can be opened via VT-2, and is also accessible using the crosh command
shell. To access full privileges in shell (e.g. sudo) a root password is requested. For some time the default was "chronos" in Chrome OS and "facepunch" in Chrome OS Vanilla and later the default was empty, and instructions on updating it were displayed at each login.
Release channels and updates
Chrome OS uses the same release system as Google Chrome: there are three distinct channels: Stable, Beta, and Developer preview (called the "Dev" channel). The stable channel is updated with features and fixes that have been thoroughly tested in the Beta channel, and the Beta channel is updated approximately once a month with stable and complete features from the Developer channel. New ideas get tested in the Developer channel, which can be very unstable at times. A fourth canary channel was confirmed to exist by Google Developer Francois Beaufort and hacker Kenny Strawn, by entering the Chrome OS shell in developer mode, typing the command shell to access the bash shell, and finally entering the command update_engine_client -channel canary-channel -update. It is possible to return to verified boot mode after entering the canary channel, but the channel updater disappears and the only way to return to another channel is using the "powerwash" factory reset.
Chrome OS on Windows
On Windows 8 exceptions allow the default desktop web browser to offer a variant that can run inside its full-screen "Metro" shell and access features such as the Share charm, without necessarily needing to be written with Windows Runtime. Chrome's "Windows 8 mode" was previously a tablet-optimized version of the standard Chrome interface. In October 2013, the mode was changed on Developer channel to offer a variant of the Chrome OS desktop.
At its debut, Chrome OS was viewed as a competitor to Microsoft, both directly to Microsoft Windows and indirectly the company's word processing and spreadsheet applications—the latter through Chrome OS's reliance on cloud computing. But Chrome OS engineering director Matthew Papakipos argued that the two operating systems would not fully overlap in functionality because Chrome OS is intended for netbooks, which lack the computational power to run a resource-intensive program like Adobe Photoshop.
Some observers claimed that other operating systems already filled the niche that Chrome OS was aiming for, with the added advantage of supporting native applications in addition to a browser. Tony Bradley of PC World wrote in November 2009:
|“||We can already do most, if not all, of what Chrome OS promises to deliver. Using a Windows 7 or Linux-based netbook, users can simply not install anything but a web browser and connect to the vast array of Google products and other web-based services and applications. Netbooks have been successful at capturing the low-end PC market, and they provide a web-centric computing experience today. I am not sure why we should get excited that a year from now we'll be able to do the same thing, but locked into doing it from the fourth-place web browser.||”|
After this 2009 statement Chrome browser rose to become the number one browser used worldwide.
- Comparison of operating systems
- Timeline of operating systems
- Instant WebKiosk
- List of operating systems
- zram – a Linux kernel feature
- Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc. Retrieved July 11, 2012.
- "Stable Channel Update for Chrome OS". October 26, 2018. Retrieved October 26, 2018.
- "Google Chrome". OmahaProxy CSV Viewer. Google.
- Davis McMahon (November 12, 2018). "Dev Channel Update for Chrome OS". Retrieved November 12, 2018.
- "Kernel Design: Background, Upgrades". Google. Retrieved September 7, 2011.
- Google. "Google Chrome OS Terms of Service". Retrieved September 5, 2012.
- "Kernel Design". The Chromium Projects.
- Vaughan-Nichols, Steven (June 18, 2012). "It's 2016, and Chrome OS is ascendant". Computerworld. Retrieved September 7, 2013.
- Enderle, Rob (May 12, 2011). "Why Google's Chromebooks are born to lose". Digital Trends. Retrieved September 7, 2013.
- "Packaged Apps - Google Chrome". developer.chrome.com. Retrieved 2016-01-26.
- "What Are Chrome Apps? - Google Chrome". developer.chrome.com. Retrieved 2016-01-26.
- "ARC Welder".
Package Android APKs for ARC (App Runtime for Chrome)
- Amadeo, Ron (September 11, 2014). "Chrome OS can now run Android apps, no porting required". Ars Technica. Retrieved 2016-01-26.
- "Chromium OS". The Chromium Project. Google. Retrieved 21 February 2016.
- "Developer FAQ". Google. Retrieved December 12, 2009.
- Brodkin, Jon (June 28, 2010). "Google Chrome OS creator takes job at Facebook, announces switch on Twitter". Business Week. Retrieved June 29, 2010.
- Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. Retrieved January 23, 2010.
- Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open source project". Official Google Blog. Google, Inc. Retrieved November 19, 2009.
- "Linux commands". The New York Times.
- Yegulalp, Serdar (December 5, 2009). "Google Chrome OS Previewed". InformationWeek. Retrieved December 6, 2009.
- Rapoza, Jim (December 3, 2009). "REVIEW: Google Chrome OS Developer Edition Provides Intriguing Look at Web-Only Computing". eWeek.com. Retrieved December 4, 2009.
- Kenyon, Chris (November 2009). "Google Chrome OS and Canonical". Canonical Blog. Retrieved December 14, 2010.
- "Google sets "late fall" release for Chrome". Reuters. June 2, 2010.
- "AOPEN collaborating with Google on new retail technology". AOPEN. Retrieved 11 March 2015.
- Martonik, Andrew (November 17, 2015). "Google and ASUS officially launch the Chromebit, available now for just $85". Android Central. Retrieved 2016-01-30.
- Lardinois, Frederic (April 9, 2012). "Google's Chrome OS Will Soon Look More Like Windows Than A Browser". Techcrunch. Retrieved June 2, 2013.
- Dignan, Larry (November 23, 2009). "Admob: Droid and Android army make big browsing splash". ZDNet. Retrieved December 1, 2009.
- Patel, Nilay (July 14, 2009). "Steve Ballmer calls Chrome OS "highly interesting," says Google "can't make up their mind"". Engadget. AOL. Retrieved November 28, 2009.
- Levy, Steven (June 7, 2011). "Jobs to PC: 'You're Busted!' And Other Notes From The OS Wars". Wired. Retrieved June 7, 2011.
- Krazit, Tom (November 20, 2009). "Brin: Google's OSes likely to converge". CNET News. Retrieved November 28, 2009.
- Olivarez-Giles, Nathan (March 13, 2013). "Google Replaces Android Boss Andy Rubin With Chrome's Sundar Pichai". Wired. Retrieved March 13, 2013.
- "Chrome OS can now run Android apps, no porting required". Ars Technica. September 11, 2014. Retrieved September 12, 2014.
- Bohn, Dieter (June 25, 2014). "Native Android apps are coming to Chrome OS". The Verge. Retrieved 2014-06-25.
- Alistair Barr (October 30, 2015). "Alphabet's Google to Fold Chrome Operating System Into Android". WSJ. Retrieved November 14, 2015.
- Sam Tran. "Chrome OS Will Be Merged Into Android - OMG! Chrome!". OMG! Chrome!. Retrieved November 14, 2015.
- Lockheimer, Hiroshi (November 2, 2015). "Chrome OS is here to stay". Retrieved November 27, 2013.
- Metz, Cade (June 9, 2010). "Google morphs Chrome OS into netbook thin client". The Register. Retrieved June 14, 2010.
- Sneddon, Joey-Elijah (February 24, 2014). "Chrome OS 33 Hits Stable Channel, Adds New 'First Run' Tour, Contact Search". omgchrome. Retrieved March 7, 2014.[self-published source]
- Rosenblatt, Seth (August 10, 1011). "Chrome OS goes offline, gets file manager". CNET download.com. Retrieved August 11, 2011.
- "Stable Channel Update". Chrome Releases. Google.
- Samson, Ted (May 16, 2013). "Google entices Chrome OS developers with prospect of native-like apps". InfoWorld. Retrieved June 5, 2013.
- "What Are Packaged Apps?". Chrome apps stable. Google. Retrieved June 5, 2013.
- "For Your Desktop". Chrome Web Store. Google. Retrieved January 23, 2014.
- "The Play Store comes to Chrome OS, but not the way we were expecting". Ars Technica. Retrieved 22 February 2017.
- "All Chromebooks debuting in 2017 and beyond will run Android apps". Ars Technica. Retrieved 22 February 2017.
- Zheng, Tim (23 January 2018). "Add Crostini experiment to field trial testing". chromium-review.googlesource.com. Retrieved 18 April 2018.
- "Crostini: A First Look At The New Linux Terminal For Chrome OS". chromeunboxed.com. February 26, 2018. Retrieved April 18, 2018.
- "Google Chrome OS – bullet proof?". Infosecurity. 6 (5): 6. July 2009. doi:10.1016/s1754-4548(09)70096-8. ISSN 1754-4548.
- "Linux apps on Chrome OS - an overview of its biggest feature since Android apps". xda-developers. 2018-04-25. Retrieved 2018-09-04.
- "Linux Apps Land On Beta Channel For A Lot Of Chromebooks". chromeunboxed.com. Retrieved 2018-09-04.
- Mathews, Lee (August 13, 2010). "Google Chrome's Remoting feature shows up in Chrome with enterprise implications". Archived from the original on 2011-02-07. Retrieved August 22, 2010.
- Claburn, Thomas. "Google Pleased With Chromebook Sales". InformationWeek.
- Thibodeau, Patrick. "Orlando tries out 600 Chromebooks, The Chrome OS-based laptops may fit into city's cloud strategy". Computerworld.
- "The Chromium Projects: Chrome OS". Retrieved July 2, 2011.
- "The Chromium Projects: User Experience". Google. Retrieved November 21, 2009.
- Stephen Shankland (April 10, 2012). "Google gives Chrome OS a less alienating interface". CNET.
- Caleb Garling (April 10, 2012). "Google Chrome OS Busts Out Of Browser With New Interface". Wired.
- Paul, Ryan (April 16, 2012). "Hands-on: getting work done with Google's new Aura interface for Chrome OS". Ars Technica. Retrieved April 17, 2012.
- "Security Overview: Chromium OS design documents". Google. Retrieved November 25, 2009.
- Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. Retrieved July 8, 2009.
- Mearian, Lucas (November 19, 2009). "Google Chrome OS will not support hard-disk drives". Computerworld. Retrieved November 21, 2009.
- Jazayeri, Mike (April 15, 2010). "A New Approach to Printing". The Chromium Blog. Google Inc. Retrieved April 16, 2010.
- Heater, Brian (April 16, 2010). "Google Talks Cloud-Based Printing for Chrome OS". App Scout. Retrieved April 16, 2010.
- Whitney, Lance. "Google moving closer to Chrome OS printing". CNET News. Retrieved April 17, 2010.
- "b793195a8a91fa9a17eaf4af0fa21fed4da4d9cc - chromium/src - Git at Google". chromium.googlesource.com. Retrieved 2016-09-17.
- "Issue 2117713002: Print directly to CUPS using the IPP APIs - Code Review". codereview.chromium.org. Retrieved 2016-09-17.
- Messmer, Ellen (March 2010). "Google sheds light on Chrome OS Netbook security". Retrieved March 8, 2010.
- Paul, Ryan (December 2010). "Google demos Chrome OS, launches pilot program". Ars Technica. Retrieved December 8, 2010.
- "Samsung Series 5 Chromebook". The Chromium Projects. Retrieved June 5, 2015.
- "Shell Style Guidelines". The Chromium Projects. Retrieved June 5, 2015.
When writing code that is used on developer systems or dev/test Chromium OS images, always use bash. For scripts that are used on the release Chromium OS image, you should be using POSIX shell.
- "Poking around your Chrome OS Notebook". The Chromium Projects. Retrieved February 6, 2011.
- "Boot and Install Chromium OS on Notebook". Keyables.
- Mark Larson (January 8, 2009). "Google Chrome Release Channels". Retrieved January 9, 2009.
- Mark Larson (January 8, 2009). "Dev update: New WebKit version, new features, and a new Dev channel". Retrieved January 9, 2009.
- Beaufort, François (January 3, 2014). "We all agree that Dev Channel is great to test out new…". Google+. Retrieved February 22, 2014.
- "Windows 8 browsers: the only Metro apps to get desktop power". TechRadar. Future Publishing. Retrieved November 13, 2012.
- Newman, Jared. "Google Chrome Gets Early Metro-Style App for Windows 8". PCWorld. IDG. Retrieved June 13, 2012.
- "Mozilla previews 'Metro'-ized Firefox for Windows 8". Computerworld. IDG. Retrieved November 13, 2012.
- "Firefox for Windows 8 enters Aurora channel with touch and gesture support". Engadget. Retrieved September 21, 2013.
- "Google is building Chrome OS straight into Windows 8". The Verge. Retrieved October 5, 2013.
- Keegan, Victor (July 10, 2009). "Can Chrome steal Microsoft's shine?". The Guardian. UK. Retrieved July 11, 2009.
- Bertolucci, Jeff (July 10, 2009). "Google, Microsoft Invade Enemy Territory: Who Wins?". PC World. Retrieved July 11, 2009.
- Bradley, Tony (April 2010). "Five Reasons the Google Chrome OS will Flop". Retrieved April 21, 2010.
- "OS Statistics". w3schools.com. Retrieved January 3, 2017.
- "PC Platform is Evolving, Not Dying: Chromebooks and Ultraportable PCs to Gain Volume Market Share in 2016" (Press release). 9 March 2016.
|Wikimedia Commons has media related to Chrome OS.|