Feedback and Changelog
How users can follow what changed and send feedback without confusing internal work with public updates.
Feedback and Changelog
ScryBrew has two public-facing update paths: feedback from users and changelog entries from the product team.
Feedback
The feedback board lets users read public requests, filter by bug-style reports and feature-style requests, submit new posts, and vote where allowed. Logged-out visitors should be prompted before actions that require identity.
Public feedback should protect private author identity. Hidden posts should not stay visible. Vote and comment behavior must respect the live Supabase and RLS contract, not just local UI assumptions.
Changelog And Update Log
The public changelog shows PM-authored major entries for ScryBrew and cross-product changes. The logged-in update popup can show a broader daily view. Raw internal notes should never publish automatically.
Last reviewed: 2026-06-15.
