Since folks asked here's the diff between @blitz_js & @redwoodjs

Redwood is tooling & conventions for traditional SPAs

Blitz is not a traditional SPA. The end UX of a Blitz app is the same or better than an SPA, but the DX is like a traditional server-rendered MVC app

Thread👇 Before I go on, Redwood looks awesome and congrats on the launch! More projects & approaches are better for everyone!

🚧 Guide to React App Architectures 🚧

1. Classic SPA
2. Hybrid SPA
3. Hybrid SSR

Please do comment if I missed a major architecture or missed any pros & cons!

👇 Thread 1. Classic SPA

⭑ Truly a "single page"
⭑ Ex: create-react-app, Parcel

Pros:
‣ Use react-router for advanced, flexible routing throughout nested components

Cons:
‣ Requires an API
‣ By default all code goes in one large bundle
‣ Can only have 1 static app shell

🚀 Technical Design Patterns for SaaS
(A thread)

Goals:
• Fantastic end-user experience
• Build as little as possible
• Speedy development
• System resiliency
• Easy for a solo dev

First part is a specific stack, but the rest is stack-agnostic.

https://twitter.com/patio11/status/1219997892028448768

Use React or Vue

Users expect rich UIs that are easier/faster to build/maintain with React. It's now a proven & boring technology, adopted everywhere from startups to enterprise. If there’s a chance you’ll need native apps, use React-native-web to run all code on every platform.