TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Assuming there is a server behind all of this, I think it's important to use the term "client". We're going to see more and more of this architecture -- eventually nearly everything will be client/server, IMO. Maybe when that becomes old news we can drop the distinction. Until then we should make it clear... People need to know the data and processing reside "out there".
I've used the terms Desktop/Web client. Desktop instead of Windows, because the day may come when the thick client works on another OS. In my experience, most thick clients have been implemented in Java anyway... OS agnostic.
For mobile platforms, I think it's Native App for a thick client??? Is that true? Native apps are there to minimize the transfers over the wire... Maybe the term doesn't work??? Is there a better one? Can't call it a Desktop client -- Windows client is a problem as well, unless it only works on Win 8.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
