3. Didn’t step away soon enough
I stayed stuck for too long.
A short break helped me think clearly, re-evaluate the problem, and fix the deployment.
13.02.2026 08:01
👍 0
🔁 0
💬 0
📌 0
3. Didn’t step away soon enough
I stayed stuck for too long.
A short break helped me think clearly, re-evaluate the problem, and fix the deployment.
2. Didn’t check the Coolify Discord
It’s a great community and chances are someone has already hit your issue.
In my case, the Rybbit docs on Coolify’s site were outdated. I found the solution in minutes by searching Discord.
1. Skimmed the docs instead of actually reading them
Simple mistake.
Take the time to read the docs and watch tutorials before jumping in. It would have saved me hours.
The other day I spent all day setting up Coolify and self hosting Rybbit.
These were my 3 biggest mistakes 🧵
If you want to take a look, you can check it out here:
https://apps.apple.com/us/app/daily-journal-private-diary/id6746052206
Recent win 🏆
My screenshot experiment with My Daily Journal is finally paying off.
Seeing organic growth again now that ASO has settled down.
Spent all day Sunday setting up Coolify and self hosting Rybbit.
Was it easy?
It should have been.
Did I learn a lot?
YES
Are the mistakes I made too embarrassing to share…
also yes 😂
Keep it up! 👌
Lesson learned this past week:
When something doesn’t feel exciting, quit early.
I don’t need to solve every problem. Better to focus on the ones that actually excite me.
Anyone else learn this the hard way?
#buildinpublic
Starting the new week with new targets 🎯
• My Daily Journal: Understand how other apps are promoting their content across platforms in this space
• AppCredo: Soft launch to test interest
• Branli: Puting on ice 🧊 Building the AI chat app integration for fun instead
For those who haven’t checked it out yet, definitely take a look! Much better experience than Caprover when I tried that a few years back 😅
Spending the day setting up a VPS with Coolify, excited to self host rybbit and some personal projects
https://www.branli.io
I’ll be opening Branli to a small beta soon.
If you care about building or thinking without noise, this might be for you.
I’ll leave the link below.
While building Branli, I realised something uncomfortable:
A lot of productivity is performance based.
I’m trying to build something that doesn’t ask for that.
What surprised me most so far building my brand:
In the tools I tried, there was plenty of functionality, but no real guidance.
When you’re starting out, that becomes overwhelming fast
I’m deliberately keeping Branli small which means saying no to ideas I’d normally chase.
It’s slower, but it allows for growth in a clear direction 🧭
Small win today:
I used Branli without thinking about it.
No distractions and extra tooling. It allowed me to focus & write.
I built a feature I was sure would matter, but after using it for 3 days I binned it 🗑️
Shipping less is harder than shipping more.
I’m limiting myself to building only what actually gets used daily.
If a feature doesn’t survive that test, it doesn’t ship.
How the week actually played out:
• Branli soft-launch content ✅
• Life admin ✅
• ASO Review ✅ (very excited about the progress here)
Not every week looks like this, but I'm taking the W
How I decide when a product goes on autopilot:
• It runs stably without constant attention
• Core metrics are predictable
• New features don’t meaningfully change outcomes
• Support and ops are low-effort
• My time creates more leverage elsewhere
Autopilot isn’t quitting. It’s intentional focus 🎯
Verdict: a success ✅
Sometimes the best decision is to stop pushing and let a product run.
• Drinking culture changed. Early on the app had steady visibility and consistent downloads without effort
• That demand isn’t even close to what it used to be
• Plenty of feature ideas, but poor ROI on building them
• It now runs on autopilot. Right price point, ~30% conversion
Not every successful product is meant to be grown forever
Case: Sociables 🧵
#buildinpublic #reactnative #iosdevelopment
I’m 33, building micro-apps and mid-pivot.
Sharing the real wins, mistakes, and trade-offs here while building in public.
This experiment had feature/solution based screenshots.
Next up: emotional hooks.
Curious what’s worked for others?
Why this worked:
• Most users only fully process the first 1–2 screenshots
• Too many options increase cognitive load and reduce clarity
• A tighter set forces a clearer value prop
Fewer screenshots made the decision easier.
ASO lesson: more screenshots ≠ better
Too many were diluting the message.
Refining the focus and testing just 3-4 screenshots performed better.
Why?🧵
Back from a great break. Life’s picked up, so building looks a little different this week.
Weekly focus:
• Branli soft-launch content
• Life admin (unexpected curveball)
• ASO review. New screenshots are live & early data looks promising 📈
Scope changed, still moving things forward where I can