Post

Next.js 16.3 Preview: Instant Navigations A new suite of tools that brings the responsiveness of client-driven SPAs to Next.js, without giving up what Server Components do best. The speed of the server, with the feel of the client. Try it and tell us what you think ↓ nextjs.org/blog/next-1...

This entire premise is flawed.

in what way?

the premise is either "nothing happens" or "show the next page's loading shell" - but there exist other ways to solve the problem without either of those (imo) flawed approaches. this is one core motivation of my upcoming rsc framework.

i see! i’d say the post intro describes two ends of the spectrum, but the actual model described in the post is more flexible. it’s more like ability to enforce which navigations have no async gap. having a guarantee like this is important, especially if routes need to work offline or w/ bad latency

I agree, the instant navigation is an interesting mechanism – this is effectively closing the "SPA" gap that the app router hasn't historically supported (where the whole router is navigable without internet). But it's still focused on shells and loading states, when I think that's missing the mark

Next and my framework are ultimately building for ever so slightly divergent use cases and mental models. I'm excited to share my ideas though, I believe I have some interesting stuff packed in here.