I Didn’t Plan to Build Loopi
Notes by SDG ·
Loopi didn’t start as an idea. It started as irritation.
Small, repeated, almost invisible friction that kept showing up in my day:
- A doctor’s appointment scribbled on paper
- A receipt I needed to track
- A message I needed to remember later
None of these were big problems.
But they all had the same annoying follow-up:
“I’ll deal with this later.”
And later… rarely happened.
The Realization: I Wasn’t Using My Own Systems
I already had everything:
- Notes app
- Reminders
- Calendar
- Expense tracker
On paper, I was “organized.”
In reality, I was:
- forgetting things
- missing follow-ups
- delaying simple tasks
Not because I didn’t care.
Because the act of capturing things felt like work.
The Problem Wasn’t Discipline. It Was Friction
Most productivity advice assumes:
“You just need better habits.”
But I noticed something else.
When capture is:
- fast → I do it
- slow → I avoid it
That’s it.
No psychology. No motivation problem.
Just friction.
So I Tried to Remove One Step
I didn’t start by building an app.
I started by asking:
What if I didn’t have to decide where something goes?
Because that’s the hidden cost:
- “Is this a note?”
- “Should this be a reminder?”
- “Do I track this as an expense?”
That tiny decision is enough to slow you down.
So the idea became:
Capture first. Decide later (or don’t decide at all).
The First Version Was Just… Convenience
No grand architecture.
Just:
- paste something → extract action
- snap a photo → pull details
- type less → get more
It wasn’t trying to replace anything.
It was trying to remove one annoying step.
Then Something Interesting Happened
I started using it myself.
And I noticed:
I wasn’t thinking about “apps” anymore.
I was just:
- capturing things
- moving on
That was new.
The Builder Trap Almost Kicked In
Once it started working, the usual thoughts came in:
- “It should also do this…”
- “What if I add…”
- “Maybe this feature…”
That spiral is endless.
Especially when you’re building something for yourself.
Because you can always justify more.
Then Came the App Store Reality Check
I decided to publish it.
That’s when things got real.
You Think You’re Done. You’re Not.
The app worked.
But the system around it didn’t.
- In-app purchases setup
- Metadata
- Review guidelines
All things I hadn’t thought deeply about.
The Waiting Changes Your Behavior
You submit the app
And suddenly, you’re not building anymore.
You’re waiting.
That’s uncomfortable.
And that’s when the urge hits:
“Let me just improve this one thing…”
The Most Unexpected Lesson: Do Nothing
This felt unnatural.
But I learned quickly:
Every change during review is a risk.
So I had to do something I’m not used to: Sit still.
No new features.
No last-minute tweaks.
Just wait.
Building for Yourself Is Both a Superpower and a Risk
The upside:
- You know exactly what matters
- No guessing
- No user research loops
The downside:
- You can overfit to yourself
- You keep adding “just one more thing”
- You never feel done
What Actually Worked
Looking back, the parts that mattered were surprisingly simple:
1. Solve one annoying problem properly
Not ten problems halfway.
2. Reduce steps, not add features
Every extra tap is friction.
3. Use it yourself daily
You’ll immediately know what’s wrong.
4. Stop before you feel “complete”
Because “complete” never comes.
What I Didn’t Expect
I thought the hard part would be: building the product
It wasn’t. The hard parts were:
- knowing when to stop
- dealing with platform constraints
- resisting the urge to keep adding
Where This Leaves Me
Loopi exists because I was trying to make my own life easier.
Not because I had a big idea.
And maybe that’s the biggest takeaway:
The best things I’ve built didn’t start as products.
They started as things I was personally tired of doing.
If I Build the Next Thing…
I won’t start with:
- features
- market
- positioning
I’ll start with:
“What is something in my day that feels unnecessarily hard?”
Because that’s where this came from.
Not ambition.
Just… irritation.