alt Hacker NewsI use eInk as my daily driver and do everything including ssh into tmux into vim and code on eInk.
I build all my UIs with Rust and Ratatui. It works very well.
So for web, I think it would translate to:
0) NO ANIMATION. You have like, 0.3 fps. You might poke somebody’s eye out if you animate something.
1) NO SCROLLING. Pagination only.
2) Use actual added visual element to tell the user where their input control / cursor / selection is. Don’t rely on color, font weight etc. Put an asterisk, Unicode arrow or something.
3) Direct(?) action controls. A button should DO something. Don’t give me a button that opens a drop-down that opens a menu to do something.
4) Use the whole screen! Keeping a pixel on/off costs nothing. Only changes do. So any whitespace is just sacrificing screen real estate and forcing more frequent changes.
Replies
All the conditions you describe are a graphic designer's wet dream, I love it
> Direct(?) action controls. A button should DO something. Don’t give me a button that opens a drop-down that opens a menu to do something.
That works until it doesn’t. Screen real estate is limited and touch accommodations are expensive. You have to be mindful of what you expose and what you hide. There’s no point in flooding the UI with buttons when people can barely make them out or even interact with them accurately—a mistouch is a lot more expensive than two correct touches.