Integrating GeckoView into a Dynamic Feature
summary
A mobile developer describes integrating Mozilla’s GeckoView into an Android Dynamic Feature module, explaining why the team replaced WebView, how they implemented GeckoView inside the feature module, and the specific issues they encountered during integration. The talk focuses on practical migration steps and troubleshooting for teams considering GeckoView as an alternative to Android WebView.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:29White screen issues
- 3:55Finding causes and Google search
- 6:43Alternative solutions
- 7:31Why GeckoView
- 9:15App structure and dynamic features
- 10:00GeckoView integration issues
- 11:50Manifest and service errors
- 13:13Rendering and scroll problems
- 14:16Image and JavaScript loading
- 15:43On-Demand dynamic feature issues
- 17:05Google Play testing
- 18:49J Bridge problems in GeckoView
- 19:34Web Extension implementation
- 21:42JavaScript testing and debugging
- 22:47AMP limitations and APK size
- 23:09Mozilla and Fabricator issues
- 24:14Conclusion and recommendations
- 25:20Q&A
related talks
50mPut a Red Panda in Your Android WebView
46mWebView as a Way to Integrate Services
23mA pragmatic approach to WebViews
15mWebViews: fast-tracking features in mobile apps
01h 12mInterview and Q&A
41mBuild a Browser by Kotlin
23mSupercharged WebView Observability
22mChrome and Android: Past, Present, Future