Chromebooks, ChromeOS and Google Chrome browser news
We all know the Android app experience on large screen devices isn’t ideal. That’s the likely reason Google shared enticing data and tool improvements for developers to make better Android apps on Chromebooks
Linux opened the door to Android development on Chromebooks thanks to Android Studio support. Now, a handful of devices open it further with support for Android device emulation within Chrome OS.
There’s a number of new gestures, visual changes and improvements for both Chromebook users and developers in Chrome OS 81. Here’s what you need to know.
Need a handy guide for getting a Chromebook configured for web or app development? Check out the Chrome OS Developer Toolbox, which is filled with tips, configuration steps and links to tutorials.
Android Studio developers using a Chromebook will have an easier time of sideloading their app to the Android container once Chrome OS 81 arrives.
At long last, Google is bringing the ability to sideload Android apps to Chromebooks. The feature is planned for Chrome OS 80, helping both developers and power users alike.
After four months in a preview release, Android Studio arrives on Chromebooks with official support. There’s still no Android device emulator, but the USB debug feature of Chrome OS lets you install and test apps on your connected phone.
Recent Geekbench listings suggest the next Pixelbook, likely Atlas, will use the same chipsets as the Pixel Slate. That doesn’t make sense for a few reasons.
Most people don’t need a super high-end Chromebook but if you do, there’s a new choice to consider: The Acer Chromebook Spin 13 can be had with a Core i7 U-series chip and 16 GB of RAM.
Originally planned for between Chrome OS 69 and 72, a recent Chromium developer comment suggests that the ability to sideload Android apps on a Chromebook isn’t even likely for Chrome OS 75.
Recent benchmarks have appeared showing a Pixelbook with Android 9 running on 8-gen Intel processors that support Android Studio. Could the Pixelbook 2 simply be an internal refresh with little change on the outside?
