5 ms·

I was probably too incendiary in my phrasing, and I agree with what you say. If Simplify solves your problems better than Stripe does, you should use it (and go

by pc 13y ago

I was probably too incendiary in my phrasing, and I agree with what you say. If Simplify solves your problems better than Stripe does, you should use it (and good job to them for doing so). It's our job, of course, to have that not be the case. The point I was trying to make was fairly narrowly scoped: needlessly copying even tiny details of Stripe is pretty uninspired. (P.S. Any chance you could drop me an email? I'm patrick@stripe.com.)

breck 13y ago
> needlessly copying even tiny details of Stripe is pretty uninspired. I disagree. Copying tiny details is a very smart strategy for non critical parts of your product. Do not try to reinvent the wheel...and the axle and the airbag, all at once. Designers should focus on what's unique and different about their offering, and leverage from the community the other parts. I'm sure Stripe put a lot of design time into those API details. Simplify is bringing new features to the market (faster payouts and lower prices), and so their time and money is better spent on those than trying to also reinvent API design. And it's better then to just copy verbatim than to put up the first thing that comes to mind. I could otherwise argue that Stripe's use of JSON and HTML is pretty uninspired because Braintree was doing it years before.