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...

nextjs.orgNext.js 16.3: Instant NavigationsA new suite of tools that brings the responsiveness of a single-page app to the server-centric model of Next.js.

Daniel Saewitz

@saewitz.com

This entire premise is flawed.

25/6/26, 7:15 pm0 reposts1 like

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.

unmaniac.bsky.social

@unmaniac.bsky.social

27 June

I'm even lost about what happens to the recent now "old" loading page 🤡

dan

@danabra.mov

27 June

nothing, that’s used as a shell when available

Daniel Saewitz

@saewitz.com

25 June

@ricky.fm put a lot of effort into solving and communicating this problem with the async client stuff (hint: pending states!), so I know I'm not alone in feeling this way.

dan

@danabra.mov

25 June

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