Nokia Asha Web App Tools is a suite of developer products that support the development of web apps for Nokia Asha software platform 1.0 and Series 40 devices. These products provide features for the authoring, debugging, previewing, and deploying of web apps supported by comprehensive documentation. The goal of the tools is to make web app development easier, more productive, and hopefully fun.

This is the 3.0 release of Nokia Asha Web App Tools and it delivers the following enhancements:

  • Nokia Asha Web App Tools support for Web App Runtime 3.0.
  • Extended USB deployment support for Nokia Asha software platform 1.0 devices.
  • Simulator support for Nokia Asha software platform 1.0 devices.
  • New simulator skin with a hardware back button for Nokia Asha software platform 1.0 devices.
  • New HTML attributes "accept" and "capture" with the supported values "image/*", "video/*" and "camera" respectively.
  • New "MediaCaptureSample" to support the Camera API.
  • New "BackKeySample" to demonstrate "mwl.addNavBackListener" events.
  • HW back button support in Multi-view project, RSS feed project, Accordion UI project and News projects.
  • Performance optimization in "News project" template and "NewsReader" sample with lazy loading.

Installation and update

  • Please note that Nokia Asha Web App Tools must be installed using an account that has administrator privileges. When installing, install with Administrator Rights. For Microsoft Windows install as Administrator, for Apple Mac install as Superuser, and under Linux ensure you have sudo privileges during installation.
  • Nokia Asha Web App Tools should not be used from the Microsoft Windows Guest account because of the restrictions that account has. To run Nokia Asha Web App Tools the user needs to have some privileges, such as the ability to read and write files from TEMP locations and access the network. Users should use a Windows account that has the standard user account privileges at least.
  • If upgrading from an earlier release, please restart WDE when prompted to do so.
  • The 3.0 release of the tools can be used both in China and the rest of the world. However, developers in China should note that some of the web app templates use websites or API service providers that are not accessible in China. In these cases the website URL or API provider will need to be changed. Details on how to do this are provided in the description of the relevant templates. The templates effected are:
    • Shopping video and music project.
    • Blogging project.
    • Videos browsing project.
    • Photo Browsing project.
  • This release is supported on Microsoft Windows 7 and XP, Apple Mac OSX 10.6, and Linux Ubuntu 10.04 (32-bit). The 64-bit version of Ubuntu is not supported.
  • On Windows (English) non-English characters should be avoided in the installation path of Nokia Asha Web App Tools, it's recommended that the default installation location is used.
  • Updates to Nokia Asha Web App Tools will be available from time to time. Updates can be accessed from the WDE Help menu by clicking Check for Updates. Updates will install new WDE and WAS features as necessary.

Tips, tricks, and known issues


  • Packaged web apps (*.wgt) need to be kept under 500 KB in size. Larger files may fail to preview on the server and not work on phones when published.
  • A web app short name in config.xml is now mandatory. It must be less than 50 characters in length and use only UTF-8 characters.
  • Moving among networks may require a restart of WDE and WAS.
  • The application version attribute in the widget element of config.xml is mandatory and must be formatted as x[x].x[x][.x[x]], where the value of x can range from 0 to 9. The default value inserted by the tool during project creation is 1.0.0. In the above [] indicates optional parts of the string.
  • When requesting the apps' JAD and JAR launcher files from the Web Developer Channel (WDC) page, using an email address, an error message may be displayed due to the latency of the request. However the request is usually successful. Please check your inbox for the email containing the launcher files before retrying. It usually takes a few minutes for the email to arrive.
  • During cloud previews of web apps, changes to config.xml are not always picked up by the server, unless the version of the previous upload has expired. However, if the short attribute in the name element or the version attribute of the widget elements are changed, then the server treats the application as new application and will pick up additional changes to the config.xml file.
  • On-screen keyboard may not launch on some Microsoft Windows 7 Professional 64-bit machines. A hotfix from Microsoft can be downloaded from here.

Web Developer Environment (WDE)

  • Bluetooth deployment of web app is not supported on Nokia Asha software platform 1.0 devices.
  • Web app runtime version 3.0 is not supported on Series 40 devices.
  • Default HTML validation throws warnings for “input” element when “accept” and “capture” attributes are used [MediaCaptureSample]. You can avoid this by disabling “HTML Syntax Validator” in the Window > Preferences > Validation page.
  • Some of the Series 40 full touch phones may exhibit problems when the Bluetooth Launcher is installed from the WDE. When this happens it's recommended that the launcher JAD and JAR file are installed by copying them using a USB connection. The Bluetooth Launcher files can be found here.
  • Where proxy servers are needed, a HTTPS proxy, in addition to HTTP proxy, must be set for short URL generation to work.
  • Non-English characters in project paths, project file names, and in paths to a *.wgt file and the file name itself should be avoided.
  • When proxy settings are needed for WDE on Ubuntu, Mac manual proxy settings should be used in the WDE preference dialogue.
  • When projects are opened and closed in Project Explorer, occasionally the icons may not reflect the state change immediately.
  • It is strongly recommended that in the WDE Preferences settings dialogue the "Auto activation triggers for JSDoc" settings under JavaScript->Editor->Content Assist are not changed. Changing this setting will impact the way code assist is currently performed during JavaScript editing. Once changed, the only way to reset the behaviour is reinstalling the Nokia Asha Web App Tools.
  • Minified JavaScript files in a project may result in errors and warnings being displayed in the WDE console. It's, however, possible to preview and deliver projects containing minified code.

Web App Simulator (WAS)

  • WAS doesn't provide pixel perfect rendering of web apps. Font and image display differences may exist between the simulated preview and the phones. Exact rendering is available by running your web app on a phone. Therefore final validation before publishing the web app should be done on the phone.
  • Long text lines that wrap may render the web app layout differently in the simulator and on a phone.
  • Preview of WML content is not supported in the WAS.
  • While visiting website links that perform multiple redirections on the request, it is possible to get blank pages at times. Usually reloading the link by going back and forth can make the link work.
  • During cloud preview, leaving a web app displayed in WAS for an extended period of time may result in the application generating a page expired message on refresh. Lack of activity for five minutes or more can cause the application session to expire.
  • Adobe Flash isn't supported in Series 40 web apps. Therefore web pages containing flash content cannot be reliably rendered in the WAS.
  • Currently MWL callbacks from WAS, during cloud preview, cannot be secured. So during app development and testing it is recommended that sensitive data is not used for situations that would normally involve a secure prompt from the remote server.
  • While previewing projects in the Mac environment the WAS can sometimes go to the background and as a result is hidden from view.
  • Use of '#<name>' in anchor tags for in-app navigation doesn't work in the WAS, even though it works as expected on phones.

Web App Debugging

  • Web app debugging is done by launching the debugger from the WAS toolbar. It should be noted that debugging is most useful when done during local preview.
  • The debugger can lose breakpoints in Mac and Linux environments when modified files are reloaded in an app being debugged, or the user switches back and forth between applications.
  • In Mac environments the scrollbars on the Simulator debugger window may not be visible. The content can be scrolled by dragging.

Web Developer Channel (WDC)

  • There may be instances where new or updated Add-on's may not show up in the WDC. Relaunching the WDC will refresh the content.

Feedback, discussion groups, and help


  • Please provide feedback or ask questions through the feedback link in the WDC or by using the Series 40 Web Apps discussion board.
  • Bugs or suggestions can be submitted here. We look forward to hearing from you.