The “one gesture” rule that stopped me from building feature museums
Hey Indie Hackers 👋
I used to build products the way a developer’s ego wants to build them:
- lots of settings
- multiple modes
- dashboards
- a roadmap that looks impressive
- “we’ll add integrations later”
It felt like progress.
But it didn’t create habit.
So at AzeniqTech we started using a constraint that keeps us honest:
Every product must be explainable as one gesture.
If I can’t describe the core action in one line, it’s not a product yet — it’s a wishlist.
Why this matters
Most early-stage products don’t fail because the idea is bad.
They fail because the user experience is fuzzy:
- too many ways to start
- too many decisions before value
- too much “setup”
- too much UI to learn
Users don’t want to learn your tool.
They want one problem to disappear.
Example: Rephrazo
One of the tools we’re building is Rephrazo.
It’s not “AI writing” or “content generation.”
It’s a rewriting helper built around one loop:
highlight → rephrase → insert
No tab-switching.
No prompt box.
No tone dropdowns by default.
Just a tiny rewrite that keeps you in flow.
The surprising part: removing options increased usage.
A strong default beat flexibility almost every time.
How we measure early traction now
Instead of obsessing over signups, we look at repeat behavior:
- time to first successful gesture
- rewrites/actions per session
- day 2 / day 7 return rate
- does the user press the same button again tomorrow?
If the core gesture isn’t repeated, nothing else matters.
Question for Indie Hackers
If you’ve built narrow tools or micro-products:
- What was the earliest signal that it was becoming a habit, not a novelty?
- Which metric mattered most for you early on: retention, frequency, sessions, or something else?
- When did you decide to add “control” (modes/settings) vs doubling down on one default?
Make the core loop boringly fast.
Would love to learn from anyone who’s gone from “tiny utility” → “sustainable business.”
