Dummy to App
summary
Shows a concrete method for building Angular apps: first define navigation and domain models, then separate UI into container components (state and logic) and presentation components (pure rendering). Extract shared capabilities into named data services (user, payment/PayPal, image‑cropper, config JSON providers), wire them via providers, and keep one data manager per module to reduce duplication, simplify unit testing, and let teams iterate mockups into working app modules.
AI-written summary · about
chapters (7)
- 0:00Zero to product
- 4:20Building apps with workshops
- 10:04Defining features
- 14:42Component architecture
- 20:58Separating logic from UI
- 25:13Module management
- 29:59Workshops for scalable software
related talks
18mFlexible data flow architecture in Angular
24mDay 2 Keynote, Angular Architecture Concepts and Practices
27mThe good, the bad and the ugly - Component architecture at scale
27mAngular Architecture: From Patterns to Implementation
51mBuilding Amazing Single Page Applications the Right Way
17mPaving the Way to Construction
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
30mAngular: Keeping it Fat, Dumb, and Happy: An Architectural Approach
