Hacker News Reader

Comment by ambiate | Hacker News Reader

I'm actually wearing Glass for my last day too.

First off, I do not have toys to communicate with Glass. I realize that Glass is too early. There are not enough data dumping devices available at decent prices. Withings, vehicle data, health data, all the things people try to keep private. That kind of data is what would be useful with Glassware.

The lack of a SDK and depending on RESTful services. I want to toy with sensors too. Delayed gratification does not work. Where are my long nights of programming?

Battery life and destroying my cell's data plan are also issues. I'll miss watching people's faces light up when they try it on.

View on HN

The Android SDK works fine with it. Turn on debugging mode on the Glass and code away. Sensors are no problem: http://neatocode.tumblr.com/post/49807659612/secret-sensors-...

Google even flat out stated at Google IO that the upcoming GDK will just be the Android SDK plus extra classes you compile against.

OK, now you have got me interested. I really have not heard anything about this. You may have just made my week. I was getting quite depressed about the money I wasted.

I can only run APKs on Glass while in USB debug mode? There is no way to actually execute the program again without being in the debugger, correct?

I've only run APKs in USB debug mode, but the main "OK glass" screen is just an Android app, which I think is started via an Intent, so I suspect you could hook this and override it.

You can install a third party launcher on Glass. Here's one that lets you switch between launching APKs and the standard Glass interface pretty easily:

https://github.com/kaze0/launchy

There's also a Mirror API based Glass app that lets you launch apks, but it's a bit more work setting up. It actually requires you install a couple APKs as well: https://pontedivetro.appspot.com/

There is a custom launcher on github called launchy.

Glass Development Kit which allows apps to get real-time access to sensors is coming later this year.

Can't you create a feedback loop with sensors, an android app and the mirror api? I know it's a kludge, but if your mobile app posted data to your web server, your glass could poll it that way. Of course, the data and battery life concerns only get worse...

At this point, without voiding my warranty, I can basically poll data, reflect data through options, and use voice commands (that barely understand me) to reflect data.

I have seen interesting manipulation of the Mirror API to make voice commanded games. I tend to get unreliable ping pong times for real time related materials. Sometimes a card opens instantly, sometimes it takes up to 15 minutes.

That was my basic idea. Device A connects through bluetooth and uploads data to Phone. Phone relays to web service. Web service relays to Glass. It works. Google App Engine/Mirror API is just not my cup of coffee.

Glass, or some offspring, has the potential to be amazing. I really cannot wait to see what comes of this. A beta device utilizing a RESTful API... I knew what I was getting into, but once I got it, there just was not anything I wanted to feed to Glass. Glass hungers.

Reply on news.ycombinator.com