Overview
Glass is always there when you need it and out of the way when you don't. The software that you build for Glass, called Glassware, should draw from the same inspiration to give your users the best experience possible. To build the next great mobile computing experience, you'll use the Google Mirror API, a set of RESTful services that transmit information to and receive notifications from Glass devices. If you're new to Glassware development, the following information goes over what you need to get started with the Google Mirror API.
How users interact with Glass
Each timeline card contains information pushed to Glass devices from various pieces of Glassware. In addition, there are default timeline cards that are "pinned" to a timeline, so they always appear in the same place. The card that displays the current time and the card that displays all of the tasks that Glass can execute are examples of pinned cards.
Many timeline cards have additional interactions associated with them that are accessible with a single tap. You can define these menu items to allow users to execute actions such as deleting or sharing a card.
How developers interact with Glass
To interact with a user's timeline, you call the appropriate RESTful endpoint to carry out the action that you want to do. Google handles all of the necessary details of syncing between your Glassware and your users' Glass. Some common actions include:
- Creating and managing timeline cards on a user's Glass
- Subscribing to notifications from Glass to be notified of user actions
- Obtaining a user's location
For a few examples of common developer interactions with Glass, see the API Usage Stories and the Google Mirror API Overview documents.
What makes great Glassware
To create the best experience for your users, we've laid out a few guidelines and best practices that help you create the best looking and behaving Glassware. You can find more information about the guidelines in the General Guidelines section, but here are the four main points that you should always follow when developing Glassware:
-
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 users 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 do on the user's behalf, and get explicit permission before you do it.
Developer Policies and Terms of Services
You must agree to the following policies and terms before developing Glassware, so take the time now to read through them all here:
No hay comentarios:
Publicar un comentario