Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Use smaller, data-oriented user interface sizes #92
I've been experimenting with different sizes on FrontierNav. Smaller font sizes, less padding, etc. The main reason being to reduce the amount of clicking around and scrolling to view data. This is especially important for #17 as finding the info you need can be repetitive and adding more steps doesn't help.
See the below screenshots for comparison. I've pushed the experiment to https://github.com/frontiernav/frontiernav/tree/experiment/small-monospace-font
In general, I do like the smaller font size and padding. It reminds me of the Haya2NOW dashboard. There's a consistency to using a monospaced font, though it's less readable to those not used to it.
I used Cousine as the font in the end as it was the most legible at 11px out of the other monospaced fonts on Google Fonts.
Brand-wise, it's also a nice callback to plain text gamefaqs walkthroughs which I hope to integrate into FrontierNav some day.
Initial feedback sides towards larger fonts, rather than smaller. This may be related to expertise, similar to how users familiar with an application would use no-so-obvious shortcuts rather than a mouse.
The smaller font size can also clash with other applications and operating system which tend to prefer larger sizes, around 14px. I used 12px in my experiment.
The reduced sidebar width may have also contributed to the feeling of "too much clutter" as details needed to use more lines in a tighter place.