A full-stack Romanian fishing platform: records, catches, and gear with unique embed IDs, MapLibre maps, E2E-encrypted messaging, integrated forum with custom BBCode, Supabase/Postgres with RLS and RPCs, and a production PWA.
Fish Trophy is a full-stack web platform for Romanian anglers: records, catches, map tooling, community forum, and admin surfaces.
Romanian anglers deserved a credible place to log progress and compare personal bests without turning every fishery into a public pin drop. Fish Trophy treats fishing as a sport worth respect: celebrate skill, protect sensitive water, and give people vocabulary to care about rivers and lakes over years, not only on opening day.
A catch or record is also a story. Stable references mean a moment can travel inside a conversation: drop a link in a thread and readers see the real card, not a screenshot of unknown origin. The point is portable honesty between anglers, not an exercise in database keys.
The map is built from vector tiles and structured data so the interface does not paint hundreds of independent DOM markers just to show hundreds of places. The bet is simple: first open should stay fast as the dataset grows, and panning should not stutter because the page is carrying the wrong abstraction.
Fishing is not only leaderboards. Discovery (species, shops, guides), daily use (messages, submissions), and occasional delight (a tiny in-browser game) all live in one product so people are not juggling five apps to stay close to the hobby they already love.
Discussion is not a bolt-on comment box beneath an article. The forum gets its own shell and navigation so categories, culture, and moderation can mature on their own timeline. That separation is deliberate: community product needs room to breathe without rewiring the whole home experience every time.
Where people debate fish and fisheries, trust is earned. Edits, reputation moves, and enforcement carry enough context that a future reader can understand what happened and why. Underneath that, reads are shaped for scale so a busy topic is not a waterfall of tiny database round trips. Concrete libraries, APIs, and admin tools are listed in Key features and Tech stack so this section can stay about values and architecture, not a second spec sheet.
