12 ms·

I'm a bit baffled by the focus on SEO on the latest frontend libraries. Sure it makes sense if you're building a store or marketplace that needs to be publicly

I'm a bit baffled by the focus on SEO on the latest frontend libraries. Sure it makes sense if you're building a store or marketplace that needs to be publicly indexed, but for most web applications SEO is only important for landing page.

Mandatum 3y ago
Most web applications are businesses reliant on income, which is also reliant on organic discovery and growth for new customers.
satvikpendem 3y ago
If I make an e-commerce page, I definitely want SEO on those products. Why not be able to use my framework of choice while also having SEO? Keep in mind these frameworks are used for making websites like blogs as well as web apps.
victorbjorklund 3y ago
Astro is probably a bad choice for an app. It shines in creating content heavy sites: blogs, marketing pages, etc
- kkarimi 3y ago
  I have been using it for an app and it’s perfectly fine. It supports middleware and doesn’t do too much magic, less complicated and more straight forward than next and the alternatives
ricardobeat 3y ago
That’s the balance swinging the other way. Since React came into the scene SEO and accessibility have been afterthoughts, but that didn’t stop millions of static* websites being built with it. It’s still not possible to do partial hydration with the majority of popular frameworks, Astro brings that back. * sites that should’ve been static but were built as an SPA
c-hendricks 3y ago
A few of the most recent JS frameworks have been scooped up by by San Francisco VC funded companies, at some point they have to align with their funding's values (generating income).
qudat 3y ago
I totally agree. All the frameworks that are “popping off” are mainly for marketing / blogs / e-commerce. None of them are a fit for SPAs or “web apps.” Vite, an API service of your choice, and a static hosting platform is pretty much all you need for web apps. It’s actually a big reason why I’m building https://pgs.sh https://pgs.sh — to cut through all the fat of publishing web apps. This doesn’t have to be anymore complicated than adding a public ssh key for production features.

Mandatum 3y ago

Most web applications are businesses reliant on income, which is also reliant on organic discovery and growth for new customers.

satvikpendem 3y ago

If I make an e-commerce page, I definitely want SEO on those products. Why not be able to use my framework of choice while also having SEO? Keep in mind these frameworks are used for making websites like blogs as well as web apps.

victorbjorklund 3y ago

Astro is probably a bad choice for an app. It shines in creating content heavy sites: blogs, marketing pages, etc

kkarimi 3y ago
I have been using it for an app and it’s perfectly fine. It supports middleware and doesn’t do too much magic, less complicated and more straight forward than next and the alternatives

ricardobeat 3y ago

That’s the balance swinging the other way. Since React came into the scene SEO and accessibility have been afterthoughts, but that didn’t stop millions of static* websites being built with it. It’s still not possible to do partial hydration with the majority of popular frameworks, Astro brings that back. * sites that should’ve been static but were built as an SPA

c-hendricks 3y ago

A few of the most recent JS frameworks have been scooped up by by San Francisco VC funded companies, at some point they have to align with their funding's values (generating income).

qudat 3y ago

I totally agree. All the frameworks that are “popping off” are mainly for marketing / blogs / e-commerce. None of them are a fit for SPAs or “web apps.” Vite, an API service of your choice, and a static hosting platform is pretty much all you need for web apps. It’s actually a big reason why I’m building https://pgs.sh https://pgs.sh — to cut through all the fat of publishing web apps. This doesn’t have to be anymore complicated than adding a public ssh key for production features.