Choose embed vs deep link
Widgets and iframes keep users in-app. A branded portal link (updates.yourapp.com) is simpler and often enough. Many teams ship the link first, then embed.
Pick high-intent placements
Help menu, empty states for missing features, account settings, and onboarding checklists outperform a tiny footer link.
- Help / Resources menu item
- “Request a feature” next to upvote CTA
- Post-login updates tab
- Support macro → roadmap URL
Keep statuses short and true
Pending, Planned, In progress, Shipped. Optional Declined. Prefer quarters over fake ship dates. Stale embeds destroy trust faster than no roadmap.
Gate only what must stay private
Public roadmaps build community. Private or logged-in views fit enterprise betas. Do not hide everything — silence recreates the support burden.
Connect feedback → roadmap → ship
The in-app roadmap should reflect the same cards as your board. When something ships, the changelog notification completes the loop inside the product habit.
Ready to put this into practice?
Create a living roadmap