Making Sense The Road to mobile Awareness
summary
Claim: contextual awareness best differentiates apps; three concrete routes are compared. Build a custom sensor fusion pipeline from accelerometer/gyro/magnetometer (up to 250Hz), run heavy math in NDK for performance, and wrestle fragmentation and battery. Or use a library like Lost (drop‑in fused location) but face licensing, mismatches and drains. Or use Google’s Awareness API (seven signals, fence and snapshot APIs, processing off‑device; ~85% coverage) for the easiest, most battery‑friendly result.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:58Mobile Contextual Awareness
- 3:49Sensor Types in Android
- 4:13Use Cases
- 5:11Sensor Fusion - What is it?
- 7:27Sensor Fusion - Example
- 11:32Sensor Fusion - Challenges
- 14:10Alternatives to the hard way
- 16:52Time
- 17:10Activity
- 17:30Headphones
- 18:48Awareness Benefits
- 19:51Fence API
- 20:02Three options
- 24:11Sources
related talks
33mMaking Android Apps with Intelligence
36mContextualize Apps with Nearby + Awareness
39mBeyond the Blue Dot: New Features in Android Location
19mFind Yourself! Navigating the World of Android Location
27mDissecting ActivityRecognition with Multi-Sensor Simulation and Its Practical Deployment
35mIntegrating Sensors into Android Hardware
26mWellness & Droid
41mMaking Android Apps with Intelligence