« driving me to drink | Main | art by prisoners »
July 21, 2006
driving me to drink part two
Okay. We have been working with a particular vendor for many years. Up until a year ago, their software was a desktop client that had to be installed. They now have a web version. However, since we didn't have anything new to throw their way recently, we hadn't really paid attention to the web version. Especially since it's just not worth our time converting current projects to it as these projects only have a limited timeframe, data migration from one database format (interbase) to another (Oracle) would be a nightmare, etc. Well, we now have a new project that we want to consider to use the web version. We had a demo of it last week.
I was actually just asked the following by someone: "Hey, why did they bother changing from a desktop application to a web version? What is their business reason for doing so?"
*blink*
Because it's freakin' 2006? Because it's a pain in the a** to install software at 300 sites? Because their other clients and we have been asking for a web version for years? Because it's flexible and will allow our sites with Macs to use it and we won't have to procure Windoze equipment for them? Etc.
Note: I'm not saying all software has to be web based. Duh. This type of software has no reason _not_ to be web based.
Jeebus.
Posted by jennj at July 21, 2006 12:21 PM
Clue-ments:
these days
there are very few applications i can think of
outside of your MS Office type software
that has no reason to be web-i-tized.
what i'd love to see,
however,
is a system like a browser
which could be used to create
web based like applications
without actually using a clunky old browser.
browsers are designed to load websites,
not software.
can we create something lighter and faster
that could run web software better?
that might really change things.
Posted by: jhimm at July 22, 2006 12:03 PM
jhimm - That would be cool. And easily accessible.
Posted by: cf at July 22, 2006 12:56 PM