Page 2 of 3   « previous page   next page »

Q: What is the difference between AJAX platforms, frameworks, toolkits and libraries?
A. AJAX platforms, such as the Opera Platform or NetFront's Embedded Ajax, when installed on the device, make it easy to develop applications and widgets using standard Web technologies, including Ajax.

There is, however, a big difference between platforms on the one hand and frameworks, toolkits, or libraries on the other. While the latter are usually loaded along with the Web application into the browser each time, i.e., in the form of an external JavaScript file, platforms are typically installed once on the device and then loaded as required by the applications run on top of it. For example, Opera Platform widgets require the Opera Platform while Nokia Widgets require the S60 platform.

Q: What existing Mobile AJAX frameworks, toolkits, and libraries should I use?
A. Currently there are no specific Mobile AJAX frameworks, toolkits, or libraries.

qAll that is required for AJAX on mobile devices is support for:

• HTML
• JavaScript
• XHR - XMLHttpRequest
• DOM - Document Object Model or at least innerHTML support

Q: Can I use existing frameworks, libraries, and toolkits?
A. Some existing frameworks, libraries, and toolkits may indeed work on some mobile browsers. Generally however, these libraries require too much memory and implement features that may simply never be used on a mobile device (i.e., drag + drop). With increasing mobile browser capabilities, this will become less of an issue as browser vendors are already aiming to make their next-generation browsers work with these toolkits; however, the overhead is still there. It can be assumed that some of these frameworks will release mobile versions, so it's more a question of when will we begin to see mobile-specific browser support within these libraries and toolkits.

Q: What is the relationship between Mobile AJAX and Mobile Widgets?
A. In its entirety, AJAX is comprised of XMLHttpRequest + DOM Scripting + XHTML/CSS. Functionally, two things are happening here: data is being fetched asynchronously and the information thus fetched is being rendered on the client through JavaScript.

Most widget engines are using the asynchronous part uniformly but are making their own changes to the rendering (display) part. While this leads to fragmentation of widget technology, the fact still remains that AJAX, i.e., Asynchronous I/O and visual rendering, are the core technologies underpinning widgets.

When it comes to the mobile environment, we are seeing the same phenomenon, i.e., we see Mobile Widgets powered by Mobile AJAX and also some fragmentation. Also, it should be noted that we are seeing the first attempts at standardization of widgets from the HYPERLINK "http://www.w3.org/TR/widgets-reqs/" W3C.

Q: Which browsers support Mobile AJAX?
A. This is the list of currently known mobile browsers supporting AJAX, which means they feature the XMLHttpRequest or an equivalent ActiveX (as in the case for IE Mobile). Some of these browsers currently exist and are widely used; others are in development and are not yet available.

• Opera Mobile (>= 8.x, not Opera Mini)
• IE Mobile (WM 5.0/2003)
• S60 3rd ed. (WebKit/KHTML core)
• Minimo (Mozilla based)
• OpenWave (>=Mercury)
• NetFront (>=3.4)
• Safari Mobile (iPhone)

There are also other devices than phones that feature Web browsers to look at, for example, gaming consoles, such as the Nintendo DS and Wii or Sony's PSP or PlayStation 3. These devices - partly mobile, partly fixed - feature Web browsers (Opera for Nintendo, NetFront for Sony) that are comparable to those found on mobile devices such as cell phones. Some of these constrained browsers support AJAX (for instance, Opera browsers in Tranzas set top boxes). Another significant similarity is that these devices also feature very constrained input methods, sometimes less than on cell phones, e.g., four buttons and a four-way directional pad on the PSP.

Q: Which enterprise applications employ Mobile AJAX?
A. SoonR is one of the early pioneers of Mobile AJAX and seems to always be the preferred example. The SoonR application is primarily concerned with access to files on the desktop from a mobile device. It mainly supports Opera Mobile and S60 3rd edition for AJAX functionality, but there also is a basic version for other browsers without AJAX. Enterprise applications offer an opportunity for Mobile AJAX because they provide a rich browser-based experience on a mobile device and, at the same time, are not constrained by the need to access device APIs (for instance pPhone book APIs on a phone).

Q: What is the role of the Apple iPhone with respect to Mobile AJAX?
A. While this is speculative since enough details of the iPhone are not known, Apple has said that the iPhone will not include Java and may include Flash. It is very likely that the Web browser of the iPhone will support AJAX. If that happens, then widgets could play a major role on the iPhone with Mobile AJAX as one of their enabling technologies. If so, it would help the uptake of Mobile AJAX post launch of the iPhone.

How do applications like mojax or bling software fit in?

Mojax and Bling Software are examples of applications that use Mobile AJAX with Java as middleware. AJAX makes a great presentation layer, but isn't ideally suited for working with device-level APIs (Bluetooth, camera, XML, etc.) where technologies such as J2ME/BREW/C++ are already being used extensively. Thus, it is possible to use the combined strengths of each technology (J2ME + AJAX) to create the best experience possible.

While not leveraging open standards exclusively, these applications can very well make sense and they show that AJAX technology is a major building block in application development - either based on the Web browser or on a Java/C++ application.

In fact, Sun is taking a similar approach with its Java FX technology.

Page 2 of 3   « previous page   next page »