we’ve seen those issues too.

We don’t treat Next.js as a default. We use it only when it clearly fits the problem, and we’re careful about how much of its abstraction layer we actually rely on.

In practice, we keep architectures simple, maintain clear boundaries between frontend/backend, and are strict about security and deployment hygiene. When Next.js would add more complexity than value, we choose a simpler stack instead.