Xcode for developers on Mac: builds, errors and previews with Lazur in Xcode 27

People search this phrase for three reasons. They are setting up Xcode on a new Mac. Their builds have slowed to a crawl. Or they want help inside Xcode without installing a plugin. This page covers all three, in the order you usually hit them.

Check your Mac before you install Xcode 27

Xcode 27 is a large update, and it does not suit every Mac. Check three things before you click Update. Look at your chip, your macOS version and the Xcode version your team uses. Each one can block a build or a launch.

• Chip: a third-party summary says Xcode 27 installs only on Apple silicon Macs. Intel Macs should stay on an older Xcode.
• macOS: the same summary says Xcode 27 needs macOS Tahoe 26.4 or later. A search result pointed to 26.6, so verify before you update.
• Team: agree on the version with your team first. A project that builds on Xcode 26 may need small changes.
• Disk space: Xcode and its simulators take real room. Check Storage in System Settings before the download. For a full guide, read how to free system data storage on a Mac.

Create your first project the right way

Start from File > New > Project in Xcode. The Welcome window offers the same choice. Pick a platform, then pick a template. The three templates people use most are Single View App for iOS, App for macOS and Watch App for watchOS.

1. Choose File > New > Project, or click New Project on the Welcome window.
2. Pick the platform, such as iOS or macOS, then select the template you need.
3. Enter a product name and an organization identifier. Use a reverse domain style identifier, such as com.yourname.
4. Choose your team, language and interface. Add unit or UI test targets now if you plan to test. You can add them later, but it is quicker now.
5. Turn on Create Git repository on my Mac. Apple's help page recommends this option.

The Git choice matters more than it looks. When a merge goes wrong later, you need a clean history to return to. If it does go wrong, see how to resolve git merge conflict markers step by step.

Keyboard shortcuts and menu paths for Xcode on Mac

You do not need every shortcut on day one. Learn the six in the table first. Each one replaces a trip to the menu bar. Menu paths follow the order you click, so you can find the command again later.

Navigators hold most of your debugging data. Press ⌘5 for the Issue navigator and ⌘9 for the Report navigator. The Report navigator keeps build logs, which you need for the speed work below. If a shortcut does nothing, another app may be taking the key first.

Why Xcode builds get slow, and how to fix them

Slow builds come up often in Apple Developer Forums threads. Those posts are anecdotes, not a survey. Still, the same causes repeat across them, and most of them are fixable. Start with Run Script phases, then compiler settings, then provisioning.

The most useful advice comes from an Apple engineer in one thread. Declare inputs and outputs for every Run Script phase. Without them, Xcode cannot tell when the script needs to run again. It may run on every build, and that adds up.

One team cut a build from 44 seconds to 14 seconds. They removed objective-c++ from MODULE_VERIFIER_SUPPORTED_LANGUAGES, a build setting. The trade-off is that the verifier no longer checks those files. Confirm your module build still passes before you keep the change.

Another thread reports ValidateEmbeddedBinary growing from about 5 seconds in Xcode 15 to about 15 seconds in Xcode 16. A reply traced part of the slowdown to explicit-module dependency scanning, controlled by CLANG_ENABLE_EXPLICIT_MODULES. Treat that as a lead, not a verdict. Measure before you change anything.

A timing routine you can repeat in one afternoon

1. Clean the build folder with Product > Clean Build Folder (⇧⌘K). Then run Product > Build (⌘B) and note the time.
2. Open the Report navigator (⌘9) and read the log for the step with the longest time.
3. Open the target's Build Phases tab. Add input and output files to one Run Script phase.
4. Change one setting at a time. Build again and compare the times.
5. Keep a change only when the time drops and the app still runs.

The same thread holds a useful clue. A poster says Xcode 26.0 fixed the provisioning slowdown, and a reply says Xcode 26 no longer contacts developerservices2.apple.com. Apple did not confirm the root cause in that thread. If the delay persists, update Xcode and measure again.

Previews, Device Hub and Instruments in Xcode 27

Previews render a view while you work. Add the preview macro to a SwiftUI, UIKit or AppKit view. Apple says selecting a control in the preview highlights the matching line in the source editor. Use that link to jump from a broken layout to the code that drew it.

Two Xcode 27 changes need checking. A third-party summary says PreviewProvider is now deprecated in favor of the #Preview macro. It also says Device Hub replaces the simulator workflow. Apple describes Device Hub as a way to prototype and test on physical devices and simulators. Treat the menu details as unconfirmed until you see them on your own Mac.

Instruments charts CPU, disk, memory and GPU performance as graphical tracks over time. Run a profile with Product > Profile (⌘I). Record while you use the slow screen, then stop. Look for the track that climbs or spikes at the moment you feel the lag.

Start with memory if the app slows down after a long session. Start with CPU if one screen stutters right away. Pick the track that matches the symptom before you open the others.

Where Lazur fits while you work in Xcode

Lazur is not a plugin. It does not run inside Xcode, and it has no partnerships with app makers. It is a voice assistant that lives in the notch of your Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud.

Ask where something is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time. It waits for each click before it moves on. Lazur does not click for you, so you stay in control of Xcode.

Hold fn to dictate. Lazur types clean, formatted text at the cursor in any app. That works well for doc comments and commit notes. Read every line before you save, because speech tools make mistakes.

Research jobs run in Lazur's own Chrome tabs through the Lazur for Chrome extension. They come back with a summary and a report. That helps when you need to compare Xcode 27 notes with a forum thread.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer you. They are not stored, and content is never used to train AI models. Read the privacy notes before you use it on client code.

Mistakes developers make in Xcode

• Trusting one forum post as a rule. Test the claim in your own project first.
• Changing five build settings at once. You will not know which one helped.
• Skipping the Git repository at project creation. Add it now so you can roll back a bad setting.
• Updating Xcode in the middle of a release without checking the team version.
• Reading only the first error. The first red line often sits below the real cause.
• Ignoring a Run Script phase because it looks harmless. Those phases are common culprits in slow builds.

Keep the previous Xcode installed until your project builds on the new one. Two versions cost disk space. They cost less than a missed deadline. Interruptions cost time too, so see how to recover focus after interruptions while coding.

Xcode Cloud compute hours and what they cost

Apple Developer Program membership includes 25 compute hours per month for Xcode Cloud. Apple defines a compute hour as an hour used to run a task in the cloud, such as a build or automated tests. Extra tiers start at US$49.99 per month for 100 hours. Apple's page does not say whether unused hours roll over, so check before you plan around them.

Use Xcode Cloud when you need builds that do not depend on one Mac. Keep local builds for learning and quick checks. A cloud build still runs your slow Run Script phase, so fix that phase first.

How many developers use Xcode

Stack Overflow's 2026 survey lists Xcode at 1,322 respondents, or 10.0% of 13,193 total. The 2025 survey put Xcode at 10% of respondents to the IDE question. These numbers measure usage, not satisfaction. They also do not count every Mac developer.

What to do next

1. Confirm your Mac chip and macOS version against Apple's release notes.
2. Open one small project and time a clean build.
3. Add input and output files to one Run Script phase, then time it again.
4. Practice the six shortcuts for a week. Write them on a sticky note if you need to.
5. Ask Lazur to walk you through the Instruments setup on your own screen.

Start with the free fixes above. If you want a voice helper on top, see Xcode with Lazur for what it does in Xcode 27. Check plans and trials before you commit. If you also write in other editors, read VS Code for developers on Mac.