Btw, before installing on your server, you can try to use demo at https://demo.will-be-done.app/

Hey! Yep, it’s planned. I already have openapi - so server already have capabilities. Also, CLI support is planned too, so agent also will be able to use CLI

Hey! Yep, thanks for the kind words. I’m fully responsible for the architecture and system design. I spent a lot of time thinking this through, and how to build good local-first apps was on my mind even before AI (I built a note-taking app called Harika before and worked at RemNote).

Oh yeah, it’s a long story!

My core idea is to build a task manager that will stay with me for the rest of my life. Because of that, my main requirement is for it to be fast even with a massive database. If I have 10k+ tasks saved over the years, it should still load and feel instant.

Another requirement is that it must be offline-first. I live in a country where the internet goes down pretty often, and I need my tasks to be available regardless of the server status.

Finally, I wanted a clean API so I could connect things like an MCP server or create tasks via Telegram.

I couldn’t find an existing app that met all these needs, here is a table where I compared all self-hosted apps that I found(in awesome self-hosted github):

Here is how my journey went:

1. First approach: I tried using Redux and MobX. Performance sucked. The main reason is that MobX/Redux don’t support B-tree indexing. Local-first apps rely heavily on “intervals”(cause you use fractional-indexing-jittered to order things and to support LWW per column), and that’s exactly where B-trees shine. Without them, it just got slower as the data grew.
2. Second approach: I tried a reactive UI based on persistent SQLite queries (using wa-sqlite). It worked well for small lists, but it felt sluggish once the dataset got large.
3. Third approach (Current): I decided to build my own DB solution, which you can see here: HyperDB. The trick is that you write the logic once, but on the frontend, it runs against an in-memory B-tree index (which is incredibly fast) and data still stored at persistent wa-sqlite layer, while on the backend, it runs against persistent SQLite (which keeps memory usage low).

This third approach finally solved all three requirements. It’s hard to find an open-source app that does this because this specific architecture is difficult to “cook” correctly. On top of the database speed, I also had to solve the sync problem, that should also somehow resolve conflicts while clients are offline, which I handled by building own sync layer with LWW CRDT per column.

I checked Planify - wow, it is a decent work. But as far as I see it misses web app, mobile mode (will be done can do it with PWA) and macOS/windows platforms.

Also, the killer feature of will be done - the planner mode. You can plan your tasks through week. It basically the main reason why I built it.

Also, I compared it will all others task managers that I found at self-hosted github (except Planify, it doesn’t relate to self-hosted)

Thanks!

Thanks! Not for now, but I am building it in a way that it will be pretty easy to add themes support

Thanks! I am already building this iteration for one year, and I enjoy it! Both development and daily usage

Oh, that’s interesting. Log in page as first page looks correct - once logged in you should always see your tasks on app launch.

But I think I should correct my manfest.json and hard-code open page to be /.

Yep, that’s actually what I am doing except moving task to next day. I am still not sure about automatic moving part, though I am doing this by hand. I will need to play with this auto-moving flow a bit and maybe will bring it as a setting option.

I also have some strong desire to make tui or just CLI, but don’t have resources for this right now.

Thanks for sharing your flow!

Thanks for the feedback!

DnD is already here. You can reorder tasks/move to other projects. And as for nesting, it’s pretty complex feature. It will be hard to implement and maintain (especially maintain), so not planning right now, unfortunately. But at least I plan to add subtask list.