Why we built a keyboard, not an app

When we started building KOPY, the obvious product would have been an app. You open it, paste in a message, get a reply, copy it back. Simple, predictable, safe.

We chose to build a keyboard instead. Here's why.

Context switching kills the moment

Messaging is fast. Someone sends you something and there's a window — a few seconds to a few minutes — where a reply feels natural. Every extra step you have to take to respond shrinks that window.

Opening a separate app, pasting text, waiting, copying a result, and switching back takes at least 30 seconds. By that point, the conversation has moved on, your mental state has shifted, and the reply you generate feels stale.

A keyboard extension removes all of those steps. You're already in the app. You copy the message, switch to KOPY keyboard using the globe button, tap Generate, and the reply appears directly in the text field. No app-switching. No copy-paste. The whole workflow takes about five seconds.

It works everywhere by default

An app-based solution only works in apps that have integrations. A keyboard works in every text field on the phone — WhatsApp, iMessage, Tinder, Gmail, Slack, Telegram, LinkedIn, Instagram, Discord. Anything with a keyboard. We didn't have to build separate integrations for each one.

This also means KOPY is useful for platforms that would never allow third-party integrations, and for niche apps that no one would bother to build for.

The tradeoffs are worth it

Keyboard extensions have real constraints. They're limited to 70MB of RAM. They can't run background processes. They require users to enable Full Access in iOS settings to read the clipboard. The setup experience is more complex than downloading an app.

We think the tradeoffs are worth it because the core behavior — generating a reply and inserting it where you're typing — is fundamentally better as a keyboard than as an app.

The friction of setup happens once. The benefit happens every time you reply to a message.