Why are companies still using Windows Forms and WPF applications instead of web applications?

Question

Why are companies still using Windows Forms and WPF applications instead of web applications?

I don't want a discussion. I want only the reasons, because in the last few days I have had a lack of confidence in my job (Windows Forms/WPF), and I think it is good way to change technology/job.

Upanddown

There is no silver bullet language / deployment - otherwise we would all be doing it. Different implementation mechanisms for different business problems to be solved. – Enlarge

Answer 1

Windows applications have the best user interface and features, but they are available to the smallest audience, while web applications have the most limited user interface features, but they are available to the broadest audience.

It's up to the companies to decide between web and Windows applications that they must develop for their growth...

Brenan

Let's also add that Windows Applications are far more powerful in terms of tools used. To make a equally good working web app you need a ton of AJAX stuff set up to emulate stuff that's for free on a desktop client. (Like instant feedback for validation etc..) I once made the decision to deliver a win-app instead of a web app to a small company that needed a problem solved. They had a web app before and love the new system that allows them to use shortcuts and multi-document windows with Drag&Drop.. Trying to do everything with web-app is like fitting a square box in a round hole. – Kirtle

Answer 2

Some possible reasons:

1. Desktop applications are easily made available offline (obviously this is changing with new HTML5 stuff)
2. Some things are just easier in desktop applications (think complex 3D visualisations, granted you could write some Flash to do some of this stuff)
3. You may need to access local files / system information / other applications that are not possible from a web application
4. You can use the local processing power more effectively with native code than via JavaScript (again, changing as browers become better)
5. The scope of skills required for desktop applications is generally less than the web (think C# vs HTML, CSS, JavaScript, Flash, HTTP, etc.) so it may suit the development resources available

Felon

Answer 3

Companies are still using Windows Forms because it allows communication with Windows on a lower level than a web application.

WPF also allows greater data binding and has easier tools to handle complex tasks.

Rhys

Answer 4

We still use WinForms and WPF because we need to deal with lots of data and need fast performance. And one other thing : We don't want to store our data on web servers (or in the cloud)!

Reno

Don't tell me you are storing all your data on the local desktop! don't you use a database? – Untaught

We are storing the data on a local database, not in the cloud. But the datebase must be on the local machine otherwise you could not take the data on the road or to the customer. – Reno

Every tool has its use. My company uses local databases as well, but for us it was the wrong decision. Its made many things much too complicated for the few benefits it provides. – Kerns

Answer 5

Windows applications are more secured from the external world.

Chromatograph

Answer 6

In my case I develop desktop applications because I need to access local resources. It can be file system, databases, native application APIs, COM components, etc.

The only web solution is to run an inhouse web server, but most of my customers don't have IT staff to maintain that. It is much easier to just ship an EXE file to the customer (via e.g. ClickOnce).

I would love to use Silverlight for the distribution. Silverlight 4 adds access to local COM resources, but access to native code seem to be far away.

Carlenacarlene

Answer 7

WPF and Windows Forms are starting to lose relevance in a lot of use cases. The only places where they still are a compelling presence, would be deep within the Windows/Windows Server ecosystem. For instance, you still can't write professional-grade Office plug-ins, without using WPF or WinForms.

In a more general use case, such as a classic CRUD application, for instance, you could get away with an app written in Angular or React. If you require OS-level privileges, it's easy enough to convert over to Ionic, React Native, or Electron, and get that deep functionality. Sometimes the functionality truly exceeds what you get "out-of-the-box" from WPF or WinForms (toasters, for instance are way more functional with Electron, since it leverages the next-gen HTML5 notifications). The coding experience is more REPL, and the actual code that you have to write is a lot less ceremonial (IMHO) than WPF or WinForms, so that's a big draw.

It's interesting to note, that VS Code is written in Electron. In fact, there is a significant, growing number of mainstream Electron apps.

Karli

Answer 8

Well, a Windows or WPF application is by far more powerful in many ways and faster to develop a richer application that is more responsive. Web applications need little more than a log on from almost anywhere but you will usually find then far more clunky and limited in functionality. So, you want a powerful Windows application with easy to use web connectivity? Simple, just create onw. We did and we can deploy a fully powered Windows based application (well WPF with amazing graphics and functionality), that our customers can log in from anywhere with the speed of a web application but without any thin client or expensive networks. My vote, stick to a windows app and leave the grunt of a web solution that provides little to those who want to develop in that technology. Having said that web is the only way depending upon what you are trying to do but if you are delivering a commercial product then say no more.

Spiroid