What are some reasons to switch to a "native" desktop stack over a web based one?

Hello my dudes.

My main projects over the past year were software solutions for various businesses. My model so far:

1. Gather relevant information for planning.

2. Develop a web app.

3. Deploy it to their network for consumption.

I chose to create solutions as web applications (even if most of the time internet connection is not required) because web development is my domain and being cross platform is important. Another point is that these are not mission-critical solutions that need to squeeze the maximum performance to operate; continuous delivery is much more valued.

So back to the question(s):

• What are some reasons to switch to a "native" desktop stack over a web based one?
• What are some good options that you can recommend based on the information above?

I could see some greenfield projects in the near future, so I'll be really appreciative for your input!

Comments

[Avalander]

What are some good options that you can recommend based on the information above?

Have you considered electron? You can use it to build desktop applications with the web stack that you're already familiar with.

[John Alcher]

Hey thanks for the suggestion, but I'm looking for native implementations. I don't really see the improvement over my current model if I use Electron.

[Avalander]

So, what do you mean by "native"?

[John Alcher]

Hiya! I definitely agree on your points. But can you expand on a couple of them, specifically

...Reliability and predictability of desktop platforms.
...Higher flexibility in terms of UI/UX.

---

Oh, IDK if it's just familiarity and lack of knowledge, but I definitely had an easier time downloading Bootstrap writing HTML and CSS in comparison with Qt (with Python bindings) or that GUI creation library in Java.

With that said, C++ and Qt sounds interesting! Any particular resource you can recommend to get started?

[esam a gndelee]

desktop apps means enterprise senario. in this senario you need something that will be staple for loooong time. web apps can be affected by browser updates.
microsoft is famous of long term combatibility.
my advice : winforms.
wpf is glmore modern but diffecult to use and slower

[John Alcher]

Update: after a month of tinkering around, I found out that Java's GUI offering isn't actually that bad. Swing and JavaFX with their respective scene builders is quite nice to work with after some familiarization. Hopefully I can try it out in a real project and see how it holds up.

[John Alcher]

Thanks a bunch! Though after an hour or so of reading up, it looks like licensing could be an issue if I ever pursue Qt. The fee is quite heavy for my liking :/