Taking Chrome Full Screen with Trusted Web Activities
summary
Trusted Web Activities put full‑screen Chrome into Android apps with no browser chrome, verify ownership via digital asset links served at assetlinks.json, and require the app package name plus SHA256 fingerprint from keytool. Implementation uses the Android support library and launcher activity; protocol builds intents so TWAs run on Chrome 72+ (Android 4.4+). Fallbacks go to Custom Tabs or a WebView. Early adopters report strong lifts: Bucher matches PWA conversions (over 3x median web), Tencent users spend ~3x more time, and 1800Flowers sees ~30% conversion lift.
AI-written summary · about
chapters (10)
- 0:00Introduction to TWA
- 2:38Use cases for TWA
- 4:49How TWA works
- 7:11TWA vs. Webview
- 9:41Getting started
- 13:09Technical architecture
- 16:58Project configuration
- 19:00Quality and policy
- 22:00Case studies and results
- 26:02Future and conclusion
related talks
22mGiving your PWA superpowers
10mWhat’s new for web apps in Play
22mChrome and Android: Past, Present, Future
19mGoogle facilitates smartphone-like app experiences in your Chrome browser
01h 01mProgressive Apps in the Wild
39mAndroid and the WebView
48mProgressive Web Apps in the Wild
01h 16mPWA - The hidden stories about the future of the web