> Every time you find one of those little gems your product owner brain goes all sparkly and happy, it jumps for joy and you see the future of the web unfolding in front of you.<p>That's the upside of the rollout process at Facebook, but the article completely ignores the downside which happens at the other end of an app lifecycle, when suddenly your app stops working because Facebook changed something, didn't document the change, and now you have no idea what went wrong or why and your users are screaming at the top of their lungs because they can't do what they used to be able to. That part of it doesn't make you sparkly and happy, let me tell you.<p>(In their defense, Facebook is getting better at documenting deprecations, but if you're at the bottom there's only one way to go...)
I'm possibly missing something, but what's NOT documented here? Aren't these plugins on Facebook's documentation page (<a href="http://developers.facebook.com/docs/beta/plugins/" rel="nofollow">http://developers.facebook.com/docs/beta/plugins/</a>)?<p>On a sidenote, I HATE that a lot of tumblr blogs don't have comments sections. How do you interact with the blog owner in these cases?
Half of the mentioned plugins don't even work on the documentation/example pages. Not to be rude, but it's not surprising, with many of these apps being "(Beta)." I already consider most of Facebook's developer products to be Beta, and for them to mark a product as Beta, that can only be a signal to stay very far away.