I Was Shipping Things Nobody Knew About

We ship most weeks.

Every Monday, a job reads the changelog and writes that week's release into our community site. Features, fixes, the whole list. It's been running for months.

And almost nobody read it.

Not because people don't care. Because reading it meant leaving the app, going to another site, and looking for a page you had no particular reason to think had changed.

That's not a discovery problem. That's asking someone to go check whether you did anything this week.

---

I noticed it in my own behaviour first.

I'd be working in PodGlue, and something would look slightly different. A button in a new place. A field that suddenly filled itself in. And I'd think, huh, when did that happen?

I built the thing. If I'm losing track, everyone else lost track a long time ago.

The work was getting done. The knowing wasn't.

---

So we moved the notes to where the work happens.

There's now a What's New item in the sidebar, down next to Help. When we ship a release you haven't seen, it gets a small dot. Open it, and you get that release, what's new, what got fixed, in plain language. There's a link to the full history if you want to go back further.

Read it once and the dot goes away. It comes back when there's genuinely something new.

That's the whole thing.

---

I want to be honest about what we deliberately didn't do.

We didn't make it pop open on its own. That was the obvious version, and it's the version I've resented in every other tool that does it. You sit down to record, and something jumps in front of you to tell you about a feature you didn't ask about.

A dot is enough. A dot says there's something here when you want it. A dialog that opens itself says stop what you're doing.

You're mid-episode. You don't need us in the way.

---

The other thing I'll admit: this took nothing to build, and that's sort of the point.

The release notes already existed. The weekly job already ran. The data was already sitting there, already public, already correct.

What was missing was three feet of distance between where the information lived and where the people were.

Most of the time it isn't the work that's missing. It's the last few feet.

---

A podcast is the same shape, if you've been doing it a while.

You publish the episode. You did the research, ran the conversation, cut it properly. And then it goes out into a place your guest has no particular reason to check.

The work happened. The knowing didn't.

That gap is most of why good episodes go quiet, not quality, just distance between the thing you made and the person it was for.

We built PodGlue to close that gap for podcasters. It was a bit funny to find the same gap sitting in our own product, pointed at our own users.

Now when we ship something for you, you'll actually find out.