ASP.net Mobile Application Development

Question

I have an existing school and college management website that is developed in ASP.NET, C #, and SQL Server.

Now I plan to support mobile applications (for example, base models from Nokia / Samsung and for opera mobile phones). I know a regular site that we can access through some devices without any changes, but it needs to be optimized.

I am preparing another version, which will be just a small number of required fields and convenient navigation for mobile devices. For this method I have to use.

• Regular ASPX files with optimized HTML code.
• Or using WAP controls
• Should I use HTML 5

Please help me decide.

Answer 1

I recommend using the HTML5 templates (includes the Upgrade ) that come with ASP.NET MVC 3 and jQuery Mobile . Let jQuery Mobile platform do all the hard work for you with multiple devices.

jQuery Supported Mobile Devices

Answer 2

• You can use regular aspx pages without any problems. only you need to optimize the file size.
• you can develop a better solution using HTML5, but the only problem is that it does not support all devices. used html5
• or just use any of the list of mobile frameworks

Answer 3

You can use regular ASP.NET web forms in conjunction with HTML5. Take a look at the HTML5Boilerplate , which includes Modernizr .

Use a combination of feature detection and CSS Media Queries to serve the appropriate files, layout, and images for a specific mobile device.

Resist " Responsive Web Design"), which are too expensive in terms of performance and aesthetics (mainly to update the browser on the site’s desktop computer and calling it "mobile"); disclosure: these are links to the blog post from me .

Answer 4

Using ASP.NET Mobile Controls : ASP.NET Mobile Controls .. (i.e. how to add mobile pages to your asp.net website)

• Within a short period of time, you will create several user interface controls, in particular for all mobile devices, and it will be much faster and more convenient for users on mobile devices.
  • The user interface displays minimal HTML and you control what gets rendered, which means much less bandwidth. Although I have a 4G phone, so many times we are in a building that does not give a 4G signal, and I prefer sites that have access to mobile devices.
  • The user interface is mobile, users do not need to zoom the page left / right up / down and zoom so that you can click buttons or elements that were made for viewing in the format of 1024x768 or higher.

Users with the latest 4G and dual-core phones, and they currently have a 4G connection, can always switch their phones to the “full HTML version” if they want more functionality than what you create with ASP.NET mobile controls However, if you switch to a different route and use jQuery-based or HTML5 code, you exclude all phones of the previous generation from accessing your website in many cases (in addition to being slower and not as good as the user interface for mobile devices in the rendering). Even if you decide to focus only on the latest phones, you will also have to deal with html rendering problems, cross-browser compatibility, in addition to problems with a slow and complex interface.

Good luck.

Answer 5

Using the .NET Mobile Framework is always a good option, as well as Web forms that will appear on all mobile devices, regardless of the operator / phone model, as well as many phones that support ajax and other client-side scripts that will work. However, HTML5 is a growing standard, and when more phones start supporting it, you will get many new benefits.

The model view controller is always good. Allows you to scale and abstract components.

Answer 6

See this link, you will get an idea of ​​how to create and use the same address for a traditional and mobile web page.

http://www.asp.net/whitepapers/add-mobile-pages-to-your-aspnet-web-forms-mvc-application

http://51degrees.codeplex.com/