Next.js dev refuses to fetch on the client, drags entire UX into the server

This deep-dive explores how far React Server Components and Server Functions can stretch in Next.js 16.3's Instant Navigations preview, using a small social app called Drop. It covers three patterns: a load-more button driven purely by URL state, a search field that renders instantly and streams results without losing focus, and a message composer whose draft preview is server-rendered on demand. The post is less about the simplest solution and more about testing the boundaries of the server-first model for performance and UX.