Release notes template users actually read
Release notes that lead with what people can now do, credit the people who reported problems, and fit in an app store’s small text box.
Short answer: lead with what changed for the person reading, not what you built. Group into new, improved and fixed. Keep each line to one sentence, and mention fixes people reported, so they know telling you was worth it.
Template
{Version} · {date}
New
- You can now {do something}.
Improved
- {Thing} is faster when {situation}.
Fixed
- {Thing} no longer {problem}. Thanks to everyone who reported it.Good and bad lines
| Instead of | Write |
|---|---|
| “Refactored the date picker” | “Picking dates is easier on small phones” |
| “Bug fixes and performance improvements” | “The total now updates when you change dates” |
| “Added CSV export endpoint” | “You can download your bookings as a spreadsheet” |
App stores show only the first lines before “more”. Put the change people care about most first.