We\'re developing several HTML5 apps based on the Sencha framework, and thinking about packaging them into apps with say PhoneGap.
However, even if you package thes
I'm assuming you still have to deal with the Android fragmentation with various manufacturers making weird modifications to the browser
PhoneGap doesn't use the browser. PhoneGap uses a Web rendering engine per platform. On Android, that is WebView
. Hence, it matters not a whit what manufacturers do the the AOSP Browser application.
is it possible to just literally put Chrome into the same package and just use that?
If you have a dozen or so Java and Android native code engineers who are capable of taking the Android build of Chromium and rewriting substantial amounts of Apache Cordova (a.k.a., PhoneGap) to use Chromium, it's at least conceivable. Then again, if you have a dozen or so Java and Android native code engineers, you might be better served simply writing a native Android app, as it will be smaller, faster, and easier to maintain than your own home-grown edition of "ChromiumGap".
To quote the Chrome for Android FAQ:
Does Chrome for Android now support the embedded WebView for a hybrid native/web app?
We are evaluating ways we can support WebView with Chrome but do not have any plans to announce at this time.
I want to point out Crosswalk: https://crosswalk-project.org/
It seems to provide what you require.
What is Crosswalk for?
If you are a developer working with web technologies, Crosswalk enables you to deploy a web application with its own dedicated runtime (ed: modified Chromium). This means three things:
- You can distribute your web application via app stores.
- Your application won't break in whatever ancient webviews or browsers your audience is using, as you control the runtime and its upgrade cycle.
- You can build applications without worrying so much about runtime differences and quirks: you only have one runtime to deal with.