Are there cases where using Web-based interface (in an organization) is inappropriate and why

Question

For example, in the assembly line I have a feeling that it is inappropriate to use web application to log production status, though I don't have any reason to back it up.

In groceries stores or airport check-in counters for example, I notice that the software used to make purchases at the counter are mostly like a DOS-style interface (or can someone correct me on this). Why is this? Is it because of the cost of switching or something else?

Also, what makes web application a less attractive choice for businesses (or what makes it a more attractive choice)?

Answer 1

Old school text style interfaces have stuck around in business both because of the cost of replacing those systems and because of the cost of retraining staff on entirely new software.

That being said, upgrading to web solutions is currently very attractive for enterprise software for two main reasons:

1. The capability of web UIs and the speed at which developers can prototype them has increased a lot over the last few years.
2. Deploying an update to a web app to an entire company only requires updating one place, and doesn't require relying on, for example, Citrix to do so.
3. Extending internal web apps to be used by actors external to the company intranet (eg. customers, subcontractors) is very easy.

A couple of instances where it wouldn't necessarily make sense to use a web application:

1. A lot of local CPU intensive data processing needs to be done (even then HTML5 would theoretically work).
2. A client app needing to be always on. It would be harder to enforce 'always keep this webpage open' than to just write a native service.