2

Is there an efficient way to distribute beta apps for Google Glass? Our current method is to email around apk files and then guide the tester through the shell commands... very painful. (Adb Chrome plugin helps a bit)

I've searched and don't see anywhere that the Play Developer console supports Glass apps, let alone distribution of beta apps.

I've reached out to 'Beta by Crashlytics' and am awaiting their reply. UPDATE 9/5/2014: They do not have Glass version at this time.

I've reached out to the 'Glass at Work' program and am awaiting their reply. UPDATE 9/5/2014: Not integrated with Google Play. Need to Submit Glassware to set up specific Whitelist. Google Group integration possible.

Any other options people have had success with? Something like...

  1. gradle plugin to push latest apk to Drive/Dropbox (easy for developer)
  2. tester plugs in Glass usb and double-clicks script to install known packages from Drive/Dropbox (easy for tester)

Any examples or ideas welcome. Thanks!

aaronvargas
  • 12,189
  • 3
  • 52
  • 52
  • You can create a simple java program which executes the shell commands by itself so the tester should only launch it and say where is the apk – Marco Acierno Sep 03 '14 at 00:21

2 Answers2

1

If you intend for this app to be distributed through MyGlass, your best bet is to do the following:

  1. Submit it for review as soon as you can.
  2. Once it is being reviewed, request a whitelist. This will let a few selected people to be able to access it via MyGlass.

This isn't quite the same as the beta channel through the Play Store, but it has some similarities.

Prisoner
  • 49,922
  • 7
  • 53
  • 105
  • That's great info, but we're not ready to submit it for review yet. – aaronvargas Sep 03 '14 at 17:03
  • 1
    If you're talking "beta testers", you might be. The Glass review process is different than the review process for other app stores - at this point, it is more to help people tune their Glassware for Glass rather than as a gatekeeper. It isn't something you do when your app is "done", it is something you should do as your app approaches that step. – Prisoner Sep 03 '14 at 17:21
0

The easiest way to do this if your app is not ready for submission is the following. (Dropbox used, Google Drive would be similar)

1) Add a gradle target to your build.gradle

// copy the apk file to shared dropbox
task pushBeta << {
    println "Beta copy starting..."
    copy {
        from("${buildDir}/outputs/apk") {
            println "Copying ${project.name}-debug.apk"
            include "${project.name}-debug.apk"
        }
        into("${System.properties['user.home']}/Dropbox/apk")
    }
    println "Beta copy complete"
}

2) Share the dropbox folder with your testers (install the dropbox sync app on yours/their local machines)

3) Add a script to dropbox folder for install:

Windows (install.bat)

adb install -r myapp-debug.apk
sleep 5

Mac (install.command) - First time, hold control key, click, and select "open". Subsequent double-clicks should then work

set -x
cd `dirname $0`
adb install -r myapp-debug.apk
sleep 5

4) Have your tester plug in Glass via USB. Double-click script. (They have to have adb installed and debug enabled, of course)

5) push new beta versions using gradle pushBeta or add a run config to Android Studio to do the same.

aaronvargas
  • 12,189
  • 3
  • 52
  • 52
  • This has been working great with my testers. There are a couple advantages to this method vs Play beta testing. 1. You can add multiple APKs to the script so your testers get an updated set of software all at once. 2. Dropbox syncs in seconds vs HOURS on Google Play! – aaronvargas Sep 18 '14 at 01:40