Monitoring and Testing for Mobile

Keynote and Mobile Complete
Lots of people are building mobile games, content and services. Billions of dollars are being made. Billions of subscribers with lots of devices are getting information and being entertained. But why is the mobile industry still struggling to gain even further momentum? Last October, when I spoke on at the Mobile Content Partnership Summit, Nanea Reeves, COO Online Solutions at Electronic Arts, was on the same panel and stated that not much has changed since about 2000 when downloading a game was a rather unengaging experience. In comparison to the Internet shopping experience, mobile still lags far behind. According to one analyst firm: “With approximately two thousand handset models currently operating in the global marketplace according to In-Stat Principal Analyst Allen Nogee, consumers have more options than ever to find the right model that suits their lifestyle.” 2000 choices of handsets! While I think there are several PCs out there to choose from, there are only a handful of browsers needed to surf most sites, but realistically, it’s two browsers to build for: Microsoft Internet Explorer and Mozilla Firefox. This means that a developer only really needs to test across two applications. With mobile, it’s at least 5 (BREW, Java, Palm, Symbian, Windows Mobile) or more. This makes it extremely difficult to please everyone and create some ubiquity.So what is a developer to do? There are quite a few options out there for mobile developers, but two standout products, Mobile Complete’s Device Anywhere and Keynote’s Mobile Device Perspective are ones examine. Both provide virtualization of a real handset that the developer can control from their PC. Both allow you near unlimited access to the device to test your application or service on almost any device, any network, any location. You can navigate through the menus and feel like you are using the device from your PC. The integration of the handset is all encompassing, one can see exactly what is being displayed on the LCD, push buttons, simulate turning the device on and off, as well as pulling the battery out. Furthermore, scripting can be added for functional testing and screenshots can be captured for collaboration to fix problems or errors.

One use case that software companies have adopted is off-shore technical development. For example, a development team in the US develops a game and hands over their QA and Support to an off-shore team in, say China. Sounds like one would just send the code over, have the Chinese team download and install it on their local device and start manually testing. While this sounds not so bad at first, imagine have dozens if not hundreds of devices, and dozens if not hundreds of titles to test. This doesn’t seem to be a cost-effective and scaleable problem. Added to the difficulty is the fact that some of the applications and services are dependent on the carrier network, which is not local and available in China. Why not access a bank of handsets that the team in China can access and virtualize on their PCs and test remotely?

This would allow greater scaleability, effective use of resources, and allow more global companies the ability to develop and test from anywhere to anywhere. As an added effect, monitoring from locations on devices for things like messaging, content downloading and mobile services could be enabled to measure performance and availability. Any IT manager, who manages an e-commerce website, such as Amazon.com or Buy.com understands that for each minute the site is unavailable, the calculated loss of revenue is a significant impact on revenue, reputation, and overall customer satisfaction. The same translation would apply to mobile commerce of downloading ringtones, games, or access services such as Gmail or Yahoo Mobile Instant Messenger. The increase dependence of mobile phones and all the services that are brought to the device will need both thorough testing and monitoring if critical mass is to be achieved when growing this channel. Subscribers have already begun to expect high availability and fast results, not to mention rather seemless compatibility across networks and devices.

So where are we in 2006 when it comes to mobile monitoring and testing? Well, unfortunately, I believe that we are just at the beginning of the web when lots of companies were just happy that sites were up, accessible and traffic was surfing their respective sites. But we are quickly expecting more as competition increases and subscriber demands become greater. The alternatives of using emulator to simulate applications will not be enough to truly grab the subscriber experience that delivers that “last mile” or 100% accuracy that developers strive for. From the looks of both Mobile Complete and Keynote, both are growing their customer based both from mobile operators, content developers and portals. Hope this bodes well for the mobile industry, it certainly cannot afford to stumble on the billions of dollars and billions of subscribers all making their mobile device one of the most important thing they carry on their person.


Related Posts:
  1. Mobile Web [and Software] Performance...

  2. In Flight Mobile Services Revisited...

  3. Integrating Religion and Mobile...

  4. Large Mobile Devices: Your Car...

  5. Sprint MBA – Consulting for Mobile...

Comments are closed.

blog comments powered by Disqus
google.load("language", "1"); var curstate = 0; var hasloaded = 0; function bnc_show_translated() { if (hasloaded == 0) { bnc_lang_callback(); hasloaded = 1; } for (i = 0; i < 0; i++) { var elem = $("bnc_original_" + i); if (elem) { if (curstate) { elem.show(); } else { elem.hide(); } } } for (i = 0; i < 0; i++) { var elem = $("bnc_trans_" + i); if (elem) { if (curstate) { elem.hide(); } else { elem.show(); } } } if (curstate) { $("bnc_trans_state1").show(); $("bnc_trans_state2").hide(); curstate = 0; } else { $("bnc_trans_state1").hide(); $("bnc_trans_state2").show(); curstate = 1; } } function bnc_detect_div(div_id) { var text = document.getElementById(div_id); if (text) { text = text.innerHTML; if (text.length > 0) { google.language.detect(text, function(result) { if (!result.error) { if (result.language != "en") { if (result.confidence > 0.25) { $("bnc_translating").show(); bnc_xlate_div(result.language, div_id, "en"); } } } } ); } } } function bnc_xlate_div(src_lang,div_id,o_lang) { var text = document.getElementById(div_id); if (text) { text = text.innerHTML; google.language.translate(text, src_lang, o_lang, function(result) { var translated = document.getElementById(div_id); if (result.translation) { translated.innerHTML = result.translation; } }); } } function bnc_lang_callback() { } function bnc_startup() { bnc_xlate_div("en", "bnc_translate_info", "en"); bnc_xlate_div("en", "bnc_translate_info2", "en"); } google.setOnLoadCallback(bnc_startup);