Roast my new tool: The ad-free, dark-mode PWA Online Alarm Clock & Timer (Be brutal)
Hey Indie Hackers! 👋
Most online alarm and timer websites look like they were built in 2012. They are clunky, glare with an all-white background (ouch), and are absolutely flooded with intrusive ads. I got tired of it.
So, I decided to build a modern, distraction-free alternative: https://onlinealarmclock.io.
My goal was to create a sleek utility that respects the user's focus (and battery). I built it using:
Native Dark Mode (easier on the eyes).
Progressive Web App (PWA) support—you can install it.
The Wake Lock API so the alarm actually works in the background (no lagging alams!).
I’m really aiming to refine the DX (Developer Experience) and UI/UX for developers who need a quick focus tool. So, please be brutal. I need your honest, raw feedback:
Is the UI too minimalist or just right?
Does it feel lightweight and fast?
What critical features am I missing? (e.g., Do I need specific loops for Pomodoro sessions?).
I'm ready to roadmap your suggestions.
Thanks in advance for the roast! 🙏
Nice angle, especially for people who just want a timer without the junk. One watchout that gets missed on clock and timer PWAs is background behavior on mobile, a lot of them look fine until the browser sleeps and notifications or audio fail. Worth testing hard on iPhone and Android lock screen cases, because that is where trust gets won or lost.
Spot on! Mobile background execution is definitely the final boss for browser timers. I'm currently utilizing the Screen Wake Lock API to prevent the screen from sleeping, but as you mentioned, iOS lock screen audio handling is notoriously strict even with Service Workers. I'll be running rigorous tests on physical mobile devices this week to ensure it doesn't fail silently. Thanks for the crucial heads-up!
The ad-free dark mode angle is the right call — that's a genuine pain point. One thing to think about: 'online alarm clock' is a utility search, meaning people land, use it, and leave. The PWA install is your retention mechanism but most users won't install unless they're prompted at exactly the right moment — after the alarm actually fires successfully. That's when the value is proven and the install ask makes sense. If you're prompting on first load you're asking before they trust it.
Wow, this is incredibly insightful. You absolutely nailed the user journey. Prompting for the PWA install on the first load is definitely asking for marriage on the first date. Delaying the prompt until after they experience a successful alarm ring makes perfect sense for building trust and proving the utility's value. I'm adding this event-triggered prompt logic to my immediate to-do list today. Thank you so much for this!
Exactly — trust has to be earned before you ask for commitment. Good luck with the implementation, curious to hear if install rates improve.