introduction to google glass and gdk

Introduction to google glass and GDK

As efficient as your in-house teamWe provide the people, the ability and the tools so you can be best at what you do.

The device has been designed for instant sharing and uploads images, video and audio on the go, online.

There is a power cable attached to the right side of the Glass frame that is used to recharge the device.

Camera -Photos - 5 MP -Videos – 720p

Connectivity -Wifi -BluetoothStorage -12 GB of usable memory, synced with Google cloud storage. 16 GB

Flash total.

Record videos, take pictures Show messages Find information Show maps Live video sharing Integrates Google Now Translate

Mirror API– web-based services, called Glassware, that

interact with Google Glass.– It provides this functionality over a cloud-

based API and does not require running code on Glass.

Glass Development Kit (GDK)– The Glass Development Kit (GDK) is an add-

on to the Android SDK that lets you build Glassware that runs directly on Glass.

The GDK is an Android SDK add-on that contains APIs for Glass-specific features.

Unlike the Mirror API, Glassware built with the GDK runs on Glass itself, allowing access to low-level hardware features.

Time line: The timeline provides a standard interface for users to

experience Glassware and for developers to display Glassware.

Static card: Static cards appear within the history section of the

timeline. Live card:

Live cards show content that is important at the current time

Immersions: Immersions are customized UI experiences that take over a

user's focus and display outside of the timeline experience.

Time line

Static Cards – appears within the history section of the timeline. Each card

focuses on one thing, is visually clear, and is simple to read. (used in mirror api as well as GDK)

Live Cards– show content that is important at the current time and

constantly update to keep information fresh and relevant.(possible GDK)

Immersions– are customized UI experiences that take over a user's focus

and display outside of the timeline experience.

Appears in the

timeline

Access to user input

Control over user interface

Major uses

Static CardsYes No No Information

display without user

interaction

Live Cards Yes Yes, but timeline takes precedence

Yes, no restrictions Rich and live content with

low user interaction

Immersions No Yes, no restrictions

Yes, no restrictions Rich and live content with

high user interaction

// Create a card with some simple text and a footer. Card card1 = new Card(context);

card1.setText("This card has a footer.");

card1.setInfo("I'm the footer!");

View card1View = card1.toView();

The card will look like the image provided below.

Low frequency - which updates the card once every few seconds.

High frequency - which updates the card many times a second.

Its Cost ($1500). Battery Backup. Privacy issues. Banned at places.