Skip to content

πŸ“§βœ¨ Beautiful email. For everyone.

2.9 KB
Raw Blame

inlark

The name inlark is always written with a lowercase β€œi”.

Overall goal

Build an exceptional email client that makes everyday email feel fast, clear, and effortless. inlark should become a dependable personal daily driver, with the visual quality and thoughtful interactions of the best modern productivity apps.

People on Linux, Windows, and macOS deserve a beautiful email client with excellent usability and reliable account connections. This project exists because existing options too often combine dated interfaces, awkward workflows, connection problems, or high costs.

Design direction

  • Linear is the primary reference for visual design and interaction quality. Aim for its restraint, consistency, clear hierarchy, and attention to detail. Every screen should feel intentional and polished.
  • Superhuman is the primary reference for email workflows. Draw inspiration from its speed, focused reading experience, efficient navigation, and keyboard-friendly interactions.
  • Notion Mail is an additional source of inspiration for thoughtful email organization and approachable design.

Use these references to inform a coherent product with its own identity. Favor calm surfaces, readable typography, subtle emphasis, and purposeful spacing. Start with an excellent dark appearance and give light mode the same care.

Good design includes behavior: predictable navigation, useful feedback, accessible controls, and remembering where the user left off. Essential actions must work comfortably with either a keyboard or a mouse.

Product priorities

  • Make reading, searching, organizing, and writing email excellent before expanding the feature set.
  • Support several accounts comfortably, with a unified inbox and clear account identity throughout.
  • Stay responsive with large inboxes and years of archived mail.
  • Make connections dependable and explain interruptions clearly.
  • Protect the user's work. Drafts should survive failures, sending status should be unambiguous, and recoverable mistakes should be easy to undo.
  • Respect message readability, privacy, and the user's control over their accounts. Require no hosted service and include no telemetry.

Scope

Build the desktop experience first, with Linux, Windows, and macOS equally supported. A future mobile app should feel like part of the same product, but mobile is outside the initial release.

The first version should be a complete, straightforward email client: conversations, folders, search, attachments, drafts, replies, forwarding, and everyday organization. Most initial accounts are self-hosted.

Favor depth and polish over novelty. AI features, automatic categorization, advanced automation, snooze, scheduled sending, calendars, and a full address book are deferred.

When making product decisions, ask whether the change makes everyday email clearer, faster, more reliable, or more enjoyable. Keep the experience focused and give small details the care needed for a daily-use application.