Night Clock
An Android bedside clock with deep customization, voice alarms, and a UI designed for nighttime eyes.
A nighttime utility for adults aged 40+ and remote workers who keep a clock near the bed or workstation. Analog or digital, fully customizable, designed to glance at in the dark without breaking sleep. This was my first project with the Product Owner who later became a recurring collaborator across three more apps over the following two years.
A new partnership, tested on the first project.
This was my first project with the Product Owner — the entry point to what later became a three-year, multi-app design partnership. The brief was a focused MVP: an Android-only bedside night clock with deep visual customization and a voice alarm.
The strategic framing was bigger than a single app. The plan was to ship three separate apps — Night Clock, Sleep Sounds, and Sleep Tracking — independently, measure which got real traction, then later combine the winners. Night Clock was the first move on that board. Android-only by design — cheaper to launch, and the target audience over-indexes on the platform.
Earn trust, ship in a saturated niche.
A new partnership, a crowded category, and a UI that has to work in the dark — without burning eyes or losing legibility from across the room.
First-project credibility
A new Product Owner, a new working relationship. The product mattered, but so did establishing how we'd work — shared decision-making, clear communication, mutual trust. Future collaborations would depend on what got built here.
A saturated niche
Bedside clock apps on Play Store are everywhere. To stand out the product had to differentiate on functionality and UI quality, not just feature count. The opening: most apps in the category felt either visually dated or feature-thin — there was room for something in between.
Designing for nighttime eyes
Most app UIs are designed for daylight. This one had to work at 3 AM, in pitch dark, glanced at from across the room. The constraint stack: legible from distance, comfortable for eyes adjusted to darkness, accent color that reads without glare, typography that doesn't blur under low contrast.
Monetization without breaking the use case
The core use case is not engagement — users open the app to fall asleep. Standard ad-driven monetization risks interrupting exactly the moment that defines the product. We had to design where and how ads appeared without compromising the nighttime experience.
Bullseye-shape the gap between dated and thin.
Discovery & competitive analysis
I went through the main competitors on Google Play plus iOS leaders for cross-platform reference — to map functionality, visual patterns, and monetization models in use. The pattern was consistent: apps in the category were either visually outdated (working features but legacy aesthetic) or too thin (clean UI but missing the customization people actually wanted).
The product hypothesis settled into building the middle ground: modern visual quality with the customization depth long-term users expect. Long-term retention and LTV were the primary metrics, not first-week installs.
Strategy alignment
We brainstormed the entire project side by side — functionality, monetization, usability. I came in with active input on every layer of the product, not just visual decisions. The Product Owner later flagged this as the moment our working pattern was set. It's why this collaboration kept going and three more projects followed.
Visual identity & UI
Dark theme as the default, built for nighttime use — with a light-theme paywall surface built later to test a hypothesis about remote workers using the clock during the day — though a full light-mode UI was never completed. Typography chosen for clarity at distance and verified against WCAG contrast and legibility standards. The primary accent: a light cyan-blue — the color most people unconsciously associate with bedside clocks, because LED clocks went blue after the year 2000 once blue LEDs became commercially viable. The choice carries quiet nostalgia. Users can also override it from a palette of five (red, green, blue, yellow, purple) to suit their preference or partner's sensitivity.
Design system & engineering handover
Built a custom design system for the product — components, type, color, iconography — and handed over with full auto-layouts, named frames, organized icon sets, and animation previews embedded in the prototype. The engineer started development the same week without back-and-forth on specs. Every project we did together since has used the same handover standard.
A nostalgic cyan-blue default, with five customizable accent options — the small detail that made the clock feel personal.
Three calls that shaped the product.
Onboarding that already feels like using the app
Most utility apps either skip onboarding entirely (and lose users who can't find features) or front-load with explainer screens (and lose users who skip them). Either way, the first impression is friction, not value.
I designed the onboarding as the first real use of the product: the user picks their clock type (analog or digital), sets their accent color, and grants the permissions the app needs — with each permission explained in context. By the time onboarding ends, the user has already configured their clock, understood why each permission is asked, and seen the app's quality. The flow doubles as a feature tour without ever feeling like one.
Ad-first monetization with a paywall escape hatch
A subscription-first model would price out the audience for this kind of app. An ads-only model would interrupt the exact moment that defines the product. Neither in isolation works.
We landed on ad-supported by default, subscription as the relief valve — users who find ads disruptive can pay to remove them. Ad placements were designed around the sleep use case: never during the night state, never blocking the clock view, only at transition points where the user is actively interacting with the app. The model funds the product from day one without breaking the experience for the people who need it most.
Ad placement designed around the use case, not against it.
Deep customization as the long-term retention driver
For utility apps people open daily for years, the difference between churn and retention is whether the product feels like theirs. Static UI loses to apps that adapt.
I built customization into the core: clock size, position, 12/24-hour format, color, and analog vs. digital type — all adjustable from a single settings surface, with changes visible in real time. The customization layer wasn't a power-user feature added late. It was central to the product hypothesis: people don't just want a clock — they want their clock.
First project. Three-year partnership.
- Positive feedback from the Product Owner and engineer on the design quality, the handover standard, and the level of strategic input from the design side.
- Three more apps followed — Sleep Sounds, LumiNap, Cleaner — across the next two years. The working pattern set on this project carried directly into every later collaboration.
- Active partnership today, three years after the first call. Continued discussions about new MVPs and product directions.
- App discontinued from Google Play. The Night Clock / Sleep Sounds / Sleep Tracking strategy was reshaped, and Night Clock was sunset to focus on follow-up products in the same family.
What I'm taking forward.
First projects are about the working pattern, not the product.
The product mattered, but what got built on Night Clock was the working relationship — how decisions get made, how I show up, how I hand over. The product can fail. The pattern is what compounds across the next three projects.
Polished handover is design work.
Auto-layouts, named frames, organized assets, embedded animation previews — these aren't "nice to haves." They're what makes an engineer trust the design and ship it the way it was drawn. The handover quality on this project is why every project since has been faster.
In commodity utilities, retention is in the small details.
Nobody installs a clock app for its onboarding flow. But the onboarding, the accent color choice, the customization depth, the brightness behavior at night — these are what decide whether the user is still using the app six months later. The product is the sum of every small detail nobody thinks they care about.
The first project that started a three-year partnership.
Night Clock taught me that on a new client relationship, the design output matters less than the working pattern you build around it. The customization model, the handover standard, the strategic involvement — these are the things the next three projects rested on. The product itself was eventually discontinued. The partnership is in its fourth year.