Glossary

Android Virtual Device Manager

Updated on May 30, 2026

Learn what Android Virtual Device Manager is and how teams create, run, and govern Android emulator profiles.

What Is Android Virtual Device Manager?

Android Virtual Device Manager is the Android Studio tool for creating and managing Android Virtual Devices. In current Android Studio documentation, this workflow appears through Device Manager, where developers can create virtual phones, tablets, Wear OS devices, Android TV devices, and Automotive OS profiles.

The tool is important because the Android Emulator needs an AVD configuration before it can simulate a device.

How Android Virtual Device Manager Works

The manager helps teams select and configure the pieces of a virtual Android device:

• Hardware profile
• Android system image
• API level
• Screen size and density
• Storage
• Google Play support
• Emulator skin
• Advanced emulator properties

After the AVD is created, the same tool can start, stop, edit, duplicate, delete, or inspect the virtual device. Developers may also use Android Debug Bridge to install apps, view logs, and run shell commands against that environment.

Why It Matters for QA and Development

AVD Manager gives developers a repeatable way to test app behavior across Android versions and form factors. It reduces dependency on physical devices during early development and makes it easier to reproduce bugs.

For QA, it is especially useful when a team needs to verify compatibility, screen layout, startup behavior, permissions, and API-level changes.

But AVD Manager does not automatically solve operational questions such as account ownership, team permissions, long-lived app sessions, or review logs.

That is why teams should document whether a virtual device is being used for engineering validation, QA reproduction, or operational workflow testing. The same emulator profile can mean very different things depending on who owns it and what data is stored inside it.

Where It Differs from Cloud Phone Management

AVD Manager is a local development tool. It is excellent for app testing, but it is not designed as a full operations console for multi-account workflows.

When teams need persistent accounts, shared access, workflow handoff, and auditability, they need a different management layer. The same Android concept becomes an operational environment rather than a temporary test target.

How MoiMobi Fits

MoiMobi cloud phones provide remote Android environments for app-based account workflows. They are closer to operations infrastructure than to a local emulator manager.

For mobile automation, the difference is practical: AVD Manager helps test apps, while MoiMobi helps teams run controlled mobile workflows with assignment, review, and persistence.

Bottom Line

Android Virtual Device Manager is the control surface for creating and managing Android Emulator profiles.

For operations teams, it is a useful reference point, but persistent mobile work needs cloud phone governance beyond local emulator configuration.