[mgkimsal]

"These don't make any sense to me because there are already apps that perfectly fulfill those needs if people have them."

Obviously not. Those other apps don't offer the simplicity and UI experience that yours does. What you're offering is resonating with some people, but they want what you have right now plus more. People are telling you this, and you're just telling them to go away and use another tool? Your prerogative, but you're asking how to take this to the 'next level', and your users are already telling you how - you don't need to ask HN.

[famfam]

I think the right answer is somewhere in the middle. I've worked at several companies that catered to every voice in the crowd, and the product gets pulled in a hundred directions. I have some semblance of a vision, and some of these ideas are antithetical to that vision. I think part of the reason that the UI is simple, is because of the minimalism and rejection of bells and whistles.

But you're right that I should not discount these things out of hand. I have a blank slate and it may be possible to incorporate the things that i think are relevant in a new and unobtrusive way. e.g. in a way that may only be visible to power users. For example, one feature request I do agree with is the idea of contexts, e.g. @work, @home, @school, etc. I think it makes perfect sense. I was thinking I could allow people to use @ tags in their task description (e.g. "Mow the grass @home"), then in the "give me something to do" section add a "at [dropdown]" that only appears if they've entered location-sensitive tasks. That way, the feature only adds complexity IF you want to use it.

Great food for thought. Thanks.