Web-Based or Windows App?

[Antony]

Excuse my ignorance, but anyone have any links to some good white papers
discussing the pros/cons for developing a Web-Based app versus a
windows/client/server app?

I would think this topic has been largely discussed many times over and I
don't need to start another discussion, just some reference to some existing
materials. I've been searching for hours and I must be having brain problems
as I'm not coming up with much with the keywords I'm using (e.g. "web vs.
windows", "web-based or windows", etc.).

Thanks in advance.

Antony

 

[clintonG]

Google: "smart client" while your at it.


<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

 

[Radek Cerny]

Here's a whitepaper that describes how to build systems that deploy as Web
Services, thus accessible by Winforms Apps and Browsers (using
javascript/dhtml), and PDAs etc.

http://members.optushome.com.au/rcerny/GenieWhitePaper.pdf

 

[Antony]

Interesting paper... I'll spend sometime studying it. Thanks.
Antony

 

[Radek Cerny]

They way you used the term client/server I figured you were a reasonably
mature and experinced developer, and was grappling with the problem you
posed. The easy answer is that for simple apps, you use a web app, and for
anything more than trivial, that browser forms are just not good enough.
You really need field-at-a-time processing with multiple open windows with
tabs, and fast response times else the users get very very frustrated. Web
forms wont do; unless they are simply an optional 'portal' into the same
system deployed as Rich Windows forms. Now that the world has come up with
a common RPC protocol (Web Services), we had better use it.

Just noticed you're an Aussie. If you are interested in seeing this in
action, register at www.professortrim.com.au, and download the rich client.
The same functionality will be avilable thru a browser at that site, and
also through the rich client (although you wont get much unless you pay$ -
but enough to demonstrate the point).

Radek

 

[Antony]

Thanks for the tips. I have a client who's wrestling with this decision, and
I was looking for some resources to help them make a decision rather than
them just relying on my advice.

I tend to agree with your thoughts below, but love the deployment advantage
of web-based apps.

 

[Radek Cerny]

but love the deployment advantage of web-based apps.

Very true, but having the ability to do both with zero server changes is
extremely compelling. I find the biggest issue is that Windows XP SP2 did
NOT include the DotNet framework, even as an option, and that if it were on
ALL Windows PCs, downloading and installing a rich thin client is not a
problem.

Radek

 

[Antony]

Agree - I've often wondered how the developer community as a whole accepted
the fact that the .NET framework has to be distributed with any app...

Then again, maybe the majority of .NET development is done on a corporate
level where the end users are accessible through the company's own network.