Aruha
182 posts

Aruha
@Higitsune123
Indie dev & biohacker Building Seedmancer which helps you recreate any test state in seconds. Sharing what I learn along the way
Katılım Haziran 2023
33 Takip Edilen32 Takipçiler

github.com/EdoStra/Market…
This guide is very helpful. I'll do it step by step.
#buildinpublic
English

@Higitsune123 Thank you so much for finding the bug. I'll fix it tomorrow - it works fine on my laptop, but I see the issue.
Can we connect to discuss it?
English

Day 88 - Premium UI is LIVE. 🚀
• 6 features (cloud sync, unlimited cards, Anki export, etc.)
• Activation via code - no registration required
• Just open, learn, and optionally upgrade
88 days straight. Still shipping. Move to real SaaS
#buildinpublic #premium #SaaS

English

Indie Hacking - Day 6
I'll start marketing.
First, I'll post to Reddit about my app.
The best time to post is
weekday mornings between 6 AM and 9 AM EST (especially Monday), and weekend mornings between 7 AM and 12 PM EST
I'm currently in New Zealand.
NZ Time: 11:00 PM – 4:00 AM (Previous night/Same day).
I need to reserve a post time.
English

Indie hacking — Day 2
I'm building Seedmancer (test data + DB reset tool).
Just added MCP → test data can now be generated locally.
It works great… but now my monetization plan is broken 😅
I was going to charge for server-side generation, but that doesn’t feel right anymore.
#buildinpublic
English

Most founders think they have a growth problem.
They don’t.
They have a signal problem.
You shipped
You polished
You posted every day
Still no users.
So you assume:
→ need more traffic
→ need better marketing
→ need more features
But here’s what’s actually happening:
No one saw something that made them stop and think
“this is exactly for me”
Early stage isn’t about reach
It’s about resonance
If 100 people see it and no one reacts
that’s not a distribution issue
that’s a signal failure
Fix that first
There’s usually one hidden break point
curious where it is for you

English

@HaykMn_iOS Thank you for the advice, Hayk! That strategy looks good!
My app is resetting the database to a known state. It is for developers who want to test repeatedly
English

@Higitsune123 I know this trap. 20 months building EasyHabits. The fix that worked for me: one metric that proves the app is actually working. Only build what moves that metric. Everything else goes in a backlog and waits. What does your app do?
English

Indie hacking — Day 1
Not released yet.
I keep falling into the same trap:
adding more features and making the product too complex.
How do you resist the urge to overbuild?
#indiehacker #buildinpublic #indiedevs
English

From today, I quit my other job and focus on my new indie hacking project!!!
Every day I'll update the progress!
#buildinpublic

English

The most valuable lesson I’ve learned as an indie hacker is:
“You don’t really understand something until you’ve experienced it yourself.”
I’d read tons of startup books saying “marketing is the most important thing.”
I knew it in my head — but I didn’t truly understand it until I failed.
Now I get it: real understanding only comes from experience.
#indiehacker #buildinpublic
English

The bucket is the product.
Pouring water is a marketing activity.
But no matter how splendid a bucket you make, it remains empty unless you pour water into it.
Conversely, no matter how much water you pour, it will leak out if the bucket is full of holes.
Marketing = Product are equally important.
But fundamentally, no matter how much water you pour into a desert, flowers won't bloom.
Ultimately, the importance is:
Market > Marketing = Product.
That's why I believe confirming “whether a market even exists” is the most crucial step.
English

My product idea is not working. I validated that it's hard to establish a business.
My app is an AI software spec documentation tool that solves the problem of "the software specs being outdated."
The initial idea was "AI Generating test cases for QA," but I realized there were problems with software specs through customer interviews. I pivot to the current one.
I interviewed a potential customer after building. He said it was not worth paying, mainly because AI provides the wrong answers. AI's accuracy is a key to paying for my app, but it is impossible to make AI better now.
Failed reasons:
• I could research the market more before pivoting.
There are huge competitors, and I must create considerable value to compete with them.
• Not enough to clarify the target user segment.
It is hard to replace the existing app with a new one due to the high migration cost for large companies. On the other hand, small teams will not be motivated to document, and there is no need for a documentation tool.
• AI's accuracy is insufficient to provide the value to replace the existing product.
It provides wrong answers; I experiment with various prompts, but it does not work.
• A better AI model's pricing is too high, and it is not possible to establish the business. Even if I choose the better one, it provides inaccurate results.
Here is what I learned:
• Should've researched the market A LOT before building or pivoting:
My app's competitors are Notion and Confluence. How hard is it to compete with them? Is it possible to create value? How to migrate from an existing app?
• It took so much time to build.
It took 5 months to build from the first idea. It should be within a month.
• There might be technical risks that prevent you from creating value. I should've experimented first.
• Customer interview is a great way to learn. It's a marketing. I was paying a gratuity; it was worth paying for.
#indiehacker #buildinpublic
English

@bohdanbasov @prisma @DrizzleORM I've been using Prisma and Postgres for over 3 years and have had no problems.
English

@DevKhan03 I recommend setting your goal as a password because it embeds to your brain😀
Me: "ExitBy35yearsOld"
English


