Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

When to use Fat or Smart Client.. 1

Status
Not open for further replies.

Tokhra

Programmer
Oct 1, 2003
134
ES
Hi all,

Im developing a customer relationship management suite as part of a commercial venture.

The application needs to be client/server, and so far i've been doing this using a centralised client/server database.

However, are fat clients on the way out? The only problem I have with smart clients is that they run on webservices right? therefore the user installing has to also setup the server / install the web service?

If so from a ease of use point of view (clients will be computer literate, and will not always have tech guys) it would be easier to install the software and delegate one to work as a server.

Id appreciate any views/comments on this,

Thanks,
Matt.
 
There's no easy way to categorize applications any more.

A fat client can be client-server or desktop-only.
Ex: Pivotal (a CRM package)

A thin client can be client-server or web-based.
Ex: some of the call-center apps

A web-client just needs a compliant browser on the desktop, but needs a more powerful server.
Ex: some of the bug-tracking tools (FogBugz)

An ASP is a business model where the end-users use a web-browser (stands for Application Service Provider), and the central servers supply horsepower for multiple customers.
Ex: Salesforce.com

A lot depends on what the usage pattern is for your app.

For casual or remote users, a web-based system is great, as they usually don't have a very rich client experience (the capabilities of HTML enforce this), so it's usually very simple and easy to use.

For users who spend a substantial amount of time in your app, a fat-client or thin-client would be the way to go. The difference is how rich an experience you want to provide. For example, if you want to provide charts, graphs, lots of analysis, then fat-client would be the way to go.

For end-users whose desktop PCs are locked-down by their IT departments, then often a web-based app (whether thin-client or ASP model) is the only way to get an app on their desktops, because they'll likely already have a web browser installed (which is why MSIE has such a large percentage of the browser market).

Yes, some styles are more more "fashionable" than others, but it comes down to how you anticipate the app being used, and selecting the appropriate deployment model.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first
 
Thanks chiph for clearing that up. I don't think my target users will have much IT skills, so my best bet is to go with a client/server fat client rather then a smart client.

Matt.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top