9CHAPTER 1: Getting Started
If your app is mainly information-oriented and does not require an advanced user interface or if a
server is required for content updates or data processing, then the Mirror API is more appropriate.
If your app requires low-level hardware access or offline processing or rich user interaction or the
user input data can be processed in the Glass itself, then the GDK is the right choice.
In some cases, you may want to build a hybrid app that uses both the Mirror API and the GDK. This
is made possible because the static timeline card inserted by your Mirror API–based Glassware can
invoke the GDK Glassware with a menu item associated with the card. I’ll show you a sample project
that does this in Chapter 10.
You can also find a good summary on when to use each one at Glass’s developer site:
https://developers.google.com/glass/develop/overview.
Google’s Glassware Policies
Understanding Google’s policies on Glass development can be important because as a developer,
you need to know what you can and can’t do; you don’t want to spend lots of time developing
an app such as facial recognition but find out later that it’s against Google’s policy. Here is a brief
summary of the Google’s Glassware policies that are most likely related to your development effort:
You can’t use the camera or microphone to present personal information
identifying anyone other than the Glass user. This means Glassware that does
Facebook or Twitter profile searching based on facial recognition and voice print
will not be approved by Google.
Don’t disable or turn off the display when using the camera to take a picture or
record a video.
Don’t develop Glassware with content or services that facilitate online gambling,
such as online casinos, sports betting, and lotteries.
You may not charge end users any fees or collect any payments or virtual goods
to use your Glassware. This can be a little demotivating to developers. But if
you think of the history of Apple’s App Store, for the first year after the release
of the iPhone, the SDK was not even available. With Glass, the Mirror API and
the GDK were available even before the public release of Glass. This shows
how important a role Google thinks developers will play in the success of Glass.
One way or another, Google will figure out something that makes developers’
investment in time and effort worthwhile.
There are a lot of other details in terms of Glassware policies. You should check Google Glass’s web
site for any updates because the policies may be revised now and then.
Why This Book?
The goal of this book is to help developers jump-start the Glass development, no matter what
their backgrounds are or whether they already own the Glass. I still remember in the first months
of my learning iPhone programming, I was not aware of the book Beginning iPhone Development:
Exploring the iPhone SDK, which is full of working code and step-by-step tutorials, so the learning
curve with online documentation and samples with no clear tutorial-like explanations was pretty
剩余357页未读，继续阅读
南风以南
- 粉丝: 424
- 资源: 40
我的内容管理
展开
最新资源
- Vue实现iOS原生Picker组件：详细解析与实现思路
- Arduino蓝牙小车：参数调试与功能控制
- 百度Java面试精华：200页精选资源涵盖核心知识点
- Swift使用CoreData填坑指南：CoreData在Swift 3.0的变化
- 微距离无线充电器创新设计及其实验探索
- MTK Android平台开发全攻略：44步详解流程
- RecyclerView全面解析：替代ListView的新选择
- Android开发：自动适配中英文键盘解决方案
- Android调用WebService接口教程
- Android开发：BitmapUtil图片处理全解析与实例
- Android多线程断点续传实现详解
- PCA算法在人脸识别会议签到系统中的应用
- EventBus 3.0：Android事件总线详解与实战应用
- Android FileUtil：全面解析文件操作实用技巧与实例
- RecyclerView添加头部和尾部实战教程
- Android实现微博滑动固定顶部栏实战与优化
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
