After having identified and designed the basic needs of your portal, you can now begin to build the infrastructural requirements to support those designs. Web applications will require a web server and potentially databases for ancillary data like ASP.NET security information.
Mobile vs. Desktop vs. Browser Application
Consider below facts to make a decision on your CRM portal architecture:
- Consider users. Consider who will be the majority the users. According to a survey, mobile phone used age are mostly between 15 to 40 years old. And 46% mobile phone users use a mobile application to help them with shopping and on-the-go research. 75% of them will make a purchase on the desktop.
- Consider resource. The desktop is limited by its hardware, and must meet the hardware requirements to run the application; while web application can provide access to complex applications delivered from a centralized infrastructure; a Mobile device is limited by its screen area, available memory.
- Consider deployment. The desktop must be installed on a particular operating system and deployed for each PC. While Web applications can have less deployment or update effort for hundreds or thousands of PCs
- Consider security. When it comes to online payments, users prefer secure web application over mobile devices. Sometimes, data is stored in local is safer than stored in a server. However, some application requires data stored in the server to be more secure.
- Consider availability. Web applications are universally available with internet connections. A stand-alone desktop solution can be used for no persistent network connectivity. Mobile device application could quit or restart when a call coming in.
- Consider supported device. For Web application consider a different version of user browsers.