|Think about Loose Coupling|
web-based application or desktop application?by pg (Canon)
|on Dec 04, 2003 at 04:19 UTC||Need Help??|
I have wanted this discussion for a long time.
There seems to be a trend going on nowadays, to make some of the internal enterprise applications web-based, and to get away from the traditional desktop application.
I and another guy recently completed the system design of an application. The system design is desktop based, but the direction shifted to web-based application in the second half of the design phase. This is not ideal, but it is still fine, as system design phase mainly focuses on functional module design, database design and capturing business requirements from a more technical view. We tried to tell what to do, not (really) how to do it.
Now we are implementing it, and implementing it as a web-based application.
The application has four main functional modules, and we started the implementation of one of them one month ago.
Today, some of us, started to see a warning sign. The server side implementation has been quickly completed, but the client side coding is still going on, and will require serveral more weeks. This means that we are not focusing on the business logic, instead lots of time have been spent on rendering those web pages. We started to question ourselves, whether it is the right decision to make it a web-application.
Serveral facts here:
At this moment, the biggest benefit everyone agrees, is that web-application does not require client side deployment.
What is your thought? Do you have a successful story or failure to share?