>>>We're building asp.net apps with javascript mapping components (ESRI) and jquery to spruce up the client side. Works fine on pretty much any current browser.
>
>Browser is not a natural decision for business apps on a mobile device- which is why banks, online travel agents, ebay and others are all offering native apps rather than pushing their traditional web interface. It was fine for desktops that usually used a network under the customer's direct control, but mobile devices are distributed by telephony providers who encourage customers to use the provider's data network and once hooked into that, it's hard to go back. Outages are to be expected and are tolerable- unless you're using a browser app that may crash or lose work if an inconvenient outage strikes at a bad moment. Customers won't put up with it, especially if somebody else is doing it properly.

I think while your cited reasons for mobile apps are valid, it is more a function of missing storage ability.
WebSQL was torpedoed by Oracle and partly MS - with such ability (and better security for cached data in SQLite storage)
many if not most native apps would have been unneccessary. Gives me an instant urge to hit something...
read up on the persons involved when "deciding" that an object store was better suited for todays client coding -
and then generously implemented on Oracle owned Berkley...

regards

thomas