Simulators and emulators help with design, development, testing and demonstration of software, when the actual environment is unavailable or unsuitable for testing. These are particularly applicable for mobile devices, as hardware is not always even out, service contracts and the number of devices to test make them very expensive, and it can be slow and cumbersome to load for each incremental code change.

Though often incorrectly used as such, they are not interchangeable terms, however.

• A simulator is software appearing on a computer that acts like the target environment, but is technical dissimilar in some key aspect, and maybe all of them. The simulator will superficially behave like the actual device, but is driven by different code entirely.
• An emulator runs the actual code, just within a virtual machine which itself simulates the hardware environment. From a technical perspective you can have much more confidence in the fidelity of the experience. Emulator problems arise from the virtual machine, which may have bugs (or the lack of them) which vary from the actual device. Often, the developer is allowed to select the available memory or processor or network speed, which is useful for unit test, but must be toned down for realistic testing or demonstrations later.

New ones are constantly being added, or replaced, so please help us keep this up to date. Visit the wiki at www.4ourth.com/wiki or contact us with updates you may encounter.

A good place to start is with MobiForge, who has published a useful guide to actually getting over a dozen emulators to run. Many of these are buried under their developer sites, so you may not have even found them. Most have some trick or other to get running, especially if you are not steeped in technical minutiae.

• http://mobiforge.com/testing/story/a-guide-mobile-emulators

Web-Based

• dotMobi Online Emulator - Web simulator (despite the name) with focus on common phones. Run by YoSpace.

• Opera Mini Simulator - Opera's J2ME browser.

• Bolt Browser Simulator - Intended to sell the product, but useful to check how things might work on a small-screen, scroll-and-select browser.

• Device Anywhere - Actually another class entirely, a remote virtualization system. Actual hardware is disassembled, things are soldered to it, and it's strapped to cabinets. You get to press buttons and it goes over a real network, and gives you the screen output. Free trials available with some developer programs, otherwise a fee service. Be careful, as they charge per minute connected, not per click or anything; disconnect as soon as you are done.

Applications

• Nokia Browser Simulator - generic Nokia phone and gateway

• Openwave Phone Simulator - Openwave's simulator (probably actually an emulator)

• BlackBerry Simulator - multiple different BlackBerry emulators

• Yospace SmartPhone Emulator - displays multiple phone instances at the same time but may not have the best fidelity to actual devices

• iPhone/Pre Emulator - Windows only desktop emulator, emulates both iPhone and Pre.

• Palm Project Ares - Full web development environment for WebOS in the browser.

Prototyping / Wireframing

• iPhone screen projector - "tethers" with your mac to display content from your desktop on your iPhone. Requires a free iPhone app.

• iPhoneprototype - Firefox plugin for iPhone mockups.

• Adobe Device Central - Part of the Adobe CS product line, lets you see what the design might look like on various mobile device screens. Includes non-whites, non-blacks, glare, etc.

Full Design Suites

• MIDS - flow charts, navigation, wireframes, rendering, and even a physical test device

Design for Web Browsers

If you are designing for the mobile web, you probably want to keep abreast of the technology, and to design for not just interesting legacy devices, but assure everything will work on the next great thing.

This is a list of ways to get legacy browsers, advanced and future browsers, and a few emulators.

• f
• f
• f
• f
• f
• f