I have created a free service for app developers to connect with their user base through discussions, bug fixes and a static FAQs section.
I have some features I will be working on soon (closing bugs, assigning bugs, "private" apps, RSS feeds).
Is the idea just not good enough, or is there something I'm missing that I should be highlighting?
The site is http://www.dcmntr.com/
Thanks!
I have to echo much of the sentiment of other comments here. The project is so busy. It does so many great things, but does it do any of them really well? I would identify the primary features the people appreciate most from your project and mercilessly slash the rest off. (If anyone wants to keep it, you've open sourced it so tell them to fork off!) In all seriousness, if you focus your project and show how simple it is to use, you'll find your adoption will improve.
Once you have simplified your offering, start improving your messaging to the public. Walk-through or tours will help greatly with communicating your value. People are typically visual. Large blocks of text tend to scare people away from the page. (You've got approx 3-5 seconds to grab a visitor's interest before they hit the back/close button.)
Hope this is helpful. :)