osel
Joined 9 years ago
Joined 9 years ago
I'm working on a new project to build some simple workflow applications for business, and one of the aspects I would like to attempt to resolve is the speed of input. It is painful watching operators work with modern GUI inputs, particularly web based as the mouse work slows them down horrendously. And keyboard 'shortcuts' where they exist are often anything but, as the entire GUI model assumes a mouse (or on the web a Document) first.
It is like you mention about this CSS library, it kind of misses the point in that the awesomeness of TUI is not in the appearance, but rather how workflows that the constraints of a keyboard-first interface enforce allow creative and highly efficient solutions.
When all you have is a mouse everything becomes a click, and that is a horrible way to input data.
It's a dark pattern Apple repeats with a lot of notifications - they are not dismissible and give the appearance they are only resolvable by completing the notified request, but it actuality just starting the setup and then cancelling will resolve it.
Having a lightweight reference for simple things that I only do occasionally is a godsend and a massive time saving. I can dive into Deployment from Scratch and tweak something that needs updating, or even deploy a new system in less time than it takes me to lookup and parse/refresh my knowledge from the actual documentation on most topics. And even if I do need to refer to the docs for something not in the book, it is much much quicker as I have the context already.
I’ve got a 2020 iPad Pro and was having great trouble using it until I accidentally found something online that suggest I turn of TrueTone. The effect was instantly noticeable. Before I could only look at the screen for a few minutes, now it is much more like my desktop where it takes hours to get eye strain.
For simplicity there are a whole host of underlying assumptions about what a work day is, what time spent means , etc.
Explaining at least some of those assumptions is on my list of improvements, but there will never be a 'correct' answer in a generic form like this. It's more intended as a quick investigation/conceptual check.
At the moment it assumes 1 year for training costs to be amortized over, so I guess one-time purchase would be similar - configurable assumptions (or at list, visibility into the assumptions) is on the list of things to do.
I submitted this just before retiring for the evening NZ time thinking not much of it, it was awesome to find this discussion this morning!
A few people expressed interest in embedding something similar in a landing page, so I've open-sourced the code for others to use if they wish.
- Super simple buttons
- No clock if you don’t set it (it turns off after a few minutes of first power on)