After years building SaaS with Next.js (since the Next 6 days), I recently migrated one of my personal projects to the App Router + React Server Components.
And honestly… the experience has been more frustrating than I expected.
Not because the ideas are bad. RSC is technically fascinating.
But in practice it often feels like we're re-solving problems that SPAs had already solved years ago.
When you're building a SaaS, engineering time should go into shipping product, not rediscovering framework edge cases.
I'm curious how other teams building serious SaaS products on the App Router are feeling about it.
Are you leaning into RSC… or still keeping most of the app SPA-style?
@leerob As a non-native speaker, I have been using AI to restructure my text; however, sometimes it sounds too formal. It’s a challenge for me to differentiate proper grammar vs AI-too-formal grammar. Ps.: I used apple proofread ai on this 😅
@nonoinvestidor Tem horas que da vontade de fazer isso mesmo, airbnb é para ser uma opção mais econômica mas o pessoal nao cuida, deixam o ar ligado o dia todo 24h por dia, a conta vem estratosférica, isso é so uma reação a falta de educação do povo.
@sseraphini Aconteceu isso na empresa que eu estava ha dois anos atras, o business querendo aumentar venda e melhorar retenção e o CTO decidiu mudar toda a stack, sai da empresa, 6 meses depois fizeram layoff e até hoje estao em transição de stack e o produto ladeira abaixo
@fortysevenfx@SandroMaglione Thank tou for sharing, we are migrating to NextJs using RSC and I’m kind of confused on best approach to use search parameters, mainly because they on RSC they are only accessible through the page component, I didn’t find a good way to access them on nested RSC