Nokia Web Tools is a suite of developer products that support mobile web app development for Nokia Series 40 phones. These products enable the authoring, debugging, previewing, and deploying of web apps supported by comprehensive documentation. These products have been created with the goal of making development easier, more productive and hopefully fun.

This is the 2.0 release of Nokia Web Tools and it delivers the following enhancements:

  • Support for version 2.0 of the Series 40 web app runtime
  • Simulator support for Series 40 full touch phones (240x400 pixel displays)
  • Integration of features such as file upload, password manager, and download manager into web app simulation
  • Option for a developer to obtain launcher JAD/JAR files for his/her published Series 40 web apps
  • Enhanced validation for platform supported CSS, HTML and APIs
  • Enhanced templates to provide more design layout options during project creation
  • More samples web apps to help developers use of the platform capabilities easily
  • Templates, sample web apps and code snippets updated to follow the platform UI style guides
  • Preview screenshots for templates displayed during project creation
  • Unified update for both Web App Simulator (WAS) and Web Developer Environment (WDE)
  • Cursor based navigation within web apps for non-touch phones
  • Easier access to Bluetooth Launcher to simplify deployment of web apps to phone during development
  • Optimized project upload for cloud-based previews that avoids the uploading of unmodified content

Installation and update

  • Please note that Nokia Web Tools must be installed using an account that has administrator privileges. When installing, install with Administrator Rights. For Windows install as Administrator, for Mac install as Superuser and under Linux ensure you have sudo privileges during installation.
  • Nokia Web Tools should not be used from the Windows Guest account because of the restrictions that account has. To run Nokia Web Tools the user needs to have some minimum privileges, such as the ability to read and write files from TEMP locations, and access the network.Users should use a Windows account that at least has the standard user account privileges.
  • If upgrading from an earlier release, please restart WDE when prompted for doing so.
  • If you are running Nokia Web Tools on a Mac and your current 1.5 installation was created by updating 1.2 version of the tool then you may see errors related to the simulator update. If you see such errors it is recommended that you install the 2.0 version of the tool using the installer biinary.
  • The 2.0 release of the tool can be used both in China and rest of the world.
  • This release is supported on Microsoft Windows 7 and XP; Mac OSX 10.6; and Linux Ubuntu 10.04 (32 bit). The 64bit version of Ubuntu is not supported.
  • On Windows (English) non-English characters should be avoided in the installation path of the Nokia Web Tools, it is recommended that the default installation location is used.
  • Updates to Nokia Web Tools will be available from time to time.
    • Updates can be accessed from the WDE Help menu by clicking Check for Updates. Unlike previous version of the tool, separate updates of WDE and WAS are not necessary.

Tips, tricks, and known issues


  • Packaged web apps (*.wgt) need to be kept below 500 KB in size. Larger files may fail to preview on the server and not work on phones when published.
  • A web app's short name in config.xml is now mandatory, and must be less than 50 characters in length and use only UTF-8 characters
  • Moving among networks may require restart of WDE and WAS.
  • The application version attributein 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 part of the string.
  • When requesting jad/jar launcher files from WDC page, using email address, it is possible to get an error message due to the latency of the request involved. But the request is usually still successful. Please check your inbox for the email containing the launcher files before retrying again. It usually takes a few minutes for the email to show up.
  • During cloud previews of web apps, changes to config.xml are not always picked up by the server unless the version of the app previously uploaded 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 a new application and will pick up additional changes to the config.xml
  • 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)

  • Some of the Series 40 full touch phones may exhibit problems when deploying the Bluetooth launcher itself from the WDE. When this happens it is recommended that the launcher jad/jar be deployed on these phones 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 (including the file name itself) a *.wgt file should be avoided.
  • When proxy settings are needed for WDE on Ubuntu, and 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 dialog the "Auto activation triggers for JSDoc" settings under JavaScript->Editor->Content Assist is not touched. Changing this setting will impact the way code assist is currently performed during JavaScript editing. Once changed, currently there is no easy way to reset the behavior to its default state without reinstalling the product.
  • Minified JavaScript files in a project may result in errors and warnings being displayed the WDE console. It is 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 do 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 simulator 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 webpages 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 be 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 be hidden from the view.
  • Use of '#<name>' in anchor tags for in-app navigation does not work in the WAS even though it works fine in the 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 between applications back and forth.
  • 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