Mike from the ChromeOS team explained plans for integration with Android
From Mike's response, several key points provide a clearer understanding of the potential transition of ChromeOS to the Android platform:
Focus on integration, not a full transition: Mike emphasizes that the project aims to continue merging technologies between ChromeOS and Android. Examples include adopting the ChromeOS update system in Android and using Android's Bluetooth stacks in ChromeOS. This suggests that Google is working on mutual integration rather than making ChromeOS entirely dependent on Android.
No Android fork: Mike clarifies that Google does not plan to create a separate branch of Android for ChromeOS. This means that components already in AOSP will remain in AOSP, maintaining the platform’s openness.
Uncertain timelines and details: Current work is still in the stages of discussions, testing, and experimentation, indicating that the project is far from completion. Most questions remain unanswered because decisions have yet to be finalized.
ChromeOS FІех will not be abandoned: Google has assured news outlets that ChromeOS FІех will continue to exist despite the ongoing integration efforts. This demonstrates that the company values users interested in extending ChromeOS to older hardware.
No public discussion of details: Mike hints that, for various reasons, official answers about the future of integration won't be provided on technical mailing lists. This is likely to avoid confusion among users and to ensure consistent messaging.
Conclusions:
Google does not plan a complete transition of ChromeOS to Android but continues to enhance their integration.
Timelines and specific details remain uncertain.
The project is focused on maintaining ChromeOS's openness and adaptability to support both old and new devices.
Users and organizations reliant on ChromeOS should not expect drastic changes in the short term.
Thus, the future of ChromeOS, based on current information, seems to be about gradual evolution rather than a revolutionary shift.
Source: https://groups.google.com/a/chromium.org/g/chromium-os-dev/c/wH6iXtTSndE