Thank you, and I agree. I want this to do one thing, and do it very well.

As to simple? If I wanted to joke, I'd say that my codebase would disagree, but in reality I see this as somewhat of a knife's edge. On the one side, you have the actual usability, and I've fought over every inch of the UI flows to try and keep them streamlined, useful. But on the other side, there is actual utility, and there are custom shapes for tasks I haven't addressed yet like scheduled tasks (e.g. watering the garden), repeating but varied tasks (e.g. school homework), and I need to make them fit in with the kinds of tasks people already put on a task list, like going to appointments, or personal projects like learning a guitar, work projects where a document must be finished before a presentation.

But the question is one I actually want to hear, and the answer is a resounding yes. I told my testers, when prompted about ideas (calendar integration, rich formatting), that I would have to weigh the utility for my users against the cost in complexity and maintenance, and it puts a silly smile on my face as I think about doing that work.

I'll take the opportunity to ask back to you. What does best in this area mean to you? What else could I be doing?