Thanks for your comment. First note that as stated in the About page, this was a personal project. As such I designed it the way I thought was best for my own

Thanks for your comment. First note that as stated in the About page, this was a personal project. As such I designed it the way I thought was best for my own use, having a free take on what my ideal UX (including shortcuts) and styling would be. Marking a todo as done is a two-motion action: hover over the todo, then click the checkmark (assuming you see the checkmark). Unless you can move your cursor telepathically I think hovering is a part of the clicking motion. The mark will appear if you hover it from the left, no need to hover the text. Besides all of those actions can and are mostly done with the keyboard. The transition to the done section could be smoother as well. I didn't actually notice what I'd clicked for a moment - took a bit of analysis to figure out that I had marked one as complete. I do agree that the done transition could be improved. I can make blank todos. Maybe someone, somewhere, would like to make blank todos - for the other 99.99% of your users, this is a bug. ... Pressing the left arrow at the beginning of a todo takes me to the previous todo (bug?). That's intentional. One of my guiding principles when making it was that it should work just as it were a plain text file. Also, I can't move between the done and not done sections with the arrow keys. That one would be a bug indeed. The text is difficult to read (which seems important to a text-based todo list). On the machines I use it the text is readable and looks better that way, but I agree that the light weight could not be the best for all setups. The entire interface is almost invisible. Apart from the previous point, another guiding principle was that the main focus of the app is the content –the to-dos–. That's why the UI is lighter, and most of it disappears when you don't need it, to let you focus on the content.