The mobile platform for web services might have been introduced at a later stage, but does that mean our developers will be partial with them? Of course not! But this is what has been happening in a while. It has been witnessed quite often that developers are in a habit of redesigning pre-defined desktop applications to suit the requisites of the mobile platform. This makes the entire development process backward and stagnant. So, how can this issue be resolved? What’s the answer to this problem? Well, the answer is User Interface (UI) designing. The process of UI designing allows developers to render creativity to applications designed for hand held devices, which redefines the entire concept of mobile development.
Persona form a significant part of UI experience. Thus, the first step of UI designing is to define a persona. Once you have successfully done that, it is time to relate the persona with your application’s user interface. You need to define how persona interact with and impact the UI of your application. ‘User stories’ form the basis of this step. These stories not define the role of a persona, but also aid developers in designing web applications that are compatible with both ‘big screen’ (PCs and desktops) as well as ‘small screen’ (mobile phones and tablets). Developers are generally heard asking one question quite frequently, “How do I make my big screen application compatible with the small screen?” Well technically, the question should be other way round. User stories will explain how and why?
Giving the Problem a Second Thought:
ASP.Net MVC development gives a solution to the problem of mapping big screen sites to the small screen. With .Net MVC you get the option of creating a copy of your views and incorporating the ‘.mobile.’ string in the name of your new view. For instance, client.cshtml will be renamed as ‘client.mobile.cshtml’. When a user accesses a .Net site from a mobile device, the file with the extension ‘.mobile.’ is sent.
This solution, to implement smoothly, requires to assumptions to be true. Firstly, while addressing to the mobile experience, only views will be changed. Secondly, we assume that the controller of the big screen will work absolutely fine as the controller of the small screen, after a few essential modifications. The related assumption that fuels this assumption is that small screen users have the same work flow as that of the big screen users.
These assumptions are quite reasonable, but only for applications with simple UIs. You need build two separate applications for two different platforms and moreover, the need of two different set of views will also be suppressed. User stories exemplify this in a proper manner.
This solution may not be applicable on existing applications, but will definitely prove helpful in future ventures. This method can be successfully adopted on both ASP.Net and ASP.Net MVC
Asp.Net development redefines the world of mobile application development by rendering a new way of mapping big screen apps to small screen or rather, building a single app that functions well on both big screen and small screen.
Steve Graham is a Sr. Content Writer in Xicom Technologies. Xicom is a leading Software Development Company provides different array of genuine software solutions like ASP.NET Application Development,Custom Software Development,Outsource .NET Development services its clients globally.