comparison, a single tweet from Twitter’s API can be upwards of 2.

5
Kb. Connect IQ does some magic under the hood to minimize the
amount of data that’s transferred from the phone to the watch, but
you can quickly see how pulling a user’s last few tweets could be
somewhat time consuming.
This classic proverb of “Less Is More” couldn’t be more true when
considering JSON responses. When working with web services, con‐
sider what information you really need to have at the Connect IQ
level and keep your bandwidth budget in mind when you make
decisions about what to ask a server to send back to you.
The projects in this chapter are meant to give you a foundation in
Connect IQ development, but also a start on whatever you might
want to build yourself. You know how to record sessions and define
your own data fields. You’ve seen how to talk to external sensors and
read their transmissions. And you have gotten an overview of using
OAuth to authenticate to web services and fetch data from them.
Now you can combine these things, or mix up your own from
scratch. For example, you could push your temperature readings to
a web service that logs them and displays them online. You could
poll a public weather API like the Weather Underground, and com‐
bine humidity and weather forecast information with your tempera‐
ture readings.
The Connect IQ SDK, while preserving backward compatibility with
older SDKs, is in a constant state of improvement. When I started
this book, a new version was in beta; it was already on its first point
release by the time I finished it. Keep an eye on the Connect IQ
developer site, especially their forums and developer blog, and sign
up for their developer newsletter to stay current with the latest
updates.

56 | Chapter 4: Projects