How to define your install strategy
summary
Shows that combining native, Play Store PWA (Trusted Web Activity) and browser Add to Home screen prompts raises installs while avoiding cannibalization by selecting the right channel per user. Recommends heuristics: web install as fallback for repeated site visitors, device-based routing using JS APIs (deviceMemory, hardwareConcurrency, Network Information) or Accept-CH client hints, and checks with getInstalledRelatedApps API. Gives Oyo example: a Lite PWA at 7% of native size; test with A/B experiments.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:22Native app installs
- 2:32Combine app installs
- 2:58Web install as fallback
- 3:52Web install prompts
- 4:43Intuitively
- 5:16By Signals
related talks
14m5 tips for your PWA
22mHow to take full advantage of a PWA install
01h 01mProgressive Apps in the Wild
48mProgressive Web Apps in the Wild
10mThe search for App-iness
43mStrategy for testing progressive web apps
44mKeynote: Uncovering the secrets of Progressive Web Apps
17mTransforming your Web Application into a PWA - Why and How?
