WebView Implementations in the 2020s
summary
Cookpad modernized an eight-year Android WebView implementation into a single centralized architecture that unifies lifecycle handling, file chooser and authentication handoffs while still allowing per-screen customization. They introduced comprehensive JS-call logging and method classification to reduce 45 unmanaged JS methods to 10 usable and 2 deprecated, raised minimum target to API 23+ (or at least API 21 for updatable WebView), and consolidated ~5,000 LOC across 2 activities and 4 fragments into the refactored stack.
AI-written summary · about
chapters (11)
- 0:00Web view implementations intro
- 2:09Why web views needed
- 3:55Android web views history
- 6:24Web view lifecycle
- 7:06Cookpad’s journey
- 9:102010s challenges
- 12:01Modern architecture
- 14:08VIPER for web views
- 17:16Centralizing code
- 21:32Gaps in architecture
- 23:15Future improvements
related talks
23mA pragmatic approach to WebViews
22mChrome and Android: Past, Present, Future
15mModern WebView best practices
23mSupercharged WebView Observability
42mOvercoming Unsecurities in WebViews
34mOvercoming JavaScript Unsecurities in WebViews
41mAndroid and the WebView
40mSo, You Want To Use A WebView? [BAD AUDIO]