We often see games that drain a phone's battery in an hour and a half. Even with steady 60 FPS, users still leave one- and two-star reviews — the battery melts before their eyes. Power consumption is a direct indicator of inefficient CPU and GPU usage. Optimizing battery consumption for a mobile game is systematic work: from FPS management to shaders and network requests. Over five years, we've optimized 15+ projects, increasing their battery life by 20–40%. Our certified engineers deliver measurable results. Contact us for an audit — we'll evaluate your project and propose a solution.

Main Sources of Power Waste — Battery Optimization

Unlimited FPS is the most common mistake. Application.targetFrameRate = -1 (or no explicit setting) means Unity renders as fast as it can. On modern iPhones with ProMotion displays, this can be 120 FPS in a simple menu. For a menu, 30 FPS is enough — the remaining 70% of CPU/GPU time is wasted and heats up the device.

An animated background in the main menu with 500 particles runs continuously. No pause when losing focus — no savings.

If the game requests Input.location or Input.gyro unnecessarily and doesn't disable them, sensors are polled constantly. On Android, that's a few extra milliwatts.

Small HTTP requests every 5–10 seconds keep the radio module active — one of the most power-hungry components.

How to Tell If Your Game Is Wasting Power?

Use profiling:

If the menu keeps CPU/GPU at 70%, that's a problem.

Why FPS Management Is the First Step in Mobile Game Battery Optimization?

The right strategy is different targets for different states:

// Gameplay: maximum quality
Application.targetFrameRate = 60;

// Menu, pauses, dialogs
Application.targetFrameRate = 30;

// Background calculations (loading, saving)
Application.targetFrameRate = 15;

On iOS, also account for ProMotion displays (120 Hz on iPhone 13 Pro+). Explicitly set CADisplayLink.preferredFrameRateRange via Native Plugin for fine-tuning.

In OnApplicationPause(true), reduce FPS to minimum or stop rendering entirely.

How to Optimize Shaders for Battery Savings?

On mobile GPUs, computation precision matters. Using half-precision instead of float in shaders on Adreno and Mali yields real energy savings. The ALUs of these chips are optimized for half-precision. For most effects (color, UV, lighting), half precision is sufficient.

Baked lightmaps instead of dynamic lighting reduce fragment shader load by 3–5 times — a direct comparison: baked lightmaps beat dynamic lighting by 3–5 times in GPU load. Complex fragment shaders with many texture samples are especially expensive — each tex2D stalls the pipeline.

Comparison of rendering approaches:

How to Perform an Initial Power Consumption Diagnosis?

1. Set target FPS for each state (gameplay, menu, pause).
2. Check shaders: replace float with half, bake lightmaps.
3. Configure network request batching — buffer and send in a batch once per minute.
4. Profile on a real device using Xcode or adb.

Network Request Batching

Instead of sending events one by one — batching (buffering and sending in a batch once per minute). Firebase Analytics does this automatically. If using custom analytics via HTTP — an explicit RequestQueue with a timer.

On Android, WorkManager with setRequiresBatteryNotLow(true) postpones non-critical requests until the device is charging.

What Is Included in the Audit and Optimization?

• Code and project configuration analysis.
• Profiling on real devices using Xcode Energy Organizer and Android Vitals.
• FPS configuration by context (gameplay, menu, background).
• Shader optimization (conversion to half-precision, baking lightmaps).
• Network request batching implementation.
• Retesting and a report with metrics.
• Guarantee of 20–40% increase in battery life.

Timeline: 1 to 4 weeks depending on codebase size. Pricing is determined individually. Get a consultation on battery optimization today.

Verification of Results

iOS: Xcode Energy Organizer + MetricKit. MXCPUMetric and MXGPUMetric in didReceive provide real consumption data from user reports.

Android: Android Vitals in Play Console → Battery → Excessive wakeups. If the app wakes the device more than 10 times per hour in the background, it's a flag from Google that affects visibility.

For local testing: adb shell dumpsys batterystats --reset before the test and adb shell dumpsys batterystats after.

Our certified engineers conduct an audit and propose a solution with a guarantee of 20–40% increase in battery life. Contact us for an audit — we'll evaluate your project and propose a solution.

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.