Client side install experience is what mobile apps have, and everyone seems to prefer them to web apps.
Web apps also have major downsides. It's easy to forget about them as developers, but for example, one is the lack of versioning. Someone pushes a new version of the app that's buggy/an UI downgrade/causes an outage and the users can't do anything about it.
Often you want an app to be local because it's interacting with local data, or local hardware, or it suffers from latency, or you don't want your data to go outside your jurisdiction, or it's doing something else where distance between you and the app is problematic.
Client side apps written using normal toolkits (not HTML) have a lot of major end user advantages, which is why:
• Mobile apps beat web apps, despite devs trying to make users accept them (recall the history of the Facebook app for example).
• HTML5 keeps sprouting features that desktop apps have had since the beginning. Filesystem access is a recent example.
Any time you want your data to be independent of the apps that work with it, web apps just faceplant.
In my view developers push web apps on users usually for our own convenience, e.g. being easier to bypass IT department bureaucracy. But there's a lot of ways to do better than web apps, and yes, the JVM is pretty good platform to do that on (JavaFX is a great toolkit for instance, and JetPack Compose is very interesting). What it needs is a great distribution and update solution.