What does this mean in your readme? How has technology for such a simple seeming project been behind and caught up?
This is my third attempt; the first two failed because the technology for fast, offline-first apps wasn't ready.
What does this mean in your readme? How has technology for such a simple seeming project been behind and caught up?
This is my third attempt; the first two failed because the technology for fast, offline-first apps wasn't ready.
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:
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.
What does this solve that a standard CalDav server doesn’t? Plenty of FOSS apps for web, Linux, iPhone that can all sync to the many caldav servers like Baikal? Caldav servers can handle unlimited numbers of tasks.
Also I read through your page it seems you don’t have CalDav implemented currently. How do you sync between local applications then? Would you sync with other CalDav servers? Or is the project just the webui currently?
Maybe I’m missing something but I don’t see how your couldn’t development meets any of these requirements except the nice ui
Nice to see CalDAV is on the roadmap. I will wait for that before trying it out, as it is the cornerstone for my system today (radicale and tasks.org)
Yep, it's on plan. Glad to hear!
What’s the difference between this and Planify? This just looks like Planify.
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 for sharing!
Pretty nice work but it's not an alternative to those. It's very lightweight which is enough for a lot of people, but this is maybe 25% feature parity with either of those
Thanks for the feedback! You’re right that it’s not a 1:1 replacement for TickTick/Todoist yet. That is why I used the word 'alternative' rather than 'replacement' in the title.
The core functionality is already there, and I’m working toward 70–80% feature parity over the next year or two.
I am also glad to know what particular features you miss so they will be more in my focus
Why even bother with the comparsion. Just call it a to do list then? Be realistic.
Ooooh, this looks good! Just after I went through most of the other task apps and found them lacking, this appears!
Thanks!
Very cool, I will absolutely give this a look, thanks!
Thanks!
This looks great. Thanks for sharing! Any chance to get a clean light skin as well?
Thanks! Not for now, but I am building it in a way that it will be pretty easy to add themes support
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!