You launch your product. There's a spike of attention. Comments roll in. And then the conversation moves on.
Maybe the launch didn't go to plan. Maybe users were confused. Maybe onboarding was broken. Maybe you spent the next week fixing everything that should have been right on day one.
That's normal. But where do you post that update?
The builder goes back to building — but now in silence. There's no natural place to share the feature you shipped the week after, the pivot when users gave feedback, the bug that took three days to find.
That's the real story of building a product: the idea, the build, the launch, and everything that happens after. whatshipped.io is where the whole journey lives.
A dev log for your projects
You create a project. Then you post "ships" — updates on what you built, what changed, and what you learned. Not filler. Not tiny changelog noise. Just meaningful progress — the work that actually moved the project forward. Each ship is a permanent page on your project's timeline. Over time, it becomes the complete story of how you built your project.
That's the core loop: build something → ship an update → build the public record.
Each ship is a public milestone. People can see your progress, comment, give feedback, and follow the project as it evolves.
What makes it different
Progress has a home and stays visible. Each ship becomes part of a timeline people can actually follow. Add context, screenshots, and demo links so others can see what changed and how the project is evolving.
You can learn from how other builders build. whatshipped? isn't just for posting your own progress. You can look at other projects, scroll through their ships, and see how they shaped the product over time — what they changed, what they shipped, and what they learned.
Progress and discussion are separate. Ships stay focused on the work itself. The community board is there for questions, feedback, and conversation around the project, so timelines stay clean without losing discussion.
Consistency matters more than noise. There's a 52-week activity grid that tracks your shipping consistency on a weekly cadence. You don't need to post every day. Real building doesn't happen daily. You spend days coding, testing, designing — and then you ship. One meaningful update per week keeps your streak alive.
Who is this for?
Indie hackers, developers, open source maintainers, solo founders — anyone who wants a public place to share progress, document what they’re building, get feedback, and build a following around the project as it evolves.
If you're building something and want people to see the journey, not just the launch, that's what whatshipped? is for.
It's early
I'm building whatshipped? solo and documenting the process on the platform itself. It's still early, and I'm looking for builders who want to help shape the first wave. If that sounds like you, I’d love for you to be part of it.
If you're building something right now — here's how to get in:
- Join the waitlist at whatshipped.io
- Get an invite — I’ll be working through the waitlist daily and inviting early builders in small batches
- Create your project — name it, describe it, add your stack
- Post your first ship — what did you work on this week? Write it up. It takes five minutes — you can even copy an update you’ve already written.
Once you're in, you've started the record. A year from now, you'll have a complete timeline of everything you shipped.
whatshipped.io is currently invite-only. If you want one place for the whole journey of what you're building, join the waitlist.
Top comments (0)