We are currently investigating whether Chromium for Android (or parts of it) can be turned into a library that our app could use. Embedding a newer version of WebKit with Android app.Looking on StackOverflow, we have also found a number of similar questions, most of which being solved by pointing to WebView (we already do that, and it's not good enough) NDK Webkit (officially abandoned by its author).mogo-browser (their last revision was to delete all source code).Webkit Android port by Company 100 (no updates for over two years).We have found three dead attempts to port Webkit to NDK (the bare Webkit for Android port uses functionality not available in the NDK and thus not to app developers): Our research so far has not turned up anything useful. It is more important that we can get our app to work consistently across as many Android devices as possible. It wouldn't necessarily have to be the latest and greatest version.
We'd like to have a component similar to WebView but where we control what version of Webkit/Chromium (or some other rendering engine) is being used. In some cases, this breaks our app or makes the fact the we embed a web page more noticeable. Some phone vendors have unfortunately decided to tweak the standard Android browser here and there. So far, we have been using WebView for this and that works for the most part. We try to do this as transparently as possible (from a visual/user experience standpoint). Significant parts of our app consist of web page fragments embedded in the view (served by the app itself). We are looking for something similar to WebView, essentially, but backed by a browser (version) that we control.
The most likely candidate for this, is Webkit/ Chromium. For our Android app, we would like to embed our own browser/rendering engine.
0 kommentar(er)
