KYUUBI

... turns chaotic Reddit mod queues into clear, one-handed decisions. A state-first mobile moderation workbench for claiming, reviewing, and resolving queue items without dashboard clutter.

Comment

Inspiration

KYUUBI started with the Reddit Developer Platform hackathon and a simple outsider question:

Why does mobile moderation still feel like a desktop dashboard squeezed onto a phone?

I was not trying to build a bigger moderation suite. I wanted to test whether a different interaction model could make moderation feel clearer, faster, and less stressful on mobile.

The core inspiration was coordination pressure.

When several moderators work through a queue, the hard part is not only deciding whether something should be approved, removed, or escalated. The hard part is knowing what is happening right now:

Who owns this item? Is someone already handling it? Is this action still safe? Did the state change? What should I do next?

That felt less like a layout problem and more like a state problem.

KYUUBI was inspired by the idea that a modqueue should not behave like a table. It should behave like a live work surface: one case, one owner, one clear next action.

The goal was to build a mobile moderation tool that reduces uncertainty instead of adding more panels, filters, and dashboard clutter.

What it does

KYUUBI is a mobile-first moderation workbench for Reddit mod queues.

It helps moderators move through queue items with clear, one-handed decisions instead of dashboard clutter. A moderator can claim an item, see whether it is active, owned, conflicted, expired, or already handled, review the relevant context, and take action from a focused mobile flow.

KYUUBI treats moderation as a state problem, not a layout problem.

Instead of showing every possible control at once, it asks:

What does the moderator need to understand right now? What action is safe right now? Who owns this queue item? Did the state change? Can this be handled with one hand under pressure?

The result is a state-first moderation interface where queue items feel like active work objects, not rows in a compressed admin table.

How I built it

I built KYUUBI as a combined mobile and Reddit-native prototype.

The mobile interface is built with Flutter. Flutter provides the app surface, interaction layer, and visual system for the one-handed moderation flow.

The Reddit-native integration is built around Devvit and the Reddit Developer Platform. Devvit handles the Reddit-side behavior, shared moderation state, queue updates, claims, leases, and moderation actions.

The UX language is driven by FLUBBER, a custom motion and interaction grammar for KYUUBI. FLUBBER is not decoration. It is used to make state changes physically understandable: claiming an item, showing ownership, expressing lease pressure, resolving conflicts, and settling the queue after action.

The project separates three main layers:

  • Flutter for the mobile app experience
  • Devvit for Reddit platform integration
  • FLUBBER for state-driven motion, feedback, and interaction behavior

The visual direction uses matte full-color surfaces, strong readable contrast, rounded physical UI objects, and direct moderation copy. The goal was to create something recognizable without turning serious moderation into neon, noise, or a generic SaaS dashboard.

Challenges I ran into

The hardest challenge was avoiding the obvious shape of a moderation tool.

It would have been easy to build a dashboard with cards, tables, filters, metrics, panels, and tiny controls. But that would not solve the mobile moderation problem. On a phone, more information is not always more clarity.

KYUUBI had to stay focused on the next useful action.

Another challenge was state correctness. In moderation, feedback cannot lie. If an item is claimed, conflicted, expired, or already handled, the interface has to communicate that clearly. Motion and color only help when they reduce uncertainty.

I also had to balance personality with seriousness. KYUUBI uses a bold, playful visual identity, but the moderation core remains direct and readable. The interface should have character around the work, but clarity inside the work.

Accomplishments that I'm proud of

I'm proud that KYUUBI does not feel like another compressed desktop dashboard.

The project takes a familiar problem — mobile moderation — and approaches it from a different angle: state, pressure, ownership, and one-handed action.

I'm especially proud of:

  • turning queue items into active state objects
  • designing a one-handed moderation flow
  • making claim and conflict states visible instead of hidden
  • using motion as state feedback instead of decoration
  • keeping the visual identity bold without making moderation feel childish
  • building a working prototype direction in a short contest window

KYUUBI is also proof that moderation tools do not have to look generic to be useful. Serious work can still have a strong identity, as long as the interface respects the task.

What I learned

I learned that moderation UX is not mainly about fitting more controls onto a screen.

It is about reducing uncertainty.

A moderator does not just need buttons. They need to know what is happening, what changed, what is safe to do, and whether someone else is already working on the same item.

I also learned that motion becomes useful when it answers a real question:

What changed? Who owns this? Is this action saved? Is this state safe, active, blocked, or failed?

When motion answers those questions, it becomes part of the moderation system. When it does not, it becomes noise.

The biggest lesson was simple:

A mobile mod queue should not start with "What can we fit on the screen?"

It should start with "What does the moderator need to understand right now?"

What's next for KYUUBI

Next, KYUUBI needs to become more complete, more testable, and easier to hand off.

The immediate next steps are:

  • polish the public demo and project website
  • improve the README and documentation
  • record a short video walkthrough
  • tighten the claim, lease, and conflict flows
  • test the Devvit integration more deeply in a real Reddit environment
  • refine reduced-motion behavior
  • prepare the repository for open-source release after the contest window

Longer term, KYUUBI could become an extensible moderation framework with clear seams for additional queue types, moderation workflows, adapters, and community contributions.

The core direction will stay the same:

Less dashboard. More state clarity. One-handed moderation that helps moderators act with confidence.

Built With

Share this project:

Updates