Consider emailing the site mods using the footer Contact link. I only saw two of them and it made me uncomfortable, and they'll be better able to consider this feedback than us HN readers will.
I'm unaffiliated with Vercel but a huge fan of their work, and want to point out that the NextJS conf is underway right now. The 2 posts I saw on HN front page (Next 10, and the Commerce one) are noteworthy and I'm glad they're there.
Is it really a push, or is it just that Next.js Conf is happening right now so there is a lot of news coming out at once? You see the same thing during Apple/Google/Microsoft/Amazon conferences, the frontpage of HN is filled with multiple stories around one topic.
Often there's a benign explanation. As other users have been pointing out, it's because it's their conference day. Usually we see this flood-of-post things with $BigCo conferences but it's the same phenomenon.
Interesting. This feels like a very specific direction for such a general framework to take, but I can see how it makes sense: e-commerce occupies kind of an awkward middle-ground in the standard document-app dichotomy, making it potentially an ideal use-case for Next.js' hybrid approach.
On the one hand you have lots of "casual" or one-time visitors, for whom site responsiveness is going to have a big impact on conversions.
On the other hand you'll probably want to support real-time searching/sorting/filtering, dynamically managing a cart and account, etc. You'll probably also have some users who stay and browse for a while, and would benefit from a partially SPA experience.
I am 90% sure the SPA ppl believe that as soon as 'first render' is detected they are done performance wise. I mean, waiting 20s looking at a grey screen with a poorly rendered spinner that renders in 100ms is obviously much better UX than waiting 0.5s for a form to render. (Looking at you AWS!) /s
So I checked out the git branch for Next.js Commerce (https://github.com/vercel/commerce/). Aside from the missing documentation, there seems to be a lot of touch points where the code is tightly integrated with BigCommerce's npm library.
At this point, it does not feel like the headless ecommerce part swappable. I'm sure that with time, the team will probably extract this out so that it's more plug and play (https://github.com/vercel/commerce/issues/2) or will require the libraries (ie. for Shopify, etc) to follow a certain pattern.
If anyone on the Next.js Commerce team is reading this, the other thing I noticed is that this requires a BigCommerce account. Would be great to have a functionality where one could test out all the end points without needing a third party service in local development. I happen to have a sandbox BigCommerce shop, but there's quite a few steps to get one set up.
Absolutely. Thanks for the feedback, drchiu. I'm @okbel, actively working on Next.js Commerce. Right now the codebase is tightly coupled with BigCommerce, but in the near future (following days) we plan to add multiple data providers. I'm about to edit docs/bigcommerce.md to clearify usage. Thank you!
Hi @okbel, nice work so far! This project could be huge, and hit the target that vue storefront/deity/others have not quite cracked yet.
I'm working on a node/typescript/graphql headless commerce framework (vendure.io) and I'd love to help on an integration if at all possible.
Pros of integrating with vendure: users can stand up a fully-functional local server in 1 npx command; no SaaS account needed; low friction for JS devs used to npm work flows & idioms.
A Chargebee alternative for digital products would have been great, or something that integrates with Paddle. Don't touch ecommerce if you can sell digital products..
27 comments
[ 4.8 ms ] story [ 49.5 ms ] threadLooks like it's still largely a work in progress
Often there's a benign explanation. As other users have been pointing out, it's because it's their conference day. Usually we see this flood-of-post things with $BigCo conferences but it's the same phenomenon.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
On the one hand you have lots of "casual" or one-time visitors, for whom site responsiveness is going to have a big impact on conversions.
On the other hand you'll probably want to support real-time searching/sorting/filtering, dynamically managing a cart and account, etc. You'll probably also have some users who stay and browse for a while, and would benefit from a partially SPA experience.
At this point, it does not feel like the headless ecommerce part swappable. I'm sure that with time, the team will probably extract this out so that it's more plug and play (https://github.com/vercel/commerce/issues/2) or will require the libraries (ie. for Shopify, etc) to follow a certain pattern.
If anyone on the Next.js Commerce team is reading this, the other thing I noticed is that this requires a BigCommerce account. Would be great to have a functionality where one could test out all the end points without needing a third party service in local development. I happen to have a sandbox BigCommerce shop, but there's quite a few steps to get one set up.
I'm working on a node/typescript/graphql headless commerce framework (vendure.io) and I'd love to help on an integration if at all possible.
Pros of integrating with vendure: users can stand up a fully-functional local server in 1 npx command; no SaaS account needed; low friction for JS devs used to npm work flows & idioms.
Let's do it!
Please do it guys! I don't mind helping out!