Skip to Content

What You Get

Everything You Need, in One Place

Capture
One box and one label. Type it while you are still thinking it; the plan it proposes is yours to edit, apply or throw away, and nothing is written until you do.
Boards
Columns you define, in colors from your own palette. Drag one card or twenty, pick a run with Shift or a box with the mouse, and take the lot to Done in one gesture.
Undo
A board keeps a log of what changed, with who changed it. Ctrl+Z reads it back, a column deleted with forty cards in it included.
Notes
Markdown with a live preview beside it. A hundred versions kept, any of them restorable, and a run of your own edits folded into one.
Calendar
Drag an event and it follows your hand, not the half hour. Bring a calendar in as .ics and take one out the same way.
Reminders
Overdue, due and upcoming are derived when you look, never kept in step by hand. Alerts on a card, an event or a reminder, as a push notification, a desktop notification or a sound.
Overview
What needs you today is the first screen, before a click: overdue, due and starting soon, in the order they matter.
Search
One box, three passes. A fuzzy filter answers on the keystroke, full text finds what is not on screen, and a model reads the shortlist when one is connected.
Keyboard
Everything by keyboard, the drag on the board included, with every move announced to a screen reader.

Where It Runs

  • In a browser, on a real monitor, beside the window you are switching back to.
  • Installed, as an app on the desktop and on a phone, on the same data and the same interface.
  • One-handed on a phone, to capture a thought before it is gone.

What It Is Held To

  • WCAG 2.1 AA, measured: the build fails if any text on any surface drops below 4.5:1.
  • Text scaled to 150% with the layout intact, because everything is sized in rem.
  • Reduced motion honored, and overridable in either direction from inside the app.
  • Light and dark held to the same numbers, so neither theme is the afterthought.

When Something Fails

  • Every failure carries a code and a reference, so the line you paste into a support email is the line that finds it.
  • Nothing native: tooltips, focus rings and validation are all the app’s own, identical on every engine.