3 ms·
Impressive, I am definitely giving this a test drive. One observation: one thing people dislike about task warrior is that it can be complicated using it on th
by atoav 2y ago
Impressive, I am definitely giving this a test drive.
One observation: one thing people dislike about task warrior is that it can be complicated using it on the go, e.g. on a smartphone. A web interface like yours offers a real chance to make task warrior usable on smartphones and solving the syncing problem at the same time.
Is this within scope of your ideas? Or is the web interface mainly thought for (unauthenticated) local use?
- t_mahmood 2y agoFor now, my scope is local usage. As I am working as a freelancer, having free time to work on personal project becomes a luxury :-( Yes, remote usage is an issue for task warrior. As I work from home, remote access is not yet a priority to me. Come to think of it, as the UI can be accessed in LAN, maybe I can use local storage to store the data on mobile, sync with the desktop when it can connect back. I will keep it in mind, to see if I can do it, I feel it's an interesting idea!
- atoav 2y agoHey, no worries, been there, done that. It is your personal project — don't ever let anyone (including me) pressure you into doing any work you would not do yourself. If this was my project and I was tasked with adding mobile support I'd add: - a simple (optional) authentification scheme that let's you deploy the whole thing server side/log in remotely - a alternative mobile interface that works well on smartphones without keyboards Then the task data lives on the server and syncing is a on-issue
- t_mahmood 2y agoIdeas and feedbacks are always appreciated, they almost always teaches you something new