Live data from Hacker News

Building a Developer Cult

subvert.substack.com

41–50 of 132 posts

Re: Building a Developer Cult

#41

If we are taking about Stripe, we should mention the silent competitor barely anyone talks or knows about outside the payments industry: Adyen. Stripe’s current, (private) valuation is $36B. Developers love them. Adyen’s current, public valuation is $43B (they IPO’d amongst little press coverage). Most developers don’t know about them. So what is the difference? Market strategy. Adyen only goes after large businesses…

I can't say much but I'll say that Adyen is light years ahead of their competition much more than they let on.

Source: Worked in software for payments processing a couple billions a year.

Re: Building a Developer Cult

#42
post #22

I recently built a Stripe integration, and can't say I'm especially impressed. Unless I completely missed some aspects, it mostly just seems like an interface to their database. While this is great for some advanced workflows, the vast majority of use cases are all very similar: "create subscription and customer", "change subscription", etc. Common workflows require quite some coding, and there's no support for trans…

As much as I love Stripe, I agree with you. Just did a Stripe Checkout implementation :

- Checkout docs are definitely not good, there is a "Getting started" and then good luck

- the CTRL+F hijack is the most annoying thing I've stumbled upon recently. Please don't do that.

Re: Building a Developer Cult

#43
post #5

Look, I know that the idea of being customer focused might seem trite, but I wanted to focus on one thing: it's the little things. "What actually differentiates stripe from the rest of the bunch though? It’s the little things.Stripe obsesses over creating a seamless CX. Small annoyances in applications compound. A user might not churn immediately because you have a bunch of unoptimized functionality or crappy UX, but…

Execution is key.

Mere "Ideas" are useless.

Re: Building a Developer Cult

#44
post #41

If we are taking about Stripe, we should mention the silent competitor barely anyone talks or knows about outside the payments industry: Adyen. Stripe’s current, (private) valuation is $36B. Developers love them. Adyen’s current, public valuation is $43B (they IPO’d amongst little press coverage). Most developers don’t know about them. So what is the difference? Market strategy. Adyen only goes after large businesses…

I can't say much but I'll say that Adyen is light years ahead of their competition much more than they let on. Source: Worked in software for payments processing a couple billions a year.

Can you say a little bit more? I'm intrigued!

Re: Building a Developer Cult

#45
post #22

I recently built a Stripe integration, and can't say I'm especially impressed. Unless I completely missed some aspects, it mostly just seems like an interface to their database. While this is great for some advanced workflows, the vast majority of use cases are all very similar: "create subscription and customer", "change subscription", etc. Common workflows require quite some coding, and there's no support for trans…

" it mostly just seems like an interface to their database. "

Payments are a huge, institutional mess under the hood, what they offer is light years better than what was there previously.

Honestly it's what 'you don't see' that's the good part.

Re: Building a Developer Cult

#46
post #3

What makes Stripe good now is what made it good way back when they first launched: Handling payments sucks and they make it suck less. The design, etc. is the gravy on top of a successful runaway train.

The remarkable thing about the culture around Stripe is that they still get the credit for the things they did well in those early days, even though they are far from the same service now that they've scaled up.

Objectively, today's Stripe is often a relatively expensive and unreliable way to collect money from your customers. The API and developer documentation are no longer as simple and effective as they once were, particularly if you need things like PSD2. Something fundamentally changed about Stripe's support a few years ago, and it seemed like almost overnight they went from routinely having knowledgeable people replying with helpful suggestions to having people who can't even be bothered to read your message before hitting whatever button sends boilerplate reply #74 with platitudes #27 and #53 at the start and end.

Much of this is understandable. Obviously you're not going to get senior people from an organisation the size of Stripe today personally responding to messages the way they used to. Some of the complexity due to PSD2 itself has been forced on them. Appealing to a wider range of merchants with more diverse needs is inevitably going to make some parts of the system more complicated.

However, the hero worship they still seem to enjoy in various forums, including this one, is remarkably cult-like now. Recommending the Stripe you remember from days gone by, particularly if you haven't recently used any of the other services now competing for the online payments market, might even be harmful to those starting small businesses today, who might be better served by one or more of the alternatives and should at least be considering the full range of options available to them.

Re: Building a Developer Cult

#47
post #10
post #9

Earlier quoted context omitted.

There has been a huge influx of articles from substack lately. I think they are trying to grow their brand.

Substack is just a publishing platform, it's not editorial.

Doesn't mean they're not submitting articles around to grow awareness of the platform/their brand.

Re: Building a Developer Cult

#48
Stripe is the most popular option out of not many options. So, when you ask a developer what's their favorite payments API, chances are they are going to say Stripe. Which isn't surprising at all.

It's just yet another post on how Stripe are customer centric.

Re: Building a Developer Cult

#49

There was a long time when Stripe was taking a significantly higher transaction fee than most other merchants for cc transactions yet there still was fervent developer push to use it anyways (Note, this hasn't been true for a few years and was only true during the first year or two of Stripe's life). People made all kinds of rationalizations to themselves for using stripe at a much higher cost simply because they did…

My first business that used Stripe was with them from their early days in the UK, and my recollection is very different to yours. They were potentially a bit more expensive in terms of fees than getting a separate merchant account and payment gateway set up, but not hugely so and at least they were consistent and transparent about those fees.

Moreover, they were vastly different in terms of the ease of integration. To take card payments via the traditional big banks and other established services, you didn't just have to put up with awful APIs and worse documentation, you also had to put up with onerous application processes that could take days to collect the required information to apply, then weeks to approve (or not), and even then often imposed severe restrictions for businesses with no trading history up to and including piercing agreements for company officers, large and long-lasting reserves being withheld, etc. The only other game in town for setting up online card payments reasonably quickly and easily at that time was PayPal, which had a reputation somewhere between Satan and the devil even then.

Of course none of this is unique today, and there are now many other services available for taking payments via card or many other methods. But in those days, it truly was a game-changer. As much as I criticise Stripe for its more recent failures, I also give credit where it's due: many small businesses, including at least one of my own, would not have gotten off the ground as early as they did without Stripe.

Re: Building a Developer Cult

#50
post #22

I recently built a Stripe integration, and can't say I'm especially impressed. Unless I completely missed some aspects, it mostly just seems like an interface to their database. While this is great for some advanced workflows, the vast majority of use cases are all very similar: "create subscription and customer", "change subscription", etc. Common workflows require quite some coding, and there's no support for trans…

If you cmd+f twice in a row that should bypass you to your browser’s native search. There’s also a toggle in the search UI so that you can opt out of the modal entirely and go straight to browser search every time. It’s in the bottom right corner of the search modal iirc (writing this comment from mobile).

Disclosure: I work at Stripe. Will pass this feedback along :)

Post reply on HN