I work at a company with a large SAP investment, and we also have dozens of large .Net systems (mostly internally for engineering systems), and Java platforms (mostly for external web applications). As such, we have large development shops on ABAP, C#, and Java EE.
We have decent standards for which platform to use in which domain, but we don't have a lot of clarity around when to use web UIs and when to use desktop UIs.
I've seen some excellent research on this topic in the past (like this), but I'd like something a little more structured
I'd like to build a decision tree based on best practices to help with this question.
Some of the criteria I've seen in the past include:
Better performance In general, desktop applications are faster than web-based ones, run independently on your computer, and do not require proper connection to the Internet. In this case, independency from web brings a positive result.
The difference in desktop and web applications is explained in a very simple manner. Desktop application is a computer program that runs locally on a computer device like a desktop or a laptop whereas a web application needs an internet connection or some sort of network to work properly.
A Smart Client is an application that uses local processing, consumes XML Web Services and can be deployed and updated from a centralized server. While the . NET Framework (Windows Forms) and the .
I think we are seeing the separation between Web and desktop applications softened quite a bit. Rich internet applications (with Flex, Silverlight, Ajax) started this trend, and WPF with XBAP is taking the user experience of browser-based applications to another level. It is becoming a bit more involved to have this argument, because there are now more flavors in the spectrum between Web and desktop apps.
Some more questions to ask:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With