In part one, I talked about the very first thing a user does with LoopSignal: submit feedback anonymously, with as little friction as possible.

A quick update since that post: LoopSignal is now listed on GitHub Marketplace . That felt like a good milestone to mention before going deeper into how the product is built.

But a submission going into a void is not a product. It is a contact form.

The next piece was building the public board — the place where approved feedback becomes visible, where users vote, where statuses are tracked, and where a team can see what their users actually want.

This article is about how I built that, and the decisions that shaped it.

What the public board needed to do

Before I wrote any UI, I listed what the board actually had to accomplish.

It needed to:

show only approved posts, not raw submissions

let anonymous users vote without creating an account

let logged-in users have their votes persisted properly

support sorting by votes and by recency

support filtering by…