Clarify UI direction: use Next batteries or switch to SPA tooling

[adelindanaila]

Hi maintainers 👋 quick architecture questions.

The UI currently looks SPA-first (Pages Router + client-side React Query) on Next.js 15. As I understand it, Pages Router is mainly kept for backward compatibility, while newer Next guidance favors App Router for new work.

Tagging @siddhant-galileo for context on the current UI direction. Also, from the outside it looks like a mixed approach (Next + SPA patterns), and I’m not sure we’re benefiting from Next’s bigger features (routing/data composition/App Router conventions).

Could we clarify:

1. Is this SPA-first setup on Next the intended long-term direction?
2. If we stay on Next, should we plan a path to latest Next + App Router + server-side fetching where it makes sense?
3. If we remain fully client-first, should we evaluate Vite + React Router?

Thanks!

[siddhant-galileo]

Hey @adelindanaila , thanks for bringing this up.

You are correct to understand that Pages router was kept for backward compatibility. Since then, the app has evolved to be largely client-first (React Query, interactive UI, no real SSR/SEO needs).

Also, in practice:

• dev runs on Next
• Docker/deploy serves a static SPA build

So Next isn’t really part of the production runtime today.
Given that, App Router likely doesn’t add much value for us. We’ve had discussions whether moving to Vite + React Router would better align with how we already operate.