MenuRun
Build and run from the menu bar.
Pick a simulator, a paired iPhone or your Mac, and hit play. MenuRun builds, installs and launches your app while Xcode stays closed.
Atlas CompileSwift MapView.swift Atlas Ld Atlas.app/Atlas Atlas CodeSign Atlas.app Atlas ** BUILD SUCCEEDED ** Atlas Installing on iPhone 16 Pro… Atlas Launched in 14s Pebble Booting iPad Air (M2)…
- One row per project. Drop an .xcodeproj, .xcworkspace or its folder on the panel
- Several destinations at once, each with its own status and log
- iPhones and iPads over cable or Wi‑Fi, every simulator, My Mac
- One-word status: Resolving, Building, Installing, Ran in 12s, Failed
- Live build log, filtered by project
- Setup guide that checks Xcode, signing, runtimes and Developer Mode
- Automatic updates, once a day
- Free up space: clear old DerivedData, stale simulators and device support files
- ⌘R from anywhere to re-run the last build
- Notify me when a long build finishes
- Run tests, not just the app, with pass/fail in the row
- Release builds and TestFlight upload
- Screenshot every simulator in one go
- Build history with timings per project
- Shortcuts app actions
No. You still write code in Xcode or your editor of choice. MenuRun only builds and runs, using the tools Xcode already ships.
Yes. MenuRun calls xcodebuild, simctl and devicectl from whichever Xcode is selected on this Mac.
No. Device builds allow provisioning updates, the same as Xcode does. Your team and certificates stay as they are.
Into Xcode’s own DerivedData. Builds stay incremental and are shared with Xcode.
The one you picked last, else one named after the project, else the first. Override it per project from the ⋯ menu. Always Debug.
Yes, once it’s paired with this Mac. A green glyph next to the device means it’s reachable right now.
macOS asks the first time MenuRun reads a project in Desktop, Documents or Downloads. Allow it once.
MenuRun checks once a day. When there’s a new version, a link appears in the panel.
Yes.