Date Clock

The Problem

Digital clocks give us more precision than most decisions actually need — a countdown to the second for something that only matters by the day or the week. I wanted to design a timepiece that was deliberately, transparently imprecise, and see whether users would still trust it, or even prefer it.

The Approach

Date Clock uses real dates — the fruit — wired as a voltage divider. As the fruit dries out over days, its conductivity drops, and that drop becomes the "hands" of the clock. There's no display to read at a glance; the state of the object itself is the interface, and understanding it requires the user to build a mental model over time rather than parse a number instantly.

That was the core design bet: could an ambiguous, decaying signal still function as usable information if the feedback loop was slow and embodied rather than instant and numeric?

What I Learned

People adapted to reading the object faster than I expected — after a day or two of exposure, testers described developing their own rough sense of "early," "midway," and "spent" without any labeling from me. It made me think differently about legibility: precision and usability aren't the same thing, and sometimes a rougher signal that a user has to build familiarity with creates a stronger relationship with the object than a screen ever could.