For product teams
Every release, announced like you meant it.
The release shipped on time. The announcement is a wall of text in a changelog nobody opens. Put the same update in a card instead: labeled, branded, and sized for the feed, the mail and the store, without waiting on the design queue.
Monocards is a Mac app (macOS 15 and up). Mail yourself the link and install it there.
Six cards for the release cycle.
The screenshot, the roadmap, the vote, the numbers, the rollout and the checklist.
The screenshot that sells
Wrap the build in a device frame and it reads as a product, not a bug report.
The roadmap
Where the release stands, quarter by quarter, with the current phase marked.
The feature vote
Let users pick the next integration, and post the result as proof you listened.
The week-one report
Adoption, crash-free rate and rating. The release, measured.
The rollout table
Which feature ships where, checkmarks doing the talking.
The ship checklist
From QA sign-off to announcement, visible to the whole team.
Or render it from the changelog.
Every example on this page was generated through the built-in MCP server, locally, from one sentence:
"Turn this changelog into a release card, aurora template."
Read the agent docs →Product updates, answered.
How do we announce a product update without a designer?
Type the changelog into the Release Notes card: New, Improved and Fixed get their own labels, the template carries the look, and the same update exports in every size your channels need.
Can every channel get its own size?
Yes. One card exports square for the feed, wide for the changelog mail, story for vertical, or all sizes at once. The content stays identical, so the update reads the same everywhere.
How does the team keep one look?
Define the look once as a template: colors, font, background, logo. Everyone who makes cards starts from it, and with a team license each person has their own key on their own Mac.
Do product screenshots and user data stay private?
Yes. Cards render locally on the Mac that makes them. Screenshots of unreleased builds never touch a cloud service on their way to the announcement.
Can this run inside our release process?
The app bundles a command line and a local MCP server, so a release script or an agent can render the announcement card straight from the changelog. The examples on this page came out of exactly that flow.
From the blog: how to make App Store screenshots that convert .
Release Notes 
Device Mockup 
Timeline 
Poll 
Stats 
Table 
List The next release deserves a better announcement.
Monocards is a Mac app (macOS 15 and up). Mail yourself the link and install it there.