Draft page
Access: Prod

Migrate BrowserStack Live and App Live Workflows

If your team uses BrowserStack Live or App Live today, the main change in webmate is that you work from a project and a device slot instead of from a disposable session picker. Once a device or browser VM is deployed, you do the rest of the work in the webmate Workbench.

Concept Mapping

BrowserStack termwebmate termWhat changes
Live sessionDevice or browser VM in a project slotYou reserve infrastructure inside a project instead of starting an isolated live session.
App Live deviceMobile device in a device slotDevice ownership is visible in the slot overview and stays attached to the project.
Session dashboardWorkbench plus test run viewManual execution, screenshots, findings, and review artifacts stay together.
Mark bug / notesFindings and comments in a test runFindings are part of the webmate test result instead of a separate annotation flow.

Typical Migration Flow

  1. Open the target webmate project and move to the device-slot overview.
  2. Deploy the mobile device or browser VM that replaces the Live or App Live target.
  3. Click Access to open the Workbench and run the manual check there.
  4. Start a test run when you want screenshots, findings, and review artifacts to be collected together.
  5. Release the device after the session so the slot becomes available again.

The browser-VM flow is closest to BrowserStack Live, while the real-device flow is closest to App Live.

What Your Team Will Notice First

  • Device ownership is explicit. A slot stays occupied until you release the device.
  • Manual evidence belongs to a named test run instead of to an anonymous live session.
  • The same Workbench UI is reused across manual web checks, manual app checks, and assisted debugging workflows.
  • Simulation features such as sensor input or biometric testing are part of webmate-specific workflows rather than a separate live-product surface.

Recording Findings

BrowserStack teams often capture notes outside the live session. In webmate, it is usually faster to create a test run and keep screenshots, comments, and findings in the same result record.

Use the screenshot tool when you want evidence, then add findings or comments before you finish the test run.

Next Steps