Home > Articles > Networking > Wireless/High Speed/Optical

Nokia Mobile Internet Toolkit 3.1

  • Print
  • + Share This
Bryan Morgan discusses how the release of Nokia's Mobile Internet Toolkit 3.1 provides WAP and MMS application developers with an integrated development environment in order to build the next generation of wireless applications. It allows developers to remain a step ahead of the general market by being able to build and test tomorrow's features — such as MMS, WTAI, and XHTML — today.
Like this article? We recommend

Mobile Internet developers interested in taking advantage of new technologies such as WAP 2.0 or MMS (Multimedia Messaging Service) are often faced with a conundrum: How do I build my application to take advantage of new phones to be released next year... without the new phones that will be released next year? Developing and testing new wireless applications over-the-air with a mobile handset certainly eliminates any last-minute browser "gotchas," but it is an extremely tedious and inefficient way to develop an application. To solve this problem, Nokia introduced a development tool—the Nokia Mobile Internet Toolkit—that includes source code editors and device emulators that allow an application developer to build a state-of-the-art application without ever handling an actual device.

A Look at the Toolkit

The latest version of Nokia's Mobile Internet Toolkit, version 3.1, can be downloaded for free after you register at the Forum Nokia site. As can be seen in Figure 1, it offers an intuitive IDE with code viewer/editor and configuration tabs that display current emulation configuration and browser settings.

Figure 1Figure 1 Nokia Mobile Internet Toolkit IDE.

To give you an idea of the level of configuration supported, see Figure 2.

The dialog box shown in Figure 2 allows the developer to fine-tune the behavior of the selected emulator. This includes the actual size of the display in pixels, connection mode, cache, WTAI configurations settings, positioning method (GPS or GSM), and the device's User-Agent variable (often examined on the server side in order to generate device-specific content).

Figure 2Figure 2 Configuring the emulator "device" settings.

  • + Share This
  • 🔖 Save To Your Account