Hi,
I think most people didn't understand what I wanted
Hybrid apps. are pretty popular (mix of native and web content) and the advantages are clear. Easier to manage the webview part (you just need to update the remote code) and less native code.
I actually have stretched this with the webviewextras and it works great. I have a fully driven jQuery interface that talks to native parts by using webviewextras. For example, I have a nicely designed gauge running in a remote webview that gets updates by a jQuery command when something changes inside the Android app.
You can run these type of commands when using jQuery:
MyWebViewExtras.executeJavascript(wvSensor,"$('#99e865bcdb7ee7198f1700930024148bcurrentval').val('88').trigger('change')") That would update a Gauge in my dashboard, even when it is hosted remotely.
Personally I prefer adaptive/responsive design for the UI (not native but HTML5) and then hookup features of Android. This way your UI can be designed by a web designer and someone else can do the Android code. UI changes are also easier to do because they are on the web so everyone gets the new stuff immediately, it adds a kind of abstraction layer.
You could easily add parameters to your web url to tell you call from inside Android, I do this with a parameter called inapp=false/true
Native isn't always the answer to every problem, that is for sure!
I did not have time to do a full demo yet but maybe I will schedule something for the future.