https:\/\/github.com\/jlooper\/angular-starter<\/a><\/p>\nGoal:<\/strong><\/p>\n\n- a single workspace with a working Angular Web App and NativeScript App<\/li>\n
- maximum code reuse, at first only templates are platform dependent\n
\n- Angular: *.html<\/li>\n
- NativeScript: *.tns.html<\/li>\n<\/ul>\n<\/li>\n
- shared code in “shared” folder<\/li>\n
- own build system<\/li>\n<\/ul>\n
Pro:<\/strong><\/p>\n\n- easy to start a project<\/li>\n<\/ul>\n
Contra:<\/strong><\/p>\n\n- mobile and web UIs are different, so at a long run, you are going to need components for each platform and can only share services and pipes<\/li>\n
- lot’s of build “magic”<\/li>\n<\/ul>\n
<\/h2>\n2. npm-package<\/h2>\n
Goal:<\/strong><\/p>\n\n- pack your shared code into a npm package<\/li>\n
- shared Angular should be placed in Angular modules<\/li>\n
- use the package and the modules in your NativeScript app<\/li>\n<\/ul>\n
Pro:<\/strong><\/p>\n\n- useful if your web app is already finished<\/li>\n
- projects can be placed in different folders<\/li>\n<\/ul>\n
Contra:<\/strong><\/p>\n\n- you need a build system and a private npm repository<\/li>\n<\/ul>\n
<\/h2>\n3. shared-folder<\/h2>\n
Goal:<\/strong><\/p>\n\n- web app client: put all shared angular code into a “shared” folder<\/li>\n
- include the “shared” folder via symlinks into your NativeScript app\/ folder<\/li>\n<\/ul>\n
Pro:<\/strong><\/p>\n\n- nice for prototyping<\/li>\n
- pragmatic<\/li>\n
- every project can use the own build tool<\/li>\n<\/ul>\n
Contra:<\/strong><\/p>\n\n- not sure, if it works under Windows<\/li>\n
- Angular versions and other dependencies always have to be the same in both projects<\/li>\n<\/ul>\n