DEV Community

Cover image for I Built a Productivity App That Tries to Stay Out of Your Way
I Am Your Sticky Note
I Am Your Sticky Note

Posted on

I Built a Productivity App That Tries to Stay Out of Your Way

Most productivity apps start with a reasonable idea:

Help people organize things.

But somewhere along the way, organizing can become another task.

A thought appears while you're working.

Instead of capturing it immediately, you're choosing a project, folder, priority, tag, due date, or deciding where it belongs.

Sometimes I don't want to organize a thought.

I just don't want to lose it.

That became the starting point

I built IAmYourStickyNote around a very small workflow:

Think → Drop → Forget → Remember.

A thought appears.

Drop it onto a spatial canvas.

Continue what you were doing.

If it matters at a particular time, add a reminder.

Otherwise, just leave it there.

Why a spatial canvas?

I didn't want everything to become another list.

Physical sticky notes work partly because placement itself carries meaning.

Something can sit in a corner, beside another thought, or somewhere prominent without needing a folder structure first.

I wanted to preserve some of that feeling digitally.

The goal was simple: make capturing a thought feel closer to putting a sticky note somewhere than filling out another form.

Then came reminders

Capturing something solves only half the problem.

Sometimes the important part isn't storing the thought.

It's having it return at the right moment.

So reminders became part of the same workflow rather than a separate productivity system.

Drop the thought now.

Let it come back when it matters.

And then Surprise Notes

I also started exploring the same idea in a different direction.

What if the note wasn't for you?

A Surprise Note lets you write something for another person and have them receive it later.

A birthday message.

Something encouraging.

Something you want someone to discover at exactly the right moment.

The underlying idea is still the same:

Something written now can matter at a different moment.

What I'm trying not to build

I'm deliberately not trying to turn every thought into a project-management object.

The goal isn't:

  • more fields
  • more configuration
  • more dashboards
  • more things to maintain

The goal is reducing the distance between:

“I just thought of something.”

and

“Okay, I won't lose it.”

Not every thought needs a system.

Sometimes it just needs somewhere to go.

Building it independently

I built IAmYourStickyNote independently, from the initial idea to the product that's live today.

And now comes the part I can't really build alone:

seeing how real people actually use it.

There's a free plan, and no credit card is required to start.

If you're curious, you can try it here:

Try IAmYourStickyNote

One question

I'm especially interested in this:

When a thought suddenly appears while you're working, where do you put it?

A notes app?

A message to yourself?

A physical sticky note?

Your head — and hope you remember it later?

I'd genuinely like to know.


IAmYourStickyNote

Think → Drop → Forget → Remember.

Top comments (8)

Collapse
 
koda2026 profile image
Harun - solo dev •

Hey — I went through iamyourstickynote.com after you followed, and
honestly? your product is the missing half of my operating system.

Your "put it down, let it come back later" is the exact prequel to
my ship log. My OS says "name the blocker, it's a 15-min unlock" —
but that only works if the raw thought got captured first instead of
rattling around my head. Your Zero-UI Canvas does the capture. My
attention budget + ship log does the shipping.

We're two indie makers who both reject bloated software, both build
calm tools, both landed on Dev.to the same week. Your users capture
the thought. My OS ships it. That's a complete thought-to-shipped
pipeline between us.

No pitch — just genuine respect, and an open door if you ever want
to cross-share audiences or think out loud about the calm-tools
space together. Following what you build next.

— Harun, 12
Founder & CEO, HYNAWEB · hynaweb.vercel.app

Collapse
 
iamyourstickynote profile image
I Am Your Sticky Note •

Harun — this is one of the most thoughtful messages I've received since I started building this. Thank you for actually taking the time to explore the site.

"The missing half" is a better description than I've been able to write myself. I've been thinking of IAmYourStickyNote as the space before the task becomes a task — capture first, decide later. Your ship log and attention budget pick up the next part: what happens after the thought is out of your head. Capture → unblock → ship.

How does a raw thought usually become something actionable in your system?

Collapse
 
koda2026 profile image
Harun - solo dev •

Glad "the missing half" resonated. Your framing — "capture first, decide later" — is exactly right. That's the space I struggle with most.

In my system, a raw thought usually becomes actionable through three gates:

  1. Capture → Voice Memo. I'm on a ₹150 phone, so I don't have a fancy keyboard setup. Most ideas start as a 30-second voice memo while I'm walking or eating.
  2. Voice Memo → Ship Log Entry. I transcribe the memo (sometimes with KODA's help) and dump it into my Ship Log as a BLOCKER or TODO. This is where it becomes a "thing" instead of a "thought."
  3. Ship Log → Action. If it's a BLOCKER, I tackle it in the next 24 hours. If it's a TODO, it goes into the backlog for the next sprint.

The friction point is gate 2. I often capture the thought but never transcribe it, so it dies in voice memo purgatory. That's why your "capture → unblock → ship" pipeline is so clean — you've solved the transcription friction I haven't.

What's your capture-to-action latency? How fast does a raw thought become a task in your system? 🐯

Thread Thread
 
iamyourstickynote profile image
I Am Your Sticky Note •

Honest answer: most thoughts in my system never become tasks. That's not a bug — it's the design.

I don't have a pipeline because I stopped believing most thoughts need one. A thought goes on the canvas and stays there. If it matters, I attach a reminder and it comes back to me. If it doesn't, it just sits and eventually stops mattering on its own. Turns out that's most of them.

The reason gate 2 is your friction point is that gate 2 assumes every captured thought deserves to survive into a task. Most don't. The transcription step dies because your brain already knows the memo wasn't important — you're just being asked to prove it.

What if you didn't have to? Keep the memo. Don't transcribe it. If it actually mattered, you'd have already pulled it out by now.

Thread Thread
 
koda2026 profile image
Harun - solo dev •

This is a massive paradigm shift for me. Thank you.

I’ve been treating "not transcribing" as a personal failure of discipline, when it’s actually my brain’s natural filter doing its job.

"If it actually mattered, you'd have already pulled it out by now."

That is brilliant. I’m dropping the forced transcription step. The memo stays in voice purgatory until it proves its weight and naturally pulls me back to it. Gate 2 isn't a failure; it's the filter.

You just saved me hours of future friction. This is exactly why I love this community. 🐯

Thread Thread
 
iamyourstickynote profile image
I Am Your Sticky Note •

This is the nicest thing anyone's said about something I wrote, and it's not even the product — it's just the idea behind it. That means a lot.

The "personal failure of discipline" framing is exactly what I was stuck on for years too. I kept thinking I needed a better system, a stricter habit, a cleaner inbox. But the real answer was that the system was asking me to do work that didn't need doing. The transcription, the tagging, the sorting — most of it was admin the thought didn't actually need.

What you're describing — letting the memo prove its weight — is the same test I use. If I don't come back to it, it didn't need me. The ones that matter pull me back within a day or two.

Curious what your ship log looks like after this. Does the filter change what ends up in it?

Thread Thread
 
koda2026 profile image
Harun - solo dev •

It changes everything, honestly.

Before this shift, my Ship Log was full of "TODOs" that were really just anxiety disguised as tasks. Now? The log is sparse but dense with intent.

If a thought doesn’t pull me back within 48 hours, it never enters the Ship Log. It stays in voice purgatory. This means when I do write something down, it has already survived the natural selection process of my own attention.

The result: Fewer entries, higher completion rate. The log isn't a backlog anymore; it's a graveyard of things that didn't matter, filtered out by time.

Thanks for asking. It clarified the mechanism for me too. 🧠

Thread Thread
 
iamyourstickynote profile image
I Am Your Sticky Note •

"The log isn't a backlog anymore; it's a graveyard of things that didn't matter" — that's the whole idea and you said it better than I did.

48 hours sounds right. Mine is closer to a day. The ones that survive that first window almost always turn out to be the real ones.

Glad it helped. Genuinely didn't expect a random reply to reshape someone's system.