Why write an app if a web server will do? [closed]

Question

I have a client who wants an app for iPhone, Android, Windows 8 phone, etc.

From his specifications I see no good reason to need an "app" per se. Seems to me CSS,JS and HTML can do the job as long as it's all written with a phone's display in mind.

If his app needed to access localized CPU power or features of a phone device, that'd be one thing, but it's nothing but interaction with a server followed by a display of the results.

Am I not appreciating something here? Thanks in advance.

Answer 1

Although it is quite a long and elaborate discussion, most people consider native apps to feel "better". Mind you, this is about real native apps and not the ones produces by PhoneGap etc.

Providing a downloadable app in a store environment gives many people the feel of (free?) marketing power; they expect their app to be "listed" in one of the short lists, the can link from email and other website to the app store and it gives a (fake?) feeling of authenticity. I think this is combined with the effect that some consumers forget they can visit just a website on their smartphone, and are only app-minded.

Besides that; Apple does not approve apps that are a mere UIWebView; the app has to contain a certain amount of uniqueness over a simple web-app. Google has no rules about that, but I don't know Microsofts' rules about that matter.

Many clients don't know what they talk about. They "just want an app". It is your concern to give the best advice, but if they insist.. well.. it maybe takes 4 times the amount of work, and the money...

edit I don't know if this platform is the best place for this discussion. Others can maybe redirect you to another StackExchange site? Nonetheless, this Quora discussion list about Mobile Website Vs. Native App should also be helpful.

Maybe you can take the opportunity to enrich the designated app a bit. Maybe its not just about simple data presentation, but the powers of an native app can give a better (not just fancier) experience?

Answer 2

It could be a disconnect in terminology; I agree - if it's only interaction with a server, then CSS/HTML etc is all that's needed. Perhaps what the client wants/needs is just an icon to click on, rather than a website to visit - maybe it's the app "experience" they're looking for - how the information gets delivered may be secondary?