The document provides an introduction to developing glassware applications using the Mirror API and Glass Development Kit (GDK). It explains that the Mirror API is used to create static timeline cards through a web-based application, while the GDK allows developing live cards and immersive Android apps that run directly on Glass. Examples of each are presented to illustrate the differences between the two approaches and how they integrate into the Glass user interface.

1. The Glass Class:
Introduction to Glassware
Development with Mirror API & GDK
July 7th – 11th 2014
Mark Billinghurst, Gun Lee
HIT Lab NZ
University of Canterbury

2. An Introduction to
Glassware Development with
Mirror API & GDK
Gun Lee
* Images in the slides are from variety of sources,
including http://developer.android.com and http://developers.google.com/glass

3. Glassware
 https://glass.google.com/glassware

4. Timeline Metaphor

5. A Card in the Timeline

6. Glassware and Timeline

7. Glassware and Timeline
 Static Cards
 Static content with text, HTML, images, and (link to)
video.
 e.g. notification messages, news clip
 Live Cards
 Dynamic content updated frequently.
 e.g. compass, timer
 Immersions
 Takes over the whole control, out from timeline.
 e.g. interactive game

8. Glassware Development
 Mirror API
 Server programming, online/web application
 Static cards / timeline management
 GDK
 Android programming, Java (+ C/C++)
 Live cards & Immersions
 https://developers.google.com/glass/

9. Mirror API
 REST API
 Java servlet, PHP, Go,
Python, Ruby, .NET
 Timeline based apps
 Static cards
- Text, HTML, media attachment (image & video)
- Standard and custom menu items
 Manage timeline
- Subscribe to timeline notifications
- Sharing with contacts
- Location based services

10. Mirror API based Web App
3. Insert a static card
User sees the card
Glassware Web app
https://developers.google.com/glass/develop/mirror/stories

11. https://developers.google.com/glass/develop/mirror/stories

12. https://developers.google.com/glass/develop/mirror/stories

13. Develop with Mirror API
 Create a project on Google APIs Console
 Prepare a web server
 https callback for OAuth 2.0
 Minimum storage for credentials
 Create a web application
 Java servlet, PHP, Go, Python, Ruby, .NET
 Implement Oauth 2.0 authentication
 Use Mirror API to make REST API calls
- Wrapper classes/methods provided

14. Mirror API in Raw HTTP

15. Mirror API
 Java
 Python
 PHP

16. Example

17. Example
 https://hello-glass-mirror.appspot.com

18. Example
 https://hello-glass-mirror.appspot.com

19. Example
 https://hello-glass-mirror.appspot.com

20. Example
On your Glass

21. GDK
 Glass Development Kit
 Android 4.4.2 + Glass specific APIs
 Use standard Android Development Tools

22. GDK
 GDK add-on features
 Timeline and cards
 Menu and UI
 Touch pad and gesture
 Media (sound, camera and voice input)

23. Live Cards vs. Immersions
 Live cards display frequently updated
information to the left of the Glass clock.
 Integrate rich content into the timeline
 Simple text/images to full-blown 3D graphics
 Immersions let you build a user
experience outside of the timeline.
 Build interactive experiences
 Extra control, less user input constraints

24. Live Cards

25. Immersions

26. Live Cards vs. Immersions

27. Develop with GDK
 Android 4.4.2 (API 19) GDK Preview from the
Android SDK Manager.
 Project settings:
 Minimum and Target SDK Versions: 19
 Compile with: GDK Preview
 Theme: None (allows the Glass theme to be applied.)
 GDK samples
 File > New Project > Android Sample Project
 On Glass, turn on USB debugging
 Settings > Device Info > Turn on debug

28. Example
 Launch with voice trigger
 Android App with a full-screen Activity
 No theme (Glass system theme applied.)
 Handle touch input

29. Example

30. Example

31. Summary
 Use Mirror API if you need ...
 Use GDK if you need ...
 Or use both

32. More Information
 Website
 https://developers.google.com/glass
 http://arforglass.org
 http://www.hitlabnz.org
 Gun Lee
 gun.lee@hitlabnz.org
 Mark Billinghurst
 mark.billinghurst@hitlabnz.org