ChatWit vs ChatFly: Why I Built Two Chat Apps

Two Products, Different Problems

On the surface, ChatWit and ChatFly look similar: both are free, no-registration chat platforms built on real-time WebSocket connections. So why build two? Because they solve different problems for different people, and trying to combine them into one product made both worse.

ChatWit is a room-first platform. You create a room, share the link, and people join. The public room directory lets strangers browse active conversations and drop in. It is built for communities and groups who need a quick, temporary space to talk.

ChatFly is an experience-first platform. It leads with chat roulette -- random one-on-one matching -- and adds built-in games to rooms. It is built for entertainment and meeting new people, not for organizing group discussions.

The Discovery Problem

The core design difference is how users find conversations. ChatWit has a public room directory that lists every active public room with its topic and participant count. New users can browse, see what is being discussed, and join based on interest. This is great for topic-based communities but useless if you just want to talk to someone random.

ChatFly does not have a room directory. Instead, it has a roulette queue that pairs you with a stranger instantly. The discovery mechanism is fundamentally different: ChatWit is "find a room about X," while ChatFly is "connect me with someone, anyone." Combining these into a single interface created confusion in early prototypes. Users looking for roulette did not care about room listings, and users looking for topic rooms did not want random matching. Splitting them was the right call.

Feature Divergence

Once separated, the products evolved in different directions. ChatWit leaned into room management: room creators can set topics, toggle public/private visibility, and moderate participants. The directory sorts rooms by activity so the most active conversations surface first. It is a lightweight forum replacement for people who do not need persistence.

ChatFly leaned into engagement: the roulette feature, built-in games that players can start within any room, and a more playful interface. Game state is managed server-side to prevent cheating, and moves broadcast through the same real-time pipeline as messages. ChatFly rooms are more like hangout spaces than discussion threads.

Shared Foundation, Separate Products

Both platforms share the same underlying technology: persistent WebSocket connections for real-time messaging, serverless compute that scales with active users, and ephemeral sessions with no registration required. The infrastructure is nearly identical. But the user experience, feature set, and target audience are distinct enough that they deserve to be separate products. Sometimes the best architecture decision is knowing when to split.