This isn't an answer, just an agreement with the original poster (though I might have couched my feelings in slightly less confrontational language). The API is beginning to feel rather like abandonware. My reasoning…

- Since the competition winners were announced, the API's not even been mentioned on the blog
- We've had no official word on updates and upgrades, except a panel discussion answer that intimates writing support might never arrive. Most feature requests are either closed, or put into a nebulous "planned" state
-  Apps and wrappers have had no publicity or support from the SE team
- The API has repeatedly randomly broken (I've reported at least 2 <a href="https://stackapps.com/questions/1690/suddenly-some-entries-on-questions-route-are-missing-display-name">such</a> <a href="https://stackapps.com/questions/1883/somethings-changed-about-user-timelines">incidents</a>, and others have beaten me to more), leading to panicked debugging sessions that end up being due to a defective code update to the API. Most of these seem due to using SE having a more advanced internal version, and leaves developers feeling like they're barely second class citizens.

Inevitably, this had lead to stagnation in application development. You had a group of people excited about Stack Exchange development - excited enough to pour thousands of collective hours into free stuff that gets the Stack Exchange name out there, adding new features and value to the platform. That interest is fading fast, and not in the normal "post release" slump. Really, who's interested in a platform that pushes out an API, then says nothing at all for over 6 months? For all we know, it may never be upgraded again, leaving work against the platform defunct and dated.

You started well with the API. Don't let it all die off. Remember, once you've alienated the people most enthused by your work - those people who evangelise it with work of their own - it's almost impossible to get them back.