Convert Rev app to run inside browser

[Richard Gaskin]

On Jan 4, 2005, at 11:29 AM, RGould8 at aol.com wrote:

 > It all works great as a standalone app.   Now, unfortunately
 > my client wants a new app that does all these things, but
 > runs within a web-browser.

Why?

The only benefit to a browser implementation is ubiquity, but since you 
can only do something that unsecure if you use Microsoft tools on a 
Microsoft browser on Microsoft OSes the ubiquity benefit is gone (EIs 
marketshare is big but not 100% and in rapid decline -- viva le Firefox!).

There are many more benefits to deploying a 'Net-savvy standalone, not 
the least of which is that it can be done. :)

Other benefits range from lower development costs to higher end-user 
productivity through cleaner UIs:
<http://www.fourthworld.com/embassy/articles/netapps.html>

If it's for employees there's another big savings:  with no browser 
there's no constant distraction of having a million other web sites just 
a click away (employers lose billions annually to random on-the-job 
surfing).  Intranets are the silliest thing to put in a browser for any 
company smart enough to consider Rev.

Maybe a better question would be to ask the client:

   "How would you like your own AOL-like service
    for less than it costs to make a web site?"

But of course all this is meaningless without first answering the most 
important question:

   "Why must it be in a brower?"

Without knowing the reasons for the decision any proposal stands a good 
chance of not satisfying them.

But with that answer you may be able to demonstrate how all of those 
perceived benefits can be delivered, with many more, if they'll consider 
going beyond the browser.

--
  Richard Gaskin
  Fourth World Media Corporation
  __________________________________________________
  Rev tools and more: http://www.fourthworld.com/rev