Kanban as a Tasks Sub-View

I hesitated for a long time on whether to add Kanban to Fecit.

At first I wasn’t going to. Kanban apps are everywhere already, and that’s not what we do well. Fecit is a tool for looking deeply at each task, not for surveying the whole board from above.

But as I kept building, I started wanting it. What did I just start, what did I just finish. You can tell from the list too, but it doesn’t land at a glance. So I made it.

A Sub-View, Not a Separate Tab

The first thing I decided after committing to Kanban was: this is not a new feature.

Kanban doesn’t create new data. It’s just a screen that groups existing tasks by state and shows them differently. If I made it a separate tab, people would get confused — “wait, where’s that task?” When the same data lives in two places, it’s never clear which one is the truth.

So I tucked it inside the Tasks tab as a sub-view. List / Calendar / Kanban — the same tasks, three layouts. You switch between them with a small toggle above the tab bar.

What’s In, What’s Out

I could have shown every task on the Kanban board. But then the Done column would stretch on forever. Show everything I finished last year and Kanban becomes an archive screen.

So the Done column only shows tasks completed in the last 24 hours. Anything older belongs in the List view, where you can filter properly.

Similarly, the To Do and In Progress columns fetch 20 at a time. More if you scroll. It’s a view for “what I’m working on right now,” not for the whole backlog.

Column Labels

The columns were originally “To Do / In Progress / Done.” Familiar Kanban language.

But everywhere else in Fecit, those same states were called “Registered / Started / Completed.” Same thing, two names. So I unified the Kanban column labels to Registered / Started / Completed too.

To Do is friendlier in Kanban-speak, but consistency mattered more. A task’s state in the List view and its state in the Kanban view should read the same.

The Real Reason, Honestly

People kept asking. “Is there a Kanban view?”

I had clear reasons not to build it, but the question kept coming. Eventually I’d rather build it on my terms than keep saying no. Don’t blow it up into a separate feature — keep it light, as a sub-view.

That’s how it landed. Looking at it now, it fits well.