Live data from Hacker News

Stripe Elements: Pre-built UI components to help you create checkout flows

stripe.com

61–70 of 124 posts

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#61

Stripe front end developers are a true inspiration. I know the linked project isn't anything revolutionary, but as someone with a decade of experience in the field, it's impressive to see such attention to detail. Their work somehow manages to be the right combination of cutting-edge flashiness (think Apple product landing pages) and a very down to earth usability. I can't quite put my finger on it, but it's rare to…

Minor nitpick: there's no way to see the tooltips on the checklist at the bottom on android for more than a second.

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#62

Stripe front end developers are a true inspiration. I know the linked project isn't anything revolutionary, but as someone with a decade of experience in the field, it's impressive to see such attention to detail. Their work somehow manages to be the right combination of cutting-edge flashiness (think Apple product landing pages) and a very down to earth usability. I can't quite put my finger on it, but it's rare to…

Minor nitpick: there's no way to see the tooltips on the checklist at the bottom on android for more than a second.

And on iOS there’s no way to see them without triggering the copy/paste menu.

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#64

Earlier quoted context omitted.

I am very curious to how exactly they made these animations! Surely they didn't hand type all of the transforms. I see a lot more of similar animations appearing on the internet. Are there tools that people use to help with the animations?

It can be done using Adobe After Effects and the Bodymovin plugin.

..except you will end up with a 300kb js file and a massive Json file. Whilst this plugin generates magic your speed suffers with it.

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#65

Slightly OT : With Stripe elements, we noticed an error in about 5% of the requests, something like "Stripe is not defined". Some of these errors were traced to older browsers with JS issues that couldn't execute " https://js.stripe.com/v3/" . But some remain unexplained. Unfortunately, it's hard to debug a client side error unless a client reports it. Just thinking out load about possible issues that could cause thi…

It could be because tracker-blocking plugins (I use Ghostery) have started blocking Stripe.js. This is because they are now recommending to include it on every page of your site for fraud protection, which is a use case of user tracking: https://stripe.com/docs/stripe.js#including-stripejs.

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#67

Earlier quoted context omitted.

Can't they just look at the referrer?

It lets them identify clicks specifically from the post link as opposed to links in the HN discussion thread.

Can't they see the path in the referrer URL? Wouldn't that differentiate which page on HN referred the visitor?

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#69

Stripe is really, really good at marketing to developers. I have to imagine it’s earned them a lot of business. To the extent that devs are involved in vendor selection, I have to imagine that a large majority of them suggest Stripe to their CFOs or whoever ultimately decides.

Yep, that's what happened at our company. Developer experience matters.

Re: Stripe Elements: Pre-built UI components to help you create checkout flows

#70

Slightly OT : With Stripe elements, we noticed an error in about 5% of the requests, something like "Stripe is not defined". Some of these errors were traced to older browsers with JS issues that couldn't execute " https://js.stripe.com/v3/" . But some remain unexplained. Unfortunately, it's hard to debug a client side error unless a client reports it. Just thinking out load about possible issues that could cause thi…

A client side error capture script like Sentry helps with debugging these sorts of errors. We have been using it successfully for some time now.

We are able to capture the error / stack with vanilla JS. Tried sentry too. Wondering how would it help in debugging. What we have is the error message and the user agent but unable to reproduce the same problem unless we no more about the extensions installed or if the user agent is fake.
Post reply on HN