Solutions

Which one describes your problem?

Most teams arrive with one of three complaints, and they lead to different pages.

"Setting up to run the app is the slow part." Every engineer maintaining their own simulator, versions drifting, a new starter losing a day to toolchain setup. Cloud simulators for development teams covers previewing any build in a browser tab with nothing installed locally. If you work in React Native and want your own machine's changes to appear on that device as you type, live development is the narrower version of the same idea.

"Our tests break every time the UI moves." AI-powered test automation (beta) is about describing a test in plain English and having an agent drive the live UI, rather than maintaining selectors that a redesign invalidates. If you are building with an AI coding assistant and want to see what it actually produced on a device after each iteration, vibe coding is that loop specifically.

"People outside engineering cannot get to the build." This is the one teams underestimate. Sales demos covers letting a prospect use the real app in their own browser with nothing to install. Support and training covers reproducing a reported issue on the OS version the customer is actually running. Interactive docs covers putting a working device next to the paragraph describing it.

They are the same product

Worth saying plainly, because seven pages can look like seven products: there is one platform underneath all of them. A device runs in the cloud and streams to a browser tab. The pages differ in who is holding the tab and what they are trying to get done.

That also means you are not choosing. A team that starts with development previews usually ends up sharing links with support and sales without buying anything else. If you would rather see the capability list than the use cases, the product overview is organised that way, and platforms covers which devices are available and what each one supports.