Big box days and small box days.

Design · 5 min read

Every calendar app you've ever used treats Monday the same size as Saturday. Seven equal boxes in a row. Doesn't matter if Monday has six appointments, three medication reminders, and a hospital visit. Doesn't matter if Saturday is completely empty. Same box. Same weight.

That's not how people experience their week. Some days are packed. Some are quiet. You already know which days are big before you look at a calendar. The question is: why doesn't your calendar know that too?

How people actually think about time

When I was working on an NDIS life management app, the client described how his users think about their weeks. Not in terms of dates or times. In terms of weight. "Tuesday's a big day. He's got physio, his coordinator visit, and a medication review." "Sunday's nothing. He just watches telly."

That's a relational understanding of time. People don't think "Tuesday has four calendar entries." They think "Tuesday is heavy." And when you lay out a month view where Tuesday gets a bigger box because it has more in it, something clicks. You can see the shape of the month without reading a single word. Big box days stand out. Small box days recede. The pattern is instant.

This isn't some radical new concept. Treemap visualisations have been doing this with data for decades. The principle is simple: let the size of the element reflect the weight of the content. But for some reason, calendar design has been stuck in the same equal-box grid since paper diaries.

Why this matters for accessibility

For users who can't read fluently, a standard calendar grid is a wall of identical squares with tiny text they can't parse. They have to open each day individually to find out what's happening. That's a lot of tapping. A lot of loading. A lot of cognitive effort for someone who just wants to know "is tomorrow a big day or a quiet day?"

Variable-sized boxes give them that answer at a glance. Paired with day-of-week colour coding, the month view becomes a visual map. Big red box? Busy Monday. Tiny yellow box? Quiet Wednesday. No reading required. The design communicates through shape and colour, not text.

A family member checking in on their loved one doesn't need to read every case note. They just need to see: "big box days, lots happening, they're being looked after." That's reassuring in a way that a spreadsheet of appointments never could be.

Applying this thinking beyond calendars

The broader principle here is that visual weight should reflect informational weight. If a section of your app has more data, more activity, or more urgency, it should look like it. Not buried behind a badge count or a tiny number in the corner. Visually larger. Visually heavier.

Dashboards already do this with charts and graphs. But most app interfaces don't. They treat every list item, every card, every row as the same height, the same weight. That's a missed opportunity to let the design itself communicate meaning before the user reads a word.

Not every app needs variable-sized calendar boxes. But every app can benefit from asking: where am I treating different things the same when they shouldn't be? Where could visual weight carry meaning that text currently carries alone?

Sources
Calendar UI Design (Nielsen Norman Group) - Research on effective calendar interface patterns.
Treemap Visualisation - Using variable-sized rectangles to represent proportional data.

Related blog posts:

Colour isn't decoration →

Don't hide things from people who forget things →

Case study: NDIS life management app →