The frenzy of activity around development of so-called “rich Internet applications” has largely ignored use of the web on mobile devices—primarily because browsers in mobile devices have historically lacked the support needed for enabling use of such applications.

However, a new generation of mobile browsers is now available: so-called “full browsers” for mobile devices that are Javascript-enabled and CSS-aware. In fact, browsers that have support for the Javascript XMLHTTPRequest object and thus are capable of the same kind “AJAX” asyncronous behavior that most Web 2.0 applications designed for PC-based viewing make use of.

That said, there are some fundamental differences between the typical user interface found on mobile devices and that found on PCs.

• screen size – mobile devices have a small screen and thus no “windowing”—one application at a time “owns” or controls the entire screen; PC devices have large screens, multiple windows
• input devices – mobile devices have no mouse and thus no drag-and-drop. they also have a number-pad for input insted of a full keyboard

This paper discusses specifics of building rich Internet applications within the bounds of those fundamental contraints. It also discusses differences in application “types” that are used most frequently on the mobile web and how developer need to change their development focus to meet address those uses. (For example, mobile-web application use is acutely service-driven.)

Finally, it presents specific details about some third-party development programs/platforms that browser vendors have created to encourage third-party developers to build applications around their browsers.