Next.js Is Ditching the Static vs. Dynamic Split

Aurora highlights View Transitions because they make it easier to create smooth animations and shared element effects. She likes the declarative API and says React handles edge cases to keep the interface stable. She also praises the Activity component for making lower-priority rendering easier to use.

Aurora previews her upcoming Next.js Conf talk about the framework’s direction and Cache Components. The proposed model removes the static-versus-dynamic split: dynamic content can suspend while the rest of the page renders statically. She says this can make apps faster and feel more intuitive, with warnings to help developers avoid problematic Suspense boundaries.

Aurora says the unified model builds on Server Components and depends on choosing and composing them well alongside interactive components. She uses Next.js for her full-time client work and would likely start a new app with it because Server Components help her build quickly. She also says AI is good at creating Next.js apps.

Aurora describes Redwood as a clean, intuitive way to transfer familiar Next.js knowledge while removing some of Next.js’s abstractions. Her example uses an entry point for a Cloudflare Worker. For the 10-minute demo, she used rehearsed code snippets to show more features efficiently.