Downloading an app in today's modern phone is almost as frictionless as entering a website.
Downloading an app in today's modern phone is almost as frictionless as entering a website.
Otherwise, build native apps.
If you can name one successful app that's just a webview then this might be an option.
All that said, it's clearly not a native app. Transitions from screen to screen are slow, do not animate smoothly, and sometimes exhibit drawing problems.
The punchline: their app description announces an upcoming native app: http://itunes.apple.com/us/app/bank-america-mobile-banking/i...
An app store is great for consumers, it sucks for developers. Especially the iOS AppStore where people spend huge amounts of time and money for an app that has a good chance of being rejected for any number of arbitrary reasons. And vendors like Apple go to great lengths to make extra sure your app code is not portable to other platforms, so it's not like you can share significant amounts of code between, say, Android, Windows, and iOS apps.
Enter HTML (5) mobile apps, which work basically the same across all platforms. Sure, you have to make adjustments for different capabilities, but that will even out over the next few years. Basically HTML 5 finally fulfills the promise of Java after all these years. Of course, there are a lot of apps that simply cannot be built with HTML yet, especially games...
Of course, if you have a non-mobile web app and are offering a mobile companion, web version it's fine, but if you're building a standalone iDevice app that you want to charge for, AppStore is the only viable option.
Of course, there are a lot of apps that simply
cannot be built with HTML yet, especially
games...
Depends on the game - many genres do not require a lot of processing power (e.g. puzzle games, many turn-based games).