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.

  • android youtube upload video with static username and password
  • How can I tell if the screen is on in android?
  • How to make oval shape tabhost in android
  • How to learn and use OpenGL ES 2.0? I just don't get it - serious Qn.
  • Is it possible to do this Android screen animation with a ViewPager?
  • Android NDK STL c++_shared w/LIBCXX_FORCE_REBUILD results in std::stringstream NOP
  • Related posts:

    Adding content to a linear layout dynamically?
    Android: how to play music at maximum possible volume?
    Loading kernel module in Android kernel
    How to download and save an image in Android
    Cannot refresh/update listview in a fragment from another fragment in ViewPager
    Is it possible to create an array of Bitmap in android
  • How can I know that my WebView is loaded 100%?
  • Does the Android emulator support OpenGL ES 3.0?
  • ContentObserver should call if and only if ContactsContract.Contacts.CONTENT_URI changes
  • How can I do something every second?
  • Displaying different text on a spinner item than the selected text, android
  • Phonegap Android app trigger update programmatically
  • 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.