A small task management system - you can not execute the execution
I want to share one of their experience teamit.org . And it's not about advertising the next project. This project was done as a sample of the pen, it is not finished and generally of little use for real use. The fact is that I absolutely do not know what to do with it and decided to ask the opinion of the habrasociety community:
The project is positioned as a simple free system for a small team to manage current tasks. Based on this definition, it is not intended here: time planning, task nesting, Gantt charts, and other tricky systems. The basic concept of separation of tasks is based on tags or tags, with which you can divide by version, importance, categories and everything. Under the same system is sharpen quick filter and search.
The internet is full of similar projects. I have no desire to copy any of them. First question: does anyone in this project see at least some zest or is he hopelessly gray?
Directions of development (if at all to develop it). A lot of ideas, a question of priorities. Here are some of them (arbitrary order):
Monetization. If you leave it, then you need to monetize, at least to pay for hosting, especially if it is possible to store files. What could be other options than advertising (such a niche project even does not click on hosting) and provided that the project is free (at least the vast majority of its functions). It begs donation and freemium. Do they have the right to live? What other options might there be?
')
Open source. Does it make sense to lay out the source. Potentially, there can be two reasons, as I see it: someone will fork and someone will put it locally. The first is doubtful, the second is even more doubtful, since the server part runs on node.js. However, I would appreciate any thoughts on this.
An article in the GTD blog, so please do not discuss the technical aspects and methods of implementation. It is interesting first of all to evaluate the project from an applied point of view.
Ps . Demo access guest / guest.
- To develop the project further.
- Leave as is (can minimally develop).
- Throw and close as completely hopeless.
Description and positioning
The project is positioned as a simple free system for a small team to manage current tasks. Based on this definition, it is not intended here: time planning, task nesting, Gantt charts, and other tricky systems. The basic concept of separation of tasks is based on tags or tags, with which you can divide by version, importance, categories and everything. Under the same system is sharpen quick filter and search.
Questions
The internet is full of similar projects. I have no desire to copy any of them. First question: does anyone in this project see at least some zest or is he hopelessly gray?
Directions of development (if at all to develop it). A lot of ideas, a question of priorities. Here are some of them (arbitrary order):
- The ability to backup their projects.
- Ability to add files to tasks.
- Cross-browser (do you need it at all for such a niche product).
- Automatic backups on schedule.
- Extended work with the list (multi-select and everything connected with it).
- Extended work with folders (add / delete your folders).
- Your thoughts are in the comments.
Monetization. If you leave it, then you need to monetize, at least to pay for hosting, especially if it is possible to store files. What could be other options than advertising (such a niche project even does not click on hosting) and provided that the project is free (at least the vast majority of its functions). It begs donation and freemium. Do they have the right to live? What other options might there be?
')
Open source. Does it make sense to lay out the source. Potentially, there can be two reasons, as I see it: someone will fork and someone will put it locally. The first is doubtful, the second is even more doubtful, since the server part runs on node.js. However, I would appreciate any thoughts on this.
Instead of conclusion
An article in the GTD blog, so please do not discuss the technical aspects and methods of implementation. It is interesting first of all to evaluate the project from an applied point of view.
Ps . Demo access guest / guest.
Source: https://habr.com/ru/post/120916/
All Articles