Components are a cornerstone of any modern web application, but they can be easy to take for granted. Bloated TypeScript files and tangled component trees make apps difficult to maintain, scale, and transition to that fancy new design system you’ve been dreaming about. Not to worry – a little architectural thinking can help you start designing your components systemically, no matter the current state of your project. In this talk, Renee will use Angular examples to discuss component architecture, API design, data flow, and business logic so you can be confident in your components and deliberate in the choices you make about them on a daily basis.
Empower developers working within component-based systems to make solid design choices about components.
Assumed Audience Knowledge
Familiarity, if not experience, with Angular – those with experience with similar frameworks should be able to follow along
Five Things Audience Members Will Learn
- Using containers to untangle component dependencies
- Thinking through your component’s API design
- Using the host component + metadata
- How to make components accessible
- How to keep component logic/data reliable + testable