“If you’re building on someone else’s platform, whenever they are down, you are down. There is no way around that.” – Brian Breslin on why TwitBin development is stalled.
A year ago, I wrote about my hesitation of building on someone else’s platform. Since then, I launched Cullect. Which is nothing if not built atop OPP .
When I first started development on Cullect – it only supported OpenID. Only. Less popular and less understood than many other services. Today, Cullect extends 3 different platforms (4 if you count OpenID). Feels right. Feels successful. Tomorrow, I see that number increasing.
Will some services fall away? Maybe. I’m not married to any of them.
So, Cullect doesn’t care if you stop using your Twitter account and move to Tumblr. As I wrote then, I’m not interested in building on a single platform. There’s plenty of rhinos to guard.
“On top of that, there aren’t all that many rewards for building things on top of Twitter. Sure, there are tons of active Twitter users. But with all the outages and the arbitrary changes in the API limits, I just haven’t been feeling the love. Tweeterboard’s gone from a fun diversion to a distraction.” – Gene Smith
1. Other People’s Platforms 😉
One thought on “Diversified Rhino Guarding”
I agree with your sentiment on OPP. But for something as simple as twitbin, we didn’t want to complicate things by throwing in every platform imaginable. My theory is the best strategy for something serious is to build it so other platforms drive traffic and use to something you own.
btw cullect.com looks very interesting.
Comments are closed.