Build

Prepare releases, watch crashes, inspect builds, and test with less friction.

Get a Release Ready to Leave Your Mac

Build gathers the tools for checking your app, preparing a release, and making sense of problems found during testing. It's a handy place to hop between local Simulator work, TestFlight feedback, crash metrics, and your release checklist.

Different tools need different setup. Overdrive works with local development tools, TestFlight needs App Store Connect, and Build Insights reads build logs from your Mac. You don't have to set up all of them just to use one.

Start With the Release

Use Release Checklists to create a repeatable set of checks, then make a separate checklist for the version you're preparing.

A checklist is great for the things that are easy to forget: trying a fresh install, checking an upgrade from the previous version, testing important links, or reviewing the store copy. Keep the steps specific enough that you'll know whether they passed.

Icon Editor can help you make a recognizable development icon while your final artwork is still in progress.

Test Locally

Launch Kickstart Overdrive for Simulator controls, design comparison, captures, location changes, accessibility overrides, and deeper inspection tools.

Use it to set up the conditions you need, then run through the behavior you're testing. A repeatable location or saved notification is a lot more useful than trying to remember the exact state from yesterday.

Learn From Beta Builds

TestFlight brings builds, tester groups, test information, and feedback together. Give testers a clear description of what changed, then turn the reports that need work into tasks.

Crashes shows available crash metrics and version breakdowns. Use it to spot a release that needs a closer look, alongside individual TestFlight crash feedback and your debugging tools.

Keep the Development Loop Moving

Build Insights shows how long Xcode builds are taking using existing build logs. It's a good place to check whether a slowdown is a real trend before you start trying to fix it.

A practical release routine is to prepare a checklist, test locally, review beta feedback, and revisit the checks after your fixes. Each tool handles a different piece of that process.