Ask HN: How do you develop MVP if your main feature depends on an external API?
I developed a web application which I find very useful. It's for a niche and I started because it resolved a problem I had.
I shared it with a few friends (who are part of this niche too) and they like it. My problem is that the main feature (the only one feature, in fact) depends on a few external API. And I am afraid if I release and start asking money for it, it stops to work for external reasons (API shuts down, API limit rates), etc.
So my question is, how do you handle this?
PS: The APIs I am using are free and have not a paid plan with more limits.
(
17 comments
| 6 points
| on HN
)
Just search HN for all the horror stories over the past few years where some promising service got screwed over by changes from upstream providers (Twitter, Craigslist, etc., etc., etc.).
Yet, there's also a LOT of businesses that have thrived and they rely on API's. Examples being HootSuite (Twitter/FB api), SocialBro, BufferApp, SproutSocial, Klout, and a lot of social media analytics platforms. It's certainly a risk, but it's better to go forward with your plan, than not even try because you're afraid of being too over-reliant.
To mitigate the risk, is there anyway you can reproduce what the API does? Even if it's slightly shady, such as scraping.
b) can you replicate those APIs yourself over time and reduce then remove the dependency?