An introduction to Google Glass and Glassware design and development. It includes a prototype built by Nurun SF using the Google Mirror and Fitbit APIs.
A few notes on the slides:
Slide 2: video URL http://bit.ly/125gztQ. This video shows the basics of navigating and reading content. It’s a good introduction, but there are a few more things to know...
Slide 4: An a advantage of Glass as a wearable device is hands free operation. For example, when a new card arrives, an audio chime is played and the user can open the card either by touching the temple or by tilting your head back.
Slide 5: In addition to gestures, voice commands are sometimes available to support hands free use. Speaking to Google Glass is entirely optional, all voice commands are also available through the touch pad.
Slide 8: The form-factor has great potential to present content without pulling you out of context. It is readily available, not in your bag or pocket. It overlays image and audio over the environment.
Slide 9: The Mirror API is the standard way to develop applications today. The interaction model strictly follows the core UX of Glass (timeline cards and actions). Web applications offer a way to break through the boundaries of the Mirror API and Native Android applications (API level 15) are useful for prototyping more extensive Glassware experiences. It is currently unknown how native apps will be discovered, installed and launched on the device.
Slide 11: A Glassware server sends content to Glass via Google servers. Google also manages responses from the user, posting data back to the Glassware server based on specifics provided in a subscription created using the API.
Slide 12: These cards are in the Mirror API documentation as examples of typical layout and information density.
Slide 17: video URL http://vimeo.com/74146772
Slide 19: The dashboard is inserted when you install the prototype. A pinned card is easier to find in the future (it appears to the left of the home screen). The card cannot be pinned by default, the user must pin it themselves.
Slide 21: When a card is shared, a copy is made and inserted into the Glass timeline, Google+ is given ownership and updates it as needed to work with their Glassware application.
Slide 28: Rather than inserting multiple dashboard cards, we update a single card. We can also use it to prompt the user to do different things (such as pin the card, or link their Fitbit account).
Slide 29: In our prototype, we confirm that water has been logged by updating the status screen. An alternative would be to insert a card with the confirmation, but that would be unnecessarily noisy.
Google Glass and the Mirror API is ideal for delivering glanceable displays of data at key moments throughout the day, adding a layer of feedback and encouragement to the Fitbit experience.