rothertech.
Side quest · In development

Build it with us.

Korabo is one community for every RotherTech app. The people who use the apps suggest features, report problems and talk them through, in public, with the person who builds them. Claude helps me read all of it and turn what matters into work.

Korabo logo: two overlapping squares, ink and red, with the overlap cut out

The idea

The name is コラボ, Japanese for “collab”. Each RotherTech app and site links to its own section of one shared portal, where people can propose and upvote features, report problems, and say what they like and don’t.

Anyone can read. Posting, replying and voting need a RotherTech account: one sign-in with Google or Apple that works across every RotherTech site, under a handle you pick. Your real name and email are never shown.

The private feedback form stays. Korabo is the public side: the place to talk an idea through and watch what happens to it.

What makes it different

You can see where it stands. Every thread carries a status set by the team: open, under review, planned, in progress, fixed, not planned or duplicate. Including the honest ones.
The builder answers. Staff replies are marked, and when Claude helped draft one, it says so. A person reads and sends every one.
Moderated from the first post. A small Claude model screens every post, a new account’s first few posts wait for review, and every post has a Report button.
Careful with who you are. One account, your handle not your name, nothing sold, no ads on Korabo, and you can delete your account yourself.

How it works

No tickets and no forms that disappear. Every post is public, and you can watch it move.

01 Say it Tap Community in a RotherTech app, or come straight to its section. Post an idea, a problem or just a hello.
02 Others weigh in People who use the same app reply and upvote ideas, so the ones that matter most rise to the top.
03 The team answers The person who builds the app reads it, replies in the open and marks where it stands.
04 See it ship When it’s done, the thread says Fixed and you get an email. You were part of it.

Read with Claude

Korabo has its own MCP server, so Claude can read and work with it the way it does with Kantan. The loop is a conversation, never an automatic pipe:

  1. I ask, “What are people saying about Nerd Toolkit this week?”
  2. Claude reads the week’s threads and reports the themes, the bugs that keep coming up and the most-upvoted ideas.
  3. We agree what’s worth doing.
  4. With my OK, Claude creates the work in Kantan, updates the thread’s status, and drafts a reply for me to send.
  5. Later, “Which of these are done?” closes the loop: finished threads get marked Fixed, and the people who asked hear about it.

What it runs on

Portal A web app, one section per product, linked from each app and site.
Built in TypeScript end to end on AWS: serverless, with DynamoDB.
Sign-in One RotherTech account, Google or Apple, shared with the other RotherTech web apps.
Claude An MCP server for reading, replying, setting statuses and working the moderation queue.
Embedding An API so apps like Bracket can run discussion in their own screens on the same store.
Email A note when someone replies to you, with one-click unsubscribe.

The design

These are design comps, not screenshots: the people, threads and numbers in them are made up. Real screenshots will replace them once it’s running.

Design comp of the Korabo home page: the headline Build it with us, and a sample idea thread marked Planned with a reply from the RotherTech team
The home page. What Korabo is, with a sample thread showing a status badge and a team reply.
Design comp of a product community on desktop: the product header, Ideas, Problems, General and Announcements tabs, and threads with status badges, plus a panel explaining each badge
A product’s community. Ideas, problems and general chat, each thread with its status, and a key to what the badges mean.
Design comp of the signed-in For you page: replies to your posts, status changes and threads you follow
For you. Replies to your posts, status changes on your threads, and everything you follow.
Design comp of a product community on a phone, with a Start a topic button
On a phone. Most visits will start from a Community link in an app, so phones come first.
Design comp of a thread on a phone: an idea marked Planned, upvotes, and a staff reply labelled Drafted with Claude
A thread. A staff reply marked “Drafted with Claude”, because a person always reviews and sends it.

Where it is

The design is done, and the shared RotherTech sign-in, the portal and the Claude tools are being built. None of it is live yet.

Planned The first community Nerd Toolkit gets the first section.
Planned More apps More communities open as apps join.
Planned Bracket’s debates Bracket’s matchup debates move onto Korabo after Bracket launches.
Planned Search Searching across threads comes after the first version.

Rather tell me privately?

Korabo is still in development. Until it opens, the feedback form comes straight to me.

Send a message