Hot take: “build for yourself” isn’t the problem.
The problem is when the “productivity” app makes you its employee.
I tried the popular trackers. They all demand too much attention.
Notifications, rituals, endless organizing… congrats, now your todo app owns you.
So I’m building Weft — a task + note tracker with an AI assistant that works for me (and my wife), not the other way around.
I’m keeping it brutally cheap + shipping fast. If it grows, cool. If not, at least I stop wasting my life in someone else’s system.
Try the alpha: https://t.co/SVTE2pX2ob
Reply with one thing that feels annoying/confusing. I’ll fix it.
I spent 6 months on my first app
I got 0$ and 0 users
Why?
Because my app was solving my problem, not others
Failure is beautiful
The impediment to action advances action.
What stands in the way becomes the way.
No matter what anyone says, but if there are AI hackathons, then everything is serious. Let’s see what’s interesting there.
Is there anyone else participating?
#metaAI#hackathon
@milesdeutscher If I study Claude code, I already know Claude. So I don’t need perplexity because Claude is better.
If I installed OpenClaw and screwed Claude to it, why do I need a useless manus.
If I know Claude, I’ve already uploaded business ideas and plans to him 10 times.
teach @claudeai
Nobody dreams of building a “speaker water ejector” app.
But everyone does panic when their phone sounds cooked 😄
That’s the reminder indie builders keep ignoring:
Boring problems print.
Not because they’re exciting.
Because they’re:
common
urgent
easy to understand in 3 seconds
attached to a “shut up and take my money” moment
Most people spend weeks hunting for a “big idea.”
Meanwhile the market rewards:
small pain + high frequency + instant relief.
If you’re stuck, stop asking “what’s a cool app?”
Ask: “what’s a tiny disaster people face weekly?”
Drop the most boring problem you’ve had this month.
If it made you say “oh sh*t”… it’s probably a business.
@thdxr You’re right to feel it. Tests passing ≠ maintainable. The move isn’t “rewrite for elegance,” it’s budgeted cleanup: refactor only the hot paths you touch repeatedly, and set a quality bar for new code so the mess stops compounding.
@agazdecki I’d love to see the caveat posted more: if you do this, be discreet. The moment it becomes public or sloppy, you risk staff/customer anxiety and buyer drop-off. Quiet competition is the cheat code.
@alexcooldev The easiest marketing for indie devs is just documenting: screenshots, tiny wins, mistakes, and what you learned. Boring, repeatable, effective.
Hot take: “failed” VC consumer apps didn’t fail because the tech sucked.
They failed because the math sucked.
2015–2022 VC era logic:
high burn
big teams
paid acquisition treadmill
“growth” that wasn’t retention
overhead that required a billion-dollar outcome
So yeah - a lot of those “we’re sunsetting” apps are now perfect $1–10M solo businesses.
AI + solo overhead flips the equation:
rebuild fast
ship cheap
run lean
survive on niche revenue
But here’s the part the rebuild hype skips:
UGC can’t save a leaky bucket.
Creators can spike installs.
They can’t fix:
weak first session
no “aha” moment
churn on day 2
unclear why to come back
The play isn’t “rebuild in a weekend.”
It’s: rebuild + fix retention + then unleash distribution.
If you had to pick one:
Would you rather inherit a dead app with distribution but weak retention,
or strong retention but zero distribution?
@openingai_com Thank you very much. I tried. 😊
In fact, I came across such a discussion this morning, and realized what a great idea for the post will come out. So I decided to share.
Probably worth closing this debate:
Users don’t pay for features.
They pay for a reality shift.
Everything else is builder cope.
B2B pays for:
ROI (make/save money, save time)
risk reduction (fewer mistakes, less downtime, compliance)
accountability (the process actually happens)
ownership (control, integrations, SLA)
B2C pays for:
identity (“this is for people like me”)
habit (I come back without thinking)
convenience (less friction, faster win)
peace of mind / status (I feel better, I look better)
Different psychology. Same rule:
If the benefit isn’t obvious in 5 seconds, you’re not selling value - you’re selling hope.
Hot take: free trials don’t fix bad products.
They just delay the “no.”
What are you building: B2B painkiller or B2C vitamin - and what’s the one “instant win” in the first 5 minutes?
@qasimbizs This is the right skeleton. The missing step is measure the loop: hook → activation → day-2 retention → paywall conversion. If retention isn’t there, 100 posts just buys you 100 churn waves.
Agree. AI raised the floor so high that ‘building’ is no longer scarce. Trust is. In 2026 the moat isn’t features, it’s proof: reputation, repeatable distribution, proprietary data, and a product that reduces doubt fast.
The big shift is filtering: people stop asking ‘can this be built?’ and start asking ‘who’s behind it, and will it work for me?’ That’s why brands, communities, and opinionated niche products win. The arbitrage is real - but it’s in trust + clarity, not in shipping another wrapper.
@thdxr Exactly. “Do it like Apple” is not a strategy, it’s survivorship bias. Apple’s model is a stack: brand, distribution, ecosystem lock-in, and insane ops. You can’t copy one layer and expect the outcome.
This is actually actionable. The missing step most people skip is distribution + access: can you reach the complainers repeatedly? G2/App Store/Reddit gives you pain, but you still need a repeatable channel to acquire them (SEO, communities, outbound, partnerships). Pain without a path to customers is just research cosplay.
Also worth adding: don’t validate the complaint, validate the workflow + willingness to switch. Ask: “What are you using now, what does it cost you (money/time/stress), and what would make you change?” That’s where real ideas survive.