Deep Android Integrations
summary
Deep linking for Uber-specific URIs uses Play Store install_referrer and an assetslinks.json verification with autoverify to preserve user context and avoid lost intent; a serious bug arises from using Locale.getDefault for lat/long parsing and is fixed by switching to Locale.US fix to stop mangled coordinates. Authentication uses OAuth implicit vs authorization-code flows and app-to-app token exchange guarded by APK fingerprints. For high-throughput integrations a lightweight AIDL IPC pipeline binds an internal service that proxies requests to the external API, avoiding per-client APIs and working reliably; also recommends account manager tradeoffs and strong logging.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:19Deep linking fundamentals
- 14:40Authentication flows design
- 31:36Inter-app communication
- 38:18Key principles and takeaways
- 40:45Q&A and resources








