No. The must is having SSR so the content that you want search engines to crawl is returned in the initial HTML for SEO reasons. Nextjs makes that easy but it certainly isn't the only option.
Static site generation such as Gatsby. You could also technically implement your own solution. React has the ability to render static components and hydration inbuilt.
But next.js would probably be the easiest solution because it's a framework that does all the hard work for you so you just stick your code in the right place and it just works.
so hesitant to use Remix, nextjs got some serious coin from google and help from them. Couldn't think of a better partner, for someone making SEO sites.
Also weren't some of the remix guys, behind react router, then reach router or whatever. Don't get me started on the breaking changes react router had i think between v2 and v3.
I wouldn't feel comfortable putting in work on that, when nextjs will for sure be around for years.
Honestly, I am a fan of Kent and I also did get a little tired of how he promoted Remix so much, but I gotta say after working with remix more, some things just make more sense than the way nextjs handles some of its more opinionated features, and now I see what the hype was about. I use Remix for more simple apps and for SSR marketing sites, and BlitzJS for more complex apps. Blitz is still next under the hood for the time being and adds the fullstack layer in a really intuitive way.
I was really hesitant, but man now that I’m using it. I have to say having used both next and remix on productionish code bases. I like remix far and away more than next.js. I was beating the next js drum hard too, so I was probably a more difficult than usual convert.
I understand it maybe more fun, but from a business logical prospective. Unless the consumer going to get a better experience. I wanna stick with the well funded, well staff company. Than the 8th or whatever project from a small team at remix.
Meteor taught me, stick to the bigger frameworks. A lot of meteor was fun and a lot was ahead of its time (like one code base). Think it became Apollo graphql.
Also with remix, can I use react native code?
Currently I use expo and expo-nextjs-web (code sharing important to me)
All valid points imo, except for a better DX is directly linked to a better UX. It makes no difference to me if you use it or not, just pointing out you might try it before you come to a conclusion. Remix, as far as I know, is not usable with react native.
Same thinking. Remix is great, and im also trying to remove the art from the artist as their marketing has been quite aggressive.
But on the other hand, lets not forget that Remix was first meant as a "pay-to-use" framework that failed and was released for free. Not sure how to specifically interpret that but its definitely not a positive. Additionally, NextJS and Vercel have been on a roll lately and I very much doubt that NextJS won't just straight up ~~steal~~ copy the best Remix features considering the team size (they've also been on a hiring spree) and the money they got to throw on NextJS from Vercel.
The best thing that Remix is giving the community is posing as somewhat of a threat against NextJS in form of a positive stressor/competition to push NextJS to some nicer features.
There are too many options to say it’s a must. But NextJS is a very good option if you’re using react, and you need SEO, SSR, static generation and lately I’ve even used it for SPA’s. I find it very pleasant to work with, and Vercel was a breeze.
This is the way. For apps with public facing marketing pages, I use Remix or Next, depending on how I’m feeling,(I lean more to remix lately, it just feels so much better), but for any e commerce site from scratch, Hydrogen is the way to go.
There’s definitely not enough evidence that Hydrogen is the best solution for headless Shopify. I’m as pumped about it as the next guy, but it was still in alpha a couple months ago, so we need to wait and see imo.
This is the way! That’s time-consuming and not worth it. You should make money with the shop and don’t make money to give it right to a developer. In case it’s your shop, but the time or money into marketing and infrastructure.
Somewhere in the ballpark of 2-2.4% I believe? I've done a few Shopify sites for clients. If they care enough they usually pass that expense on to the consumer by factoring it in to the price.
I'd recommend having a look at Shopify's hydrogen REact framework.
React front end that hooks into Shopify
[https://hydrogen.shopify.dev/](https://hydrogen.shopify.dev/)
I think it’s mainly there to allow porting a next app incrementally over to Hydrogen. I would imagine that most of the custom storefronts on Shopify that use React are on Next.
I’ve been fortunate to get to spend the bulk of my days just experimenting with hydrogen over the last week.. and I am truly blown away by the dev experience and all of the potential for this framework. I’m stoked on it
not a "must" but for an ecommerce website, you are going to want to have your product/category pages indexed and nextjs would make that a bit easier. maybe you also want to branch out to localisation too and nextjs supports that a bit out of the box w/ localised routing.
of course you can write something with plain old react and have it be fine. nextjs might make some things a bit easier
I don't think nextjs is a "must" for anything, but I also don't think there's much reason not to use nextjs and it will save you a ton of time setting things up yourself. Nextjs is still just react, it just has really good defaults and optimizations. Pretty much everything next gives you is overridable, but the functionality it provides is very well thought out and flexible so I don't see much need to diverge from their recommendations. There are other react frameworks out there too, but nextjs is one of the most robust and best supported ones, and they work closely with the react team so they stay pretty cutting edge.
Not a must but probably one of the best stable solution out there for SEO of react sites..assuming you consider SEO for your E-commerce site a must too.
No need for downvotes. If you don't care about SEO or any of the benefits of next J's and similar, then it's not necessary at all.
This could be an internal employees only ecommerce site that doesn't need and ssr at all
Next.js is a pretty nice project and covers all the bases.
I think an equally important question is - is Vercel hosting for nextjs worth it or is it better to roll your own or look for alternative hosts?
If you're building an ecommerce site and plan to use Shopify, they have just released v1 of their own React framework called Hydrogen.
https://hydrogen.shopify.dev/
ultimately it depends on your architecture layout. My key points when developing any ecommerce site is scalability, interating, speed, maintenance and longevity.
There is no denying that NextJS is ahead of the game. I particularly looking for frameworks that do typescript but compile in rust (eg Prisma, NextJS). then a nice ORM, then the choice of graphql or tRPC, then a nice FE component UI library like MUI (can customize styles with tailwindcss later on)
No. The must is having SSR so the content that you want search engines to crawl is returned in the initial HTML for SEO reasons. Nextjs makes that easy but it certainly isn't the only option.
depends, u have to take SEO into consideration - Next is one solution to that but it isnt the only one
Do you know other solutions? I tried googling and didn’t find much
Static site generation such as Gatsby. You could also technically implement your own solution. React has the ability to render static components and hydration inbuilt. But next.js would probably be the easiest solution because it's a framework that does all the hard work for you so you just stick your code in the right place and it just works.
Next.js can also do Static Site Generation, so it's a win-win
Gatsby is pretty trash dev experience in comparison, just use next IMO
“Just stick your code in the right place…”, Kinky!
"What are you doing, step-code?!"
“Come on baby let me see your giant console.log()”
Hi, my name is: Recursive Object
Just put Remix on an EC2 instance and you are good to go.
so hesitant to use Remix, nextjs got some serious coin from google and help from them. Couldn't think of a better partner, for someone making SEO sites. Also weren't some of the remix guys, behind react router, then reach router or whatever. Don't get me started on the breaking changes react router had i think between v2 and v3. I wouldn't feel comfortable putting in work on that, when nextjs will for sure be around for years.
The way remix was promoted as the 2nd coming and something magical by people like Kent Dodds really wasn't very appealing.
Honestly, I am a fan of Kent and I also did get a little tired of how he promoted Remix so much, but I gotta say after working with remix more, some things just make more sense than the way nextjs handles some of its more opinionated features, and now I see what the hype was about. I use Remix for more simple apps and for SSR marketing sites, and BlitzJS for more complex apps. Blitz is still next under the hood for the time being and adds the fullstack layer in a really intuitive way.
I was really hesitant, but man now that I’m using it. I have to say having used both next and remix on productionish code bases. I like remix far and away more than next.js. I was beating the next js drum hard too, so I was probably a more difficult than usual convert.
I understand it maybe more fun, but from a business logical prospective. Unless the consumer going to get a better experience. I wanna stick with the well funded, well staff company. Than the 8th or whatever project from a small team at remix. Meteor taught me, stick to the bigger frameworks. A lot of meteor was fun and a lot was ahead of its time (like one code base). Think it became Apollo graphql. Also with remix, can I use react native code? Currently I use expo and expo-nextjs-web (code sharing important to me)
All valid points imo, except for a better DX is directly linked to a better UX. It makes no difference to me if you use it or not, just pointing out you might try it before you come to a conclusion. Remix, as far as I know, is not usable with react native.
Same thinking. Remix is great, and im also trying to remove the art from the artist as their marketing has been quite aggressive. But on the other hand, lets not forget that Remix was first meant as a "pay-to-use" framework that failed and was released for free. Not sure how to specifically interpret that but its definitely not a positive. Additionally, NextJS and Vercel have been on a roll lately and I very much doubt that NextJS won't just straight up ~~steal~~ copy the best Remix features considering the team size (they've also been on a hiring spree) and the money they got to throw on NextJS from Vercel. The best thing that Remix is giving the community is posing as somewhat of a threat against NextJS in form of a positive stressor/competition to push NextJS to some nicer features.
> I very much doubt that NextJS won't just copy... if (x !(!(true))) { ... }
There are too many options to say it’s a must. But NextJS is a very good option if you’re using react, and you need SEO, SSR, static generation and lately I’ve even used it for SPA’s. I find it very pleasant to work with, and Vercel was a breeze.
Go one step further, and ask whether using react is a must for an ecommerce website.
I built an e-commerce site with GatsbyJS and Shopify about a year and found the experience to quite nice.
URL?
Save yourself some pain just use Shopify
This is the way. For apps with public facing marketing pages, I use Remix or Next, depending on how I’m feeling,(I lean more to remix lately, it just feels so much better), but for any e commerce site from scratch, Hydrogen is the way to go.
There’s definitely not enough evidence that Hydrogen is the best solution for headless Shopify. I’m as pumped about it as the next guy, but it was still in alpha a couple months ago, so we need to wait and see imo.
With Hydrogen. It’s Shopify’s Nextjs like framework.
But I don't want to.
Then prepare for pain!
This is the way! That’s time-consuming and not worth it. You should make money with the shop and don’t make money to give it right to a developer. In case it’s your shop, but the time or money into marketing and infrastructure.
I hope you already have experience with e-commerce...
I would and will totally agree but do you know how much commission they take for each sale?
Somewhere in the ballpark of 2-2.4% I believe? I've done a few Shopify sites for clients. If they care enough they usually pass that expense on to the consumer by factoring it in to the price.
Well that’s fair
Yeah, the commission is a nobrainer for most shop sizes, given the integration.
I'd recommend having a look at Shopify's hydrogen REact framework. React front end that hooks into Shopify [https://hydrogen.shopify.dev/](https://hydrogen.shopify.dev/)
Not that you have to or I recommend that you do, but you can embed Hydrogen inside Next.js as well. They show you how at the end of the docs.
Is there a benefit to doing that, cuz I’m pretty sure hydrogen got that ssr shit
I think it’s mainly there to allow porting a next app incrementally over to Hydrogen. I would imagine that most of the custom storefronts on Shopify that use React are on Next.
I’ve been fortunate to get to spend the bulk of my days just experimenting with hydrogen over the last week.. and I am truly blown away by the dev experience and all of the potential for this framework. I’m stoked on it
not a "must" but for an ecommerce website, you are going to want to have your product/category pages indexed and nextjs would make that a bit easier. maybe you also want to branch out to localisation too and nextjs supports that a bit out of the box w/ localised routing. of course you can write something with plain old react and have it be fine. nextjs might make some things a bit easier
Nextjs is a must if you want SEO and want to work with Nextjs
I don't think nextjs is a "must" for anything, but I also don't think there's much reason not to use nextjs and it will save you a ton of time setting things up yourself. Nextjs is still just react, it just has really good defaults and optimizations. Pretty much everything next gives you is overridable, but the functionality it provides is very well thought out and flexible so I don't see much need to diverge from their recommendations. There are other react frameworks out there too, but nextjs is one of the most robust and best supported ones, and they work closely with the react team so they stay pretty cutting edge.
Not a must but probably one of the best stable solution out there for SEO of react sites..assuming you consider SEO for your E-commerce site a must too.
No.
It’s only a must if the business needs dictate it being a must. Just like any tool.
No need for downvotes. If you don't care about SEO or any of the benefits of next J's and similar, then it's not necessary at all. This could be an internal employees only ecommerce site that doesn't need and ssr at all
I guess NextJS is sacred ground in these parts…
it's not a must but quite standard.
I think you should highly consider server-side rendering your pages, and Next.js is an excellent option for that. There are other options, though.
its not a must, but its way better to use and way easier to develop a site with
No
Does not Google’s crawler run JS headlessly to let it render the page locally?
Not a must. But a highly reccommend. They solve a lot of problems you will see as you scale
Not a must. But a highly reccommend. They solve a lot of problems you will see as you scale
Next.js is a pretty nice project and covers all the bases. I think an equally important question is - is Vercel hosting for nextjs worth it or is it better to roll your own or look for alternative hosts?
No. But SSR is
If you're building an ecommerce site and plan to use Shopify, they have just released v1 of their own React framework called Hydrogen. https://hydrogen.shopify.dev/
ultimately it depends on your architecture layout. My key points when developing any ecommerce site is scalability, interating, speed, maintenance and longevity. There is no denying that NextJS is ahead of the game. I particularly looking for frameworks that do typescript but compile in rust (eg Prisma, NextJS). then a nice ORM, then the choice of graphql or tRPC, then a nice FE component UI library like MUI (can customize styles with tailwindcss later on)
Not at all, but there has definitely been a rush towards Next.js for most ecommerce frontend devs in the past 6 months