Angular For Enterprise
summary
A cross‑company readout convenes ~20 enterprises (teams with hundreds of devs or billions of users) and extracts eight questions that actually drive architecture and process choices. Recommendations name concrete tools and tradeoffs: use PWA Ionic NativeScript for mobile needs, NX and mono‑repos for hybrid apps, Angular Elements for CMS integration, Karma/Protractor (or Cypress/Jest where ergonomics demand), Storybook/visual tests, LaunchDarkly/rollout IO for feature flags, and Bazel to cut build time.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:20Traditional mindset
- 3:06Questions
- 3:32Information Asymmetry
- 4:16Mobile Apps
- 5:51Shared Components
- 6:17Three Layers
- 7:32CDK
- 7:43Collaboration
- 8:18Ownership
- 9:21Hybrid Applications
- 11:22Testing
- 13:12Should You Build APWA
- 14:30Release Management
- 15:52Multiple Builds
- 16:18Updating
- 18:15Build Time
- 19:28Conclusion
- 19:58Hallway Track
related talks
20mArchitectures for huge Angular based Enterprise Applications...
22mCommon Challenges Facing Angular Enterprises
01h 02mAngular 2 War StoriesAngular 2 War Stories
33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
32mAngular as strategy for collaboration and scale
29mCrossing Across Platforms
20mBuilding Platforms with Angular
32mAdventures in Angular
