I just built a product catalog app with @nextjs new app folder
I just built a product catalog app with @nextjs new app folder.
I’m impressed.
✅ The new file-based routing with nested layouts works great, and feels intuitive.
✅ I like the separation between the page, loading, error, and not-found, files.
✅ I don’t have to wire up Suspense fallback or Error boundaries directly anymore. I create error.tsx or loading.tsx instead. Elegant.
✅ If a server-side fetch is slow, it need not slow the entire page. I can create a separate component and use Suspense to display a fallback. Slick.
✅ I can easily find what I’m looking for because the URL correlates with the folder structure.
✅ I like that I can colocate other files alongside the page component. This makes it easy to decompose the page component if it’s complex, and I can keep related files nearby.
✅ The new routes API works great. I like that it uses the web standard Response and URL objects.
✅ Fetching on the server with React Server components is so effortless! Love how little code it takes.
✅ Switching between server and client components via 'use client' is easy. I create little client components when needed, so most my components are server components.
The combination of the new /app folder routing and React Server components feels intuitive and productive. 🔥
@nextjs That said, there are some pain points.
🚫 Some docs pages are missing.
🚫 I occasionally have to delete the .next folder or restart Next because it displays old code.
🚫 I got some strange errors about duplicate "body" when implementing parallel routes.
🚫 I have to display…