Design Principles of Glass applications
Google Mirror API is a RESTful Web Service API. Applications written by developers to Google Glass are called "Glassware ". Google hopes that Glass can bring users "the next generation of mobile Internet experience" and also provides four design principles:
- Designed for Glass. Your applications should be designed, developed, and tested specifically for Glass to ensure a good user experience for Glass.
- Do not impede users. Glass users want to use technology when they need it, instead of removing it. Do not over-use unwanted notifications.
- Timeliness. The real-time and timely information will make the Glass platform the most effective.
- Avoid unexpected events. Applications, including functions not expected by users, are not good on any platform. However, because Glass is too close to the user's life experience, we must avoid them. You need to be honest with the user to explain the purpose of your application and the user authorization required.
Obviously, Google's attitude towards Glass is a bit like that of its own child. Everything is careful, and the Glass application threshold may be higher than that of Android applications.
Timeline card everything
Glass displays information to users through the "Timeline Card" Timeline Card ). Timeline cards can display text, images, videos, and HTML. In addition to single card display, developers can also place multiple cards together with bundle), and then users can browse through sound or touch.
This also means that the final information of the developer's "Glassware" application is presented through these timeline cards. The most common API behaviors include:
- Create a card on the timeline
- Update Original card
- Obtain user input from the card menu
- Receive notifications from Glass, so you can respond to user behaviors accordingly.
The timeline card for attaching a background is as follows:
The following describes the development practices of the Mirror API. First of all, we are familiar with Hello World.