Share via

When Do You Switch From The Emulator To A Device?

  • Article

As a comment on my last post, Matthew pointed out that he generally only uses the emulator for simple apps and generally uses real devices for testing.  Our long term goal for the emulator is to make it good enough for many developers to build and test their applications without the need to purchase devices.  There's a few reasons for this :

  1. The Windows Mobile development platform is consistent so the APIs exposed by the emulator are consistent with the APIs exposed by devices 
  2. Devices are expensive (both device and service)
  3. You can't always buy your target device in your territory, for example a European developer can't easily buy the Q
  4. With the proliferation of different device form factors, keeping the test matrix up to date is time consuming and expensive

We've made big strides with our device emulator in the last few years.  We moved to true ARM emulation, we've improved performance and in Windows Mobile 6 added new functionality for testing interaction with cellular events and testing GPS applications.  With the emulator we're able to release emulator packs to support new form factors as they come to market.  For example, we were able to release a Smartphone Landscape emulator pack to support the Q and Blackjack when they launched.

Which brings me to my question!  What programming tasks have forced you to move from working in the emulator to working on an actual device?