Do you keep a public changelog for your product?
Hey IndieHackers! I just implemented a new public changelog for my B2C SaaS PodQueue, the missing "Listen Later" for audio on the web: https://podqueue.fm/changelog
I wanted a good place to keep people up to date with new product features and changes—to be able to capture the things that are too small for a blog post, but still worth noting in case someone wants to see what's new and what's changed. Right now, it's pretty minimalist, but has an RSS feed available as well. I could see an email option being viable too. I don't see this as supplanting other ways of building in public (e.g. on Twitter), but supplementing them.
I was inspired by the GitHub public changelog and Placemark's changelog blog posts, but I can see this being part of a greater trend in keeping users updated with product changes.
So what do you think? Do you keep a public changelog for your product? If not, why not?
I’ve always been a fan of changelogs, if for nothing else than helping me remember all the hard work I’ve put into the product haha.
Yes and no 😄 Some of my products had public changelogs because that was the best and easiest way to show that they were live and actively maintained. I used a simple javascript snippet to display a "what's new" section on product pages, nothing fancy. There are great free tools out there that you can use to create a "power" changelog for your product.