Well, I expect Alex to speak up for himself.
But no, when you expose a public API, that's as much a part of your support environment as the applications you provide directly.
The company benefits when the community develops apps for others to use. The developer team can't hold people's hands, but they do have to ensure that no app is actively harming the system, and if an app is very popular, it's in their best interest to ensure it works efficiently and correctly.
Alex mentioned providing a better set of tools developers can use for testing and/or finetuning their applications. This is part of the support. Good documentation is another. Monitoring tools so they can tell when an app is harmful is essential.
I'm not talking about email support. I see that for end users--the non-techs.
And I did not mention about helping end users use community provided apps--I'm talking about support for the developers so that they provide applications that don't cause harm. And perhaps even embracing apps that achieve a certain level of popularity.
As for Bruce, well I can't speak for him. But if I were him, I wouldn't want my app to be used by people if there are underlying infrastructure issues causing problems with it. I don't have enough hours in the day to help the end user because of issues out of my control.
When people provide apps, they're doing the rest of us a kindness. And we should never take any of it for granted, or develop such expectations that we blame them if they decide it's in everyone's best interest to pull the app. If the app has become such an integral part of the device, then it is up the ST team to reach out to the developer and see what they can do to roll that app into the company-supported environment.
By no means do any of us have a right to have a snit. Ever.