Developing and Testing for Google Glass

Google Glass is shipping and first generation users can expect to have the newest mobilewear tech in their hands soon. But what good is a new device if it doesn’t have many apps? As it turns out, you won’t have to wait long¬† for Google Glass apps – er, “Glassware.”

While things will likely start slowly at first (TechCrunch is reporting that only developers with a physical Glass device will be able to access the Glass API for the time being), Google has added a Glass section to its developers site. The site gives potential developers, testers and other interested parties a look at how Glassware (aka, apps) will work and what Google expects from third party developers.

In addition to the API, quick start guides for Java and Python and walk-throughs of several key Glass features, the site also outlines best practices for Glass in general, its user interface and best performance tips. The best practices all boil down to four main points Google is doing its best to promote:

  • Design for Glass – Design, build, and test your application specifically for Glass to ensure that the user experience is appropriate.
  • Don’t get in the way – Glass users expect the technology to be there when they want it and out of the way when they don’t. Don’t be too frequent and loud with notifications when the user doesn’t expect it.
  • Keep it timely – Glass is a platform that is most effective when in-the-moment and up-to-date.
  • Avoid the unexpected – Surprising the user with unexpected functionality is bad on any platform, but especially on Glass given how close it is to their daily experience. Be honest about the intention of your application, what you will do on the user’s behalf, and get their explicit permission before you do it.

 

Google understands the importance of in-the-wild testing – and it practices what it preaches!

Leave a Reply

Your email address will not be published. Required fields are marked *