

I actually agree with you. I was avoiding making doc the whole time, but as amount of features growth, readme is not enough. I will introduce a good doc soon. Thanks!


I actually agree with you. I was avoiding making doc the whole time, but as amount of features growth, readme is not enough. I will introduce a good doc soon. Thanks!


You still need to sign up to sync between devices. With the self-hosted version, you also create an account, but authentication and all synced data stay on your own server.
Offline-first means the app works without an internet connection; it doesn’t necessarily mean that no account is required. After sign up/sign in, you can use it offline without any problems.


It is just LWW per column. On each client I track last change of each field with current time(actually sysytemTime-counter-clientId to make time uniq). Then, when changes arrive to server, I compare previous clock time with new clock time from client. If client win, it overwrite server column time + value. No tracking causality for now, just current system time of the client.


Fixed. Thanks for the hint!


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 /.


Thanks for the honest feedback!
Could you share what specifically makes it feel like a bloated todo app to you? Also, what deployment or distribution method would you prefer over Docker?


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!


Yep, I agree too, it’s totally fair 👍
Thanks for your feedback!


Yep, that’s why I don’t like SuperProductivity, it’s hard to make proper sync on top of json/caldav(especially with proper conflict resolution). As far as I know, SuperProductivity building its own cloud sync protocol, but it’s plan to be a paid feature anytime.
As for mobile version - yep, I plan to add them too. It’s already support PWA, so you can install app as a bookmark (and it opens pretty fast btw! And works offline also). But I want to have proper notifications in future and maybe widgets, so andriod/ios will be, but not sure when.
Thanks for the feedback!


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.
Nah, it will very hard to do. I wanted it to be fast from the start, so I was playing with sync and how I store data in browser.