Deployment was quite complex for the target audience, due to requiring mutual TLS and thereby requiring the management of self signed key infra or a commercial TLS cert.
I've had good success using Syncthing to keep my tasks in sync between my phone, laptop, desktop, etc. Point it at your Taskwarrior data folder and you're off.
I see taskwarrior-tui being mentioned a couple of times in this thread. If anyone is interested in why or why not to use taskwarrior-tui, the biggest advantage of taskwarrior-tui are 3 fold:
1. Previously you would have to type `task report`, `task add …`, `task report` again to see how your priorities have changed. With the TUI you can get live feedback.
2. By default, the TUI comes out of the box with intuitive (in the author’s opinion) single-key press actions that map to various taskwarrior subcommands on single or multiple tasks.
3. The UI lets you as a user run 9 custom bash scripts as shortcuts that can extend features without changing the source code.
There are a few things not so good about it though.
1. Everything is accomplished by shelling out to the taskwarrior `task` cli, which has some nuances in parsing command line arguments, and all the corner cases haven’t been ironed out.
2. The calendar feature, the contexts feature, styling features etc are all underbaked or incomplete.
3. This was the author’s first Rust project and definitely needs some refactoring love.
The author definitely recommends reporting any issues or feature requests. He’s also extremely appreciative of the fact that people use the tool and advocate it to other people on threads like this!
An IDE or a browser have a huge number of failure points.
Just starting up initiates large numbers of complex operations, file I/O, processing, database, graphics, platform specific operations, what not. They are in a way OS of their own.
Comparing a CLI application, that's scope is tiny compared to a full-blown IDE or a browser, is absurd!
I wish cross-device-sync was feasible, but it's pretty good.