> I'd write a cross-platform HTTP local-server and use the regular browser.
That doesn't actually solve the biggest problem. How do you package up that server? Can you make it something people can run like a regular executable on that platform? How do you distribute it?
Right, it doesn't address that at all. Browser's have minimal support for local cross-browser apps.
The fact that you can't easily piggyback on the local browser irks me somewhat. If it's inherently a behemoth, maybe have it be reusable, i.e. piggyback friendly. You wouldn't want a per-app installation of Qt, for example, but even that would be less stressful on the system.
I have a lot of fantasies about how the web stack could be different. I guess that's reflective of some kind of frustration.
For many apps I'd ask if it really needs to be local. I've had some success with compiling my application to a pile of javascript and then it's possible to go from there to "works offline" functionality, at which point you have a de facto local application that just happens to be opened by putting a particular URL in the browser.
I wasn't aware that that kind of offline web app was possible. I'm surprised there aren't more of them.
My impression was that with an offline capable web app you need CDNs et al to be reachable to load the web app, and then if connection was lost the app could handle it, but if you were to close and reopen the app, it would again need an internet connection to load.
That doesn't actually solve the biggest problem. How do you package up that server? Can you make it something people can run like a regular executable on that platform? How do you distribute it?