Timothy Jordan at SXSW Glass Talk

Timothy Jordan at SXSW Glass Talk

A while back, Timothy Jordan did a presentation at SXSW on Google Glass and the Mirror API that will be used to make applications for Glass.  In the video, Jordan talk about how the user interface is used and sample bits of how the Mirror API is used to write apps.

Watch the video below and tell us what you think of it!  Any of you ready to start developing for Glass?!

Timothy Jordan posted the following on his Google+ page about the event:

“A few weeks ago at SXSW in Austin, TX, I gave developers a sneak peek at the Google Mirror API, which is what they’ll use to build services for Glass.  With the presentation, we set out to help developers and entrepreneurs start imagining what they could do on Glass.

The Mirror API is a cloud platform that uses OAuth 2.0 and REST as an architecture for delivering a new class of experiences to people using Glass.  We walked through the basic building blocks of the API: timeline cards, menu options, share contacts, and subscriptions.  We then demonstrated some early uses of the Mirror API on Glass that were built by Evernote, The New York Times, Path, and our own Gmail team.

Developing for this type of device is a little different because you’re wearing it and it’s a very intimate experience.  So we also gave would-be Glass developers some recommended guidelines:

Design for Glass – The Glass design is unique and fundamentally different than existing mobile platforms.  It’s important to build and test specifically for Glass to create a great service.
Don’t get in the way – Services should be there when you want them and out of the way when you don’t.  They should never take precedence over what else the user may be doing.
Keep it timely – Glass is most effective when in-the-moment and up-to-date.  User requests should be handled immediately and information should always be fresh.
Avoid the unexpected – Giving users unexpected and unpleasant functionality is bad on any platform, but particularly bad on Glass given how close it is to the user’s senses.

For more, watch the video on this post.  Keep in mind that we haven’t launched the Mirror API yet; we’re still building it and getting feedback from a small group of testers. Stay tuned for more updates in the coming months.

Please note, unfortunately the demo & slides stream at SXSW wasn’t recorded. The demos in this video were redone to match the presentation.  Please forgive any slight discrepancies.”

Sarah Price (Google Glass Community Advocate) has shared the post above and has given her insite:

“I’m not a developer, and I’m not a programmer. My coding abilities consist of an intro Java class I took about a decade ago and some self-taught HTML and CSS.

Yet (with a bit of Python syntax help from my more technical friends 😉 I was able to build a working Glass service in just a few hours. That’s how easy the Mirror API is to use. My service was super simple, but check out the cool stuff in this video that people have been building with Mirror.

Can’t wait to see what everyone will build for Glass.”

With Sarah’s comments as evidence, it sounds like Glass will be extremely east to develop on with the use of the Mirror API.  Myself, as a Glass Explorer, cannot wait to receive my Glass and start developing on it!

Source | GoogleDevelopers | Timothy Jordan | Sarah Price

Share on Facebook0Google+1Tweet about this on TwitterShare on Reddit0Share on LinkedIn0Pin on Pinterest0Email to someone
Justin Duino

Justin Duino

(Founder | Editor-in-Chief) - I am currently a student at the University of Nevada, Reno getting my degree in Computer Science.I have been fortunate to work with some brilliant people in the technology industry and plan to continue so for the rest of my life.I am currently using a Nexus 5, a Nexus 7 (2013), and a Nexus 10. Additionally, I am one of the first Glass Explorers with Google Glass and loving it!
Justin Duino

Warning: Parameter 1 to W3_Plugin_TotalCache::ob_callback() expected to be a reference, value given in /home3/androin7/public_html/wp-includes/functions.php on line 3509