Deep Android Integrations
summary
Practical how‑tos and concrete implementations: building HTTP and app‑scheme deep links that survive install flows and Play Store referrers, implementing native single sign‑on with package and certificate checks, exposing data via a content provider for batch uploads, wiring an Android sync adapter and AccountManager for authenticated syncing, and using AIDL for IPC. Examples include an Uber deep‑link/native SSO rollout and an Evernote ↔ Samsung S Note integration; deployed approaches work but require strict fingerprint validation and jittered sync schedules.
AI-written summary · about
chapters (22)
- 0:00Android developer platforms
- 1:32Traditional vs deep integrations
- 2:15Deep links and URI handling
- 4:45Handling missing apps
- 6:52App linking and verification
- 8:43OAuth and mobile login
- 10:49Native sign-in and SSO
- 13:56Security for native sign-on
- 17:47Samsung S Note with Evernote
- 19:13Android components for integrations
- 20:38Intents and limitations
- 23:07Implementing edit actions
- 27:22Custom actions for CRUD
- 29:29Content providers for batch data
- 31:37Query methods in providers
- 34:50Account manager for accounts
- 36:54Account authenticator
- 40:06Sync adapters for syncing
- 43:14Optimizing sync intervals
- 45:00Inter-process with AIDL
- 46:24Permissions for integrations
- 47:27Debugging deep integrations
