Ultimately though, I would like Textual to simply be the easiest way of creating a useful UI. Something that you could quickly become productive in with just Python skills. There are a lot of new Python developers that didn't come from a web background, but still need a custom UI.
I don't see it as replacing web apps. If you have the skills and you think you need a web app, then you probably should make a web app. I see it more as allowing UIs to be built that simply weren't being built before due to a lack of skills or resources.
This may become moot, because we have plans for the same API to also serve web applications.
SSH is a great option that I hadn't thought of, and that's good to know it works well over it. I have always seen web UIs being inherently easy to share as a benefit over others, but for dev-focused stuff and SSH connection isn't much harder than web access.
I wasn't thinking about full web apps, more things like status pages and other little utilities exposed on an internal server interface. I've built these for software before, and things like Fish Shell have them too. I'm not sure they require much in the way of web skills, but pure-Python would certainly be easier.
For those loving Textual, can I ask why you’d use this over, say, a web UI?
There’s a joy to using well made libraries and frameworks like this, but apart from that I’m having a hard time justifying this to myself for projects and keen to hear what others are using it for where it’s a better fit than other types of UI.