61–70 of 81 posts
Look hopefully they'll improve on this a lot, but lets be honest, this API is pathetic. If there are significant technical (power, weight, etc) reasons why this is all that can be done, then they probably aren't ready for prime time. I'm trying to stay positive and imagine the future for this product is bright, but wow wow wow this is bad.
This is so exciting. Just how a completely new user experience paradigm was uncovered when high quality touch screen devices like iPhone etc. first launched, this is yet another milestone in how we will continue to interact with the petabytes of data that we as mankind have digitized. It's worth pondering how significantly new I/O devices change the game -- the first tty, the commercial keyboard & mouse, the touch sc…
> It's worth pondering how significantly new I/O devices change the game -- the first tty, the commercial keyboard & mouse, the touch screen, multi-touch trackpads, and voice activated smartphones. This comment actually explains my complete disinterest in Glass :) I don't see how voice-activated smartphones have changed the game yet, IMHO they're in the same league as Glass - "this might be worth it later" (especiall…
Yes it does. It completes the connection between what you see and the rest of your digital world. That's significant.
I've been a Google Glass skeptic. But I just got back from Mexico, where I was walking all over waving my phone at various signs so Word Lens could translate them for me... skeptic no more! Word Lens is a killer app for the platform. Except now I see that there's no API to access the camera. Seems like a huge mistake.
No camera API access? That's ridiculous! Not only does it restrict about 70% of the possible usefulness of a head-mounted computer (so it's basically just a fancy news-feed display), but it'll allow competitors to move into the arena having a clear advantage. The only reason I see for Google to be doing this is resource allocation, but I feel like image processing could be offloaded to a linked smartphone, if necessa…
I can't find any info on how to write a Glass app that actually interacts with the camera or does geolocation. Am I missing something?
You can get a user's geolocation ( https://developers.google.com/glass/location ). Couldn't find anything about the camera. However, the API doesn't seem to offer any way to run code on the actual device aka "apps".
This is... pretty seriously disappointing, if it's supposed to be the whole thing (or close to the whole thing). I'll give them the benefit of the doubt and assume that they're going to publish the rest later, and not deliberately hobbling it to prevent the public from getting creeped out by the hardware's capabilities.
hm... only support for java and python. I hope they release a version for Go since it is Google's language.
hm... only support for java and python. I hope they release a version for Go since it is Google's language.