The honest answer
A specialised email triage interface is possible, but Superhuman parity is not a small vibe-code build. Provider sync, threading, drafts, search, offline state, keyboard interactions, notifications, security, and edge-case correctness are foundational.
The hard parts
What actually makes this difficult
- Bidirectional email sync
- Draft/thread correctness
- Offline conflict resolution
What you lose
The parts that make the paid product hard to replace
- Universal email client
- Offline-first parity
- Enterprise security guarantees
People still pay for Superhuman because interaction polish; reliable provider integration; speed-focused product support.
What your first version needs
Useful capabilities, not a clone checklist
SyncMirror provider mailbox state safely.
- OAuth
- Incremental sync
- Threads
- Labels
TriageProcess messages at speed.
- Keyboard commands
- Split inbox
- Archive/snooze
- Search
ComposeCreate reliable outbound mail.
- Drafts
- Replies
- Scheduling
- Signatures
Before you start
Superhuman build questions
Can I vibe code Superhuman?
Not at full parity. Start with a read-only workflow layer or one narrow triage job rather than becoming an email client.
Why is email sync hard?
Providers expose different models, threads mutate, users act in multiple clients, tokens expire, and every outbound or state-changing operation must be safe to retry.
What can ship without sending mail?
A read-only inbox prioritiser, follow-up detector, search assistant, or daily digest can create value while delegating actions to the existing provider.
Sources
Reviewed 2026-08-10. This is a scoped independent build, not a claim about the proprietary implementation behind Superhuman.
