Small task management system - executions cannot be pardoned

    I want to share one of my achievements teamit.org . And it's not about advertising another project. This project was made as a test of the pen, it is not finished and generally unsuitable for real use. The fact is that I absolutely do not know what to do with it and decided to ask the views of the habrasociety:
    1. Develop the project further.
    2. Leave as is (can minimally develop).
    3. To abandon 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 supposed here: planning time, nesting tasks, Gantt charts and other goodies of sophisticated systems. The basic concept of task separation is based on tags or labels, with which you can divide by version, importance, category, and anything else. Under it the system of fast filtering and search is ground.

    Questions


    The internet is full of similar projects. I have no desire to copy any of them. The first question is: does anyone see at least some zest in this project or is he hopelessly gray.

    Directions of development (if at all to develop it). There are many ideas, a matter of priorities. Here are some of them (random order):
    • The ability to backup your projects.
    • Ability to add files to tasks.
    • Cross-browser (whether it is needed at all for such a niche product).
    • Scheduled automatic backups.
    • Expanded work with the list (multiselect and everything connected with it).
    • Advanced work with folders (add / delete your folders).
    • Your thoughts in the comments.

    Monetization. If you leave it, then you need to monetize, at least to pay for hosting, especially if it will be possible to store files. What can be the options besides advertising (such a niche project does not even click on the hosting) and provided that the project is free (at least the vast majority of its functions). Donation and freemium begs. Do they have the right to life? What other options could there be?

    Open source. Does it make sense to spread the source. There can be two potential reasons, as I see it: someone will fork and someone will bet locally. The first is doubtful, the second is even more doubtful, because the server side runs on node.js. However, I would be grateful for any thoughts on this subject.

    Instead of a conclusion


    A GTD blog article, so please do not discuss technical aspects and implementation methods. It is interesting first of all to evaluate the project from an applied point of view.

    PS . Demo access guest / guest.

    Also popular now: