Tomorrow's UI Architecture — Structuring UI applications Around Features
summary
Argues that UI apps should be organized around concrete features called scenes so each URL identifies the data and the linear flow to render it, using React/Redux, react_on_rails or react-native-web and micro‑frontends. Describes building a production front end that splits client state into denormalized feature stores, moves gateway logic next to the feature, and favors server‑side rendering for first load. Reports faster parallel team development and simpler reasoning at the cost of cache consistency and SSR performance tradeoffs.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 2:35Complexity and human cognition
- 9:24Techniques against complexity
- 17:48Building modern UI platforms
- 24:35Feature-based architecture
- 31:44Scenes and linear workflows
- 35:13Final advice and conclusion
related talks
34mFunctional UIs and Unidirectional Dataflow
30mFeature Driven Architecture
30mThe Art of Front-end Architecture
01h 22mAnti-fragile frontend development
30mMicro Frontends in React — a State of the Art Approach
31mLessons from 5 years of UI architecture at GitHub
19mHarnessing Microfrontends: Platforms for Web Apps
18mSoftware Architecture Building Better Applications with Architecture Best Practices