@Angularnyc
  @Angularnyc
AngularNYC | Sharing Code Between Web and Mobile apps - Sebastian Witalec @Angularnyc | Uploaded December 2018 | Updated October 2024, 2 hours ago.
Building separate web and native mobile apps, requires a lot of effort and is very expensive. This often forces us to pick just one and as a result sacrifice overall user experience.

But you don’t need choose, you could do both with a single code sharing project.

All it took, was a few sleepless nights and a few months of collaboration with the Angular team.

I hear you ask: “How?”

Simple: Structure your project with the power of Angular CLI and “Custom Schematics”. Then use Angular and NativeScript to build for web and native mobile.

Do you want to transform your existing web project to a code sharing structure? We’ve got you covered with ng add and a collection of migration schematics.

Join me and AngularNYC team to learn how the code sharing projects work, what can be shared, and how to transform existing projects. And all of that with just a couple of new CLI commands.
Sharing Code Between Web and Mobile apps - Sebastian Witalec#angularnyc: React vs Angular 2 vs Backbone - Paul Burt - 09/20/2016AngularNYC: From AngularJS to Angular: the Seamless approach - Eric Tsai (@tsaibot)Angular Route Guards - Chris SamuelsWeb Design is design in the Web - Peter B. Smith and James GibsonBuild real-world form systems with Angular | By Nir KaufmanChris Samuel 🎤 Angular Routing and NavigationCreate Your First Angular Library - Nir KaufmanCreating an observable from scratch (live-coding session) - Ben LeshAngularNYC - Working with WebSockets in Angular apps - Yakov Fain (@yfain)AngularNYC - Patterns on top of Patterns: A discussion of ngrx-entity - Nate KidwellAngularNYC - Angular 6 vs AngularDart - David Christian Liedle

Sharing Code Between Web and Mobile apps - Sebastian Witalec @Angularnyc

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER