> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roveflow.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Map a competitor

> Plug in your phone, point Roveflow at any app, and walk away with a clickable map of how it works.

Want to know exactly how a competitor's app works, screen by screen? Plug in your phone, pick their app, and let Roveflow's AI tap through it for you. You end up with one page you can hand to design.

<Steps>
  <Step title="Plug in your phone">
    Connect your phone (iPhone or Android) with a USB cable and keep it unlocked. First run, you approve one prompt, on iPhone a Mac **Allow** plus your **passcode**; on Android, **Allow USB debugging** on the phone.

    ```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
    roveflow setup
    ```
  </Step>

  <Step title="Find the app">
    List the apps on your phone and grab the one you want to map.

    ```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
    roveflow devices
    ```

    Install the competitor's app from the App Store first if it isn't already on the phone.
  </Step>

  <Step title="Let the AI map it">
    In Claude Code, trigger the autopilot with the `/rove` skill. Name the journeys you care about, the more specific you are, the better the map.

    ```
    /rove   map this app, sign-up, the main action, and settings
    ```

    Roveflow opens the app and finds its own way through it, capturing each screen and the paths between them.
  </Step>

  <Step title="Open the Atlas">
    When it's done, build and open the map in your browser.

    ```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
    roveflow atlas
    roveflow serve
    ```

    Everything lands in `roveflow-out/`, screen tiles wired into journeys, with a short video per flow.
  </Step>

  <Step title="Hand it to design">
    Share the `roveflow-out/` folder, or open `roveflow-out/atlas.html` directly. Your team can click through every flow and rebuild, or out-design, what they see.
  </Step>
</Steps>

## Get specific in your ask

The autopilot follows what you tell it. Instead of "map this app," name the journeys that matter to you:

```
/rove   map onboarding, the checkout flow, and the settings screen
```

## Next steps

<CardGroup cols={2}>
  <Card title="Curate the map" icon="pen" href="/guides/journeys-and-screens">
    Rename screens and shape the journeys in `journeys.json`.
  </Card>

  <Card title="Share the Atlas" icon="share" href="/guides/export-and-share">
    Send the self-contained page to your team.
  </Card>
</CardGroup>