Not Every App is a SPA
summary
Argues that some sites ship faster by avoiding a full SPA up front and shows concrete techniques: Angular Elements turns components into web components using Ivy's renderComponent so tiny widgets boot without a platform, used in production on the docs site and at Capital One for AngularJS upgrades; introduces research work Photon that combines pre-render/SSR, minimal initial JS, per-component lazy loading via dynamic import and progressive bootstrapping to send HTML first then fetch component code on demand.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:20Mixed Environments
- 5:05Design Systems
- 5:26The struggle is real...
- 18:03Motivations
- 19:07What we want
- 20:59Ease of use
- 21:23Additions to Angular
- 21:45Automatic code splitting
related talks
32mBuilding a dynamic SPA website with Angular
43mRethinking SPAs: web-native apps
31mFaster content websites via SSR and progressive hydration of Web Components
54mBuilding Fast Angular Applications by Default
37mUsing Lit and Web Components to build Single-Page Applications
21mStrategies for Server Side Rendering Angular Applications
17mRethinking Angular Architecture & Performance
30mDazzingly discoverable, furiously fast web apps with Angular