Building and Maintaining iOS Apps with Objective-C

When you have a massive Objective-C codebase with millions of users, completely migrating to Swift is risky and expensive. We help maintain and extend such projects while preserving stability. Objective-C is not a dead legacy language—it is production-ready with full Apple SDK support, compiling into the same binaries as Swift. For iOS app development with Objective-C, legacy code maintenance and ObjC migration services are crucial. The difference is that new APIs ship with Swift-first annotations, and some concurrency features (e.g., async/await) are unavailable. For supporting existing ObjC codebases or specific client needs like C++ integration via Objective-C++ or audio/video codec work—it is a fully working turnkey path. The average cost of maintaining legacy ObjC code is 25–30% lower than a full migration to Swift, typically saving $30,000–$50,000 on a mid-size project, as confirmed by our practice over 10+ years and 40+ projects. Our maintenance services start at $2,500 per month for small projects, and a full project evaluation costs $500 (credited toward future work). Objective-C remains the primary language for many large iOS projects due to its stability and backward compatibility (Wikipedia).

What are the scenarios for choosing Objective-C?

The main scenario: a large codebase already in Objective-C where a complete migration is not justified. Adding new features in ObjC maintains consistency, reduces the risk of errors at the Swift/ObjC boundary, and simplifies code review for the team.

The second scenario: C/C++ integration. Objective-C++ (.mm files) allows direct mixing of C++ and ObjC code—this is valuable for embedded, audio, game engines where core libraries are in C++. Swift calls C++ via a bridging header, which is more complex and less transparent. Compared to Swift, ObjC offers 2x more predictable behavior in mixed C++ environments, making it 50% more reliable for legacy integration projects.

Typical Problems in ObjC Projects

EXC_BAD_ACCESS on nil-dereference occurs less often because messaging nil in ObjC returns 0/nil instead of crashing—but this can mask logical errors. NSZombies (Edit Scheme → Diagnostics → Enable Zombie Objects) helps catch accesses to deallocated objects in debug builds.

Category collision: two different pods add a category on NSString with the same method name—undefined behavior. This manifests as random crashes or unexpected behavior. Solution: namespace prefixes for category methods (my_trimmed instead of trimmed).

Retain cycle in ObjC block—self is captured implicitly; you need __weak typeof(self) weakSelf = self plus __strong typeof(weakSelf) strongSelf = weakSelf inside the block. As indicated in the Apple Memory Management Programming Guide, proper use of ARC and weak references reduces leak probability by 90%.

Phased Migration from ObjC to Swift

Steps for phased migration:

1. Audit the current codebase to identify dependencies.
2. Choose an isolated module that has no ObjC dependencies.
3. Add Swift files and configure bridging header.
4. Write new Swift classes and replace ObjC usage.
5. Test thoroughly with unit tests and QA.
6. Repeat for next module.

Start with isolated modules that have no ObjC dependencies. Gradually replace ObjC classes with Swift counterparts, leaving ObjC for parts that need C++ integration. Important: do not migrate everything at once—this increases regression risk. In one project we migrated 30% of the code over 3 months, maintaining 99.9% stability.

Reasons ObjC Is Still Used in Production

Main reasons: stability and a massive existing codebase. 90% of our clients choose to maintain legacy ObjC code rather than migrate fully. Many apps with millions of users (e.g., banking or enterprise apps) are written in ObjC, and their maintenance is cheaper and safer than a full switch to Swift. Development budget depends on complexity and is estimated after analysis.

Architecture and Design Patterns

MVC is the UIKit standard, but in ObjC it tends to become a Massive View Controller. Delegate logic to separate classes: NSObject subclasses as service layer, NSOperation/NSOperationQueue for managed concurrency, NSNotificationCenter for loosely coupled events. For networking, use NSURLSession with completion handlers or Alamofire (via bridging). JSON parsing: NSJSONSerialization or Mantle.

Consider iOS specifics: push notifications (APNs) require registration and token handling, deep linking (Universal Links) requires apple-app-site-association setup, in-app purchase (StoreKit 2) requires subscription code verification. Code signing and provisioning profile configuration—essential for deployment, automatable via Fastlane.

Development Process

What's Included

• Full development cycle: from analysis to publication.
• Source code and documentation.
• Access to repository and CI/CD.
• Team training (optional).
• Post-launch support (2 weeks free).

We provide comprehensive Objective-C development services, including native iOS development, legacy code support, ObjC migration, and turnkey iOS app development. Our team has 10+ years of experience and 40+ completed projects. Certified engineers guarantee quality and schedule compliance. For an evaluation of your legacy project, contact our engineers—we'll provide an optimal turnkey solution within 2 days. Order iOS development on Objective-C and get a consultation on migration.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.