Originally posted by Frank Carver:
We really do need to know a little more about what this application will do before helping with a decision like this.
Some applications are naturally more suited to a web interface (sequential form filling, or simple report generation, for example), whereas others are much more suited to a desktop style (device control, interactive graphics, etc.)
The number and location of users is often only a minor part of the decision process.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by rathi ji:
As I told, it will be used at four different locations. The number of users will be four at max untill the company does't open a new branch. No device control or system or graphics programming is needed.
Is it sufficient information to come up with any answer...
Originally posted by Frank Carver:
Not really.
You still haven't really told us anything about what your application will do, and how the users will expect to use it. There are so many variables that affect this decision, and so many compromise solutions (from things like a desktop application that sends HTTP to a server, through to a "web" application with a complex Applet, Flash or JavaScript user interface sitting in a page).
Honestly, the more you can tell us about your application, what it should do, and how it will be used, the more likely we are to be able to help.
There is no simple answer. This is one of the reasons why consultant analysts are often paid so much money!
Originally posted by Ernest Friedman-Hill:
Write down some use cases (stories or diagrams about what the system will do and how people will interact with it.) Look at each one, and think about how it would be implemented. If all the use cases you can come up with would work easily in a Web application environment, then generally that's what I'd want to do, for the zero-deployment/ease-of-maintenence angle.
If, on the other hand, you come up with use cases that sound hard to implement as a Web application, then you need to consider a desktop app. Even in this case, consider how much of the app could (or must) be a server application of which the desktop app is a client.