# Supported platforms

<figure><img src="https://1411608689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCbCMt5C3rawmE9oIus7f%2Fuploads%2FE30yKYC8HhMlUbnMEuym%2Fimage.png?alt=media&#x26;token=ed9c1d5a-6074-44da-a0ac-b6fd5ca6958e" alt=""><figcaption></figcaption></figure>

Maestro operates on the principle of UI-layer automation rather than code instrumentation. Like a test driver interacting with any vehicle through its controls (steering wheel, pedals), Maestro interfaces with applications through their visual and accessibility layers, regardless of the underlying technology stack.

### Mobile operating systems (core)

Maestro provides comprehensive automation support for major mobile platforms:

* **Android:** Full support for emulators and physical devices
* **iOS:** Full support for simulators

Both platforms pass validation at scale by enterprise teams at Microsoft, DoorDash, and others for complex automation scenarios.

### Framework agnosticism

Maestro decouples test automation from framework implementation by interacting directly at the UI layer. This removes the need for framework-specific instrumentation, which is a departure from tools like Detox or Appium, which depend on complex native drivers and in-app code injection.

Supported technology stacks include:

* **Native:** Swift, Kotlin, Java, Objective-C.
* **Cross-platform:** React Native, Flutter.
* **Other hybrid frameworks.**

### Web automation

* **Status:** Functional with ongoing development.
* **Approach:** Maestro extends support to web applications, enabling cross-platform test consolidation using consistent automation syntax.
* **Use Case:** Unified testing strategy across mobile and web surfaces.

### System-level interaction

Maestro supports device-level automation beyond app boundaries:

* **System Interaction:** Navigate to Settings, modify permissions, toggle Wi-Fi, and monitor app behavior in response to system state changes.
* **Real-world Scenarios:** Automated testing of notification handling, permission flows, and inter-app interactions.

### Next steps

Explore the details on how to use Maestro in each one of the supported operating systems and frameworks:

* [android](https://docs.maestro.dev/get-started/supported-platform/android "mention")
* [android-native](https://docs.maestro.dev/get-started/supported-platform/android/android-native "mention")
* [jetpack](https://docs.maestro.dev/get-started/supported-platform/android/jetpack "mention")
* [ios](https://docs.maestro.dev/get-started/supported-platform/ios "mention")
* [swiftui](https://docs.maestro.dev/get-started/supported-platform/ios/swiftui "mention")
* [uikit](https://docs.maestro.dev/get-started/supported-platform/ios/uikit "mention")
* [react-native](https://docs.maestro.dev/get-started/supported-platform/react-native "mention")
* [flutter](https://docs.maestro.dev/get-started/supported-platform/flutter "mention")
* [web-browser](https://docs.maestro.dev/get-started/supported-platform/web-browser "mention")