The Way of the Web
summary
ING replaces frameworks with Web Components and Polymer, building a pure custom-element frontend plus BFFs that ships as two files (index.html and ing.js), yields a 538 KB app, 9 requests and 2.3s load with 98% GT score, and uses 350 custom elements wired to generated APIs that return rich responses (cutting ~50% I/O). Components live in separate repos, include i18n, a11y and tests, enable parallel work and faster delivery, and the approach proves performant and maintainable.
AI-written summary · about
chapters (15)
- 0:00The problem with modern apps
- 2:55Increasing complexity
- 5:00The impact of developer tools
- 5:58Architecture and silos
- 7:55Embracing web standards
- 9:37Defining web performance
- 10:34Building immortal apps
- 12:24Quality standards for components
- 13:40Microservices and APIs
- 15:26Implementing the architecture
- 16:57Components as a market
- 18:32Assemblers and craftspeople
- 19:43Runtime results
- 21:24The case for web components
- 22:43Learning and conclusion
related talks
41mComponents Approach to Building Web Apps
43mFrameworks and the Future of the Web Platform
52mWeb Components Can Do That?
01mWhy use Polymer?
36mWeb components - A whirlwind tour thru the future of the web
19mWeb Components
43mWeb Components: From 'Why Not?' to 'Why Now!'
20mAvoiding vendor lock-in through Web Components