I have been struggling with this question myself. Over the last 1.5 years, I have developed a relatively complicated Java desktop application. It is designed fo

I have been struggling with this question myself. Over the last 1.5 years, I have developed a relatively complicated Java desktop application. It is designed for use in a tugboat company. The same application is used by staff at desks on land and by crew operating out in the ocean with only occasional Internet access. A connected web app was out of the question. It uses a local SQLite database to synchronize when it is connected to the Internet. It has a very rich mapping interface to show courses, routes, etc. I could not stand the idea of forcing this into an Electron shell and the associated performance problems. As it is, I have a watchdog running inside the app that diagnoses any hangs of more than 100 milliseconds. (Such hangs are easy to fall into when doing GIS SQL queries.) I don't see how I could have had any better productivity as a developer using any other software stack, but man, the GUI is very dated and out of place.