# Local or cloud?

Source: https://olef.dev/docs/start/environments

Choose the environment that gets you to a running app most easily. Both builders and experienced Android engineers can use either route.

| | Local environment | Olef Cloud |
| --- | --- | --- |
| Best fit | You already have an emulator, phone, or Android setup | You want a managed build environment and emulator |
| Where Android runs | Your computer or connected phone | An Olef-managed workspace |
| Local Android SDK | Needed for local builds and emulators | Not needed for the Cloud workflow |
| Local device connection | Android Platform Tools and USB debugging where relevant | Managed by Olef |
| Coding agent | Runs where you normally work | Can stay in your usual environment and use the Cloud workspace |
| Access | Install the CLI | Cloud account and enabled access |
| Next step | [Install & connect](https://olef.dev/docs/start/install) | [Start a cloud workspace](https://olef.dev/docs/cloud/quickstart) |

## For a first app

The important thing is getting to a running app quickly. If Android Studio and an emulator are already working, keep using them. If you prefer not to set up an Android toolchain locally, choose Olef Cloud when your account has access.

You do not have to learn CLI commands to describe an app or ask for changes. Your coding agent can handle the commands and explain any setup that needs your input.

## For an existing engineering workflow

Keep your source, editor, and review process. Use Olef to drive the app and return structured diagnostics. The [engineering path](https://olef.dev/docs/engineers/overview) explains how it fits alongside Android Studio, Compose, and existing tests.

## For a team

[Olef Cloud](https://olef.dev/docs/cloud/overview) handles provisioning so the team can work with managed Android environments. Organizations with private infrastructure requirements can discuss [enterprise deployment options](https://olef.dev/docs/cloud/enterprise).