In my experience (as an iOS app developer) people overestimate the returns they'll get from being listed in the app store. It might make sense for big brands because people might search for them, but smaller brands will not be more visible than when having a mobile site. In fact, when it is necessary to search, getting an app from the store and then using it takes a lot more steps then searching in the browser and going to the website.
My standard response when people ask me about building an app is if they've considered creating a mobile site. Unless they have something platform/device specific in mind, like in app purchases, push notifications, using the camera or compass or if the UI is important, it often does not make sense to create an app.
Most important, however, is the user (surprise, surprise). What is the task the user will perform at your site/with your app? If it's something they'll only do a couple of times (or even once) it's not worth an app (unless, maybe, you want them to pay for it). Installing an app is a much bigger upfront commitment (even if it's free) than visiting a website.
I fully agree with you, mobile apps are the way to go, and you can still build native apps for advance feature or mnetisation as well as part of a strategy to reach a broader audience, I use http://www.gmbhnews.com as a base for mobile apps to help bloggers achieve this.
I agree. Native apps are great if you have some features you want to implement that aren't practical in a web app, but I can't think of any case where a website with a native app for mobile devices has any good excuse not to also have a web app to fall back on.
I very much like the idea of producing webapps rather than iPhone apps in my business, and I think they could probably provide all the functionality I require.
For me the catch is monetisation. With the App Store, this is clear: I release paid apps. With webapps... Advertising seems viable, except that my apps need to work offline (and may solely be used in that way), which as far as I know scuppers the advertising approach. So what's the alternative? Set up a paywall and require users to login to get the webapp in the first place? That seems to defeat the point somewhat.
Anyone have bright ideas or links to clever thinking on the subject?
The equivalent of an app store fee is a pay-wall to the application. It would probably drive away more customers than the equivalent app store fee, but I don't think it is defeating the point at all.
As a user I don't have any strong preference either way but the presence of a shiny icon on my home screen prompts me to visit a site more often than a bookmark that is several taps away. Adding bookmarks to the home screen on the iPhone is more realistic with folders to organize them in but it's still a multi-step process to put it there in the first place. It's unfortunate tapping a piece of glass more than once is a barrier but it just seems to work out that way these days for me.
Are there likely to be the same lowest-common-denominator problems as you get with cross-platform development of console games, or those seen with Java apps like OpenOffice.org?
[+] [-] eelco|15 years ago|reply
My standard response when people ask me about building an app is if they've considered creating a mobile site. Unless they have something platform/device specific in mind, like in app purchases, push notifications, using the camera or compass or if the UI is important, it often does not make sense to create an app.
Most important, however, is the user (surprise, surprise). What is the task the user will perform at your site/with your app? If it's something they'll only do a couple of times (or even once) it's not worth an app (unless, maybe, you want them to pay for it). Installing an app is a much bigger upfront commitment (even if it's free) than visiting a website.
[+] [-] pwim|15 years ago|reply
If warranted, you can follow up with apps for specific platforms.
[+] [-] Concours|15 years ago|reply
[+] [-] zweben|15 years ago|reply
[+] [-] webdragon|15 years ago|reply
[+] [-] jerrell|15 years ago|reply
For me the catch is monetisation. With the App Store, this is clear: I release paid apps. With webapps... Advertising seems viable, except that my apps need to work offline (and may solely be used in that way), which as far as I know scuppers the advertising approach. So what's the alternative? Set up a paywall and require users to login to get the webapp in the first place? That seems to defeat the point somewhat.
Anyone have bright ideas or links to clever thinking on the subject?
[+] [-] superdavid|15 years ago|reply
Offline access is a problem.
[+] [-] jsz0|15 years ago|reply
[+] [-] suxargs|15 years ago|reply
[+] [-] superdavid|15 years ago|reply
[+] [-] draper|15 years ago|reply
[deleted]