5 ms·

You could embrace email and build a super simple task system. Issue commands via subject line. Add / Update / Close Task Assign / Transfer Task Timesheet Ta

You could embrace email and build a super simple task system. Issue commands via subject line. Add / Update / Close Task Assign / Transfer Task Timesheet Task Share Task User could add whatever they want to save about a task in the email body. Archive the emails centrally and provide full text search. Hook into the customer database and tag the content. Centralize knowledge in the organization. Use a tool everyone already owns and understands.

notahacker 16y ago
There's certainly a lot to be said for seeing email as your platform to improve upon rather than your competitor, and remembering that the luddites who prefer it to sexy Ajax GUIs quite possibly include a lot of the senior management who sign off enterprise apps.
stephen 16y ago
A really simple version of this is on my "next hobby project" list. Seems like it should have been done before though. My impression is that a lot of bug tracking tools integrate with email (e.g. lighthouse, surely others), but usually it's a minor support role to the webapp, instead of being the main focus.
- aaronblohowiak 16y ago
  Doesn't matter if it was done before if you do i "right" (for some new function of right or a competitive edge in market-finding.)
jasonlotito 16y ago
That's what I originally envisioned with DuctMail. It's a simple reminder system at the moment, but the basic idea was: command@ductmail.com Subject: Plain English Arguments Body: whatever else we might need. For example: Email: reminder@ductmail.com Subject: Today at 5PM Body: Buy milk! Also, don't forget to buy some KY, and a lawn chair. The problem with other systems is they usually try to put the arguments into the email. I'm working on a todo system as well. Email: todo@ductmail.com Subject: Name of Todo List Body: One Todo For Every line Of the email Sends you a reminder every so often, and you can reply back with what you've accomplished by putting a - in front of the item. Their are other ideas being worked on. One I'm trying to find time to finish up is a daily habit system. It would email you in the morning reminding you what you want to do every day, and then at the end of the day, it will email you, asking you for an update on how you did, and you could reply back, etc.
jonsmock 16y ago
I was about to suggest the same thing, except it basically turns you into a computer. If the app (/api) is small enough, this could work really well. But even for something as "small" as Basecamp, the "protocol" could get decently complicated fast. Somehow this equates to the Terminal vs. GUI apps debate to me.
auxbuss 16y ago
I've done this, almost exactly, with a client by using Redmine rather than email. Forcing communication through the web interface, but sending notifications via email. It worked really well. And folk (all non-tech) adjusted very quickly, since they benefited from lots of shared info. It also has a wiki and file storage, and folk started using these without them ever being mentioned. Kinda supports the idea of: give folk the tools and let them get on with it. (I am not recommending Redmine, per se, it was just what I grabbed to quickly bring sanity to an out of control situation at the time. It's not bad, though.)

notahacker 16y ago

There's certainly a lot to be said for seeing email as your platform to improve upon rather than your competitor, and remembering that the luddites who prefer it to sexy Ajax GUIs quite possibly include a lot of the senior management who sign off enterprise apps.

stephen 16y ago

A really simple version of this is on my "next hobby project" list. Seems like it should have been done before though. My impression is that a lot of bug tracking tools integrate with email (e.g. lighthouse, surely others), but usually it's a minor support role to the webapp, instead of being the main focus.

aaronblohowiak 16y ago
Doesn't matter if it was done before if you do i "right" (for some new function of right or a competitive edge in market-finding.)

jasonlotito 16y ago

That's what I originally envisioned with DuctMail. It's a simple reminder system at the moment, but the basic idea was: command@ductmail.com Subject: Plain English Arguments Body: whatever else we might need. For example: Email: reminder@ductmail.com Subject: Today at 5PM Body: Buy milk! Also, don't forget to buy some KY, and a lawn chair. The problem with other systems is they usually try to put the arguments into the email. I'm working on a todo system as well. Email: todo@ductmail.com Subject: Name of Todo List Body: One Todo For Every line Of the email Sends you a reminder every so often, and you can reply back with what you've accomplished by putting a - in front of the item. Their are other ideas being worked on. One I'm trying to find time to finish up is a daily habit system. It would email you in the morning reminding you what you want to do every day, and then at the end of the day, it will email you, asking you for an update on how you did, and you could reply back, etc.

jonsmock 16y ago

I was about to suggest the same thing, except it basically turns you into a computer. If the app (/api) is small enough, this could work really well. But even for something as "small" as Basecamp, the "protocol" could get decently complicated fast. Somehow this equates to the Terminal vs. GUI apps debate to me.

auxbuss 16y ago

I've done this, almost exactly, with a client by using Redmine rather than email. Forcing communication through the web interface, but sending notifications via email. It worked really well. And folk (all non-tech) adjusted very quickly, since they benefited from lots of shared info. It also has a wiki and file storage, and folk started using these without them ever being mentioned. Kinda supports the idea of: give folk the tools and let them get on with it. (I am not recommending Redmine, per se, it was just what I grabbed to quickly bring sanity to an out of control situation at the time. It's not bad, though.)