Building a dedicated platform for frontend developers @ NAV
summary
Norway’s NAV runs ~1,600 applications across ~100 product teams and ~400 frontend apps and is shipping a dedicated frontend platform: a global CDN-backed static hosting with per-team namespaces (about 20 teams onboarded so far) to avoid rollouts breaking users; a design system Axel shared across agencies; observability via OpenTelemetry with Grafana Faro to capture web vitals and traces; and per-team feature flags using Unleash Writer per-team feature flags so gradual rollouts and rollbacks work in browsers. Community channels and a front-end forum drive adoption; GA is targeted over the summer.
AI-written summary · about
chapters (12)
- 0:00Introduction to NAV
- 0:53Frontend landscape
- 2:58Team autonomy challenges
- 5:05Axel design system
- 8:12Platform and infrastructure
- 12:40Frontend platform goals
- 17:35Community and knowledge
- 19:26Content delivery network
- 26:11Frontend observability
- 33:31Feature management
- 39:07Future roadmap
- 48:22Q&A session
related talks
44m5 Building Blocks for Successful Frontend Platform
23mFront-End Platform Engineering
44mMicro Frontend Architecture Building an Extensible UI Platform
21mMicro-frontends: 3 years ago
19mIn the Ocean of Angular Web Applications
40mScaling Frontend Development
22mSetting up Enterprise Frontend for Success
37mDemystifying Micro-Frontends