> ## Documentation Index > Fetch the complete documentation index at: https://docs.revyl.com/llms.txt > Use this file to discover all available pages before exploring further. # Explore your app > Launch explorers from the Revyl dashboard and turn their discoveries into an Atlas map Explore sends parallel agents through your app on real devices. Each explorer takes a different path, records what it sees, and adds that evidence to Atlas. Use Explore when you want broad product discovery before you know which flows should become durable tests. ## 1. Open Explore From Atlas, click **Map app** above the apps list. From an app workspace, click **Explore app** in Atlas or Builds. You can also open **Sessions** and choose **Explore**. The app is selected automatically when you start from an app workspace. Otherwise, choose the app you want to map. ## 2. Choose the build Select the build the explorers should install. **Latest build** uses the app's current build, or you can choose a specific uploaded version. Use a preview or production-like build that contains every screen and native dependency you want Revyl to reach. ## 3. Plan the exploration Choose how many explorers to run, how they should divide the work, and how long they can explore. * **Balanced** mixes broad discovery, deeper flows, edge cases, complete journeys, and less obvious paths. * **Surface sweep** prioritizes distinct screens, tabs, menus, and top-level areas. * **Journey focus** follows multi-step flows to their natural end states. * **Hard edges** looks for settings, permissions, empty states, and setup blockers. More explorers can cover more ground in parallel. If other device sessions are already using your organization's concurrency, Revyl may launch fewer explorers than requested and will show the number that started. ## 4. Prepare sign-in and runtime settings If the app requires authentication, describe how explorers should sign in. Keep credentials in stored launch variables or an auth bypass instead of writing secrets into the instructions. You can reuse authentication context from the previous exploration or customize it per explorer when different accounts should take different paths. Open **Device & runtime** when you need to: * Attach stored launch variables. * Supply non-secret inline environment values. * Choose a device model and OS version. Open **Advanced** and use **Exploration notes** for product areas, flows, or states you especially want explored. Keep the goal broad enough that the explorers can still discover unexpected paths. ## 5. Launch and watch Click **Launch 3 explorers** (the number matches your selection). Revyl shows each explorer as its device starts and its status changes. Click **View run** to follow every explorer, watch discoveries arrive, inspect findings, and jump into the resulting Atlas map. You can leave the page while the run continues. To stop the run and release its devices, click **Cancel exploration** from the live run or report. ## 6. Read the result An exploration can finish in a few different states: * **Completed**: the explorers finished and Atlas processed their maps. * **Partial**: at least one explorer produced a usable map, but another lane did not finish processing. * **Failed**: the run could not produce a usable result. * **Cancelled**: someone stopped the run before it finished. An explorer may complete after reporting a blocker such as OTP, missing test data, payment setup, or unavailable credentials. Treat those findings as instructions for the next run, not as proof that the rest of the app was covered. After processing finishes, open Atlas to inspect the discovered screens, variants, transitions, and evidence. Turn important paths into tests when they should be checked on every release. ## Troubleshooting If explorers stop at sign-in, add an auth bypass or the required stored launch variables and run again. If fewer explorers launch than requested, stop unneeded device sessions or wait for capacity to become available. If Atlas is partial, open the report to see which lanes completed and which were blocked or failed. If an important area is missing, add a short note that names the area without prescribing every tap, then start another exploration. Learn how Atlas organizes screens, variants, and transitions. Turn exploration evidence into useful coverage. Let test builds enter a known authenticated state safely. Prevent network controls from cutting exploration short.