Myths about the Deep Links
summary
Deep linking requires assetlinks/universal links, handling URI schemes, deferred deep linking and the unreliable install referrer so the real work is building redirection, temporary storage and fingerprinting logic. DIY implementations hit maintenance hell — one client with 300 devs abandoned their attempt and returned after two months. Expect about 400 test cases across browsers and social apps, use Google Play Install Referrer API plus fallbacks, and measurable wins like a 77% improvement in onboarding conversion. Consider ready solutions such as Firebase Dynamic Links or Branch instead of building from scratch.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 3:35History of deep links
- 11:24Common deep link misunderstandings
- 18:45Why app links aren't enough
- 25:36Implementation challenges
- 34:50Recommendations and solutions
- 37:39Closing and Q&A
related talks
33mMeasuring the Insecurity of Mobile Deep Links of Android
41mDeep Android Integrations
16mNavigation in Modular Applications with Deep Linking
32mInstant Apps + Deep Linking 101
28mInstant Apps + Deep Linking 101
44mDeep Android Integration
11mCodelab: Deep Linking for Instant Apps Made Easy
33mNavigation in Modular Applications with Deep Linking