> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/no-code-studio/overview.md).

# Overview

App Studio is Mozark's no-code test automation for mobile apps. You record a test by using a real device in your browser, reuse steps as modules, vary the data per device, and run the result across a fleet of Android and iOS devices. No code to write and nothing to install.

## Where to start

| If you want to...                                         | Read                                                                                                                            |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| See the whole flow in one page                            | [User journey](/no-code-studio/getting-started/user-journey.md)                                                                 |
| Record and run your first test (about 15 minutes)         | [Author your first test](/no-code-studio/getting-started/author-your-first-test.md)                                             |
| Learn the vocabulary: elements, steps, modules, data sets | [Core concepts](/no-code-studio/concepts/core-concepts.md)                                                                      |
| Reuse a login flow across tests                           | [Modules](/no-code-studio/authoring-tests/modules.md)                                                                           |
| Run the same test with different data on each device      | [Test data](/no-code-studio/authoring-tests/test-data.md)                                                                       |
| Bring an existing Optics Framework suite                  | [Importing an existing script](/no-code-studio/authoring-tests/importing-an-existing-script.md)                                 |
| Understand a failed run                                   | [Reports](/no-code-studio/running-and-reporting/reports.md) and [Troubleshooting](/no-code-studio/reference/troubleshooting.md) |

## How these docs are organised

1. **Getting started**: the end-to-end journey and a hands-on first test.
2. **Core concepts**: the building blocks every other page refers to.
3. **Authoring tests**: recording, modules, conditions, test data and importing.
4. **Running and reporting**: launching runs, scheduling, and reading results.
5. **Advanced**: API calls, live run view, per-test-case data and error definitions.
6. **Reference**: keyword catalogue and troubleshooting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mozark.ai/no-code-studio/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.