DEV Community

Cover image for Android Studio Cloud Alternatives After Firebase Studio
CodeItBro
CodeItBro

Posted on

Android Studio Cloud Alternatives After Firebase Studio

Firebase Studio shuts down on March 22, 2027, and any workspace data still in it after that date is permanently deleted. Android Studio Cloud ran inside Firebase Studio, so it disappears the same day. If your Android work lives there, it's time to pick from the Android Studio Cloud alternatives below and move it.

What's going away, and what isn't

Google announced the sunset on March 19, 2026. New workspace creation was disabled on June 22, 2026, though you can keep working in and migrating existing workspaces. So if you still have one, it's the last one you'll get.

Android Studio Cloud was always labelled experimental. It gave you a browser-based Android Studio session through Firebase Studio, which was handy on a Chromebook or a locked-down work laptop. That's the part that's ending.

The desktop Android Studio IDE isn't affected. Neither is your backend. Google says core Firebase services like Cloud Firestore and Authentication aren't affected, and databases and user data keep working normally. You're moving tooling. Your data stays put.

Google is steering people toward Google AI Studio and Google Antigravity. Both picked up real Android features this year, which I'll get to, but neither is a drop-in Android Studio.

What you actually need from a replacement

Start by being honest about how you used Android Studio Cloud. Most people fall into one of two camps.

Some used it as a code editor with Gradle attached. They wrote Kotlin, ran builds, pushed to Git, and tested on a physical phone or barely tested at all. For that group, almost any cloud IDE works.

Others used the full IDE: Layout Inspector, Compose previews, the profilers, and an emulator running alongside. That group has a much shorter list of options, because the emulator is where most cloud setups fall apart.

The emulator needs hardware virtualization. Cloud machines are usually VMs already, so the emulator needs nested virtualization or a bare-metal host. Without it, the emulator either refuses to start or crawls. It also wants a GPU. Without one it falls back to software rendering, and a simple Compose list scrolls like it's on a budget phone from years ago.

Then RAM. Android Studio, the Gradle daemon, the Kotlin compile daemon and an emulator all want memory at once. Google lists 16 GB as the minimum for running Studio with the emulator, and 32 GB as the recommendation. Plan around the recommendation. The minimum is where the fan starts screaming during a clean build.

Team consistency matters more than people admit. Five developers with slightly different SDK and JDK versions means someone eventually loses a Friday afternoon to a build that only fails on one machine.

Cost comes last, and it includes two numbers. The monthly bill, and the hours someone spends keeping the thing running.

Android Studio Cloud alternatives, option by option

1. Desktop Android Studio on a high-spec workstation

The boring answer. For a lot of people, also the right one. The desktop IDE is the version Google actually invests in, and the emulator runs with real hardware acceleration on a real GPU.

The catch is hardware. Android development punishes weak machines, and a properly specced workstation per developer adds up fast, then needs replacing on a cycle.

The other catch is drift. One person updates the SDK, another doesn't. Someone installs a different JDK vendor. Gradle wrapper pins and toolchain settings help, but emulator images and IDE plugins still wander.

It also doesn't fully solve the reason many people picked Android Studio Cloud. Android Studio does install on ChromeOS through its Linux environment, so a capable Chromebook isn't automatically out. But the budget models most people actually carry weren't built for Gradle and an emulator at the same time.

If you're one developer with a good machine, install the desktop IDE and stop reading. Seriously.

2. Self-managed cloud VMs (AWS, Azure, GCP)

This is the most direct way to run Android Studio in the cloud. Spin up a VM, install the IDE, connect over a remote desktop protocol. In theory, done.

In practice, the emulator decides whether this works, and each cloud handles it differently.

On GCP, Linux KVM is the only hypervisor supported inside the VM, Hyper-V isn't, and E2 machines are excluded. No Hyper-V means a Windows VM on GCP is a poor fit for emulator work. Google also notes nested VMs can lose 10% or more performance on CPU-bound workloads.

On AWS, nested virtualization used to require bare-metal instances, which are expensive to leave running. That changed in early 2026, when AWS enabled it on regular virtual instances, starting with its C8i, M8i, and R8i families. AWS still recommends that performance-sensitive or latency-sensitive workloads evaluate bare metal.

Azure has supported nested virtualization on many general-purpose sizes for years. But developers regularly report the emulator failing even on sizes that should work, and some report that Azure's GPU-equipped N-series sizes don't offer nested virtualization at all. So you may end up choosing between a GPU and an accelerated emulator. Not a fun trade.

And even when you get it working, Google's emulator acceleration docs say a VM-accelerated emulator can't run inside another VM. Some setups work anyway, but you're outside what Google supports.

Display is the other problem. Plain RDP over an average connection makes the emulator feel laggy even when the VM is fast. A protocol built for graphics work helps, and it's one more piece to pick and maintain.

Then there's everything you now own: OS patches, disk snapshots, IAM policies, shutting machines down at night so nobody pays for idle compute, and figuring out why a VM won't boot on Monday morning. For a platform team, that's normal work. For a five-person studio, it's a part-time job nobody signed up for.

What you get in return is control. Pick the region and the instance size, bake a golden image with the exact SDK and JDK, and every new VM matches it.

3. Cloud development environments (Codespaces, Coder, Ona)

Here's where I disagree with a lot of the advice going around. CDEs keep showing up on lists of Firebase Studio alternatives, and for Android work they're a partial answer at best.

GitHub Codespaces runs your environment in a container on a GitHub-managed VM. It's excellent for backend work. For Android, you'll mostly be in VS Code with Kotlin and Gradle support, not Android Studio. Builds work. Unit tests work. GitHub doesn't document KVM access inside Codespaces, and I wouldn't build a workflow around hoping it's there. Honestly, Codespaces is the wrong tool if you live in the emulator.

Coder is more interesting. It's self-hosted, so workspaces run on infrastructure you choose. You can pick hosts with KVM support, bake the Android SDK into templates, and wire up a full desktop session inside a workspace if you need the GUI. It works. But you're doing all the infrastructure work from option 2, plus running Coder.

Ona is a different story now. Gitpod rebranded as Ona in 2025 and repositioned around giving AI agents persistent cloud environments instead of giving people workspaces, and Ona is now part of OpenAI as part of the Codex team. I wouldn't start a human-driven Android workflow on it today.

The pattern holds. CDEs are great at reproducible environments defined in code (devcontainer.json and friends), which handles SDK drift nicely. They're weak at the GUI-heavy, GPU-hungry parts of Android. If your team ships mostly through CI and tests on physical devices or a device cloud, a cloud IDE for Android development can still be a reasonable trade.

4. Remote device and emulator services

These aren't IDEs. They're where your app runs while your editor lives somewhere else, and they pair well with every other option here.

Firebase Android Device Streaming connects you to physical devices in Google's data centers from inside desktop Android Studio. Both the Spark and Blaze plans include 30 free minutes per project per month, and Blaze charges 15 cents for each extra minute. That's $9 an hour. Great for checking a layout on a Samsung you don't own, expensive as an all-day emulator.

Genymotion SaaS gives you cloud-hosted Android virtual devices you reach through a browser or ADB. It offers usage-based billing per running device, plus an unlimited plan with a flat monthly fee per virtual device. Useful precisely because so many cloud dev setups can't run an emulator themselves.

BrowserStack leans toward QA, with manual and automated testing on real devices. Great for regression passes. Overkill for your daily inner loop.

The shared limitation is latency. Pushing an APK over the network and watching a video stream is fine for a test pass. For tweaking padding on a Compose screen over and over, it wears thin fast.

5. Google AI Studio and Google Antigravity

These deserve more credit than I'd have given them a year ago, and less than Google's migration page implies.

AI Studio can now generate a native Android app in Kotlin and Jetpack Compose from a prompt. Its emulator runs in the cloud and streams to your browser, with no SDK, Android Studio, or local emulator to install. For a Chromebook user who wants to prototype, that's useful.

The limits are just as clear. Only single-activity, single-module projects are supported, apps must use Compose with no Java or XML layouts, and native code through the NDK isn't supported. The browser emulator lacks camera, NFC and Bluetooth, simulates GPS, and doesn't run Google Play services features like Sign-In or Maps. That rules out most production apps. To keep developing in Android Studio, you download the project as a ZIP, which tells you where Google expects serious work to happen.

Antigravity is Google's agent-first IDE. Firebase's migration guide has you extract your project locally and open it in Antigravity, so it's a desktop tool, not a browser one. Antigravity 2.0 added official Android development support through the Android CLI. That makes it a reasonable place for an agent to write and build Kotlin. Layout Inspector and the profilers still live in Android Studio.

Use them as AI tools, because that's what they are. If you relied on Android Studio Cloud for the full IDE, they won't fill that hole.

6. Managed cloud desktops (VDI) with full Android Studio

This is the option people overlook, and it's the one closest to what Android Studio Cloud promised: the full desktop IDE, reachable from any device, without owning the hardware.

A managed cloud desktop is a Windows or Linux desktop running in a data center, with the provider handling the OS, the virtualization layer, backups and uptime. You log in from a Chromebook or a thin client and get the same desktop every time. Compared with a raw cloud VM, the practical differences are that GPU-backed desktops come standard and you aren't the one patching them late at night.

Ace Cloud Hosting is one provider here. Its Android Studio VDI runs on Windows or Linux, GPU-ready, with the IDE, Android SDK and Gradle pre-installed, and it lists 99.99% uptime, 30-day automated backups, free migration and onboarding within 48 hours. Every developer gets the same environment, so SDK drift goes away without anyone writing a devcontainer file.

Be clear on the support boundary, because it matters. Ace's support is limited to the OS level and VDI registration, and Android Studio is managed by the customer, outside VDI support. That covers IDE updates, plugins, SDK components and emulator images. If the IDE misbehaves after an update, that's your problem, same as on a local machine. I'd rather know that before signing than discover it in a support ticket.

General VDI limitations apply too. Everything you see is streamed, so you need a steady connection, and offline work is out. And ask any VDI provider, this one included, whether the Android Emulator gets hardware acceleration on the plan you're quoting. That depends on whether the provider exposes nested virtualization, so test it during the trial with your heaviest AVD. If it doesn't, device streaming from option 4 covers the gap.

Side-by-side comparison

Option Best for Emulator experience Setup effort Main catch
Local workstation Solo devs, anyone with a strong machine Best available, with native acceleration and a local GPU Low Hardware cost per developer, SDK drift across machines
Self-managed cloud VM Teams with a platform or DevOps person Needs nested virtualization or bare metal; GPU and acceleration don't always come together High You own patching, images, shutdowns and uptime
CDE (Codespaces, Coder) Code-and-CI workflows Absent on Codespaces; on Coder it depends on your hosts Medium Mostly VS Code, not full Android Studio
Remote device services Real-hardware testing, QA passes Real or virtual devices, streamed with network latency Low A complement, not an IDE; per-minute costs add up
Google AI Studio / Antigravity Prompt-based prototypes, agent-driven coding AI Studio streams a limited browser emulator; Antigravity uses whatever you run locally Low Single-module Compose apps only in AI Studio; not an Android Studio replacement
Managed VDI Teams wanting the full IDE without buying hardware GPU rendering; hardware acceleration depends on the provider Low Needs a steady connection; you still manage the IDE

How I'd choose

Solo developer: get a machine with 32 GB of RAM and run desktop Android Studio. Add Firebase Android Device Streaming for devices you don't own. I wouldn't put a solo dev on a self-managed VM unless they really can't run a local IDE, because you'd be taking on ops work to avoid a hardware purchase.

The exception is the Chromebook or locked-down-laptop crowd, who used Android Studio Cloud precisely because they couldn't install anything. If you're only prototyping, AI Studio might be enough. If you're shipping a real app, an Android Studio virtual desktop is the closest like-for-like move.

Five-person studio: I'd lean toward managed VDI, or good workstations plus a strict setup doc that someone actually maintains. The deciding question is whether anyone on the team wants to run infrastructure. Usually nobody does. A managed desktop keeps everyone on the same SDK and JDK, and new hires log in to a working environment instead of spending their first days installing SDKs. I'd skip self-managed VMs at this size. Whatever you save disappears the first time a VM breaks during release week.

Thirty-person team: you probably have, or need, someone who owns developer infrastructure. At that size, self-managed VMs with golden images, or Coder on your own cloud, start to make sense because the overhead spreads across more seats and you get full control. Managed VDI is still a fair option if you'd rather buy than build. Either way, I wouldn't commit 30 people to anything without a two-week pilot on a real project.

What I wouldn't do at any size is move the Android team to Codespaces because it worked well for the web team. Different workload, different needs.

Migration checklist before March 22, 2027

Do this soon. The workspaces you've forgotten about are the ones that get deleted.

  • Export each workspace with the Move now button and Zip and Download, or run the Firebase Studio: Zip & Download command from the command palette. Include old workspaces you think you don't need.
  • If you want your Gemini chat history, copy the files from the /home/user/.idx/ai directory in your workspace.
  • Confirm every project has a Git remote and that every branch is pushed, not just main.
  • Copy everything that isn't in Git: keystores, local.properties, .env files, and google-services.json if you don't commit it. Losing a signing key is a very bad day.
  • Write down your versions: compileSdk and targetSdk, Android Gradle Plugin, Gradle wrapper, Kotlin, and JDK.
  • Record your emulator setups (device profile, API level, system image and any custom hardware settings) so you can recreate them.
  • Do a clean clone and a full build in the new environment before deleting anything.
  • Put March 22, 2027 in the team calendar, with a reminder a month earlier.

Where this leaves you

Android Studio Cloud was a decent idea that never got time to mature. The desktop IDE is still here and so are your Firebase backends, so this is an inconvenience rather than a crisis. Pick the option that matches how your team actually works, and test it on a real project well before the deletion date. If you'd rather not babysit VMs, Ace Cloud Hosting's Android Studio desktops are worth a trial.

FAQs

When does Firebase Studio shut down?

Firebase Studio shuts down on March 22, 2027. New workspace creation was disabled on June 22, 2026, and any workspace data left after the shutdown is permanently deleted.

Does the Firebase Studio shutdown affect desktop Android Studio?

No. The desktop Android Studio IDE isn't affected, and neither are core Firebase services like Firestore and Authentication. Only Firebase Studio, and Android Studio Cloud with it, is going away.

Can I run the Android Emulator on a cloud VM?

Sometimes, on instances that expose nested virtualization or on bare metal, and support varies by cloud and instance family. Expect a performance hit, and know that Google's docs don't support running a VM-accelerated emulator inside another VM.

What's the closest replacement for Android Studio Cloud?

For the full IDE from any device, a managed cloud desktop running desktop Android Studio is the closest match. Google AI Studio can now build simple native Android apps in the browser, but it's limited to single-module Compose projects and doesn't replace Android Studio.

Top comments (0)