Do you know of any good resources that discuss TUI user interaction/research?
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.
You can remove the 'iCloud' notification by starting the setup for it, and then cancelling.
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.
Do you know if this is related to why Apple’s TrueTone would make me feel nauseous too?
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.
Exactly, and scale is important too. The initial target audience was small (as in very small, maybe 1-10 people) businesses, whose owners often don't intuitively understand how beneficial small services costs can be.
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.
Hmm, cost of meetings (similar to training costs) is a good idea, definitely an issue I've seen before - thousands of dollars wasted arguing over $50/month for a tool.
Cheers, a few people of suggested this. As you note, it rather depends on the amortization period.
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.
This is just an iPhone 8 mk II (it even fits 8 cases!), and that means those of us who want an actual SE replacement are now out of luck. Rather disappointing.
I’ve found sketchy styles to be immensely useful in getting clients to focus on UX and structure rather than getting stuck on minor irrelevant details. My background is construction, and architects do the same thing with initial concepts.
The disabled toolbar is easier because it still gives context and confidence you are looking in the right place.
'This is what I want...hmm...how do I make it work?' is a far easier process than 'I can't find what I want...where on earth is it?..does it even exist?'
From my brief play with your demo it's a bit of both.
The toolkit is very small and lacks good definition of elements (both visually in that it lacks contrast, and practically in that I have no idea what is clickable or editable).
The page structure isn't that clear either, where are the column headings? And on my widescreen browser window the isn't a limit on horizontal stretch - I have to play with the browser to find a good width. Also, I can expand code, but how do I shrink/hide it?
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.