>>AFAIR they have only a native client, but always need a server to call.
>>A road warrior (disconnected native) app can IIRC be done only by installing a local server part, which incurs even more cost.
>>So native vs. browser based yes, but not standalone native.
>>And on iOS and android *only* browser based, not even native client -
>>and these HW types need the native speed boost most.
>
>Being full HTML/Web has so many advantages compared to thick client / local server, and given the infinite possibilities of connection today, I personally see no future market for 'desktop' app or their equivalent on mobile devices.
>Most iApp are in fact wrappers around Safari to query a web App.
>FoxInCloud is used in Madagascar, where connections are far less fast and reliable than in our western countries.

In Q1 I was traveling by train quite a bit over europe - I was very happy to work offline ;-)
But for new dev I probably will often argue for including only an option to work with a HTML5 local browser cache copy of the data.
And this translates to replication into SQLite from my POV - which could probably be generated from your architecture,
but not as it stands now. Just my idea where to develop next, if your approach sells enough.

regards

thomas