Ask HN: review my app - a minimalist's to-do organizer
getcodo.com
getcodo.com
But I agree that there's a need, though it is a crowded market.
But overall nice presentation!
About web UI - there are a lot of web-based to-do list out there, so it's not really a big differentiator. For me, being a heavy user, web based to-dos didn't work very well and that was one of the main reasons I built Codo. Nevertheless I can see how it adds some value.
Mobile client - this one I'm also lacking most of all, so will do something about it sooner than later.
It's really clean and simple, which is great. I also like that you used Air, even if others disagree.
I wish I could see all tasks at once. It looks like just adding an "All" list would accomplish that.
I also wish I could select more than one list at once (with cmnd and/or shift) and see both of them merged together in the main pane.
Adding tags with the pound sign is great, and the auto completion is even better. I really like that.
I wish the tag section could include a "tagless" option, to show me all tasks that lack tags.
If I select more than one task, I wish clicking a checkbox would effectively click all their checkboxes.
It really needs to have an online counterpart though. This unfortunately is really essential. I need my todo lists at home, at work, on my phone, just about anywhere. If you had that, I think I would totally use your app.
I understand there maybe be certain issues with the platform but it doesn't come without it's strengths.
Minimum Viable Product: http://en.wikipedia.org/wiki/Minimum_viable_product
The canonical MVP strategy for a web application is to create a mock website for the product and purchase online advertising to direct traffic to the site. The mock website may consist of a marketing landing page with a link for more information or purchase. The link is not connected to a purchasing system, instead clicks are recorded and measure customer interest.
Codo is a desktop application and therefor the MVP is a desktop application. Prototyping a web application for a desktop application usually requires a complete rewrite not iteration.
MVP in general seems suspect and something hackers should avoid.
Example: Feature: (deploy first, code later) A link to a new feature in a web application may be provided in a prominent location on an existing website. The feature is not implemented, rather an apology, mock-up, or marketing page is provided. Clicks of the link are recorded and provide an indication as to the demand for the feature in the customer base.
I can understand the apprehension about MVP. As a coder myself, it is not an obvious approach (vs. putting out an actual beta) and I've not yet tried it. I'm interested in other people's stories and experiences though, and I'm not inclined to downmod a constructive conversation about it.
Would help to see numerical numbered list. I get a good kick personally knowing I have x things to get through.
2. Assuming that were possible, how is this to be packaged for Linux and Win32 such that it Just Works?
First time I looked at an AIR app I was also annoyed about having to install yet another VM thing. But, a few actually useful AIR apps later, I didn't care. So long as there isn't some creepy eternal background process running (cough Google updater cough Apple's itunes spy cough ) as residue, it's not an issue.
I wonder what it would take? I often have a list or two going, but .txt is just so convenient. Why leave emacs at all?
Current site I'm using is:
Figured a few people might be interested in taking a look at this approach which is different to most others I've tried and quite simple.
Especially since the primary niche I'm building this for is a technically-savvy crowd, such as developers and development teams.
This way you might even use a text file if you prefer for managing to-dos, but Codo would make sure it's synchronized to web and even take care of teamwork-related aspects.
Personally, I use a white board for lists of projects that need to be accomplished, and my e-mail inbox for the list of things that need to be accomplished soon. Not a perfect system, but at least I can glance at both quickly as I always have Thunderbird open and sit in front of my whiteboard.
Most of current tools in the market focus on projects rather than teams. My believe is that there is a need for both.
To-do app serves as logic starting point for this, kind of a core.
For example, the todo might be "Fix the bug #1234". In Evernote, this will be the name of the note, and in the body of the note, I copy the bug description, and write any other stuff I discovered during my work. I found that the applications which only maintains the lists of todos are not useful for me.
I'm actually using Evernote myself, it's a good app, but still there are are a number of unnecessary features, and couple critical ones missing.
You say this is a minimalist app, but these are essential for me.
About multiple fields per to-do - that's actually against one of the key principles - keep it simple, be minimalist. It keeps your to-do list focused, not overloaded with too much noise and secondary information.
Done button - you can use "Space" shortcut key for that.
One suggestion: I think it would be nice if you could tag when a task is "done". At first it doesnt mean much but I can imagine 3-4 weeks into using this id have hundreds of tasks completed. It would be helpful to be able to see when stuff was completed.
The desktop app is free and it always will be. I'm even intending to open source it one day once the code is solid.
The business model is to provide added value via web-services. Some of it may also be free and some may be charged for.
So, being said that, It makes sense to provide migration path from RTM and alike, but integrating directly with it - not so much.
On a related noted - some in-app "hints" that explains this would be great. Something I should really add ...