The document discusses developing web applications for Google Glass using the Mirror API and highlights the use of 'cards' in the glass interface, as well as interaction with contacts. It introduces 'phass', an open-source Zend Framework 2 component designed to facilitate building Glass applications by managing backend complexities. The talk also features a demo app and outlines future enhancements for improved functionality.

1. PHP Development for
Google Glass with Phass
John Coggeshall
@coogle

2. Welcome!
 Thanks for coming to my talk!
 A little about me
- Core PHP Dev
- Author
- Speaker
- Aquarium Hobbyist

3. Building GlassWare
Building GlassWare for Google Glass comes in
two different flavors
-Native Applications
-(Java-based Android SDK)
-Web Applications
-(Whatever you want, JSON API)
This talk is going to focus (obviously) on Web
applications

4. Building GlassWare – Getting Started
Building GlassWare using the JSON API (called
the Mirror API) is relatively straightforward
-https://developers.google.com/glass/
Before we get started, let’s review some basic
Glass concepts

5. Building GlassWare – Terminology
The glass interface is
represented primarily
as a series of ‘cards’
chronologically
ordered in a timeline
Timeline cards are
HTML/CSS
- Can contain payloads
(video, audio, etc.)
- Can be grouped into
bundles of cards

6. Building GlassWare – Terminology
 Things your Glass interacts
with (i.e Sharing) are
‘Contacts’
- Contacts can be individuals
(Share with Sue)
- Contacts can be
applications (Share with
Twitter)
- Building a feedback loop
between glass and your
application will require a
contact

7. Building GlassWare – Terminology
 Your Glass application can
‘subscribe’ to events happening
on glass and interact with them
- Timeline card events for cards
you create (i.e. card is inserted,
deleted, etc.)
- Subscribe to location events
(i.e. user is located at these
GPS coordinates updated every
10 minutes)
- Subscription notifications are
handled through URI callbacks.

8. Building GlassWare – Example
Here’s a few examples:
- User takes a picture, shares with the ‘Twitter’
contact, which posts the picture to their feed
-Your app receives a location update, and inserts a
timeline card which shows the closest bar
-Your app on a periodic basis inserts a kitten video
into the timeline, and based on feedback (i.e.
deleted?) automatically curates future videos.

9. Introducing Phass
So what’s Phass?
Phass is a Zend Framework 2
component which abstracts away all
of the plumbing for your Glass
applications
- OAuth2, Notification Events,
Dealing with Attachments, Timeline
items, Contacts, etc.
 Of course, it’s open source and
available on Github:
http://github.com/coogle/phass

10. Introducing Phass
The Goal is to like all frameworks, let you focus on
your app and not the details
- I.e. automatically creating the proper user context
when a location event comes in, so you can focus
on what to do when the event happens
Designed as a ZF2 module intentionally – can be
loaded up and immediately used by any ZF2 based
application to make it Glass-friendly

11. Phass Demo App
To facilitate both testing and assist people, there is
a demo application for Phass as well
-http://github.com/coogle/phass-demo
-http://phass.coogleapps.com/
We’re going to use this demo app to walk you
through some of the basics of using Phass to
build Glass applications of your own!

12. …. Bring on the demos!

13. Upcoming enhancements
More powerful view rendering based on common
Glass card UIs
-https://developers.google.com/glass/tools-downloads/
playground
Implementing some of the less-used API calls
that I haven’t gotten to yet
Bug fixes
Want to help? Pull Requests welcome!

14. Questions? Thanks!
John Coggeshall
@coogle
http://github.com/coogle/phass
http://github.com/coogle/phass-demo
http://phass.coogleapps.com/