Nokia Web Tools is a set of products that support mobile web application evelopment for Series 40 Nokia devices. The products provide for project creation, coding, debugging, previewing, and deployment of web apps supported by comprehensive help. These feature have been created with the goal for making development easier, more productive and, hopefully, fun.

This release of Web Tools incorporates a number of significant changes including the following

  • Support for version 1.5 of the webapp platform for Series 40 devices
  • Eclipse JSDT replaces Aptana components as web authoring enabler
  • New Simulator skins.with touch & type and non-touch profiles
  • Debugging support for web apps
  • Support for geography specific Data center
  • Improved code assist and validation during app authoring and packaging
  • Various Usability related enhancements such as new toolbar, better icons and labels
  • Clearer preview workflow in the form of local and cloud preview
  • Option for Developer feedback
  • Option for running Network Diagnostics
  • Support for Symbian Web Runtime has been deprecated. Earlier 1.2 release of the tools should be used if needed.

Installation and Update

Please note that Web Tools application must be installed using an account that has Administrator privilege.

Also the Web Tools should not be used from the Windows Guest account because of the amount of restrictions that account has. The user needs to have some minimal privileges like being able to read and write files from TEMP locations, and access network.Users should be using a Windows account that at least has the standard user account privileges.

  • The 1.5.0 release can be used both in China and Rest of the world.
  • This release is supported on Microsoft Windows 7, XP and Vista; Apple Mac OSX 10.6; and Linux Ubuntu 10.04 (32 bit). 64bit version of Ubuntu is not supported.
  • When installing, install with Administrator Rights. For Windows install as Administrator, for Mac install as Superuser. In Linux you must have sudo privileges during installation.
  • 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.
    • For WDE updates can be accessed from the Help menu by clicking Check for Updates.
    • For the Simulator updates can be accessed using the Update feature in Settings dialog.

NOTE: If you update Web Development Environment or Web App Simulator, it is recommended that you check for update in the complimentary product also. If the Web Developer Enrolment and Web App Simulator are not updated together you may encounter issues with compatibility and the tools may not function as expected.


For more complete details on using the Nokia Web Tools, please review the Getting Started Guide. Additional documentation can be accessed via the Web Developer Channel page in the WDE.

Tips, Tricks, and Known Issues


  • At this time Web app (WGT) size need to be kept below 500 KB in size. Else server preview may not work.
  • Web App short name in config.xml is now mandatory and must be less than 50 characters in total length and only UTF-8 characters
  • Moving from network to network may require restart of WDE and Simulator.

Web Developer Enviornment (WDE)

  • 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 at this time.
  • 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 explore, occasionally the icons may not reflect the state change right away.
  • It is strongly recommended that in the WDE Preference 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.

Web App Simulator (WAS)

  • WAS doesn’t provide pixel perfect rendering of web apps, exact rendering is available by running your web app on a device. Therefore final validation should be done on the device.
  • Adobe Flash Lite isn’t supported in Series 40 web apps. You can access additional information regarding Flash on Nokia devices here.
  • Using variables called "map" may cause the web app to render in correctly in WAS.
  • Currently MWL callbacks from WAS, during cloud preview, cannot be secured. So during app development and testing it is recommended thatsensitive data be not used for what would normally be a secure prompt from the remote server.
  • The WAS 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.
  • While doing local preview for a project, the Simulator is currently not able to leave out project resources that are marked for exclusion in WDE.
  • Currently scrollbars when visible in simulator will offset the viewable area by 4 pixels, vertically or horizontally. However, as long as the rendered content fits within the simulator viewable area, vertically or horizontally, without scrollbars showing, then there is no need to resize the content layout for fitting the supported device screen resolutions.

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.

Debugging with Web Tools

  • Web app debugging can be done by launching the debugger from the Simulator toolbar. It must be noted that debugging is most useful when done during local preview.

Feedback, Help and Discussion Groups