Android Studio Cloud, accessed through Firebase Studio, enables developers to conveniently open Android Studio projects anywhere with an internet connection. While we're experimenting with streaming technologies, you'll be interacting with a remotely streamed Linux virtual machine (VM) running Android Studio on the web. Expect a user experience similar to running the Linux version of Android Studio.
Whether it's exploring sample projects or accessing existing Android app projects on GitHub, our goal is that this feature can streamline your development workflow by eliminating the need for local installations.
You can expect:
- Dedicated workspaces in which we have pre-downloaded the necessary Android SDK components and Android Studio IDE for you to explore and build your Android app
- Access to your Android Studio Cloud from anywhere
- The ability to create multiple workspaces at once
See the current known limitations and workarounds. We wish to learn more about your feedback and gradually add more capabilities as Android Studio Cloud progresses through the experimental stage. Please report any feedback and issues through the issue tracker and this survey.
Get started
| Steps | |
|---|---|
| Try Android Studio Cloud and name your workspace. |
|
| Click Create and wait for the workspace to be initialized. |
|
| Once loaded, you will land in the VM linux environment where Android Studio launches. Choose whether or not you would like to send analytics to Google. |
|
| To start a new project or open a project for the first time, either create a New Project, Get from VCS, or click More Actions and select Import an Android Code Sample to get started with an Android project. |
|
| As an example, you can select New Project and open an Empty Activity. |
|
You will then land in Android Studio, and you can try development tasks that you would usually do:
|
|
Workflows to try
You can access many of the same services in Android Studio Cloud as on the desktop version. Try these common workflows:
Deploy your app on a virtual or physical device.
- If you deploy to the Android emulator, we recommend using the Pixel 8a API 35 (that is pre-configured) or Small Phone API 35. We've found that these two devices work better than other emulators, which are generally very slow—especially on first start—due to nested virtualization.
- Alternatively, you can deploy to a physical device by using Android Device Streaming, powered by Firebase. Running the app on a real device should be faster than an emulator.
Try Gemini in Android Studio. Ask questions, get AI-assisted code completion, get code suggestions, and more.
Get your code into Android Studio Cloud from a version control system using Get from VCS from the welcome dialog. For more information about importing projects from Git, see Set up a Git repository in the IntelliJ documentation.
Known issues and workarounds
- To interact with Android Studio Cloud you must use a Linux keyboard mapping.
- Only the latest stable version of Android Studio is available.
- If you are logging into Android Studio, accounts that require physical two factor authentication won't work. Consider using alternative methods, if supported, for example authenticator apps like Google Authenticator.
- The Android Emulator will be slow to boot up for the first time. We recommend letting it run for about 10 minutes after you first create it before deploying your app to it.
- You can't deploy to a local Android physical device.
- Sometimes the "Choose password for new keyring" popup appears. When this happens, click Cancel to close it.
- Ignore popups related to updates from the Linux machines for now.
