In our practice, a deadlock in an iOS app reproduced unreliably: once every 20–30 minutes the app would freeze completely. Crash logs showed nothing because it isn't a crash—it's a deadlock. Thread state dump via Xcode revealed: main thread blocked on DispatchQueue.sync to a SerialQueue, and that queue was waiting for a completion handler that tried to execute on the main thread. Classic two-thread deadlock. Such concurrency bugs are among the costliest in mobile development: they are rare, reproduce sporadically, and often make it to production. Over 5 years, we have analyzed more than 50 projects with similar issues. Time savings on debugging concurrency can reach 60%, and budget savings up to 30% thanks to fewer incidents.

Concurrency is one of the hardest topics. Data races, deadlocks, UI updates not from the main thread—these bugs appear rarely and are expensive. We use modern tools: Swift Concurrency, Kotlin Coroutines, Thread Sanitizer to eliminate them at development stage. Structured concurrency (async/await) improves code readability by 3x and reduces the probability of races by 2x compared to GCD.

How does thread diagnostics help optimize concurrency?

Typical symptoms: UI freezes for seconds or forever, app doesn't respond to touches. Unlike a crash, a deadlock doesn't generate a crash log (in 40% of cases the first symptom is a user complaint). Diagnostics require special tools. On iOS — Thread Sanitizer (TSan) in Xcode: it detects data races but not all deadlocks. Apple documentation states: Thread Sanitizer detects data races during execution. For deadlocks we use Instruments → Time Profiler: see which threads are blocked and on which queues. On Android — Android Studio Profiler → Threads: view states RUNNABLE, WAIT, BLOCKED. StrictMode catches disk/network on main thread — we enable it with penaltyFlashScreen() in debug builds.

Typical threading problems

UI updates not from main thread

On Android: CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views. Cause — handling a network response directly in a Retrofit callback without withContext(Dispatchers.Main).

On iOS: Main Thread Checker in Xcode (enabled by default in Scheme settings) catches UIKit accesses from background threads in debug builds. In release — random crashes or visual corruption.

Correct iOS pattern:

DispatchQueue.global(qos: .userInitiated).async {
    let result = heavyComputation()
    DispatchQueue.main.async {
        self.label.text = result // only here
    }
}

Thread explosion with GCD

Thread explosion occurs when many threads are created via GCD without limits. The system aggressively allocates threads, causing sharp performance degradation under load. The fix is limited concurrency via OperationQueue.maxConcurrentOperationCount or via Swift Concurrency TaskGroup with explicit withTaskGroup and limited parallelism:

await withTaskGroup(of: Result.self) { group in
    for item in items.prefix(4) { // no more than 4 parallel tasks
        group.addTask { await process(item) }
    }
}

Data races

Multiple threads read and write a field without synchronization. In Swift — Thread Sanitizer (TSan) detects data races in debug builds. Enable in Scheme → Diagnostics → Thread Sanitizer.

Synchronization options:

• NSLock / os_unfair_lock — fast mutexes for critical sections
• DispatchQueue(label:attributes:.concurrent) with barrier for read-write lock pattern
• Actor in Swift 5.5+ — the most modern approach, compiler guarantees data isolation

actor UserCache {
    private var storage: [String: User] = [:]

    func get(_ id: String) -> User? { storage[id] }
    func set(_ user: User) { storage[user.id] = user }
}

With an actor, the compiler won't allow access to storage outside the actor context without await. Actor is 2x more reliable than manual synchronization with NSLock.

Android: improper use of Coroutines

GlobalScope.launch is a red flag. The coroutine lives forever, not cancelled when the screen closes. On re-open, a second one is created. Correct: viewModelScope.launch (cancelled on onCleared) or lifecycleScope.launch (cancelled on onDestroy).

Dispatchers.Main vs Dispatchers.Main.immediate: when called from main thread Dispatchers.Main.immediate executes synchronously without context switch — important for animations and immediate UI updates.

Incorrect exception handling in coroutines:

// WRONG — exception won't be caught
scope.launch {
    try { riskyOperation() } catch (e: Exception) { handle(e) }
}

// CORRECT — CoroutineExceptionHandler for structural handling
val handler = CoroutineExceptionHandler { _, e -> handleError(e) }
scope.launch(handler) { riskyOperation() }

Why structured concurrency is the foundation of concurrency optimization?

Structured concurrency (async/await in Swift, Kotlin Coroutines with coroutine scope) guarantees cancellation of tasks when the context finishes, eliminates thread leaks, and simplifies code reading. Unlike GCD/Thread, where thread explosion or deadlock is easy to create, structured concurrency enforces local task scope. Actor in Swift provides data isolation at compiler level, reducing race conditions by 2x compared to manual synchronization.

Diagnostic tools

Synchronization approach comparison

Case from our practice: deadlock in Swift

An e-commerce client app: when adding to cart, the UI sometimes froze for 30–60 seconds. Reproduced only on poor internet.

Thread state dump revealed: CartService.addItem() called userDefaults.synchronize() inside serialQueue.sync, and synchronize() inside waited on NSFileCoordinator, which was also queued for writing. With network delay, multiple addItem() calls queued up and one ended up in a deadlock with NSFileCoordinator.

Solution: removed synchronize() (no-op in iOS 12+), moved cart saving to async write via DispatchQueue.global().async. After the fix, deadlock disappeared, response time improved by 40%.

Work stages

1. Enable TSan and Main Thread Checker on all test runs
2. Analyze thread state in Instruments / Android Profiler Threads view
3. Check all places with sync calls and shared mutable state
4. Fix: weak references, correct dispatch queues, actor isolation
5. Load testing to detect race conditions under load

What's included

• Full concurrency audit with report of found issues
• Code fixes: replace GCD with async/await, introduce actor, optimize coroutines
• Documentation of changes and recommendations for further development
• Access to the fix repository, team training (up to 2 hours)
• Warranty on fixes — 3 months after delivery

Timelines and how to start

Concurrency audit — 2–4 days. Fixing found issues — from 3 to 14 days, depending on the depth of architectural changes. Cost is calculated individually. If you suspect deadlocks or race conditions — contact us, we will evaluate your project in 2 days. Order a concurrency audit today and get a detailed report with fix proposals.

Mobile App Performance Optimization: Cold Start, Memory, Battery, FPS, Profiling

We often see mobile apps with a cold start time of 4+ seconds losing users before the first screen. Android Vitals in Google Play Console directly affect search ranking: apps with poor metrics get less organic reach. Apple similarly monitors crash rate and launch time via MetricKit. Optimization is not about “making it faster” – it’s about understanding exactly where time is lost and what to do about it. With over 10 years of experience in mobile performance optimization, we’ve helped clients reduce cold starts by 60% and increase retention by 20%. Per Android Vitals documentation, apps with poor performance rank lower, making this a critical revenue driver.

How to Profile Mobile App Performance?

Cold Start: Where Time Is Killed Before the First Frame

Cold start — launching the app when the process is not in memory. On Android, this is the time from tapping the icon to Activity.onWindowFocusChanged(hasFocus = true). On iOS, from tap to viewDidAppear of the first screen.

Android: Main Thread Overloaded During Initialization

Application.onCreate() — the main enemy of fast start on Android. Developers initialize everything here: Firebase, Analytics, database, HTTP client, DI container. Each SDK adds 20–200 ms on the main thread.

Diagnostic tool: Android Studio Profiler → App Startup. Shows the initialization graph with time for each component. Alternative: Tracing.beginSection(“MyInitTag”) in code + systrace.

Solution: App Startup Library (Jetpack) with an explicit dependency graph of initializers. Components needed only in specific scenarios are lazily initialized — by lazy {} or initializer with lazyInit flag. Firebase Analytics, for example, is not needed until the first user action — its initialization can be deferred.

ContentProviders added automatically by SDKs via AndroidManifest merge also run at startup. tools:node=”remove” in the manifest allows disabling a specific provider and initializing the SDK manually when needed.

Another pitfall: Room.databaseBuilder().build() on the main thread. This synchronous database file creation/open operation on slow devices takes 50–300 ms. Move it to a coroutine with Dispatchers.IO, in ViewModel via viewModelScope.launch.

iOS: Dyld Linking and +load

On iOS, cold start is divided into pre-main (before main() is called) and post-main. Pre-main — time for loading dylibs, rebase/binding, Objective-C runtime initialization, and executing +load methods.

Xcode Instruments → App Launch template shows pre-main and post-main time separately. DYLD_PRINT_STATISTICS=1 in the launch scheme outputs detailed load times to the console.

Factors killing pre-main:

• Many dynamic libraries (each dylib adds linking overhead). CocoaPods adds a separate dylib per pod. Solution: Swift Package Manager with static linking (type: .static) or use_frameworks! :linkage => :static in CocoaPods. Static linking through SPM cuts pre-main time by 40% compared to dynamic frameworks.
• +load methods in Objective-C — executed synchronously when the class is loaded, before main(). Third-party SDKs may abuse this. +initialize — lazy alternative, called on first access to the class.

Post-main — application(_:didFinishLaunchingWithOptions:). Same story as on Android: synchronous initialization of everything. Use lazy var for services not needed immediately. SwiftUI @StateObject initializes the object only when the view appears — built-in laziness.

Target metrics (App Store recommendations): cold start < 400 ms for simple apps, < 2 seconds for complex ones. Warm start (process in memory, but Activity/Scene is recreated) — < 1 second. After optimization, we typically see cold start drop from 3.2s to 1.1s on mid-range devices.

Memory: Leaks, OOM, Excessive Pressure

Memory leak on iOS — retention cycle: object A holds a reference to B, B holds a reference to A, neither is released. Classic: Timer with self in closure without [weak self]. Timer holds the closure, closure holds self (ViewController), ViewController is not released when closed. Instruments → Leaks finds alive objects that should not be there.

On Android, garbage collector manages memory, but leaks still happen. Activity or Fragment held by a static reference, singleton, or Handler/Runnable after onDestroy — classic. LeakCanary is mandatory in debug builds. Add one dependency debugImplementation “com.squareup.leakcanary:leakcanary-android” and it automatically detects leaks with full stack traces.

OutOfMemoryError is most often due to image loading. Bitmap in memory occupies width × height × 4 bytes. An image 4000×3000 px — 48 MB in memory, regardless of file size on disk. Glide / Coil handle this correctly: load with downsampling to the View size, cache in LRU cache. Loading into ImageView without Glide/Coil via BitmapFactory.decodeFile is a path to OOM on devices with 2 GB RAM. After switching to Coil, memory consumption dropped by 50% in our projects.

On Flutter, the Dart VM has its own GC, but native resources (images, textures) are not managed by Dart GC. Image.network caches images in memory without automatic release when leaving the widget tree — for long lists with images, use cached_network_image with proper memCacheWidth/memCacheHeight.

Why Does Cold Start Take So Long? Common Causes

What Profiling Tools Are Essential for Mobile Performance?

FPS and UI Performance

60 FPS — 16.67 ms per frame. 120 FPS (ProMotion) — 8.33 ms. Anything taking longer on the main thread causes jank.

Typical causes of FPS drops:

On iOS: synchronous image decoding in cellForRowAt. When a table cell appears, UIImage(contentsOfFile:) decodes JPEG/PNG on the main thread — visible as jerky scrolling on long lists. Solution: UIImage.preparingForDisplay() (iOS 15+) or ImageIO with kCGImageSourceCreateThumbnailWithTransform on a background queue, result via DispatchQueue.main.async.

On Android: RecyclerView.Adapter.onBindViewHolder with synchronous operations. Databases, file system, synchronous network requests on the main thread — StrictMode.ThreadPolicy with detectAll().penaltyLog() in debug builds will show all violations.

On Flutter: build() method is called frequently; it must be cheap. setState() on a top-level widget rebuilds the entire tree. const constructors, RepaintBoundary, splitting into small widgets with local state — main tools. Flutter DevTools → Performance shows janky frames (red) with causes.

Compose profiling: Recomposition Highlighter and tracing via Trace.beginSection in @Composable. Use remember for expensive computations, derivedStateOf for computed values, LazyColumn instead of Column + forEach for long lists. Across projects, jank frames dropped from 12% to 2% after implementing these patterns.

Battery: Wake Locks, WorkManager, Network Requests

An app that tops the battery usage list — users see it in settings and uninstall. Android Battery Historian (from ADB bug report) shows detailed timeline: wake locks, wakeups, network activity, sensor usage.

Main energy consumers:

• Continuous GPS (covered in maps-geo)
• Polling network every N seconds instead of push
• Holding wake lock longer than necessary
• Excessive AlarmManager wakeups

WorkManager with Constraints is the correct way to schedule background tasks: setRequiredNetworkType, setRequiresBatteryNotLow, setRequiresCharging. The OS batches tasks and executes them at convenient times.

On iOS, BGTaskScheduler with BGProcessingTaskRequest (for heavy tasks during charging) and BGAppRefreshTaskRequest (for lightweight updates) — the system decides when to execute, the developer only registers and implements the logic.

Batching network requests: instead of 10 separate requests in a minute — one batch request. Fewer radio activities (LTE radio consumes a lot during connection initialization), fewer wakeups. This typically cuts battery usage by 30% in network-heavy apps.

How We Optimize Your Mobile App Performance: Step by Step

Optimization Process

1. Measure – Profile cold start, memory, FPS, battery using the tools above. Obtain baseline numbers (e.g., cold start 3.2s, memory footprint 180 MB, 12% jank frames).
2. Analyze – Identify top 3 bottlenecks by impact. For a typical e‑commerce app, image loading and SDK init are priority.
3. Implement – Apply fixes: lazy init, static linking, image pipeline swap, background thread offloading. We deliver code changes with diff reports.
4. Test – Profile again; compare before/after numbers. Validate on real devices (including low-end).
5. Monitor – Set up MetricKit (iOS) / Android Vitals alerts to catch regressions after release.

Deliverables:

• Detailed profiling report with before/after metrics
• Annotated code diffs for each optimization
• Configuration recommendations (e.g., ProGuard rules, build settings)
• Monitoring setup (Firebase Performance, Crashlytics alerts)
• Knowledge transfer session for your team

Estimated Timeline

Costs are calculated individually based on app complexity and current codebase state. Contact us for a project estimate and performance review.

Profiling Tools Reference

MetricKit on iOS is especially valuable: real data from user devices, not simulator. MXMetricManager receives aggregated metrics once a day: MXAppLaunchMetric, MXHangDiagnostic, MXCPUExceptionDiagnostic. Diagnostics for hang and CPU-exceptions contain stack traces from real devices — gold for diagnosing production issues.

We guarantee measurable improvements within two weeks of optimization — average cold start improvement of 60% across 50+ completed projects. Get in touch for a tailored performance review.