Bridging the gap between API documentation and Stackoverflow

Like most developers, I have to face the reality that often the documentation for APIs and technical information is lacking. This applies especially to Google, Microsoft and many other large corporations. They have certainly gotten better over the years but are still lacking. My biggest issue is the amount of time I end up spending hunting down an answer to my problem. First I might use Google to search Stackoverflow but often end up going through several posts before I find the solution. If I can't find it in Stackoverflow, then I search the web and slowly prod my way through all the articles. We've all been there.

I asked myself whether this problem couldn't be reduced by a large factor. I came up with the idea that if I created a desktop app that synchronizes with your browser's url, you could post content that would remain attached to the url. Then I could post my question in the app. Others who use the app and who visit the same url would see my question and could respond. Maybe that other person could be another developer or the technical writer of the documentation.

I ended up spending a long time building the app and launched it a week ago but it hasn't caught on. It's called Skutti and is available at skutti.com

So now I'm asking myself a fundamental question. Was this a problem worth solving? Have developers simply accepted it as part of their work to have to repeat the exact same solution of searching for a solution in Stackoverflow and the web every time they have trouble with the documentation? Or is my problem that I face a chicken vs. egg issue, where users won't use the app until they see enough other users using it? Or am I fundamentally wrong about something in how I am going about bridging this gap between the documentation and the developers?

Please let me know your thoughts.