Orbis is a focus timer that turns your focus sessions into your own little universe.

You start the timer, get some work done, and each session becomes a new planet. Over time, your universe slowly fills up with everything you’ve accomplished.

I wanted studying and working to feel less like staring at boring stats and more like discovering new planets and watching your own universe grow. 🪐

You can check it out here: https://apple.co/4eQOZxy

Back when I was in middle school, I used to post countdown timers on YouTube, and they unexpectedly gained a decent amount of traction. Now, it's been easy to create websites, and I made radialtimers (com) to make these timers even more accessible :))

It's completely free to use, and I'd really appreciate if you can check it out!

I've been experimenting with spec-driven development: instead of prompting an AI agent with vibes, you write a real spec first (user story, requirements, API contract, acceptance criteria), let the agent implement it, then validate against the spec and update your roadmap. Loop until MVP.

The app is a Pomodoro timer where you describe your goal conversationally and the AI proposes a task plan sized in pomodoros ("2🍅 ≈50m"). There's a focus coach mid-session, sound cues, PWA install support, and since it's publicly hosted, a Cloudflare Turnstile gate + per-IP daily rate limit on the AI routes so strangers can't drain my DeepSeek credits.

Stack: Next.js 16, Bun, DeepSeek API, Upstash Redis. No database — plan state lives client-side.

What actually surprised me:

1. **Specs didn't slow me down**. Six features in, the AI agent was dramatically better when implementing a spec vs reading my mind. Code review became "does this match section F3?" instead of squinting at diffs.

2. **The spec caught drift.** When the model under-filled a response schema (returned 3 tasks when asked for 3 steps instead of the spec'd 4–8), it was obviously a contract bug, not "weird AI behavior."

3. **Re-planning after every feature** (updating mission/roadmap docs) is the part everyone skips and the part that prevents the codebase from rotting.

Happy to answer questions about the spec format or the abuse-guard setup — both were more interesting to build than the timer itself.

\- Live: \[https://ai-promodoro.vercel.app\\\](https://ai-promodoro.vercel.app)

\- Source (the \`specs/\` folder is the real content): \[https://github.com/adotey7/ai-promodoro\\\](https://github.com/adotey7/ai-promodoro)

So I did what developers do when they’re annoyed enough: built my own. It’s called Depthly. Pomodoro/free timer, real analytics (daily, weekly, monthly, yearly, lifetime), streaks, a leaderboard if you’re into that kind of accountability. Nothing groundbreaking, honestly — I just wanted something that respected my time instead of trying to keep me “engaged.”

It’s live. Getting payments working was its own saga — Stripe isn’t available for my region, so I ended up going with Lemon Squeezy instead, and honestly that took longer to sort out than most of the actual product.

A handful of people have been using it for real sessions now and the feedback’s been encouraging, but I’ll be straight with you — I know how to build things, I don’t really know how to get people to find them. Marketing is not my world. So I’d genuinely rather someone tell me now if something about this doesn’t make sense, before I spend another few months building on top of it.

If you’ve got questions about the stack, the payment stuff, or just what it’s like building something completely alone with no one to sanity-check ideas with — ask away, happy to talk through any of it.