build() Developers
Move from “the code looks right” to evidence that the change actually works.
Explore developers ↗ Recommended workflows
Start with the decision you need to make.
Come in through your team or through the workflow that hurts today. Every path below lands on the same live runtime and the same evidence.
01 Four ways in. Same runtime.
02 Six workflows. Pick the one that hurts.
01
AI agent development
Give coding agents a device, not just a diff.
For Developers · Enterprises ↗ 02 Mobile test automation
Automate by intent, not brittle selectors.
For QA & testing · Enterprises ↗ 03 Pull request validation
Attach runtime proof to every merge.
For Developers · QA & testing ↗ 04 Release readiness
Make the ship call from evidence.
For QA · Product · Enterprises ↗ 05 App exploration
Discover the app and keep what you learn.
For Product & design · Developers ↗ 06 Cross-platform testing
Prove iOS and Android match.
For QA & testing · Product & design ↗ 03 Every workflow above is the same four-stage loop, scoped to one decision your team needs to make.
See the platform ↗04 Bring your first workflow.
Start from one decision. The shared runtime and Atlas context are there when you expand.