Some of the reasons I came up with are.
1. One app works on all devices (except some layout and css issues). Write once, run everywhere.
2. Easier to maintain.
3. Don't have to deal with App Approval process.
If you're looking for a boolean answer, there isn't one.<p>Web apps are superior for the reasons you mentioned. As a developer, it's just <i>easier</i> to deploy a web app. That being said, I think you ought to be thinking about the users experience, not the developers.<p>App store approval processes mean that users have to wait longer for fixes. Using a particular device API means that your app just isn't available to a lot of users.<p>On the other hand, native apps tend to respond faster, be more in line with the users expectations, and offer the developer a slick way to accept the users money without asking them to put in all their credit card info.<p>You also have to look at how users expect to install apps. At least on iOS, every web app I've seen has to include install instructions because users don't think about installing them.<p>I think I can give users a better experience with a native app, and that's what makes the choice for me.
I agree with you. I have been playing around with some mobile frameworks (phonegap, titanium and rhomobile) and I must say that coding a native app for different mobile platforms isnt too attractive to me. using any of the aforementioned frameworks, you can develop mobile apps that will run across most major mobile OS's like iOS, blackberry and Android, although you might not get a 100% native app, the pain of learning all the SDK's of each mobile platform is skipped. Its just like Java's once stated goal of "write once, run anywhere"