> I think it depends on the industry. The lest tech-savvy a customer is, the > less likely a client will want to deploy a solution to that customer that > requires downloading anything.
Perhaps. I've had pretty good experience showing clients a competitor's web app, then something like i-Tunes. They pretty much get it right away. Of course it depends on what you're trying to accomplish. If you have a complex application, you probably get much more bang for the buck using a standalone interface than a AJAX'd stuffed web app. If you've got a very simple idea/product, like BackPackIt, then AJAX works fine-- though I would suggest that 37 signals could benefit from a client version of BaseCamp. You can certainly create a much more *compelling* and media rich UI in a standalone app. Try doing Google Earth in AJAX. BTW, and [OT], is it just me, or do these different AJAX and Java enabled web apps tend to crash each other? _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
