Frontend At Scale - Experiences Using React In A Large Organization
summary
At SpareBank1 the team adopts React and Redux across desktop online banking, creates a shared component library of hundreds of npm modules published to Nexus, and coordinates nearly 150 developers across 20+ teams. Tooling includes a package generator (yo/Jomon), CI hooks that rebuild an automatically updated design guide from example HTML, Gemini screenshots surfaced in Bitbucket for visual diffs, and discovery to avoid duplicate widgets. Results: faster reviews and designer‑dev feedback, but ongoing costs, maintenance work and cultural shifts around purity and ownership remain.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:00Speaker background
- 3:58Organizational context
- 5:30Product showcase
- 7:38Moving to components
- 8:37Component development
- 11:06Documentation culture
- 12:18Scaling challenges
- 13:39Visual communication
- 14:15Design collaboration
- 16:04Centralized style guide
- 17:34Automated design system
- 19:45Paradigm shifts
- 21:43Organizational hurdles
- 23:33Conclusion and future
related talks
26mIntroducing and Implementing React at Coolblue
41mBuilding a design system with React in 2025, what's new?
44mApplications instead of libraries: Micro frontends implemented through module federation
31mReact on Rails
25mLessons for frontend development at scale
01h 03mMonorepo – How to do frontend faster, better and safer
49mScalable Best Practices for Your Development Team
30mDesigning with React