Why write an application if the web server will do?

Question

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

From his specifications, I see no good reason for the need for an “application” as such. It seems that CSS, JS and HTML can do this work while all this is written with the phone display.

If his application is necessary to access the local processor power or the functions of the telephone device, this will be one thing, but this is nothing more than interaction with the server, followed by the display of results.

Don't I value anything? Thanks in advance.

Answer 1

Although this is a fairly lengthy and thoughtful discussion, most people find that native applications feel “better.” Keep in mind that we are talking about real native applications, and not about those that are produced using PhoneGap, etc.

Providing a downloadable application in a store environment gives many people a sense of (free?) Marketing power; they expect their application to be “listed” in one of the short lists, can contact email and another site in the application store, and this gives a (fake?) sense of authenticity. I think this is combined with the effect that some consumers forget that they can only visit the website on their smartphone and only addiction.

Besides; Apple does not endorse applications that are simple UIWebView; the application must contain a certain uniqueness over a simple web application. Google has no rules about this, but I don't know Microsoft's rules about this.

Many customers do not know what they are talking about. They just want an app. It is your concern to give the best advice, but if they insist .. well .. it can take 4 times more work, and money ...

edit I do not know if this platform is suitable for this discussion. Can others redirect you to another StackExchange site? However, this Quora discussion list on the Vs. Mobile site. The native application should also be useful.

Perhaps you can take the opportunity to enrich the specified application a bit. Maybe this is not just a simple presentation of the data, but the capabilities of the native application can give a better (and not just a favorite) experience?

Answer 2

This may be a gap in terminology; I agree - if this is only interaction with the server, then CSS / HTML, etc. - Everything that's needed. Perhaps what the client wants / needs is just an icon to click on, and not a website to visit - maybe this is the experience app they are looking for - how will the information be delivered, maybe secondary?

Answer 3

If you currently have specs, just “iPhone, Android, Windows 8 phone, etc.,” perhaps deepening your “application” concept inside your client will save you some headaches. I hope the application has no special functions for you, except for viewing [remote | local] text and images. If this is not the case, then the development of such a wide list of devices and platforms will be very large.

Nevertheless, I already had to develop fast and inexpensive business applications for these platforms (exception from Windows Phone), and the transition using the HTML + CSS + JS stack, packed inside my own container, did the job pretty well (and without any special errors) .

I suggest you take a look at http://cordova.apache.org/ , it allows you to develop in the same way as with a local website, and then collect everything inside the native one that can be deployed to the device.

For a more complete shell with access to some built-in functions (such as cameras, etc.), see http://phonegap.com/ .

To develop application code, good JS-based work may work. I usually use Sencha Mobile, it has a little learning curve, but its pretty stable and powerful (as far as possible, Javascript, nothing compared to native code).

Only quirk, I do not know about the Windows Phone platform (and if the above solutions can work on it).

Hope this was helpful. Good luck.

Answer 4

IF the requirement is the same for all applications, then it can be developed using any cross-platform tools. Aspects of your question constitute support for your point. I just add some advantages of my own application on top of html5 applications

• advantage of built-in apis, functions, guis, which are not always easy to implement with html5
• Application store support has a big advantage.
• Native application supports additional security settings.

Just written a few points on which I would have thought that the list could be longer.