Designing a clock you don't read
Most clock apps are designed to be looked at. Huge Clock Digital is designed to be glanced at — and that one distinction changed every decision in the product.
There is a difference between reading something and glancing at it, and almost every clock app gets it wrong.
Reading is deliberate. You bring your attention to the thing, you focus, you parse it. Glancing is the opposite: your attention is somewhere else entirely, you look for a fraction of a second, and you need the answer to already be there. Nobody picks up a bedside clock at 3am to read it.
When we started work on Huge Clock Digital, that was the whole brief. Not "build a clock app" — build something you can resolve in a fraction of a second, from across a room, half-asleep, without your glasses on.
Everything follows from the distance
Once you decide the product is for glancing, a surprising number of decisions stop being matters of taste.
Type size stops being a style choice and becomes a legibility requirement: the digits have to survive being viewed from three or four metres away, which is much further than any default clock face assumes. Contrast stops being a mood and becomes a function of the viewing distance too — at a glance, from an angle, in a dark room, subtle grey-on-grey numerals simply fail.
And the layout has to be ruthless. Anything that isn't the time is competing with the time. That is why the full-screen mode exists and why it is one tap away: it removes every remaining thing that could take a share of that half-second.
The 3am problem
A bedside clock has a genuinely hard constraint that a desk clock does not: it has to be readable in a dark room without becoming the brightest object in it.
This is a real tension. Increase brightness and you get legibility, but you also get a device that lights the ceiling and keeps someone awake. Decrease it and you get a clock that is comfortable but no longer glanceable — which defeats the entire product.
The answer was to treat night mode as its own design state rather than a dimmer slider bolted onto the day view. Dimmable brightness lets the display drop far lower than a normal app would allow, and because the layout is already high-contrast and enormous, it stays readable at brightness levels where a conventional interface would disappear.
Staying on is a feature, and a problem
A clock that stops being visible is not a clock. That is why the app runs as a foreground service: it keeps the display and widgets alive rather than being quietly stopped in the background while you use something else.
But a screen showing the same digits in the same position for eight hours is exactly the scenario OLED panels are worst at. Static, high-contrast, unchanging content is what causes burn-in.
So the always-on behaviour comes with anti-burn handling — the image shifts over time so no single pixel carries the same bright element all night. It is invisible when it is working, which is the point. Auto-close options exist for the same reason: some people want the clock up all night, others want it to stand down after a while, and the app should not decide that on their behalf.
What we would tell ourselves at the start
The useful lesson was that "make the text bigger" is not a feature — it is a consequence. The feature is the decision about how the product will be used, and how far away the user will be when they use it. Once that was settled, the type size, the contrast, the full-screen mode, the night mode and the burn-in handling all followed from it, and stopped being arguments.
Everything else — the fonts, the colours, portrait versus landscape — is personalisation layered on top. It matters, and people use it. But it is not what makes the product work.