I need a quick primer on how spa does seo? Do they "server-render" the individual instances of pages too?
Yes. Take a look into Next.js which does this using React and it's really simple to start with.
You probably don't need a single-page app
11–20 of 522 posts
Re: You probably don't need a single-page app
#12This feels like clickbait, but just as an aside there's nothing that says you can't do server side rendering and react. Next.js is what I'm using on my current project and it's server side out of the box. So you have text rendered in source like you would with a traditional server side app with the benefits of SPA. So at least one of his nitpicks sounds like he didn't do his homework.
Re: You probably don't need a single-page app
#13I need a quick primer on how spa does seo? Do they "server-render" the individual instances of pages too?
In theory google can crawl SPAs, but in practice it doesn't work all that well. Server side rendering is one solution, a pre-rendering proxy is another.
Re: You probably don't need a single-page app
#14I have always used SPA for line of business applications. The SPA SEO request seems like a red flag that the wrong approach has been taken.
Re: You probably don't need a single-page app
#15This feels like clickbait, but just as an aside there's nothing that says you can't do server side rendering and react. Next.js is what I'm using on my current project and it's server side out of the box. So you have text rendered in source like you would with a traditional server side app with the benefits of SPA. So at least one of his nitpicks sounds like he didn't do his homework.
Of course you can use server side rendering with Next.js,but it adds some work/complexity
With a server rendered website, you don't have to do anything
Re: You probably don't need a single-page app
#16While I've long been more comfortable with server rendered pages, I feel like we're oversaturated with this sentiment. I don't think it matters all that much. The message is build with what accomplishes your goals and works with your team's skills. The notion that SPAs are only good for certain types of applications or organizations doesn't make much sense to me. Building server-generated web sites works faster for m…
> The message is build with what accomplishes your goals and works with your team's skills. Unfortunately most teams cannot be trusted to pick the right tool for each job without overcomplicating the planned implementation. Ego and the yearning to do “cool stuff” conspire to derail projects that could have been built without fuss using simpler tools.
>Unfortunately most teams cannot be trusted to pick the right tool for each job without overcomplicating the planned implementation. Ego and the yearning to do “cool stuff” conspire to derail projects that could have been built without fuss using simpler tools.
Force them to only use simple tools and the good ones will move elsewhere because they know that being stuck on just the simple things is going to limit their careers.
edit: And losing them will probably cost you more project velocity than you'd ever gain with different tools.
Re: You probably don't need a single-page app
#17> Frameworks like Rails, Phoenix, Lavarel, etc. have been around for a while and they are very stable.
Laravel is stable in production but they break backwards compatability all the time and not always in major versions.
Symfony is much better about it.
Re: You probably don't need a single-page app
#18I'm more interested in the future of "you probably don't need a native app" . It feels like browsers are closing the gap pretty well with things like IndexedDB, offline features, WASM, etc. Still a ways off, but seems like it's getting there. I do worry, though, that it's not really in Apple's or Google's best interest to move that along.
Native will always be the best solution... Because it's native.
Re: You probably don't need a single-page app
#19If latency drives your conversion, then SPA is [probably] not for you.