ikieEngineeringGet started
All posts

TasksUXApp policyiOS

Rebuilding the inbox: 10 of 16 ideas, in both apps

We compared six apps, let the owner pick from mockups, and shipped filters, multi-select, manual order, saved views and plan-my-day to web and iPhone in 10 PRs. The server decides filter values and the screen only compares them. Bulk actions got no new server path.

한국어

ikie's inbox is where tasks without a date gather. You could write them down, check them off and decide when to do them. As they piled up, it was clear the inbox had too few features. It needed filters at the very least, and more ideas besides, covering design and interaction as well as features.

Compare first, then pick

Before building anything, we looked at how other apps handle the same job.

AppWhat we looked at
ThingsFiltering with a tag bar, manual order, Someday and Logbook
TodoistA view menu for grouping and sorting, saved filters, completed tasks
TickTickThe urgent/important four-box view
AkiflowClearing tasks that come in from many apps, morning planning
SunsamaPicking today's tasks while watching the total time
LinearFilter chips that stack, saved views

Then we put three sets of choices side by side as mockups on one page.

  1. Filter shape: out of a chip bar, quick views plus a view button, and a search field with tokens, we picked the chip bar. What's applied is always visible, and one tap clears it.
  2. Task row: the due date sits at the right edge, short like "Due tomorrow" or "2 days overdue", and everything else goes on one line below.
  3. 16 ideas, of which we picked 10.

Picked: group and sort, total time, search inside the inbox, completed tasks, expanding steps in place, tidying stale tasks, drag to reorder, multi-select, saved views, plan my day.

Left out: full swipe for today, web keyboard shortcuts, today/tomorrow buttons on missed rows, #tag !flag 30m syntax in the capture field, the urgent/important four-box view, and an empty-inbox screen.

What we picked became the work list. Over the next six hours, 10 PRs merged. Web first, then iPhone on the same policy.

  1. 0.9 hFilter chips, group, sort, search, total, new row (web)
  2. 1.1 hCompleted and stale folds, expanding steps (web)
  3. 1.3 hAll of the above on iPhone
  4. 1.5 hMulti-select (web)
  5. 4.7 hMy order (web)
  6. 5.2 hMulti-select and my order (iPhone)
  7. 5.4 hSaved views (web)
  8. 5.7 hSaved views (iPhone)
  9. 5.9 hPlan my day (web)
  10. 6.1 hPlan my day (iPhone)

Filters: the server decides the keys

There are seven filter kinds: due, source, tag, calendar, status, time needed and flag. For every task row, the server sends keys shaped <kind>:<value>.

due:over  source:notion  tag:4f1c…  calendar:9a2e…  status:todo  size:quick  flag:yes

"Is it late?" and "Is it 15 minutes or less?" are decided in one place on the server. A due time is late once that moment passes; a due date is late once that day ends. Within a week is due:week, 15 minutes or less is size:quick, an hour or less is size:hour. The screen only checks whether keys are equal. If web and iPhone each computed "late" on their own, they would drift apart one day.

The rule that splits values lives in one place on the server. Screens only pick and count the keys they receive.

How keys are picked and counted is written once as app policy, and the web (TypeScript) and iOS (Swift) interpreters are tested against the same scenarios.

  • Several picks within one kind mean "or"; across kinds, "and".
  • Counts in a picker leave out that kind's own picks, so you can see how many rows one more pick in the same kind would add. Linear and shopping-site filters work this way.
  • A kind whose one value covers every row is hidden. If everything was written in ikie, or nothing has a tag, that chip would narrow nothing.
  • The header total adds the matching row count and only the time that was actually written down. Tasks without an estimate aren't filled in as 30 minutes. Only what's written is a fact.

Multi-select: no new server path

Pick several tasks and move them to today, tomorrow or a date, tag them, finish them or delete them at once. On the web, tap "Select" or hold ⌘ or Shift while clicking rows (Shift selects a range). On iPhone, it's the list's edit mode.

We didn't build a bulk API. Each selected row sends the same board write the app already uses, and only the toast and undo show once. Board writes already keep order per item and wait when offline. A separate bulk path would mean doing that job in two places.

The rules live in policy. Only rows you can edit and haven't finished can be selected. Rows that a filter or search hides drop out of the selection, because a bulk action must never reach rows you can't see. For tags: if every selected row has the tag, it's removed from all of them; otherwise it's added only to the rows missing it.

My order: leave room between rows

We added "My order" to the sort options. On the web you drag a handle or move a row with the keyboard (dnd-kit); on iPhone you long-press a row and drag. On drop, the app sends only the rows before and after, and the server decides the spot between them.

Each row has a number (position), spaced 1024 apart when first assigned. A moved row takes the midpoint of its neighbours, so the moved row is the only one that changes.

RowAt firstC moved between A and B
A10241024
C30721536
B20482048

Keep inserting into the same gap and it halves each time, so after about ten moves there's no room left. Only then is the whole inbox renumbered at 1024 apart. Moving a row between filtered rows leaves the order of hidden rows unchanged.

Saved views and the current view

The filters, grouping and sort you have now are remembered on this device. Views you save with a name live on the account, so they're the same on every device (up to 20 per person).

A saved view holds tag ids, not tag names, so renaming a tag doesn't break it. When it opens, keys that no longer exist (like a deleted tag) are dropped.

Plan my day

This is the morning routine of picking what to do today from the inbox, borrowed from Sunsama and Akiflow. Tap "Plan today" in the header and pick tasks, and a line at the top shows today's free time, the written-down time of what you picked, and how much is left or over.

  • The server reads free time. It's the time from now until 22:00 today, starting no earlier than 08:00, when my calendars are free. This path (POST /api/v1/inbox/plan) only reads; it changes nothing.
  • Tap "Into free time" and the server finds the earliest free slot for each task in the order you picked, starting on a 15-minute mark.
  • The app does the placing. Each row goes to its time through the usual board write; anything that doesn't fit just moves to today's date. It's the same path as multi-select.

Stale and completed tasks

Tasks without a date that haven't been touched for over two weeks fold into "N stale tasks" at the bottom of the inbox. They're folded, never deleted. Open the fold to move all of them to today or keep all of them. Keeping them sets their last change to now, so they show in the inbox for another two weeks. Nothing folds while you search, since a search means you want to see that row.

At the very bottom there's also "N done". Open it to see tasks finished in the last two weeks, and uncheck one to bring it back.

What we learned

  • Build mockups to be picked. Three mockups side by side decide faster than any description. What gets picked becomes the work list.
  • Decide the rule in one place. Because the server decides what "late" means, web and iPhone filters have nowhere to drift.
  • Look at existing paths before adding one. Multi-select and plan my day both ride the per-row board write. We didn't rebuild offline waiting or per-item ordering.
  • Count only what's written. Don't pad totals to look plausible. Show an empty value as empty.

The ikie teamikie is a calendar for your events and to-dos in one place. Here we write about the problems we run into while building it, and how we solve them.