Simple like Reminders
Open the popover via shortcut and immediately capture a thought. Capture has to be enabled faster than thoughts disappear, offering simple distribution of thoughts later.
Structured like a real tool
Projects, topics, tasks and notes live together, with priorities, due dates, search and a focus session in the same place. One app instead of several, without a database to configure or a template to maintain.
Private like post-its on your desk
No account, no cloud, no analytics. Everything lives in a local database on your Mac and can be exported at any time, for free. There's nothing to sign up for and no server holding your notes.
Between simple and structured, without an account or a cloud
Simple tools stay flat, and structured ones usually come with an account, a cloud and maintenance. SEKI aims for the gap in between: enough, well thought out structure to actually handle real projects, while storing everything locally on your Mac. *The placements are my own positioning judgment.
Leaving Notion behind
Notion lagged, and I was building against my live data. To scale this whole project I needed to replace it: one storage interface, a local database, a verified import with a safety checkpoint. This also improved the general UX dramatically for onboarding.
No web access, sync later
I gave up Notion's sync and web access. When sync (iPhone x MacBook) comes, it will run through iCloud on each person's own Apple ID, still without requiring a SEKI account and without any data I could ever see.
Why this matters
Pay once, as a supporter
The free tier covers everything essential: capture, search and export never sit behind a paywall. Pro mainly adds delight, like color themes, focus sessions and Spotlight search integration, for one payment. It's meant as a nice supporter gesture.
The exit is never paywalled
Export and backup stay free forever, as a full backup or a single project. Anything you've created stays usable if Pro ever lapses, because users should never lose their work. Otherwise trust can’t be maintained.
“I wanted to build it natively in Swift and do it properly instead of building another web-based tool, which would only work in the browser and hardly port to the App Store.”