Just wanted to put what I thought down on paper (so to speak). I figure it would help trying to sort it out. The typical answer 5 years ago would have been a web application allows for quick deployment, avoids the dll hell but would have limited interface capability. Not sure any of this still applies.
On the client side, you can use java web start or the .NET equivalent. They can be downloaded and kept updated every time you launch it.
I suppose Applets, Silverlight and Adobe Flash take it to another level but you sill need to have a runtime engine installed. At least it would not change as often, the code gets updated on the fly and cached I believe if you do not need to change it. The size of the runtime is important, but I suppose not essential for me to figure out some more.
The web applications those days are fantastic, to the point where desktop applications try to look more like them. The boundaries are constantly being pushed. I am still amazed we can have a work processor and a spreadsheet with just html code (and JavaScript of course). Not always up to par but getting closer and closer. Not sure where Flash and Silverlight fit in, they can of course interact with the web pages. But they are not necessarilly part of the page. I am on the fence here as to where they belong. If they serve the page as opposed to be the page, I would be tempted to make part of the web technology.
However I have come across a few screens that I don’t believe would be possible in a web page. I am not one of those who think web applications are not user friendly, although I have found quite a few of those. The choice, as always, is it depends. What the requirements are should be the main driver. For complex screens, use Flash, and applet or Silverlight (no preference really). I think it should be the preferred solution and should only be rejected if notthing else can be done about it.
One of the greatest benefit I can see all applications benefited from the merge of those options is a greater freedom for designing the interface. We are not longer bound by what Microsoft thinks it should look like (the visual basic look I like to call it) or the not so good java look and feel. Every product should have a graphic designer, no matter how small the product.
No comments:
Post a Comment