Designing for Privacy in Mobile and Web Apps
summary
Argues privacy succeeds when it’s specific: use a Minimum Viable privacy policy listing who you are, data categories, purposes, named third parties and deletion timelines; build temporary authentication (geofence-based location permissions) and contextual permissions so camera or mic access asks only when needed. Cites a working app (GeoLoci) with a simple on/off location button that users accepted, a failed IoT pet feeder that left animals unfed when servers died, and Google Glass’s social failure—recommend a visible red recording light and easy data export.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:35Changing user interfaces
- 13:01Compare to iPhone Developer Launch
- 24:09Privacy by design vs. privacy by disaster
- 24:34Consolidate and simplify settings and permissions
- 25:11Contextual Privacy
- 26:08No one is perfect
- 26:52Authentication and Permissions
- 29:33Community Involvement
- 39:10Own your own data
related talks
38mDeveloping Mobile Apps with Privacy as a Baseline Need
47mDesigning for User-Centered Privacy
17mPrivacy Design Flaws
33mDesigning and Building With Privacy In Mind
28mEmbracing innovation by building privacy friendly apps
04mDeep Dive: Identity, Privacy, and Informed Consent in the...
01h 10mDIGITAL PLATFORMS, THE NEW PRIVACY CHAMPIONS? BETWEEN MYTHS AND REALITIES
21mDeveloping privacy user-centric apps