---
title: Live iOS preview links and cloud simulators for teams
description: Share live iOS preview links from Linux CI. Limrun's cloud iOS
  simulators run on real Macs and open in any browser for reviewers.
author: Limrun
date: 2026-11-03
url: https://limrun.com/blog/live-ios-preview-links/
---

# Live iOS preview links and cloud simulators for teams

Teams can share live iOS preview links with stakeholders by extending their existing Linux CI or coding-agent sandbox with Limrun. The platform runs Xcode builds and iOS Simulators on real Macs. It streams them through a browser link that a reviewer can open without a Mac. That removes the back-and-forth of screenshots and status updates, and it avoids buying Mac hardware or switching CI platforms.

## Why do stakeholders need a live iOS preview link?

Stakeholders need a live iOS preview link because static screenshots and status updates hide how a build actually behaves. A browser link that opens the running simulator lets a reviewer tap through the flow instead of asking what changed.

Live iOS preview links close the loop between a build and the questions about it. The reviewer sees the current build in the same state as the simulator, not a screenshot from an earlier run.

Every running Limrun simulator has a signed stream URL that opens the live session in a browser, with no Limrun account. It works only while the instance runs, and anyone who has it can watch and control the device. A team can send one link that points at the running iOS simulator. That replaces a new build report for each stakeholder. Product managers can check a flow while design still has it open. QA can reproduce a bug from the same link. That turns the build into the status update.

## How do you produce a live iOS preview link from a build?

A live iOS preview link comes from a real Mac Xcode build. That build compiles the app and attaches a shareable simulator session to the result. The Xcode build sandbox at Limrun compiles on real Macs. It transfers only the files that changed, so the preview reflects current code rather than an earlier snapshot.

On GitHub, its Action builds each pull request and posts the [preview URL](https://docs.limrun.com/docs/ci/pr-previews) as a comment on that PR. Reviewers who belong to your Limrun organization open that link, select **Start device**, and get a fresh simulator with the build installed, without a local simulator or a Mac. The Action runs only on GitHub, but the same `lim xcode build --upload` pattern works on GitLab, CircleCI, Buildkite, and Jenkins with your own comment step. The preview can follow the CI system the team already runs.

These live iOS preview links turn each pull request into a reviewable artifact. The preview comes from the same build that CI would validate. That gives QA and product reviewers one stable link per pull request. It always opens the latest pushed build, and the comment shows which commit that is. Teams can also produce live iOS preview links through the same [Xcode cloud build options](https://limrun.com/blog/xcode-cloud-alternatives/) they already use. They keep their current Linux runners.

## Can I run multiple iOS simulators in parallel in the cloud?

Yes. Parallel iOS simulators are created through an API and can span iPhone, iPad, and Apple Watch profiles. A single CI run can split device coverage across jobs instead of waiting for one simulator at a time. Each instance is isolated, so one failing job does not block the others.

The platform's iOS Simulator supports iPhone, iPad, and Apple Watch. That device matrix is what makes parallel cloud iOS simulator runs useful for mobile teams. A pull request can be checked on an iPhone-sized screen, an iPad layout, and a watchOS app at the same time. The iPhone and iPad jobs can install the same simulator build, the watch job needs a watchOS build, and each runs in its own instance.

Teams create these parallel runs programmatically rather than through a manual dashboard. Limrun exposes a [mobile test infrastructure API](https://limrun.com/blog/mobile-test-infrastructure-api/). Developers can use the REST API plus TypeScript, Python, and Go SDKs. A CI job can call that API to create a set of simulator instances. It can wait for them to boot, run tests, and tear them down.

In practice, each simulator should map to one job or one test scenario. That way a failure on the iPhone run does not block the iPad run. Each job still collects its own logs and screenshots. Each simulator can record its own video, so each parallel job can capture evidence independently.

## How does a remote iOS simulator work on a Windows machine?

A remote iOS simulator runs on a Mac in Limrun's cloud and streams its screen to a browser. A Windows user can tap and type against an iOS build without installing Xcode or owning Apple hardware. The browser becomes the only client. App logs, screenshots, and video stay in the same session.

The platform streams the live simulator session to a standard browser rather than requiring a native client. For a Windows-based QA owner or stakeholder, that browser link is the practical form of an iOS simulator for Windows. No local Apple software is involved. The simulator itself stays on a real Mac. The browser session sends touches and receives the updated screen over the stream.

This approach removes the local iOS toolchain from the workflow. A Windows user does not need Xcode, a Mac, or a macOS virtual machine. Instead, the same [remote iOS development environment](https://limrun.com/blog/remote-ios-development-environment/) that creates the simulator also provides browser access. Stakeholders get the same live preview link on Windows and macOS.

## How do live iOS preview links fit an existing sandbox?

Teams keep their current Linux CI and coding-agent sandbox. They add live iOS preview links through Limrun's MCP server, CLI, and SDKs. They do not switch platforms; agents and CI jobs call it as another tool in the existing workflow. That keeps the daily review loop inside the systems the team already runs.

For mobile platform teams, coding agents are already part of the daily workflow. Adding a tool call for a live simulator link fits the way work is already requested.

The remote MCP server has 16 tools for creating, driving, streaming, and deleting devices. Existing agent workflows can adopt those tool calls without leaving the environment they already use. With the lim CLI, teams can add prebuilt agent skills to Claude, Cursor, and Codex. An agent can create an iOS simulator, run the app, and share the signed stream URL that `lim ios create` prints.

That is the core of the sandbox extension. The Linux environment gains a set of mobile capabilities through tool calls and SDKs. The result is a stakeholder app preview produced from the same pipeline that builds and tests the app.

## FAQ

### Does a stakeholder need an Apple ID to open a live iOS preview link?

No. The browser preview links open in a standard browser. A stakeholder does not sign in with an Apple ID or install anything. A signed stream link needs no account at all, while a PR preview link asks the reviewer to sign in as a member of your Limrun organization. The simulator runs on a real Mac in the platform's cloud, and the reviewer only interacts through the shared stream.

### Can I embed a live iOS simulator directly in a product page?

Yes. The platform provides a React component for embedding a live simulator in a web page. Tokens are scoped to that instance. This is useful for support pages or internal tools where visitors should try a specific build without leaving the page.

### How do I keep a live iOS preview link private?

Treat a signed stream link like a password. Anyone who has it can watch and control that one simulator without an account, until the instance stops. It carries only that instance's token, never your API key. Delete the instance when the review is finished to end the link. For links only your team can open, post PR preview links, which require signing in to your Limrun organization.

### Can a live iOS preview link replace a recorded walkthrough?

It can replace the basic walkthrough for interactive review, because the stakeholder taps through the current build. The platform also records demo videos. You can attach a recording when the reviewer needs a fixed narrative or offline evidence.

### Can a live iOS preview link also cover Android builds?

Yes. The platform runs Android emulators alongside iOS simulators. Each running emulator has its own signed stream link, and the Android preview Action posts PR preview links for APK builds. This lets stakeholders compare both platforms from one workflow.

### Can I install a preview build on a physical iPhone from the browser?

Use TestFlight for that. The same remote Xcode build can sign the app and upload it with `lim xcode build --upload-to-appstore`, and stakeholders install it from TestFlight on their own iPhones. This is useful when a stakeholder needs to test camera input, device motion, or push notifications on hardware.

### How does a live iOS preview link differ from a TestFlight invite?

Live iOS preview links open the app in a browser with no install. A TestFlight invite requires an Apple ID, the TestFlight app, and an accepted invitation. The platform can also publish signed builds to TestFlight. Teams often use the browser link for early review and TestFlight for later beta distribution.

Start with Limrun's free API key, create an iOS simulator, and share live iOS preview links with reviewers.
