3 ms·
In the last few months, I put together a tiny static website for my SO to sell her photographs to clients, and I budgeted a lot of time for integrating a paymen
by gen220 7y ago
In the last few months, I put together a tiny static website for my SO to sell her photographs to clients, and I budgeted a lot of time for integrating a payments solution. Like many others will say, I was pleasantly surprised how little time the integration step took.
I used the "beta" react hooks integration, and the UX of getting it all set up was basically flawless. I found the documentation (especially the quickstarts/tutorials) to be incredibly helpful.
Four pieces of constructive feedback:
- There seemed to be 3 or so quickstarts/tutorials for the same developer flow, at varying levels of detail (good), but they all had similar names and were difficult to distinguish from each other. My impression was that they were built on top of each other (i.e. one was X years old, another one X-2, etc.), but the old ones weren't removed? Unsure.
- I found the API documentation to be very good on big screens, but relatively painful on smaller screens.
- On my personal laptop (an older thinkpad), scrolling through the docs was unresponsive at times. In general, I'm a fan of the "everything-on-one-page" approach, because it makes grepping the docs easier. But I think that the quantity of dynamic elements in the API interferes with this approach :/
- I don't appreciate applications that hijack ctrl+f. I appreciate that you can double click to get native browser search, and that this is explained in the modal, but I really wonder if this helps people navigate more efficiently. I appreciate that the work that's gone into this feature must be very impressive, but I'd prefer a search bar with a different hotkey than ctrl+f. Might be worth AB testing.
Ending on a note of praise, the dashboard experience is incredible. Huge kudos on how far it's come, and how easy it is for nontechnical people to use and discover.
- mikeappell 7y ago> - There seemed to be 3 or so quickstarts/tutorials for the same developer flow, at varying levels of detail (good), but they all had similar names and were difficult to distinguish from each other. My impression was that they were built on top of each other (i.e. one was X years old, another one X-2, etc.), but the old ones weren't removed? Unsure. Second this. Stripe's documentation is generally great, but when looking for recipes/tutorials you run into a lot of seemingly duplicative content which makes it confusing to figure out which is right for you. I had this issue trying to create Connected Payments, specifically.
- pc 7y agoWe just revamped our Connect docs... would love to hear any thoughts you have on the revised version. (Feel free to email me directly -- patrick@stripe.com -- and I'll forward your thoughts to the team.)
- mikeappell 7y agoOh hey, just saw your response =) Not something I'm likely to be looking at in the nearish future, but the next time I need to do some refactoring/rolling out a new Stripe feature, I'll definitely drop you a line with my thoughts. Thanks for the heads up!
- bluehatbrit 7y agoI want to third this, this last week I've been integrating payments and I'll soon be adding in Connect as well. It took me quite a bit of back and forth on whether to use Checkout or Elements and I then ended up with 2 different recipes which resulted in the same thing but both highlighted different "important information". Eventually I just picked one and it seemd to work out really well though. I've also recently been working with the slack docs and they're the total extreme, 8 different guides with similar names and various different deprecation notices around. On the upside I felt like having both recipes was really useful to get a good overview of the options and possibilities. I'm really happy with my implementation now and I don't think slotting in Connect should be too tricky. Using the stipe docs was a breath of freshair compared to the Slack api docs which I've been using recently and have been an abysmal experience filled with hundreds of open browser tabs.
- pc 7y agoThanks! Very helpful on all counts. (And thank you for the kind words on the Dashboard... the team has made a lot of progress there.)