![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |