Objective-C.
Objective-C is the language iOS and macOS were built on before Swift, still present in long-lived applications and in many binary frameworks. It is dynamically dispatched with a C foundation, which makes it flexible at runtime and considerably less safe at compile time.
Where Objective-C fits on a long engagement.
Objective-C work is almost entirely maintenance, and the reason the code survives is usually that it works. A view controller written in 2014 that has shipped without incident for a decade is not a defect; rewriting it in Swift for consistency is a cost with no user-facing benefit unless something else forces the issue.
The practical risk is the shrinking pool of people who are genuinely comfortable in it. Manual memory semantics, the runtime's dynamic behaviour and category conflicts are unfamiliar to specialists who started after Swift, and a small mistake at the interop boundary produces crashes that are difficult to attribute.
What an assigned team does with Objective-C.
On a mixed estate the right strategy is usually containment rather than migration: Objective-C stays where it is stable, new work happens in Swift, and the boundary is kept explicit. That is a policy held over years rather than a decision made once.
Holding it needs specialists who know which parts of the estate are load-bearing, which is knowledge that accumulates in a standing assignment. What that continuity costs and how it is agreed is set out in how the monthly fee is built.
What we use Objective-C for.
- Maintaining stable legacy without rewriting it Changing code that works, safely, rather than replacing it for consistency alone.
- A clean Swift interop boundary Nullability and generics annotated so the Swift side gets accurate types instead of implicitly unwrapped guesses.
- Migrating only where there is a reason Rewriting the modules that genuinely block new work, and leaving the rest.
How Objective-C capacity is assigned.
Objective-C capacity is assigned inside mobile development under software development outsourcing, normally alongside Swift rather than on its own.
Tell us what your roadmap needs Objective-C for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.