The case for a smaller app

Every productivity app eventually grows databases, boards, automations, and a template gallery. It is not a conspiracy; it is gravity. Features are the easiest thing to add, the easiest thing to demo, and the easiest thing to put on a pricing page.

The cost is quieter, and you pay it every day: the app becomes something you maintain. There is a right way to set it up, a backlog of tidying, and a small ongoing tax on knowing where things go. Eventually the tool for keeping track of your work is itself work.

What we left out, deliberately

• No workspaces or projects hierarchy. Tasks, notes, and your calendar. Folders exist for notes, and that is the whole filing system.
• No boards, no swimlanes, no custom fields. These are good tools for a team shipping a roadmap. They are overhead for one person getting through Thursday.
• No templates to choose before you can start. Open the app and it is already useful. There is no correct setup to discover.
• No streaks, no scores, no nudges. Handled will remind you of things you asked to be reminded of, and otherwise stay quiet.

What a small app has to get right instead

Subtraction is only a virtue if what remains is excellent. Three things carry the whole design:

• Capture has to be instant. If getting something in takes more than a couple of seconds, you will keep it in your head instead, and the app is worthless. A hotkey from any app, the share sheet, your voice.
• One screen has to answer the question. Not "where is everything", but "what does the rest of today actually look like" — meetings and tasks on one timeline, including the ones you have been avoiding.
• Nothing may disappear quietly. Overdue work keeps resurfacing. An app that silently drops what you missed is worse than a paper list, because it also costs you your trust in it.

What that looks like on a Tuesday

You are in a call and agree to send someone a file on Friday. You press a hotkey, type "send Lena the v2 mocks friday", and hit return — about two seconds, without leaving the call. On Friday morning it is on your Today screen alongside your meetings, in the order the day will actually happen.

That is the entire loop. There was no project to file it under, no priority to pick, no board to drag it across. In a bigger app every one of those steps exists, each individually reasonable, and together they are the reason the task stayed in your head instead.

The honest trade

If you are running a team, tracking a launch across twelve people, or building a wiki, Handled is the wrong tool and we would rather you knew that now. It is built for one person’s day.

What you get for that constraint is an app with no operating manual. You will not become a Handled power user, because there is no such thing — and that is the point.