It's just for me

I've been saying "it's just for me" about rcordr for months. Every time I show someone, I lead with it. Before they've even seen the screen, I've already told them the design is basic, the onboarding is rough, and I built it mostly for myself anyway. I do it so fast it feels reflexive.

It isn't really true, though. Or it's only half true.

rcordr is live. The website is up, the app works, I've spent a meaningful number of evenings on it. I do use it myself, and I'd be fine if it stayed a personal tool. But I also want other people to use it. I want it to eventually make money. "Just for me" is a disclaimer, not a description.

What the disclaimer is actually doing

When you pre-empt every reaction, you can't really be judged. If I tell you it's rough before you see it, your silence isn't disappointment -- it's confirmation of what I already said. If you look confused, I've already explained why. The disclaimer is a way of controlling the verdict by delivering it myself first.

The problem is it does something to the thing you're showing. When I introduce rcordr as a basic personal project, that's what it becomes in the room. I'm not giving it a fair hearing. I'm sandbagging it before anyone else gets the chance.

I showed it to my wife and a couple of friends. Not for long, talking it down the whole time. I'm not sure any of them really saw it. I made sure of that.

The work I keep avoiding

There's a version of rcordr that would feel ready to share without the disclaimers. It has decent onboarding, a short tutorial, enough signposting that a first-time user doesn't have to figure out the logic on their own. That work has been on my list for about four weeks. I haven't touched it.

The easy read is that I'm avoiding effort. But I think it's more specific than that. Finishing the onboarding means I lose the excuse. Once it's genuinely ready for someone to use, the disclaimers stop working. If they don't get it then, that's a real result rather than a predictable one.

Avoidance is often just extended preparation to be disappointed.

The design thing

I'm happy with how rcordr looks. I'm less sure anyone else would be. My design instincts might not be calibrated well enough to know if it's actually good, or if I've just spent enough time with it that I can't see it clearly anymore.

What I do know is that I use that uncertainty as more insulation. If I've already decided the design isn't good enough, I'm protected from anyone else arriving at the same conclusion. That's a different problem from the design actually being bad. One is a craft problem with a solution. The other is fear wearing a craft problem as a costume -- and the costume is convincing enough that I don't always notice which one I'm dealing with.

The contradiction worth naming

"It's just for me" and "I want it to make money someday" are not compatible positions. I hold both of them. The first one lets me off the hook. The second one means I have to let people actually use it.

Most builders I'm aware of sit somewhere in this gap. The project is genuinely personal -- built out of a real need, used by the person who made it -- but the ambition attached to it is slightly larger than that. The disclaimer manages the distance between those two things. It keeps expectations low enough that the ambition stays safe.

The trouble is it also keeps the project small. Not in scope, but in what it's allowed to become.

Letting a real result land

At some point the disclaimer has to go. Not because confidence is the right posture, or because you should stop caring what people think. But because you can't find out if something is useful to anyone if you spend every introduction undermining it.

The practical version is finishing the onboarding, writing the FAQ, making it feel like something worth someone's time. That removes one layer of legitimate excuse.

The harder version is showing it to someone and then staying quiet. Not explaining, not softening, not pre-empting. Just watching what they actually do with it -- and letting that be information rather than a verdict you've already written for yourself.