Description:
Enable the 'Access to Android applications' setting for G Suite for Education customers. This option already exists for non-education domains. Reference: https://support.google.com/chrome/a/answer/2657289?hl=en

Use case:
Currently, Android support in education domains is limited so that only approved apps are available for students to install. This is desirable for our students, but unnecessarily limiting for staff users. Teachers need to be able to discover and try out apps on their own, in order to find apps that will meet learning objectives for their students, and then request the Google administrator to enable those vetted apps for students. Since this is a user setting, it would be very easy to allow this setting for our Teacher OUs, but leave it disabled for our student OUs.

Motivation:
As an education G Suite Domain, the recent addition of Android support on Chromebooks is very exciting, and we have purchased ~500 Chromebooks that support this feature (displacing iPads). With our iPads, we had a procedure in place where teachers could use their teaching iPad to download apps at their discretion and try them out, even letting students use them on the teacher's iPad, to evaluate them. Once they determined that it would meet the needs of their students they would notify IT and we would push that app out to all student iPads, as the student iPads did not have the ability to discover and install iPads on their own. With the current Android options in G Suite, there is no way to allow teachers to discover apps and try them in order to recommend them for install for students. With no way to try apps, there's no way to know what should (or shouldn't) be installed, crippling the usefulness of the feature. Considering that the setting to control this behavior already exists and is only removed for education domains, it seems like it would be a simple thing to allow the setting for education domains as well, and allow education IT admins the choice to use it if it makes sense in their organization.

Existing workarounds:
I haven't tried it, but I guess a workaround is for us to allow personal Google accounts from outside our domain to login on our Chromebooks. Then teachers could login with a personal Google account to install and test apps. This seems like a terrible idea, because it could potentially expose personal teacher information (e.g. emails) to students who are using the device under the teacher's personal account in order to try out apps. Teachers could instead create a new Google account specifically for this purpose, but now they have another account to juggle. In the end this convoluted process will just sour teachers on the Google experience compared to what they were used to with the iPads.