Why we chose Next.js for church software

Churches need software that loads quickly on modest networks, works on phones in the pew, and can grow for years without a rewrite. Next.js gives us server rendering, clear routing, and a mature ecosystem around React and TypeScript.

Locale-aware routes (`/en`, `/ko`) map naturally to how churches operate bilingually. Server Components and server actions keep auth and session handling straightforward for early PoC dashboards.

We deploy on Cloudflare Workers via OpenNext so global churches get edge performance without operating our own servers. The tradeoff is discipline: we document architecture decisions here so future contributors know why the path was chosen.