When we reach for it
iOS work where the product is the device — camera and capture, offline behaviour, background processing, accessibility, and anything depending on a framework Apple released this year.
Swift development
Apple’s language for iOS, iPadOS and macOS, and the only way to reach the newest platform capabilities on the day they ship rather than when a bridge catches up.
When we would argue against it
Two native codebases cost roughly twice as much to build and considerably more than twice as much to keep in step. If the interface is mostly screens over an API, we will say so and propose React Native instead.
What it looks like in delivery
Where we write Swift, it is usually for the layer that has to be reliable when the network is not: durable local storage, an outbox that survives termination, and capture flows a field worker can complete with one hand and no signal.
Where this appears on the site
Published work that names it
- Making offline receipt capture reliable in Vertigem's expense platformCase study · architecture
- Mobile developmentService · stack
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Working in Swift?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.