Wearable Android
Travis Himes
CODE:
Introductions
- Who am I?
- What's this about?
- How can I get the most out of this?
- What are we going to do?
Repo Urls:
Glass aside
- Swiping
- Cards
- Active cards vs Passive
- "timeline"
Goals
- Consume a REST service
- Display info on a device
- More interesting things!
Goals
- Display SOMETHING on the watch!
Consume a REST serviceDisplay info on a deviceMore interesting things!
CODE
Consume a REST Service
- Github
- Retrofit
- RxJava
CODE
Display results on a device
- Simple
- Pages
- Actions
CODE
Wear Remote Input
- Similar to what we've done
- Doesn't make sense in this exact context
- Entirely possible, STT handled for you
- setChoices if you don't need them to speak
<no code, yet>
More Interesting Things
- App running on Wear
- Communication
- Example
Wear app
- Wear is its own Android OS
- App distributed within phone app
- Uses phone for networking
- No keyboard!
Device Communication
Phone <=> Watch
- Data Items
- Asynchronous
- Guaranteed
- Suggested Size limit (~100KB)
- Circumventable
- Callbacks to implement
- State to maintain
- Messages
- Synchronous
- Not Guaranteed
- Hard Size limit (~100KB)
- Service to receive messages
- State to maintain
Important Considerations
- Be stingy with your network usage
- Be stingy with your battery usage
- Network
- Sensors
- Display Updates
Help me choose
- Runs entirely on watch
- Input is quick and easy
- Stops itself when it's done
CODE
Other Options
Do it with Notifications, from the Wear device
Questions
Comments
?
CODE:
Thanks!
@travis_himes
deck
By Travis Himes
deck
- 1,046