dbdesc blog

database documentation

Future Features and Users' Feedback

I have a pretty big list of features planned for dbdesc. One way I use to look at them is grouped like this:

  • Features from users’ feedback.
  • Features to catch up with competitors products
  • Features ‘needed’ to implement future ones
  • Features which probably will produce a major version.
  • Features which have little probability to be implemented for now.

It’s a big temptation to blog about what features I’m planning for dbdesc. However I think I have to control myself and don’t reveal features which have no due date.

The group of features which I’m having trouble to populate are the features from users’ feedback. I think that these features are the most important ones for a product. However I’m not getting as much feedback as I would like.

Most of the feedback I’m getting comes from registered users, in other words, customers. This feedback is great and it’s easy to get more feedback from them as they see that their suggestions are considered and, in most cases, added to dbdesc. But what I would like to get is more feedback from those who downloaded dbdesc, tried it and decided that it is not good enough for them. So if you have downloaded dbdesc PLEASE tell me about it. Why it didn’t suit your needs? What did you miss? Feel free to contact me, even anonymously.

Comments