258 users in 2 days(Now 285) with zero ads — here's exactly how we did it (and the real problem we're solving)

300+ in 2 days is wild — the WhatsApp college group move especially. That's distribution, plain and simple.

I'm in a similar spot with HealthOS, except the opposite end: TestFlight's live, zero users so far. The distribution problem changes completely with the audience, though. WhatsApp groups are perfect for students. Health and quantified-self people are way more scattered — a niche subreddit here, a Discord there, some Twitter health circles. Harder to hit a room full of them at once.

Did you already have a foot in those WhatsApp groups, or were you cold-sharing into ones you found?

Love that you focused on getting users without ads and by really understanding the core problem first. I run retreats and a community for digital nomads in Zanzibar, and I also see how powerful word-of-mouth and relationships are compared to paid ads. Thanks for breaking down your exact steps – especially what you decided not to do, that’s super insightful.

Congrats on the insane traction! Going from zero to nearly 300 users in 2 days without ads is wild.Quick question as you start scaling this up: how are you handling security checks for your routes right now? Are you just relying on your framework's built-in protection, or have you done any manual logic checks (like testing for multi-tenancy flaws/IDORs) to make sure users can't mess with each other's data?Best of luck with the growth!"

I've watched tutorials for months without building anything that stuck. 285 in 2 days with no ads is real signal. Curious if the challenge format keeps people past week 2 - that's where most learning apps lose them.

The honest answer to 'is this worth working on': the insight is, your signup number isn't proof of it yet. 258 signups from WhatsApp groups and personal DMs in two days tells you the pitch lands, not that the product works. The metric that actually answers your question is week two: how many of those 258 come back and finish a challenge path without you nudging them. If that holds, you have something real. 'Busy but not learning' is a durable problem, so I'd build the whole thing around proving people retain, not around XP and gamification (which you already found nobody signed up for). One tactical note: your edge right now is that you lived the problem and can DM the exact people who have it. Don't trade that for paid ads too early, manual outreach is the unfair advantage at your stage.

This is impressive 👍

Impressive for 2 days, especially with zero ads. The WhatsApp college group approach is underrated — you went where your users already were instead of trying to pull them somewhere new.
The insight about "feeling busy but not actually learning" is the real hook. That's a much stronger message than "adaptive learning platform" — it names the exact guilt people feel. Worth putting that front and center in your copy.
One question: how are you thinking about retention? Getting 258 signups in 2 days is one thing, but coding challenge apps tend to have brutal drop-off after day 3. What's your plan for keeping people coming back?

The growth approach is right, and you already found the real lesson: you didn't win on the XP system, you won because you went where people already felt the pain and asked them directly. Manual WhatsApp and LinkedIn outreach doesn't scale forever, but it's exactly how you should start, because it teaches you the words your users actually use. On "is it worth working on": the signal that matters isn't 285 signups, it's whether they come back next week and finish a challenge path. Watch 7-day retention and how many complete a second session. If people keep returning to practice, you've got something real. If they sign up and vanish, the problem is real but the solution isn't sticky yet. Either way, shipping at 18 and getting 285 humans to try it is a genuine start. Keep going.

Stories like this motivate me a lot to continue developing my services. I'm happy that you've achieved these results hope to get there someday too.

This is worth working on. The tutorial trap is a real problem, and turning videos into active coding challenges makes a lot of sense.

258 users in 2 days with no paid ads is a strong signal. I’d focus next on retention and whether students actually finish the challenge paths.

One of the most honest breakdowns on here.
The part that stands out: you led with the problem before pitching the solution. Most founders do it backwards.
258 users in 2 days without ads means your messaging was doing the heavy lifting — people only share things that describe their pain better than they can themselves.
What was the single line of copy that drove the most signups? Curious whether it was pain-focused or outcome-focused.

I'd push back on treating 258 signups as validation just yet — those came from WhatsApp groups and your own LinkedIn DMs, warm channels where people sign up partly because it's you personally asking. The number I'd actually watch is day-3 return: how many came back and finished a second challenge path? Your real wedge is one line near the end — students 'tired of feeling busy but not actually learning.' What does retention look like so far?

The real signal here isn't the 258, it's WHY they signed up: 'tired of feeling busy but not learning'. You found the pain, not just a feature. That's worth working on. The manual distribution (WhatsApp groups + DMs) is also the honest lesson most people skip - it doesn't scale, but at 2 days in it's exactly right, because it tells you if the pain is real before you spend on ads. My only worry for you: retention. Lots of students will try a learning tool once. The question that decides if this is a business isn't signups, it's how many come back on day 7. Track that next.

the WhatsApp college groups distribution is something most founders completely overlook because it feels too simple.
but that's exactly why it worked — you went where your users already trusted each other, not where founders hang out.
genuine question: did you validate the idea before building or did you build first and then share? trying to understand if the 258 came from pre-existing demand or the product itself.

this is exactly what i'm trying to figure out right now. i'm about to launch
my first app (solo, no ad budget) and the "how do you get the first users
with zero spend" part is the scariest. saving this — the zero-ads angle is
gold.

That is impressive. What does success looks to you and your team?

We are LIVE on Product Hunt! 🚀
14 days ago, I set out to solve the massive friction between raw data and usable UI.
Today, I'm shipping Axelr AI—an intelligence execution platform designed to automate the bottleneck.
⚡ No manual data entry.
⚡ No manual UI boilerplate.
⚡ Just production-ready results.
I'm 16, I'm building this solo, and I’m ready for the real-world feedback.
Support the launch.
If you're a builder, developer, or founder—come stress-test the engine. Let's build.

258 users in 2 days without paid acquisition is a good signal, but I'd focus less on the signup count and more on whether users keep coming back to complete challenges. If the retention is there, it definitely feels like a problem worth solving.

That’s cool! Trying to get my first clients too 💪

The passive-retention gap is such a real problem to build on. The watch-and-feel-productive trap is everywhere, not just coding. We are building in a totally different space, learning that actually sticks, and we landed on the same core belief: if the user is not actively producing something, almost nothing stays. The adaptive path rewriting itself is the smart part, that is where retention really lives. Genuinely curious where the first 258 came from with no ads. Was it one channel that overperformed or a slow spread across a few?

the part I'd want to understand is the moment after someone completes a challenge path. do they feel like they can build something from scratch or do they feel like they completed a set of exercises. those are different outcomes and the second one has the same problem as tutorials just with more active participation. what does your most successful user look like and what did they do after finishing a path

258 in two days with zero ads is a real signal, and the sharpest line in your whole post is the one you almost threw away: people signed up because they were tired of feeling busy but not actually learning. That is the product, not the XP system. Most ed-tech sells engagement mechanics. You found a shame people will not say out loud until someone names it for them. Put that sentence on your landing page, because right now it lives in your head and in this post but not where a cold visitor sees it first.
One honest caution from someone who ships small things solo. Those 258 came through WhatsApp and DMs, which is warm traffic from people who already trust you or feel a bit obligated to help. That is exactly the right move at day two, it tells you the pain is real before you spend a rupee. But it has a ceiling, and it flatters your numbers. The metric that actually decides whether this is a business is not signups, it is how many strangers come back on day seven and finish a challenge without you nudging them. Watch that number more than the signup counter.
So yes, worth working on. Just measure the right thing from here. Good luck.

258 users from WhatsApp groups and personal messages is a better result than most founders get from paid ads. The "busy but not learning" angle is the thing. That's a real pain people recognize immediately.

A product’s value ultimately comes from the strength of the demand behind it, and your approach is a valuable example for others to learn from.With the rise of AI, I think understanding real product demand matters more than ever. That’s how you solve problems at the root and build something people are genuinely happy to use.

The line that stuck with me wasn't the 258 — it was that people signed up because they were tired of feeling busy but not actually learning. That's the real wedge, not the XP system.

My first ~30 installs for a tiny iOS memo app I build solo came the same way: two honest replies in one niche community, zero ads, and everyone who converted had lived the exact friction first. Manual outreach feels unscalable, but early on it's the only thing that tells you the problem is real instead of imagined. One thing I'd watch — WhatsApp and LinkedIn shares tend to spike then flatten fast once the obvious groups are tapped. Did you see a second-day drop-off, or is retention holding past the launch rush?

You got the successful launch like FB did. Launched, these users are warm and grow fast. You will get honest feedback. You are young and get this success already, congrats!

The "personally messaged for honest feedback" step is underrated. Most people blast links and hope. You actually talked to people.

We did something similar launching Swiftbill (invoice generator for freelancers) — reached out directly to designers and devs we knew asking "does this solve anything for you?" Those early conversations shaped the whole product far more than any analytics.

The WhatsApp group angle is smart for student tools specifically. The trust transfer in existing communities is way higher than cold traffic. 258 in 2 days without ads is a strong signal the problem resonates. What's your main conversion drop-off right now — first session engagement or getting them to come back?

Hey man, thank you so much for building this.

Guys, trust me — this is going to become something big. There's no doubt about that. This 18-year-old is cooking up something truly special.

Let's all do our part to help him out.

And hey kid, I'll do my best to bring this to the attention of as many people as I can, and I believe others will too.

The reason is simple: you're solving a genuinely important problem. So many people spend hours learning yet struggle to actually master what they've studied. You've recognized that problem and built something meaningful to address it.

Most importantly, you had the courage to build it without worrying about whether you might fail.

Keep going. We're rooting for you, and we won't let you lose without a fight.

Your project and results are impressive; the fact that you've generated traffic through LinkedIn makes me want to promote my product through it as well.

258 users in 2 days with zero ads is a strong signal - especially because you can trace exactly where they came from. That traceability matters more than the number at this stage.
The insight about why people actually signed up is the most interesting part of your post. "Tired of feeling busy but not actually learning" is a much sharper problem statement than "tutorials don't work" - it's emotional, not just functional. If that's not already your headline, it probably should be.
One question worth sitting with: what does retention look like at day 7? The WhatsApp/LinkedIn launch gives you a warm audience who wanted to support you. The harder signal is whether strangers who found it cold come back and finish a challenge path. That's where the adaptive engine either proves itself or needs work.
Worth working on? The problem is real and the early traction is genuine. Keep going.

"Busy but not actually learning" is so real, I've lost whole weekends to tutorial playlists. 258 in 2 days at 18 is no joke, keep going.

Congrats on the launch, Arshad! The immediate traction is impressive for an 18-year-old bootstrapped team. The fact that people signed up because they were "tired of feeling busy but not learning anything" is your core value proposition. Double down on that copy. One thing to watch out for with an "adaptive coding challenge path" is the accuracy of the LLM/engine generation. If the real-time generated challenges become too hard or too easy too quickly, students will drop off out of frustration. How are you handling the accuracy of the automated compiler grading to ensure students don't get stuck on false negatives? This is definitely worth pursuing if you can nail the path progression.

I'll give a try... But all that purple colors hurt my eyes 😅

258 users in 2 days with zero ads — that’s real.

Ran your landing page while reading. You named the exact problem in your post: “Students watch 6 hours of tutorials, feel productive, and actually retain almost nothing.” That’s specific and painful.

It’s not in your H1.

“Learn to Code. PLAY TO WIN.” is what every coding platform promises — Codecademy, freeCodeCamp, LeetCode, all of them. The thing that makes Lumetrix different — the tutorial-fatigue problem you actually solve — is invisible above the fold.

One swap:

Before: “Learn to Code. PLAY TO WIN.”
After: “Stop watching 6-hour tutorials. Build what you actually want — in days.”

Does this match the gap you’re seeing — people get it when you explain it, but the page doesn’t land it first? https://outboundautonomy.com/fix-sprint?ref=fixsprint-lumetrixplay

Users from China finding it on their own is the best signal you could get - it means it's spreading past the people you DM'd. That's the line between a push and a pull. Keep doing the manual work that keeps them engaged, but start watching where the China users came from; if you can find that channel, that's your next 258 without the manual grind. Will check it out, good luck brother.

258 signups from WhatsApp groups is a strong signal that the problem resonates with people who already know you. The real test starts now: how many come back on day 3, day 7, day 14 without you personally messaging them?

A couple of things worth watching early. First, track where users drop off in the challenge sequence. If most people complete challenge 1-2 and then stop, the adaptive engine might be stepping up difficulty too fast, or the gap between "I watched a tutorial" and "I can write this from scratch" is wider than one challenge can bridge. Consider adding a "hint" step between watching and solving, something like partially completed code where they fill in the key logic.

Second, the WhatsApp distribution channel has a ceiling. College groups are great for the first 500, but they're closed networks. The next step is figuring out where students go when they're stuck on a tutorial (Stack Overflow, Discord servers for specific courses, Reddit learn-to-code subs). Showing up there with a genuine answer plus "I built something for this" is more sustainable than link-dropping.

On the "is this worth working on" question: the fact that 258 people signed up for a learning tool with no brand, no polish, and no ads is a better answer than anyone here can give you. The market is telling you something. Listen to the users who come back without being asked, not the ones who signed up once. Those repeat users are your real product.

the 'tired of feeling busy but not actually learning anything' line is the most important sentence in this post and it generalizes way beyond tutorial-learning. the shame gap 3vo named above shows up in productivity tools, fitness apps, journaling apps, every category where the actual job is 'help me close the gap between intention and result.' you're not selling code education, you're selling proof-of-progress. the brutal test is whether your D7 returners can articulate that on their own. if they say 'i learn faster now' you have a product. if they say 'i like the streaks' you have novelty.

Why are you offering such a good product for free though?

Feeling productive without actually learning is a painfully accurate problem statement. The strongest products seem to solve frustrations people already know they have.

Yes, it's worth working on, but not for the reason you think. The signal isn't 258 signups, signups are cheap. The signal is that you found a group who felt the pain so sharply they got it instantly with no pitch. That's the start of product-market fit, so protect it. Two things I'd watch from here. First, retention over signups: of those 258, how many came back on day 2 and actually finished a challenge? That number tells you whether you built a learning tool or just a better-feeling tutorial. Second, your manual WhatsApp and LinkedIn outreach won't scale, but it just handed you the exact words students use to describe this problem. Write those words down. They become your landing page, your cold message, your everything. You're 18 and already doing the part most founders avoid, talking to users one at a time. Keep doing that long after it feels like you should have automated it.

18, bootstrapped, MSME registered, 258 users in 2 days with zero ads
you're already answering your own question.

Yes, absolutely. 258 users in 2 days without ads is a strong signal. The biggest positive for me is that you're solving a problem users already feel every day. Keep going and keep talking to users.

258 users in 2 days is a real signal. The problem you identified is genuine.

The thing to watch now: those 258 came from WhatsApp groups and communities you seeded manually. That's warm traffic from people who know you or felt obligated to help. The real test is what happens in week 2 and 3 when you stop manually sharing.

Two metrics that will tell you if this is worth pursuing:

1. D7 retention. Do users come back 7 days later without you prompting them?
2. Cold user behavior. Find 3 people who don't know you and watch them use it without explaining anything.

If strangers return on their own and can't stop using it, that's your answer.

The tutorial-to-project gap is probably one of the biggest problems in programming education. I like that you're focusing on getting users to write code immediately instead of consuming more content. Definitely seems like a problem worth working on if users keep coming back after the initial curiosity.

Yes brother, this is worth working on.

The problem is very real. Many students finish tutorials but still cannot build anything from scratch. If Lumetrix Play can turn passive watching into real coding practice, that is a strong use case.

258 users in 2 days without ads is a good early signal. Now focus on retention: are students coming back, completing challenges, and improving?

Your best positioning is simple: “Stop watching tutorials. Start building.”

Keep going, but measure user retention and learning outcomes closely. That will tell you if this can become a serious product.

The WhatsApp college groups angle is the interesting part. You found a channel where your exact ICP already trusts each other -- that's harder to replicate at scale but it's also proof you understand who you're building for better than most.

The thing you buried in the post: people signed up because they were tired of feeling busy rather than for the gamification. That's more useful signal than any survey. Most ed-tech bets on engagement mechanics. You found a shame gap -- finishing tutorials, retaining nothing -- that people won't say out loud until someone names it first.

On "is it worth working on": 258 users via DMs and WhatsApp in 2 days isn't viral but it's genuine pull. If 10 of those 258 come back without you nudging them a week from now, that tells you more than the signup number does.

Proof that starting with your local community works. 258 users in just 2 days! Congrats on the amazing launch.

258 users in 2 days through manual WhatsApp outreach is honestly a stronger signal than most polished Product Hunt launches — those are real people who felt the problem, not curiosity clicks. The fact that they signed up because they were "tired of feeling busy but not learning" tells you the core value prop landed, which is the hard part.

Is it worth working on? I'd say the better question right now is: what does day 7 retention look like? Early signups from your personal network are warm — the real test is whether students come back after that first session without you nudging them. If they do, you have something. If they don't, that's your next thing to solve before scaling acquisition. Either way, keep going.

I'd be careful with one thing.

The interesting question may not be whether students like the product.

It may be what kind of success would actually deserve confidence that this is worth building long term.

Those sound similar, but they can lead to very different decisions from the same early traction.

I wouldn't make that call casually from the current signals.