We’re excited to announce initial support for Chrome OS within the Android developer environment. Starting in Unity 2021.2.0a14 Alpha you’ll be able to add Chrome OS as a supported device alongside Android in the Unity Editor. Chrome OS has been growing rapidly - Chromebook shipments surpassed 30 million units in 2020. We believe that adding support for Chrome OS devices presents an interesting opportunity for Android developers to further extend their game’s reach. There are 2 new Target Architectures that have been added for Chrome OS, x86 and x86-64. Select these, in addition to the existing ARM options, to natively support the full spectrum of Chrome OS devices. We’re also working on bringing this functionality to 2020 LTS later in the year. You can find the all the details in the official documentation A couple things to keep in mind: Keyboard and mouse support: Best practice is to write your own input controls because your app will receive all mouse and touchpad events. By default, on Chrome OS, an app will miss mouse positional updates (when a button is not pressed) and both mouse or touchpad scrolling events and button presses. By writing your own input controls you create a better user experience and can take full advantage of touchpad events. You can write your own input controls by unchecking the Chrome OS Input Emulation box. Chrome OS also supports emulation for basic keyboard and mouse functionality. Depending on your title, the emulation functionality may be sufficient. Windowing: Currently, windowing will be full size only, with re-sizing to come in future releases and updates. Monetizing your app: Since any game on Chrome OS will go through the Play Store, monetization, including ads and in-app purchases work in the same way. Known issues: Considering this is launching in our 2021.2 Alpha there are a few known issues we think you should be aware of (please see the release notes and documentation for an exhaustive list). x86 and x86_64 architectures are only supported for running on Chrome OS devices, not any other Android device with an Intel processor. Script debugging and profiling is only supported over WiFi or Ethernet (where available). Profiling and debugging in Android Studio will only work if your target device is in developer mode. See this document for more information. https://chromium.googlesource.com/chromiumos/docs/+/main/developer_mode.md We’d also like to get feedback from the community about bugs, and other concerns. Please feel free to start new discussions in our dedicated Chrome OS forum!