Lotus. A to-do list built around constant reordering, not fixed buckets.

In 2026, I built Lotus to take on a problem every designer eventually tries their hand at — the to-do list — from a different angle. The aim was a super simplified interaction model: no settings screen, no action buttons, everything driven by a single text composer enriched with contextual commands. Charlie Deets' LinkedIn pitch about Things 3's rigid Today/Tomorrow/Anytime buckets pushed me to think outside the box, from a completely different perspective, toward a completely different interaction model. The result is an app where slash commands and an @ shortcut stand in for every menu, toggle, and settings screen a typical to-do app would ship with.