Subscribe via RSS
Select Language

Using AJAX to improve your mobile website

BlackBerry Development Advisor

There are several methods to enhance user experience using advanced web development strategies on your mobile website.  One of the more popular methods for enhancing mobile websites would be the use of AJAX (asynchronous JavaScript and XML). Grabbing data from outside of your webpage to update it in real time is a great way to give your website a “web 2.0” look and feel. Typically, using AJAX and more specifically XMLHTTPRequest is the best way to do this.
 
Here’s a short snippet of code for using the XMLHTTPRequest:
 

var request = new XMLHttpRequest();request.open('GET', ‘mydata.html', true);request.onreadystatechange = function (event) { if (request.readyState == 4) { alert(request.responseText); }};request.send(null);

 

Setting the ‘onreadystatechange’ value of the object makes this request asynchronous, so your webpage will not be blocked waiting for the response to come back.

XMLHTTPRequest is fully supported by the BlackBerry® Browser as of BlackBerry Device Software v4.6, and is something that can open a lot of doors to developers.  When using XHR, it’s very important to use it wisely.  While it does enable web developers to create stunning UI’s and a terrific user experience, and possibly even build an entire web application using it, there are a couple of properties to be aware of.

You’ll need to keep in mind when using the XMLHTTPRequest object that the BlackBerry® Mobile Data System™ (BlackBerry MDS™) does not transcode any of the data when using your XHR object.  Usually, when making a request that goes through the BlackBerry MDS, the HTML, CSS and JavaScript™ are transcoded. Specifically, JavaScript is precompiled on the BlackBerry MDS which is a significant performance enhancement.  When using XHR objects, you’ll lose those performance enhancements since none of the BlackBerry MDS transcoding takes place.

However, it is important to note that it is not XHR which is slow, but it is the compilation of JavaScript which is the bottleneck in the process.  As the BlackBerry Browser continues to improve and evolve, it will allow for more speed and efficiency throughout the process, and I think this method will become more commonplace.

A terrific example of how a web application or website can be enhanced through the use of AJAX is the MLB Gameday web application.  It uses AJAX to update the screens in virtually real time to display updates to the user.

If used properly, AJAX is a fantastic way to improve the look of your website, and will provide a unique experience for your users. 


Comments
by (anon) on 09-02-2009 12:21 PM
what if the user has javascript disabled or the device does not support it? I seen plenty of sites that rely on ajax and are rendered useless when the javascript is disabled. Even the mlb example fails to properly acommodate users with javascript disabled
by Nick D(anon) on 09-02-2009 01:46 PM

Great tip about the XHR/MDS transcoding issue Prosanta. Thanks. I'm sure simple things like minifying the XHR response would help with performance too.

 

In my opinion, the best use of AJAX on a made-for-BlackBerry site is via a few sparing widgets. Too much AJAX can cause a lot of "hidden" network traffic which can drain the battery perhaps more than the user might be expecting.

 

But then I'm a proponent of the "less is more" philosophy in my UI designs anyway :smileyhappy:.

by on 10-24-2009 12:00 PM

It's not the setting of the onreadystatechange that makes the XHR request asynchronous. It's the "true" that you're passing in as the third argument to the open method. See http://www.w3.org/TR/XMLHttpRequest/

Post a Comment
Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
About BlackBerry Developer's Blog
The Developer Relations team at RIM is focused upon providing solutions for all stages of the BlackBerry development lifecycle. The Developer’s Blog is a forum to share best practices, market insight and developer-engagement opportunities with the development community. The Developer’s Blog complements our existing outreach programs (BlackBerry Developer Conference and Developer Newsletter) while giving us an opportunity to share our personalities too!

About the Author
  • Adam is a product manager at RIM in the platform product management team. Adam’s focus and responsibility is on setting the strategy and direction of the BlackBerry web platform, including the web developer tooling products. He is also responsible for RIM’s involvement with the Eclipse Foundation and the Pulsar project. Adam hopes this blog will allow him to share his knowledge, viewpoint and passion for BlackBerry, but is really interested in what capabilities the community feels should be added to the web platform and tooling to create even more compelling web applications and content.
  • Adam is an Application Development Consultant with the Developer Relations Team at RIM. As a member of the Developer Relations Team, Adam manages the technical relationship with ISVs who specialize in producing applications based on web technologies. Adam's development background consists of a degree in Computer Science and work in web development for both the insurance and technical support industries.
  • I joined Research In Motion in 2005 working with Independent Software Vendors (ISVs) who specialize in Bluetooth, GPS, multimedia, and gaming. As a senior member of the Developer Relations Team it's my mandate to not only support the application development efforts for a number of ISVs, but it's also to act as a voice at RIM for third party application developers. Like RIM, my roots are in the enterprise world, but over the past couple of years I've quickly adapted to the consumer space, and that's where I spend most of my time today.
  • Chris has been at RIM since 2001 and runs R&D for the BlackBerry Development Platform. Practically speaking, this means day-to-day he is busy harnassing the innovative power of a talented group of RIM engineers to serve the needs of the BlackBerry Developer community.
  • Denver is a software developer at RIM, working on the BlackBerry Java APIs. Denver has been working at RIM for 4 years and started in automated testing of the APIs, making the switch to development in 2008. He enjoys programming, and finds developing for BlackBerry especially interesting. Denver also enjoys writing and sharing his development experiences, and hopes his posts will be useful and informative to other developers out there.
  • With more than a half-decade of experience in the wireless industry, Douglas “tr0n” Soltys has chronicled the evolution of mobile culture in both the consumer and enterprise space. Prior to joining RIM, Douglas manned the helm of wireless weblogs QuicklyBored and BlackBerry Cool. When not blogging about all things BlackBerry®, Douglas can be found extolling the virtues of Strunk and White. He uses a BlackBerry® Bold™.
  • As Manager, Developer Programs at Research In Motion (RIM), Ian and his team are responsible for the design and delivery of programs and services for BlackBerry developers – including support tools and resources, recognition, advocacy, go-to-market, and regional programs. Ian is passionate about making sure that BlackBerry developers have everything they need in order to be successful from the inception of an idea to app deployment or commercialization. Prior to joining Developer Relations, Ian was a Product Manager for various BlackBerry solutions including the BlackBerry Java Development Environment, BlackBerry Maps, and BlackBerry Mobile Voice System.
  • Kamen is a Senior Architect, Strategic Initiatives, and started at RIM in 2001 with already established expertise in development for the BlackBerry platform and other mobile devices. Since then Kamen has been part of both device and server-side design and development activities - helping to evolve the BlackBerry development environment. As part of the Strategic Initiatives group he is now involved in looking for new ways to bring additional value to third party developers.
  • Mike Kirkup is the Director for the Developer Relations program at Research In Motion (RIM), which is responsible for managing the technical relationships and programs for RIM’s developer community worldwide. Mike and his team work with RIM’s developer community to provide support and guidance as developers work to integrate their applications to the BlackBerry platform. Mike joined RIM in 2001 as a Security Software Developer in RIM’s Wireless Security Group. As part of the Wireless Securty group, Mike contributed to the development of the BlackBerry Cryptography API, S/MIME and PGP implementations. Mike holds a Masters of Management Science and a Bachelor of Mathematics from the University of Waterloo.
  • When he’s not out riding the waves off the sunny eastern coast of Australia, you’re likely to find Neil at his desk answering emails, taking calls, or cutting code in his role of Application Developer Consultant for RIM. As a member of the Developer Relations team Neil spends a great deal of time working with Independent Software Vendors (ISVs) in Australia and New Zealand helping them get the most out of the BlackBerry platform, and also working behind the scenes to ensure everything is “most excellent” for all developers. Neil’s been developing for the BlackBerry for five years and prior to joining RIM ran a successful BlackBerry software company. He also likes hats.
  • Prosanta is a member of the BlackBerry Developer Relations team specializing in Web Development. Prosanta’s focus is on developing out the web platform and tools associated with web development while supporting the development efforts of a number of Independent Software Vendors. Prior to joining RIM, Prosanta had worked on numerous web portals for major multinational firms writing both front and backend code.
  • Tim is the Development Manager for BlackBerry development tooling. This includes Java, Web and also Theme creation tools. He is always hanging out in the development forums trying to help out where he can and to bring your feedback into the next releases of BlackBerry tooling. You’ll also see Tim presenting various topics at the BlackBerry Developer Conference and Wireless Enterprise Symposium so be sure to stop by and say hi. Just don’t start talking about cars or Batman or you won’t be able to get rid of him.
  • I work on the Developer Relations team at RIM, with a focus on enterprise applications for Sales Force Automation, Health Care, Public Safety and Real Estate. I started on the team at the beginning of 2007.
Categories