Building an Invisible App
summary
Mobile “invisible” features automate tasks using iOS background services — background fetch, remote notifications, significant-change location — to run location+calendar+MapKit ETA checks like Google Now’s appointment reminders. Real examples: SMS-based services (Invisible Boyfriend, Magic), Uber’s seamless billing built on Braintree tokenization and vaults, and Robin using beacons plus iPads to auto‑check into rooms. Key data points: Localytics reports 20% of apps open only once and average session ~1 minute. Design rules: don’t automate everything, use notifications sparingly, and earn user trust.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:32Braintree
- 0:50Invisible Apps
- 1:35The Invisible Boyfriend
- 2:54Magic
- 3:29Product Hunt
- 5:32Research Report
- 6:06Average App Session
- 6:53Automating Tasks
- 7:33Background Services
- 9:59Google Now
- 11:08Summary
- 11:24Location Services
- 15:03Maps Services
- 15:50MapKit
- 17:20Uber
- 18:38Tokenization
- 20:06Robin
- 20:37Beacons
- 22:28Things to consider
- 23:33Swarm example
- 24:46Notifications
- 25:31Usage Patterns
- 26:52Location
- 27:34Establish Trust
- 28:22Outro
related talks
17mPrivacy First! Mobile Engagement in the Fast Emerging New World
28mEmbracing innovation by building privacy friendly apps
38mDeveloping Mobile Apps with Privacy as a Baseline Need
53mDesigning for Privacy in Mobile and Web Apps
06mWhere You Go Matters: A Study on the Privacy Implications of Continuous Location Tracking
43mThe importance of privacy
26m"Reality Mining for Compan
08mBest practices for building privacy-friendly apps