Android Apps on Chromebooks

One of the most significant announcements coming out of the Google I / O developers conference this past May was the launch of Android Apps for Chrome. While this announcement didn't make the headlines of the conference, it has significant implications for educators and the classroom.

Early Access to Android for Chrome

An early release of the Google Play Store for Chrome was expected to come to three devices in June: the Asus Flip, Acer R11, and Chromebook Pixel. As of this post, only the Asus flip has received access.

The Google Play Store for Chrome can currently only be accessed by switching to v. 53 of Chrome which is currently in developer preview. The developer release channel is used to test out new features however it is fairly unstable and not for the faint of heart.

Android for Chrome was expected to progress through the Chrome release channels as follows:

• Developer - June 2016
• Beta - July 2016
• Stable - August 2016

This progression seems to be delayed, however, as not all of the selected devices have been updated to v. 53. At this point, it is unknown if Android for Chrome will be released prior to the start of the 2016-17 school year. It seems unlikely.

Android on Chrome - First Look

I have had an opportunity to test out some Android Apps on my Asus Flip Chromebook. The experience is interesting as it is a bit weird to be accessing The Google Play Store on laptop. I am super excited about having access to new tools that were previously unavailable on Chromebooks (e.g. Adobe Creative Suite, Skype, and Minecraft).

Android Apps do not load in a new tab like Chrome Apps do. Instead, they open in a floating window roughly the size and dimensions of a mobile phone. While this floating window can be expanded, the visuals do not always support full screen mode. Android Apps can't be docked into the Chrome browser, pinned, etc.

One interesting thing to note is that at this time, Google Play does not support account switching. I log into my Chromebooks using a Gmail account, but typically work within my Google Apps for Education account. The Google Play Store recognizes my Gmail account and will not allow me to switch to a secondary account; something that I can do on my phone or if I visit the Play store via the Chrome browser.

Here are a few screenshots:

Not all Chromebooks will support Android Apps. Generally, devices purchased within the last 2 years will be compatible. A list of supported devices is available here. 

The best thing about Android for Chrome is that App developers don’t have to do anything to make their app compatible with Chromebooks. Interoperability is automatic. This is a vast improvement over past attempts by Google to integrate Android and Chrome as they all required modifications for apps to run on a Chromebook.

Why should educators care about Android on Chrome?

Why is this a big deal for teachers, students, and administrators? Five reasons: 

1. More Quality Apps Available - there are over 2 million Android apps.
2. Increased Touch-screen capabilities - touch-screen is the future of all devices however many web apps are not [currently] touch optimized. Touch optimized apps are easier for younger students to use and are great for math and science classrooms.
3. Increased developer focus - If it is easy to make your Android app run on the 10 million Chromebooks in schools around the world, developers will create NEW tools for the classroom. There are more Android developers than web app developers.
4. Access to previously unavailable tools - There are many tools that are NOT currently web-optimized and can't be run on a Chromebook. Adobe Creative suite, Skype, and Minecraft are three popular examples. These titles DO have Android apps.
5. Increased offline capabilities - While Chromebooks are designed to run on the web, there are still many students who do NOT have web access at home. Android apps are built with offline capacity, making them helpful tools when not connected to the web. 

Unanswered Questions

While the availability of Android on Chrome opens up lots of exciting possibilities, there are quite a few unanswered questions. 

1. Administrative Controls - There are lots of Android apps that are not classroom appropriate. How will district administrators manage Android apps on Chrome? We don't know. Will it similar to Chrome App management? Similar to the old Google Play for Education?
2. Paid Apps - There are also far more paid apps for Android than there are for Chrome OS. Overall, I think that paid apps are fine. I would rather pay for a quality app than deal with lousy, free apps. However, there needs to be a very simple method for schools to purchase and deploy paid content. Google Play for Education was outstanding (schools could pay via PO and distribute apps via Google Groups) and I hope the same features are made available.
3. App compatibility - Not all apps are compatible with Chromebooks. There are a few that will not work, but I don't know why. We need a greater understanding of the specs required to run Android apps.
4. App Overload / Overlap - Instructional coaches and technologists will need to begin thinking about "app overload syndrome". There are so many different ways to get apps now - Chrome Webstore, Google Play, Drive Apps, Drive Add-ons, regular websites etc. How does a teacher decide if she should visit mindmeister.com, install Mindmeister for Chrome, Android or the Docs Add-on? There is a really possibility of increased confusion and frustration with the many different channels that are available for classroom content. 

Have you had an opportunity to play with Android on Chrome? What are you initial thoughts? 

Don't have access yet? What questions would you like answered?

Additional Information and Resources: 

• Google Play is coming to Chromebooks [Chrome Blog]
• Bring your Android Apps to Chromebooks [Android Developer Blog]
• Supported Devices
• How to enable developer mode