Did PayPal Just Clone Stripe’s API Documentation?
techcrunch.com
techcrunch.com
The visual design and structural layout of the documentation is certainly not of Stripe's creation. That's all Jeremy Ashkenas. He gave us permission to riff on it a few years ago.
I called their docs a clone on Twitter because of the original elements that were copied: the language switcher along the top; sample curl invocations on the right, with sample responses immediately afterwards; etc. Even the tiny details, like the order of the sections and URLs themselves, are shockingly similar: theirs now too live at /docs/api. The strangest detail, in my opinion, is copying the motif of having a blueprint in the background on the homepage.
The end result is that they're pretty much identical.
All of this is fine. This is just a set of arbitrary design decisions, and they're absolutely free to copy them. We assert no ownership. But given how arbitrary the design choices are, the fact that they picked all of the same ones was somewhat surprising to us -- especially since there are many ways our docs could be improved. (We hope to do so soon.)
#humility
I would have gone for something like 'sup bitches this is Patrick Collison'. Perhaps thats why I'm not the CEO of Stripe.
The world needs more business leaders with that kind of humble, thoughtful, and down-to-earth attitude and approach.
Compare PayPal's typically corporate cult of ego statement: "Under David's leadership..."
To be honest, I do wish such CEOs was more common.
For those curious, he's referring to Docco:
https://github.com/jashkenas/docco
http://jashkenas.github.com/docco/
Which is used on the Coffeescript annotated source (amongst other places): http://coffeescript.org/documentation/docs/grammar.html
The web has always been about getting inspiration from other sites on the web. As long as it's not an obvious ripoff - this is how we move forward. Building on what works. Let's worry about bigger problems.
If you want to see an example of some typical PayPal documentation, feel free to peruse this 150 page pdf on adaptive payments:
https://www.x.com/sites/default/files/2102_pp_adaptivepaymen...
Rocco is open-source.
Would you be willing to email the list of links etc for learning Ruby that you mentioned in that comment? Please send to info(at)tximmigration.com ... thanks!
That is why they look so similar.
I probably was not the first person to extend the idea of the side by side layout to an API spec and example, but I had not seen anything like it when I built the Stripe docs two years ago.
Looking through the PayPal docs quickly, they don't show any particular similarity to Stripe, besides both being REST APIs for a payments platform.
Of course new, better products will inspire others to try to best them; looking too similar is a sign that the competition is failing at that.
If anything its an improvement.
Basically, both PayPal and Stripe have text on the left half of the screen, and code on the right half. The right half also have buttons to switch between the different languages for the example.
1 - We are talking about an api documentation not a website used by 1B members .
2 - The person who called them out works at stripe...
3 - The design we are talking about is far from being very unique to stripe (today), except maybe for the blueprint.
If indeed paypal is copying stripe, it would have been more convincing demonstrating this through a set of new features they allegedly copied from stripe. That would have been more convincing and worth writing about.
Non-story.