Inspiration

One day, I watched a fellow moderator log into their shift and type: "Did anyone handle that misinformation post from last night?" Someone replied hours later — "Yeah, I was looking into it, don't touch it." By then, it was already removed. The investigation was gone.

That kept happening. Notes buried in chat, context lost between shifts, mods unknowingly duplicating each other's work. I could clearly see there was a huge gap in communication and coordination between mods — everyone was working in silos, with no shared view of what was open, what was being handled, or what had already been dealt with.

I felt that if mods had one place to see everything, that gap would close. That's what pushed me to build Mod-Sync.


What It Does

Mod-Sync is a Kanban-style case board that lives natively inside the mod dashboard. When a moderator logs in for their shift, they can see exactly what's open, what's being handled, and what's already resolved — without asking anyone.

  • Kanban board — three columns: Open, In Progress, Resolved — drag cards between them as cases move forward
  • Case notes — append notes across sessions so the next mod knows exactly where things stand
  • Case templates — quickly create common case types like ban appeals, spam reports, and content reviews without filling in the same fields every time
  • Flags — mark cases as Urgent (red) or Sensitive (purple) for instant prioritization
  • Mod assignment & filtering — assign cases to specific mods and filter the board to see just your cases
  • Assignment notifications — mods get notified the moment a case is assigned to them so nothing slips through unnoticed
  • Time estimates — set expected effort via free-text or preset chips (30m, 1h, 2h, 4h, 1d, 3d)
  • Sprint week navigation — organize cases by week; move open ones forward for long-running investigations
  • Team activity log — see the last 50 actions taken by the team in a slide-up drawer
  • Zero setup — install once, pin it to the dashboard, and it's live — no accounts, no external tools

How I Built It

Layer Technology
Frontend React 19, Tailwind CSS 4, Vite
Backend Devvit serverless functions, Node 22
API layer Hono REST API
Storage Redis

Accomplishments That I'm Proud Of

I built this entirely within the course of this hackathon — from idea to a fully working product — picking up Devvit, Hono, and Redis along the way and shipping a complete Kanban workflow with drag-and-drop, sprint navigation, and a live activity log.


What I Learned

I learned a lot about how moderators actually work day to day — the recurring cases they deal with, the patterns in their workflow, and where their time gets wasted. Seeing the same case types come up repeatedly — ban appeals, spam reports, content reviews — made it obvious why case templates would matter. Mods were rebuilding the same thing from scratch every single time.

On the technical side, this was my first time working with Devvit and building an app that lives natively inside Reddit. Learning how the iFrame model works, setting up a serverless backend with Hono, and using Redis as shared persistent storage were all new to me — and putting it all together within a hackathon timeline pushed me to learn fast and ship something real.


What's Next for Mod-Sync

  • AI case summarization — when a case has a long note history, auto-generate a one-line TL;DR so an incoming mod can catch up instantly without reading everything
  • Smart assignment — AI suggests which mod to assign based on current workload and past case history
  • Weekly summaries — automated reports on cases opened, resolved, and average resolution time
  • Multi-board support — separate boards for separate workflows (spam, appeals, content policy)
  • Export — download a week's case log for retrospectives or transparency reports

The foundation is solid. Everything above makes it deeper and more useful for teams running large, active communities.


Built With

  • devvit
  • react
  • serverless
  • tailwind
Share this project:

Updates