I spent 8 months solo-building a time-travel puzzle game for my kids — launched yesterday with zero audience
Hey Indie Hackers 👋
Long-time lurker, first-time poster. I launched Chronos Time Puzzle two days ago after 8 months of solo dev — and I want to share the honest journey.
What I built
A narrative puzzle-adventure where kids travel through 3 eras (Prehistory 🦕, Renaissance 🎨, Future 🚀). Actions in one era ripple to another — teaching cause & effect through play.
Three age-adaptive modes:
- Wonder (4-7): tactile puzzles + printable parent certificate
- Discovery (8-11): gentle narrative causality
- Engineer (12-16): complex logic paradoxes
Anti-features I'm proud of:
- Zero ads
- Zero in-app purchases
- Zero data collection without parental consent
- COPPA & GDPR-K compliant by design
- 12 languages (Arabic RTL, Japanese, Chinese included)
- Works offline
The Stack
- Frontend: React + Tailwind + shadcn/ui
- Backend: FastAPI + MongoDB
- AI: Claude Sonnet (hints), OpenAI TTS (voice narration), Sora 2 (trailer), Gemini Nano Banana (Grimoire illustrations)
- Infra: Deployed via Emergent, DNS on Cloudflare, transactional emails via Resend
- PDF: reportlab (with Arabic RTL and CJK support)
The honest metrics after Day 2
- 🐦 X thread posted → 1 like (mine), 0 retweets, 0 replies from strangers
- 🔴 Reddit r/SideProject post → filtered by AutoMod (new account)
- 🔵 Hacker News "Show HN" → restricted (new account)
- 💼 LinkedIn post → few likes from personal network
- 📧 New beta signups → 0
Yeah. Zero.
What I learned in 48h
- No audience = no launch. You can't shortcut "build in public" — you need to be public BEFORE you build. I did it in reverse.
- Anti-spam filters are everywhere in 2026. Reddit, HN, IH, BetaList — all block new accounts. The bar to distribute is higher than the bar to ship.
- The people around me are skeptical. Not a single friend RT'd or shared. That hurts more than the metrics — but it's also strangely liberating: nobody's expectations to meet.
What I'm doing next
- Reddit round 2 on r/webdev Showoff Saturday (account is now mature)
- Product Hunt "Upcoming" prep for a real launch in 7-10 days
- Building LinkedIn presence for the EdTech/parent audience
- Consistency over 30 days — not chasing overnight virality
Questions for the IH community
- Anyone here launched an EdTech product solo? How did you find your first 100 users when your inner circle doesn't get the vision?
- Is "no ads, no IAPs" a viable model for kids' games? Or should I add a €5 one-time unlock for the full Grimoire?
- What would YOU test on the landing page? Brutal honest feedback welcome. Link in my profile.
Building alone is lonely. This community is one of the few places I feel understood.
Thanks for reading 🙏
With zero signups, the bigger question may be demand before pricing. Have any parents or kids shown enough interest to justify testing a paid unlock?
That plan sounds much sharper.
I wouldn’t treat 10 families as a statistical answer. I’d treat it as a pattern-finding test. For me, 4/10 coming back unprompted would be “there’s something here, keep digging.” 6/10 would be a much stronger signal that Discovery deserves the next proper push. But the notes will matter as much as the number: where they stop, what they ask for, whether parents have to explain the goal, and whether the kid talks about it after closing the app.
For recruiting, I’d start with friends-of-friends first because trust matters a lot with kids’ products. Then maybe small parenting or homeschooling groups where you can be transparent that you’re looking for observation, not promotion. I’d avoid broad Reddit as the first test. Too much noise, not enough context.
And yep, Discovery feels like the right first bet. Old enough to play independently, young enough that the cause-and-effect mechanic can still feel a bit magical.
Stefan, this is a full playbook — I'm literally converting your advice into a Notion doc right now.
Three things I'm actioning this week:
Recruitment funnel: friends-of-friends first (I have 3 target families in mind), then I'll approach 2 homeschooling parents I know on LinkedIn — transparent framing as "observational research, no promotion, no price mention." Broad Reddit dropped from the plan.
Observation protocol (not just a return counter). I'll build a lightweight 4-question note-sheet per family:
Signal thresholds: I'll hold my product decisions until I have 8-10 families through (not 3). 4/10 unprompted returns → "keep digging" (product tweaks). 6/10+ → "push Discovery to a public campaign with the €5 unlock."
The "after-effect" question is the one I hadn't thought about at all. If a kid brings up a chapter at dinner without prompt, that's the deepest engagement signal a kids' game can have. Adding that to the sheet.
Will report back in ~4-6 weeks with the pattern notes, good or bad.
Thanks again — this genuinely reshaped my next quarter 🙏
Two days with most channels blocking the post isn’t a product verdict. It’s barely a distribution test, so I wouldn’t read much into the zero yet.
I’d narrow the next test rather than launch more broadly. Ages 4–16 are really three different markets, so pick one mode, put it in front of 10 families, and watch whether the kids return without being prompted. If several finish the five free chapters and ask for more, the €5 unlock becomes a much easier decision.
Which mode did your own kids keep coming back to?
Stefan, this is exactly the reframe I needed. "Not a product verdict, just a broken distribution test" is going on a sticky note.
I owe you a correction on the question though: my daughters are 21 and 27 — so the "built for my kids" framing in my post is retrospective, not literal. This is the game I wish had existed when they were young, before free kids' apps became ad-farms. Watching that shift from the parent side over 20 years is what pushed me to build.
Which means I have a real gap you just pointed at directly: I don't have live child-user data. My testing so far has been product-heuristic-driven (COPPA age gates, screen-time research, parental control patterns), not observational. That's cheap validation and I know it.
Your suggested test is the missing loop. Applying it, here's my plan:
Two follow-ups if you have a minute:
Genuinely grateful for this comment. It beat 100 upvotes.
I wouldn’t make 4/10 a hard pass/fail rule with such a small sample. Four unprompted returns would be promising;