I understand some cases: * Need for offline; * Need to work like an IM (instant updates pushed from a server, like a telephone / IM / email service); * Need to avoid latency in user experience (a native game, vs a web-based flash-style game).
But I don't understand any others, and really would like to know.
2. With my iPhone at least, I enjoy the predictable user interface that comes with doing stuff inside IOS.
3. I'll be honest. I don't like typing in URLS on my phone, and typing in passwords. It is a real pain when alternatively I could just click an app.
4. I really hate the mobile sites for some companies. The mobile site for my school is awful and always redirects you to some ugly main menus from the page you actually wanted. I would much rather just have the regular website.
(2) is bit hand-wavy in my opinion
(3) is spot on, bookmarking to homescreen is something people don't know about; typing a password is okay if it's only once I think
(4) is about prioritizing resources to the most popular platform: a website on desktop, a native app on mobile
2) To each his own. I've never really figured out what a native look and feel was since every app looks different. And it's not like non-native slowed down adoption of the WWW for desktops.
3) Bookmarks. Android at least lets you put a URL bookmark on your desktop too.
4) Same as 1.
Well I'm not a web guy, but I can imagine at least one reason: having to learn and work with a slew of proprietary software stacks to deploy the same thing over multiple platforms - the web finally looked like the solution to this problem until about 5-6 years ago.