---
title: "Xcode | Skills We Assign For | Azendo"
description: "Xcode as the Apple toolchain — Instruments, code signing, simulator limits, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/xcode/"
---

[Skills](https://azendo.co/skills/) Mobile platforms and frameworks 

# Xcode.

Xcode is Apple's IDE and the only supported way to build and submit Apple-platform applications. It carries the compiler, Interface Builder, simulators, Instruments for profiling, and the signing and submission workflow.

## Where Xcode fits on a long engagement.

Code signing is the part of Xcode that consumes disproportionate time on every team. Certificates, provisioning profiles, capabilities and team membership interact in ways that produce errors which do not describe the actual problem, and the fix is often in the developer portal rather than in the IDE reporting it.

Instruments is the underused counterpart. Time Profiler, Allocations and Leaks answer performance questions definitively, and the Energy Log matters on a platform where users attribute battery drain to specific apps. Teams that never open Instruments ship performance problems they could have measured.

## What an assigned team does with Xcode.

Signing configuration is exactly the kind of knowledge that lives in one person and blocks everyone when that person is unavailable. Automating it in CI and documenting it is a small piece of work that removes a recurring delivery risk.

Where the release path rather than the code is the constraint, that automation is scoped under [devops as a service](https://azendo.co/services/cloud-and-devops/) alongside the application capacity.

## What we use Xcode for.

* Signing that is not one person's knowledge Certificates and profiles automated in CI, so a submission never waits on an individual.
* Performance measured in Instruments Time Profiler and Allocations used before optimising, so effort goes where the cost is.
* Simulator and device used appropriately Logic verified in the simulator, performance and camera work verified on hardware.

## How Xcode capacity is assigned.

Xcode and signing work sits inside iOS capacity, with the release path automated rather than held as individual knowledge.

## Roles we assign Xcode for

* [iOS Developer Mobile development](https://azendo.co/services/mobile-development/ios-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in mobile platforms and frameworks

* [SwiftUI — skill we assign for](https://azendo.co/skills/swiftui/)
* [UIKit — skill we assign for](https://azendo.co/skills/uikit/)
* [Jetpack Compose — skill we assign for](https://azendo.co/skills/jetpack-compose/)
* [Coroutines — skill we assign for](https://azendo.co/skills/coroutines/)
* [Flutter — skill we assign for](https://azendo.co/skills/flutter/)
* [React Native — skill we assign for](https://azendo.co/skills/react-native/)
* [Expo — skill we assign for](https://azendo.co/skills/expo/)
* [Ionic — skill we assign for](https://azendo.co/skills/ionic/)

## Tell us what your roadmap needs Xcode for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)