As a developer it is always good to keep up with trends and have an understanding of the direction the field of computer science or web development is moving. Recently I have started to notice just how many thin client applications that are out there that do the exact same thing as many thick client applications. Now for those who don’t know what I’m talking about in terms of thin and thick client apps let me break it down a little.
Thick client applications are your traditional applications. These are the software that you go out and buy from the store then download onto your computer from a CD like Quicken or MS Office. Such applications are then stored on your personal computer’s hard drive taking up memory and runs completely on that computer’s resources. This also means that the security of the application is dependent on the local computer, which in most cases has a limited amount of users and access. These apps, because they are stored on a person’s local computer, are always readily available as long as there are no issues with the computer housing them. This also means that the only way to us such an application from a different computer is that it has to be loaded on that machine, and an individual would have to have there information on some kind of portable media so that it can be uploaded an reused. That means these kinds of apps are not very portable and in most cases can not be used with a mobile device.
Thin client applications are web applications. These are applications that can be accessed from the internet with out the use of a CD or any other type of media. These applications are purchased by paying for an account or subscription to a website which gives you access to the app, as opposed to purchasing it at a store. With the application itself being used from the web it dose not take up any space on the local computer, but still uses other resources from the local computer. Instead the app resides on a server somewhere that can be accessed by many users at any time, which means a need for greater security measures to be taken. Also thin client apps can be accessed by any computer or mobile device that has internet access making them very portable. With that said thin apps are only as fast and reliable as the user’s internet connection and the producer’s server. This also means that if either is not working correctly for any reason then the application could be unreachable or extremely slow.
Now with a better understanding and some background information of what is a thin client and thick client app, I go back to the original questing of which one is better? Well that’s a tough question because at the end of the day they both do the same job and usually cost about the same. Even though thin apps are easier to access and do not take up any memory of the local computer, thick apps are more reliable and usually a lot more secure. Thus I think the best way to answer this question is for users to first decide how big of an issue accessibility is. If it is a big issue for the user then yes, a thin client app is defiantly better. Yet, if that is not the case then maybe a thick client app is better. It all depends on what the user is looking for out of their apps. If you have any questions and want to know more about thick and thin client apps you can e-mail me at me_conwell@compscistuff.com.
Also a side note: Thin client apps are the basis of cloud computing, which is the idea of a computer running with its apps being ran from a remote server as opposed to on the local computer itself. This is an Idea that will be further explored in a later article so being on the look out.
Popularity: 23% [?]
A winforms applications is far easier and quicker to build than a web based application. Thin clients don’t always have to be web apps either. I dont understand why there is this huge trend towards web apps. It’s retarded, the UI is just a hack. For mine, use winforms and citrix/terminal or the linux equivolent for internal business applications.
I hate the HTML and the web, I wish it would bugger off and the world would develop with winforms.
Yay for winforms.
The above comment is ..to use common terms he may understand…RETARDED
I believe a combination of the two will serve professionals the best. Outside of applications, a lot of companies are turning to thin clients to save money. What is thin client(in terms of PC hardware)? A thin client is a computer that usual only has components for sound, I/O and networking. Usually a CPU is not required but small cheap ones are implemented. These “clients” connect to a server and access a session of windows via terminal services. LTSP is a Linux technology that also does similar things. Essential a company only has to buy one copy of the software that runs on the server and everyone can use it(this is the combination I mentioned before). The only thing the sends back is mouse movements and keystrokes, visuals are rendered by the client. In a world where visualization is getting popular and companies are tightening there belts, I believe that thicks client apps will be reduced because they are more expensive and I believe that having access to an application on-demand is the wave of the future which thin client/thin client apps can provide.
There is also a new trend around combining the two. The Rich Applications concept is driven from the limitations of web apps.
One big limitations of web apps is there is no easy way to do a push from a server to the desktop. Reverse Ajax only goes so far in dealing with this. I don’t know if it was even doable before Ajax
I’d love to read more about this