# Get Started

- [Maestro documentation](https://docs.maestro.dev/get-started/readme.md): Overview of Maestro documentation with links to guides, tutorials, and community resources.
- [What is Maestro?](https://docs.maestro.dev/get-started/what-is-maestro.md): Maestro is an open-source UI automation framework for mobile and web with built-in tolerance, zero-wait intelligence, and declarative YAML syntax.
- [How Maestro works](https://docs.maestro.dev/get-started/how-maestro-works.md): Learn how Maestro simulates user interactions using the accessibility tree and device-level commands.
- [QuickStart](https://docs.maestro.dev/get-started/quickstart.md): Install Maestro Studio, set up your environment, and run your first automated test in five minutes.
- [Maestro solutions](https://docs.maestro.dev/get-started/maestro-solutions.md): Explore Maestro's ecosystem: Studio, CLI, Cloud, and Flows, plus how they fit into local automation and CI/CD workflows.
- [Supported platforms](https://docs.maestro.dev/get-started/supported-platform.md): Platforms supported by Maestro: Android, iOS, React Native, Flutter, and web applications via UI-layer automation.
- [Android](https://docs.maestro.dev/get-started/supported-platform/android.md): Configure Maestro for Android app testing with emulators or physical devices.
- [Android Native](https://docs.maestro.dev/get-started/supported-platform/android/android-native.md): Black-box testing for Android Views and Jetpack Compose via the Accessibility layer. Target elements by text, Resource ID, Content Description, or testTag.
- [Jetpack Compose](https://docs.maestro.dev/get-started/supported-platform/android/jetpack.md): Black-box testing for Jetpack Compose via AccessibilityService. Prioritizes text-based matching and semantics over testTag for refactoring resilience.
- [iOS](https://docs.maestro.dev/get-started/supported-platform/ios.md): Black-box iOS testing via the Accessibility layer. Run on Xcode Simulators, handle permissions, test multi-app journeys, and parallelize with Cloud.
- [SwiftUI](https://docs.maestro.dev/get-started/supported-platform/ios/swiftui.md): Configure SwiftUI apps for Maestro testing with proper accessibility identifiers.
- [UIKit](https://docs.maestro.dev/get-started/supported-platform/ios/uikit.md): Black-box testing for UIKit via the accessibility layer. Use accessibilityLabel for text and accessibilityIdentifier (gold standard) for id selectors.
- [React Native](https://docs.maestro.dev/get-started/supported-platform/react-native.md): Configure React Native apps for Maestro testing on both Android and iOS platforms.
- [Flutter](https://docs.maestro.dev/get-started/supported-platform/flutter.md): Test Flutter apps via the Semantics Tree. Use semanticLabel, Semantics widget, or identifier (Flutter 3.19+) instead of Keys for stable automation.
- [Web Browsers](https://docs.maestro.dev/get-started/supported-platform/web-browser.md): Test web applications in desktop browsers using Maestro's web automation capabilities.
- [Maestro MCP Server](https://docs.maestro.dev/get-started/maestro-mcp.md): Use Maestro's MCP server to let your coding agent write, run, and debug mobile and web UI tests.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.maestro.dev/get-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.