Core Risks of Developing with Third-Party APIs
I'm not really fond of using third-party clients, because there's a core risk: your service could become unusable at any moment if the API gets shut down. If it's a free third-party service, sure, give it a shot. But if you're paying for it, you should count yourself blessed just to know how long it'll keep working.
The case mentioned in the article is a service built on Twitter's API. It was generating $14K in monthly revenue, but when Twitter suddenly started charging for API access, many developers—unable to afford the $42K annual API fee—were forced to shut down their services. My case was no different: I reluctantly sold the project for $128K (it could have fetched $500K before the API pricing change).
HuntsBot Weekly Issue 25: I Sold Black Magic for $128K
