Crossing Across Platforms
summary
Concrete claim: an Enterprise Healthcare product uses Angular CLI + libraries to produce Web (responsive), Mobile (Ionic or NativeScript) and Desktop (Electron) from one repo and a shared codebase, reusing UI and services. Techniques: generated apps and shared libraries in a mono repo, component inheritance (base “shadow” components with platform templates) and configurable modules using injection tokens for white‑label variants. Result: one codebase delivering three platforms in production for that client, reducing duplicate work and keeping platform differences isolated.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:30The client demands
- 5:39Challenges of cross-platform
- 8:46Ideal solution architecture
- 10:14Why choose Angular
- 13:03Tech stack overview
- 14:53Code sharing strategies
- 17:27Advanced inheritance
- 20:12White labeling and conclusion
related talks
29mCrossing Across Platforms
52mOne Source to Rule them All
20mArchitectures for huge Angular based Enterprise Applications...
21mBuilding Cross-Platform Component Libraries for Web and Native with React
01h 13mIonic, ngrx and Angular: building web and mobile apps with one code base
25mOne Source to Rule them All
39mOmnichannel Applications with AngularJS
01h 09mSharing Code between Mobile Apps with Angular and NativeScript
