Use firefox as render engine for Android webview

Anybody has a feeling how much effort it would be to replace the webkit engine with firefox in Android for webview rendering? I am quite unhappy with the webkit engine on some features.

  • How to move SearchView 's search Icon to the right side?
  • How to add android to cordova platform? PATH error?
  • Can I set “android:layout_below” at runtime, programmatically?
  • Move snackbar above the bottom bar
  • Keyboard navigation with Android GridView doesn't scroll grid
  • NavigationView and ActionBarDrawerToggle
  • Related posts:

    how to change color of TextinputLayout's label and edittext underline android
    How to make slide to unlock button in android
    onSaveInstanceState() and onRestoreInstanceState(Parcelable state) are not called?
    Getting started on iOS - for Android developers?
    Execute code on main thread in Android without access to an Activity?
    UDP or RTP streaming solution for android
  • React Native: Change the Entry file path to specified custom file path
  • How to generate signed and unsigned APK's using gradle?
  • Android: How do you check if a particular AccessibilityService is enabled
  • Getting the physical screen dimensions / dpi / pixel density in Chrome on Android
  • Calling Custom ListView Adapter from Fragment Class Main Activity
  • Returning value from Thread
  • 3 Solutions collect form web for “Use firefox as render engine for Android webview”

    Mozilla started working on GeckoView, which does exactly what you need. This blog post points to some sample code.

    Here is the master bug, in case you want to follow progress:

    Non-trivially difficult. Depending on how much consistency you need between your new WebView implementation and the existing implementation you could have a lot of work to do. There is an existing Firefox browser on Android so you could start with that (which would hopefully save you a lot of time) but at the very least you would need to check that the Firefox libraries exist and are accessible, you would probably need to bundle them with your app to get them to work (which would massively increase the size of your app) and then hooking up all the WebView apis would involve a lot of work.

    The good part: there is an ‘official’ geckoview tutorial about how to integrate GeckoView, and a geckoview demo project on github:

    The sad part: the official mozilla download site does not host the libraries anymore, and the latest available zips are from 2014:

    At some moment there was a geckoview gradle artifact and a AAR, but the URLs are now dead.

    Conclusion: apparently, GeckoView development has been halted, since URLs from the wiki page are broken, the library has been removed from the Mozilla continuous integration, and the bugs keep piling up with nobody to handle them. Hopefully I am wrong.

    Android Babe is a Google Android Fan, All about Android Phones, Android Wear, Android Dev and Android Games Apps and so on.