+mario martinez asked for some details about native Glass app development. I too was underwhelmed with the Mirror API. On paper it seems like the right choice, give developers a nice simple API that is going to be hard to abuse and hope the users and dveelopers like that kind of stuff. Unfortunately, micro-webpages are just not exciting and gives little more functionality than I could get with a smart watch.

The GREAT news is, that despite being completely undocumented, that there is a way to upload typical Android APKs. Debug mode is an option buried inside of settings that you can enable to gain ADB access. YAY!

You are flying a bit blind here and have no SDK and no documentation. Decompiling the stock apps is going to be a must for anyone wanting to build a great Glass experience. It's simple to use typical Android views to create your apps, but those are not designed for the Glass experience. There's quite a few custom views that GlassHome uses to create a great user experience. GlassHome doesn't act as a launcher, so installed apps won't be relaunchable without a dev tool, but I'm working on solving that!

If you install a completely unstyled app, you will notice that you see the stock Android notification bar and clock and icons. This, along with a few other things, leads me to believe that they haven't stripped much, if anything, out of Android for Glass.

Android on Glass is supposedly 4.0.4, however it appears that guest mode is available via the multi user mode that did not appear in code until Android 4.1 and was not even released publicly until 4.2. Very strange.

There's quite a few new broadcasts going around and even some new sensors. Native Glass development is, by far, the most exciting development that I've done in years.
Shared publiclyView activity