Moving to Mobile

The increasing popularity of wireless mobile devices is prompting organizations to examine when and how they’re going to make the transition to a wireless format for their Web applications. This batch of reports from popular Giga analyst Carl Zetie examines this transition from a variety of angles. He sets out to answer several questions, and comes up with some thought-provoking responses. With future developments leading down the WAP path, does this mean that existing applications written with present Web technologies (HTML, Java etc.) will have to be completely rewritten? Presently (or in the near future), what are the methods for porting existing applications to a WAP platform? What are the dangers to WAP adopters in the Phone.com vs. Geoworks lawsuit? How can WAP adopters protect themselves? What are the possible approaches to integrating mobile clients with enterprise architectures? Is it possible to provide a single Web site for both mobile and desktop browsers? Can they both connect to the same URL? Even if it is possible, is it a reasonable idea to try to use the same content for both, or must the content be custom designed? What is IBM Transcoding Publisher, and how does it differ from other translation products?