We are working on a project to develop a solution with a large number of modules in which the client wants a website as well as mobile application.

As a team we're working using ASP.NET MVC and Web API. So we can create a MVC website and an API for mobile applications, in Web API. In that case we can create a separate BL and DAL and use common logic into both projects.

But now we have ASP.NET Core, so I'm considering handling it with single controller methods, which avoid controller logic duplication.

So, currently we've chosen Angular2 for the website and Web API as a back-end. But I'm still confused on the issue about handling a single controller from Angular2 and mobile application.

  • Is this the best way to go with or any other way to go with?

  • What further issues may I face?


If you are not stuck with .net, It think the most efficient way(time/money/quality) is using ionic (which is angular) and Firebase. They are more focused on mobile side, but I don't see any reason not to use it for web too. One app, works everywhere.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.