Typography as Interface Logic

I spent an embarrassing amount of time on Rift's typography before I understood why it mattered beyond aesthetics. I kept adjusting font sizes and weights without feeling like I was getting anywhere. Then I realised I was treating type as decoration rather than structure.

Here's the shift that changed how I work: typography is a hierarchy system that the user reads before they read your content. The moment someone lands on a page, their eye is already parsing the size relationships, weight contrasts, and spatial rhythm of the text — forming an impression of the information architecture before a single word registers.

Once you accept that, choices like line-height stop being aesthetic preferences and start being arguments. A line-height of 1.4 says: "this content is dense, read carefully." A line-height of 1.9 says: "breathe, take your time."

Practical things I've changed because of this framing:

Scale with fewer stops. Most projects I see use 6–8 distinct font sizes. I rarely use more than 4. The contrast between each stop matters more than having many options. A jump from 14px to 32px reads clearly; 14px to 18px to 24px to 28px to 32px reads as noise.

Weight over size for emphasis. Bold at the same size is almost always cleaner than larger at the same weight. It emphasises without breaking rhythm.

Treat font choice as brand positioning. The font you choose is the first opinion your interface expresses. Inter is fine. It is also saying nothing. That might be exactly right for your product — or it might be a missed opportunity to say something.

Typography, at its best, is invisible infrastructure that shapes every reading experience on your site. Worth the time.