Crossing Across Platforms
summary
Shows a real enterprise healthcare app that uses Angular plus Ionic (or NativeScript) and Electron to produce web, mobile and desktop from one mono-repo, sharing logic via ng generate application/library and a shared library. Uses TypeScript, Angular Universal for SSR where needed, component inheritance for platform-specific behavior, and injection tokens for white‑label configuration. The claim is concrete: one codebase powers responsive web, mobile builds and an Electron desktop shell and it succeeds for that real-world project.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:24Speaker background
- 3:12Client’s impossible demands
- 5:17Web app vs new platform
- 7:49Ideal cross-platform solution
- 9:37Angular for cross-platform
- 13:05Multi-platform use case
- 16:15Code sharing with Angular CLI
- 19:10Platform-specific logic
- 21:39Component inheritance issues
- 23:22White labeling in Angular
- 26:57Prioritizing requirements over solutions
- 28:21Q&A
related talks
23mCrossing Across Platforms
52mOne Source to Rule them All
01h 13mIonic, ngrx and Angular: building web and mobile apps with one code base
01h 09mSharing Code between Mobile Apps with Angular and NativeScript
25mOne Source to Rule them All
27mSharing Code Between Web and Mobile Native Apps
21mAngular For Enterprise
41mSharing Code between Web and Native Apps with Angular and NativeScript.
