Stop 09 · Mobile TestingTopics · 4/8

Mobile Emulators & Real Device Testing

In short

Emulators are free, fast and live on your laptop. Real phones catch the bugs emulators can't fake. Good teams use both, at the right moments.

Emulators/simulators run virtual devices for fast, convenient testing; real device testing catches hardware-specific issues (camera, GPS, performance) that emulators can't fully replicate.

The purple blob sits at an arcade driving simulator while a real scooter waits outside the door.

Think of it like this

The driving simulator and the real road

The arcade simulator is perfect for learning the controls without denting anything. But it can't give you a real pothole, a honking bus or a scooter that cuts in. Emulators are the simulator. Real devices are the road.

Watch it happen

Emulator vs real device

Emulator

Free, quick to start and reset
Easy to fake GPS and network
Great for CI and daily checks

Real device

True speed, battery and heat
Real camera, sensors and fingerprint
Brand quirks and real interruptions

Run most automated tests on emulators and simulators. Before release, run key flows on real phones your users actually own.

The big ideas

What you need to know

Emulator vs simulator

Android emulators mimic the device hardware. iOS simulators run the app on your Mac without emulating the phone's hardware.

iOS needs a Mac

The iOS Simulator ships with Xcode, which only runs on macOS.

Cloud device farms

Services like BrowserStack, Sauce Labs and Firebase Test Lab rent real devices remotely.

Performance on real phones

Laptop-powered emulators can feel faster than a budget phone. Judge speed on real hardware.

See it in code

Walk through the code

bash

1# Android: list and start an emulator2emulator -list-avds3emulator -avd Pixel_8_API_344 5# iOS (macOS only): list and boot a simulator6xcrun simctl list devices7xcrun simctl boot "iPhone 15"8open -a Simulator9 10# Fake a GPS location on the Android emulator11adb emu geo fix 77.5946 12.9716

1/3List the virtual devices you've created, then start one by name.

Device names depend on what you created in Android Studio or Xcode. geo fix takes longitude first, then latitude.

Save yourself the pain

Common mistakes

Oops

Signing off a release after testing only on emulators.

Do this instead

Run the critical flows on at least a couple of real devices before release.

Oops

Buying a dozen phones before checking what users actually own.

Do this instead

Use analytics to pick devices, and use a cloud farm for the long tail.

Your mission

Same app, two worlds

~30 min

Quick check

Which bug are you most likely to miss if you test only on emulators?

Go deeper

1Test an app on both an emulator and (if possible) a real device, comparing the experience.
2Learn why certain bugs (performance, hardware sensors) only surface on real devices.
3Understand cloud-based real device testing platforms as a way to access broader device coverage.