k7d

There is a bigger vision for new kind of teamwork web service and methodology. It came from my own experience while leading a product development team for several years. General idea is to have a very light / low friction way of planning and tracking teamwork.

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.

check out this post from Marc Andreessen http://pmarca-archive.posterous.com/the-pmarca-guide-to-pers...

It's kind of parking area where you can put to-dos which you haven't decided what to do with yet i.e. For example, for quickly dumping ideas etc. Later on you can go over the list and decide whether an item needs to be done today, someday etc.

On a related noted - some in-app "hints" that explains this would be great. Something I should really add ...

Recurring & scheduled to-dos - although it was tempting, I decided to leave it out. First because it's against good productivity principles (the less you commit to specific dates, the better), second because calendar software works good enough for that.

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.

Yes, absolutely, the web syncing is a must. The idea is to take it a step further with some cool teamwork capabilities.

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.

The most important thing I take away from this: Peldi's success is very inspiring for anybody intending to do their own thing

This is somewhat similar to "curse of knowledge" principle described in the idea stickiness theory book "Made to stick".

Although it's probably one of the symptoms, it's not the most important one.

They don't share because of their EGOS.

programmers and creative people in general are usually impractical type. well, at least a lot of them. myself included

I had Aeron at office and didn't like it that much...

sure you can customize it every imaginable way, still it's conservative and quite static chair, and it wasn't that comfortable for really long hacking sessions

The main challenge with bidirectional browser communication is really in the backend. It does not scale nearly as easy as easy as RESTful HTTP requests.

I'm sure Google has developed some serious technology to address this while building Wave. Wondering if some of it come to Google AppEngine anytime soon?