Chrome OS may jump straight to eating Android Pie rather than munching on Oreo

A recent comment posted on the Chromium board indicates that Chrome OS may completely skip Android “Oreo” (v8.x) and support Android “P” (v9.x) when it arrives later this year. Right now, compatible Chromebooks support Android “Nougat” (v7.x) while smartphone manufacturers are still working on rolling Oreo out to customers before the end of 2018. 

The developer preview of Android “P” is already available for the Pixel, Pixel XL, Pixel 2, and Pixel 2 XL smartphones. The company isn’t expected to officially reveal this next version of Android until the Google I/O developer conference in May, followed by an initial public release possibly in August. As with Android “Oreo,” the rollout across millions of devices will be a long update process well into late 2019. 

Despite the web-centric nature of Chrome OS, Google introduced support for Google Play and Android apps in 2016 providing many Chromebook owners with the best of both worlds. Currently, Chromebooks supporting Android apps are still upgrading to Android 7.1.1, but comments posted on the Chromium project don’t mention Android “O” whatsoever. Instead, the version jumps from “N” to “P” and here’s the latest example: 

arcnext: Hook up _P tests to androidcontainerpi builds. 

The comment follows another one posted in early March, stating: 

arcnext: Hook up _P tests. 

Split tests into N and _P to bootstrap CQ/PFQs. 

As for the dessert that will be associated with Android 9.0, Google may stick with Android Pie as seen in the comment listed above. “Parfait” would be a more fitting choice given Google used cold deserts with three other Android builds: v2.0 “Éclair,” v2.2 “Froyo,” and v4.0 “Ice Cream Sandwich.” But given that Google cycles through an assortment of deserts, Android Pie works just as well. 

With the possible upcoming support for Android “P,” is Google planning to merge Chrome OS and Android into one operating system? Perhaps not. The company still stands behind its opinion that the two serve different users. On the Chrome OS front, the platform was originally designed for laptops and desktops used by students. It supports apps that mostly depend on the internet and cloud services. Even more, software updates are specifically managed by Google. 

Meanwhile, Android started on phones but moved into cars, tablets, Internet of Things devices, TVs, and so on. The platform supports downloadable apps that mostly work offline save for email clients, cloud storage services, and so on. Updates are managed by device manufacturers (Samsung, Huawei) and mobile networks (AT&T, Verizon). 

“I think we’re very fortunate as a company to have two very successful platforms each in their own way and in their own segments,” Senior Vice President of Android, Chrome OS, and Play Hiroshi Lockheimer said in late 2016. “For us, there’s no point in merging them. They’re both successful. We just want to make sure both sides benefit from each other, so that’s why we brought Google Play from Android over to Chrome OS.” 

You will see a lot of “cross-pollinating” between the two platforms, but not an official merge, he added.