Explanation/Reference:
Explanation:
How ASP.NET MVC applications can present mobile-specific pages
Since the Model-View-Controller pattern decouples application logic (in controllers) from presentation logic (in views), you can choose from any of the following approaches to handling mobile support in server-side code:
1. Create separate areas for desktop and mobile browsers, implementing independent controllers and views for each. This option works best if you're displaying very different screens, containing different information and leading the user through different workflows optimized for their device type. It may mean some repetition of code, but you can minimize that by factoring out common logic into an underlying layer or service.
2. Use the same controllers for both desktop and mobile browsers, but render different views depending on the device type. This option works best if you're displaying roughly the same data and providing the same workflows for end users, but want to render very different HTML markup to suit the device being used.
3. Use the same controllers and views for both desktop and mobile browsers, but render the views with different Razor layouts depending on the device type. This option works best if you're displaying identical data on all devices, but simply want to supply different CSS stylesheets or change a few top- level HTML elements for mobiles.
References: https://docs.microsoft.com/en-us/aspnet/whitepapers/add-mobile-pages-to-your-aspnet-web- forms-mvc-application