Does GDS recommend Next.js for government digital services?

GDS (Government Digital Service) does not mandate a specific framework but strongly influences adoption. Evidence of Next.js preference: (1) HMRC uses Next.js for several tax services, (2) Companies House digital service uses Next.js, (3) GOV.UK Frontend React (govuk-react) is a React component library — Next.js is the natural host, (4) GDS Service Standard Point 11 (choose right tools) cites large talent pool — Next.js has the largest UK developer pool. Remix consideration: GDS's own HTML-first, progressive enhancement philosophy (forms work without JavaScript — accessibility) aligns better with Remix than Next.js. ClickMasters GDS approach: Next.js App Router for most services (better ecosystem), Remix for services where JavaScript-free form submission is a hard requirement.

Which framework do NHS patient-facing applications use?

NHS patient-facing applications: NHS App is React (React Native for mobile, React web). NHS Digital builds: Next.js is increasingly standard (NHS Login integration examples use Next.js, NHS FHIR R4 starter kits use Next.js). NHS UK Core FHIR R4 integration: Next.js App Router Server Components query NHS FHIR APIs server-side (no FHIR data in browser — security benefit — Article 9 health data not in client-side code). ClickMasters NHS Next.js setup: OpenNext deployed to ECS Fargate in eu-west-2 (NHS DTAC Domain 2 — patient data never leaves eu-west-2, not processed by Vercel US servers). Remix and Astro are not commonly used for NHS clinical applications — NHS Digital community knowledge is Next.js-centric.

Nextjs Vs Remix Vs Astro Uk Fullstack 2026

Next.js vs Remix vs Astro — UK Full-Stack React Framework (2026)

Updated: May 20269 min read

🇬🇧 UK💷 GBP📊 Comparison🔒 UK GDPR⚖️ UK Law

Direct Answer

Next.js App Router is ClickMasters' default for all UK full-stack projects: the UK standard (GDS uses Next.js for government services, NHS for patient-facing apps), best ecosystem (Vercel, AWS via OpenNext), and React Server Components for performance. Remix is right for forms-heavy applications where progressive enhancement (works without JavaScript) is required — government digital forms, NHS clinical forms. Astro is right for content-heavy marketing sites where no JavaScript is the performance target. Framework choice affects Core Web Vitals (Google UK SEO ranking), GDS and NHS Design System compatibility, and deployment platform options.

Factor	Next.js 15 (App Router)	Remix v2	Astro 4
UK GDS compatibility	✅ GDS uses Next.js — full compatibility	GDS compatible — less common	Static site generation only
NHS Design System	✅ NHS App Router + nhsuk-frontend-react	NHS compatible — less common	Not suited for NHS clinical apps
Core Web Vitals (LCP)	✅ RSC + ISR + CloudFront — LCP < 1.5s	Streaming + progressive enhancement	✅ Zero JS by default — best LCP
Forms without JavaScript (GDS Point 5)	Requires JS for most functionality	✅ Built for progressive enhancement	Static forms only
FCA/NHS regulatory apps	✅ Default — established patterns	Good for form-heavy workflows	Not suitable for regulated apps
Deployment (AWS)	✅ OpenNext — ECS Fargate or Lambda	Node.js adapter — ECS Fargate	✅ Static S3 + CloudFront — cheapest
Developer familiarity (UK 2026)	✅ Highest — most UK devs know App Router	Growing — less common than Next.js	Marketing/blog teams
TypeScript support	✅ First-class — end-to-end types	✅ First-class	✅ First-class
ClickMasters default	✅ All UK full-stack applications	Government forms, NHS clinical forms	Content sites, documentation only