Ask HN: Is relying on scribd's API a big mistake?

2 points

18 years ago

I have a web application I'm working on that essentially shares documents within a small niche community. Scribd has done alot of the hard work as far as managing documents go, their iPaper allows me not to worry about storing documents, making them easily readable, etc.. Most of the heavy lifting is done by them.

HOWEVER, I am now building a web service that depends on scribd.com for full functionality. If scribd goes down, I go down. If the documents on scribd no longer become available, my service fails. I've already discussed the implications of copyright for my service with the scribd guys and that's not a concern of mine.

I've been told that scribd has enough momentum to not have to worry about it, but adding that extra coupling still makes me wary. It will save me LOTS of time and effort though and my release date will be MUCH earlier and alot more flashy and stable. I've decided to go forward with scribd.

Am I making a mistake here? I'd like to hear what you guys have to say.

6 comments