Read Next

SDK Adoption: Doubled Our Conversion Click Rates

I received an email from the CEO of another SDK-based technology company asking how we've been so successful getting developers to adopt the Socialize SDK.

I like to have conversations like these in public so that other entrepreneurs in the same position can benefit from what we've learned, and share their knowledge as well. What he's asking about is a very sensitive subject: Mobile app developers are already suffering from SDK overload, and the problem is just going to get worse before it gets better. Knowing how to successfully get developers to adopt and implement an SDK is a huge tactical advantage. Having said that, I'm not going to give away the many things we do at Socialize, but I'll give a bit of knowledge away in the spirit of doing so, and I'll hope that other entrepreneurs do the same.

First things first: For those of you who don't know the difference between an API and an SDK, here's a high-level analogy to baking a cake:

What Socialize has developed is an SDK that gives any mobile app developer the ability to drop social functionality into their app. I recently wrote a related blog showcasing how these social features can help any company create Instagram-type viral growth through social actions.

No, really. It doesn't have to be perfect. Just get it launched.

On The Best of Sett

I get so many entrepreneurs telling me that their product isn't ready to be launched. While you definitely have to have something to launch, you almost surely don't need something as good as you think.

As a reminder, here's what the Amazon.com site looked like when it launched:

You might say, "but that was a long time ago. the world has changed." Oh yeah? Here's what Twitter's site looked like in 2006 when it launched:

Rendering New Theme...