I'm interested in using Genymotion SaaS for ARM64. Can you walk me through setting that up?

Absolutely. Here’s a straightforward setup for using Genymotion SaaS with ARM64.

Step-by-step guide

• prerequisites
• Have a Genymotion SaaS account with access to ARM64 images (this is now the standard for new ARM64 devices).
• A Google account if you plan to use Google Play, and be ready to install GAPPS after boot if needed.
• Optional: a project plan for which Android version you want (Android 12, 13, or 14 ARM64 images are available).

1) Sign in to Genymotion SaaS

• Go to your Genymotion SaaS dashboard and log in with your credentials.
• You should see ARM64-based device options available in the device/recipes area. Source: Genymotion’s ARM64 live release.

2) Create a new ARM64 virtual device

• In the Virtual devices or Recipes section, choose an official arm64 recipe/image.
• Select the desired Android version (e.g., Android 12/13/14 ARM64) and confirm to create the device.
• Start the device. The VM will boot with an ARM64 image by default. Source: ARM64 documentation and latest SaaS guides.

3) Install Google Play Services (Open GApps) if needed

• Open the device’s UI.
• Use the on-screen controls to install GAPPS (Open GApps) if you need Google Play.
• Reboot when prompted. After reboot, Google Play should be available for app installation. Source: SaaS user guidance.

4) Deploy apps on ARM64

• Install apps via Google Play, APK drag-and-drop, or ADB, depending on your workflow.
• Most modern apps are ARM64-compatible; if an app isn’t, you may need a different ARM64 image or recipe. Source: ARM64 guidance and app deployment notes.

5) Save and reuse

• Save your configured ARM64 VM as a custom recipe/image so you don’t repeat the setup.
• This allows you to quickly spin up identical ARM64 environments for testing or demos. Source: SaaS User Guide.

Tips and important notes

• Arm64 transition timeline: Genymotion SaaS will move to arm64 exclusively for all devices on a future date (watch for updates; x86-based devices will be limited or phased out). Plan migrations accordingly. Source: Genymotion SaaS arm64 transition article.
• Performance and features: arm64 images provide more faithful app behavior and support for ARM-only apps; some features (like certain GPU accelerations) may have limitations depending on the exact ARM64 image and server configuration. Source: arm64 release notes.

Sources

• Genymotion SaaS is moving to arm64: https://genymotion.com/download
• Genymotion’s ARM64 virtual devices are now officially live: https://docs.genymotion.com/gmsaas/04_Issues
• How to run Google Play and apps on ARM64 SaaS: https://support.genymotion.com/hc/en-us/articles/360003125617-How-to-run-automated-tests-with-Genymotion-Desktop

One quick question to tailor this further: what Android version do you want to target (e.g., Android 12, 13, or 14), and do you need Google Play access included in your ARM64 environment? 🚀