Automated Version-to-Version App Size Tracking in CI/CD

Without systematic monitoring, app size grows unnoticed. Recent case: a messenger startup grew from 50 to 85 MB over three releases — conversion dropped by 12%. After we implemented automatic tracking, we rolled back the regression to 55 MB. Every megabyte above threshold costs real money: a 6 MB increase can cost $1,000 per month in lost revenue. Conversion losses can reach $10,000 monthly for popular apps.

We configure automatic version-by-version size monitoring for iOS and Android, integrated into your CI/CD pipeline. You get a transparent change history, threshold alerts, and regression blocking before release.

Why App Size Is Critical for Conversion

According to Google (Google study), every 6 MB above a certain threshold reduces install conversion by 1%. App Store warns users on mobile networks when downloads exceed 200 MB — a direct risk of losing customers. For games and media apps, the threshold is even lower: each additional 1 MB of resources reduces installs by roughly 0.5%. Controlling size directly impacts LTV and retention.

Which Tools to Choose for Size Monitoring

bundletool is ten times more accurate than manual analysis, and appstoreconnect-swift-sdk is 10x more precise than manual App Store Connect downloads. It automates data retrieval from App Store Connect. Compare effective solutions:

bundletool provides byte-level precision — an order of magnitude above manual analysis. For iOS, appstoreconnect-swift-sdk lets you get metrics without manual exports. Both tools integrate easily into GitLab CI or GitHub Actions.

What to Monitor: iOS and Android

iOS: In App Store Connect → TestFlight → App Size, you see compressed and uncompressed sizes per version per device type. App Thinning creates unique builds for specific models — monitoring each is important. Key metrics: Compressed (downloaded) size and Uncompressed (installed) size. Typical range for a medium app is 50–150 MB. Also track the linkmap size to see each library's contribution. IPA size — the final distribution file — is another metric to control.

Android: In Google Play Console → Android Vitals → App size, you see APK size and AAB download size per device. AAB automatically trims resources, so the real installed size is 10–30% smaller than the APK. Raw APK size is not always indicative — use bundletool to get the accurate download size.

Setting Up Monitoring in CI/CD

Step-by-step plan for both platforms:

1. iOS: After building xcarchive, extract size using Xcode size report or via App Store Connect API.
2. Android: From AAB, get the real download size using bundletool get-size total.
3. In CI scripts, compare size with the previous version from the main branch.
4. If a threshold is exceeded (e.g., +3 MB warning, +8 MB error), the pipeline fails or sends a notification.

java -jar bundletool.jar get-size total \
  --bundle=app-release.aab \
  --dimensions=ABI,SCREEN_DENSITY \
  --device-spec=device-spec.json

For iOS, we use appstoreconnect-swift-sdk to fetch size from App Store Connect.

Blocking the Build When Threshold Is Exceeded

This process is key protection against regressions. In the CI script, we extract the current build size and compare it to the last stable version from main. If the error threshold is surpassed, the pipeline fails. For the warning threshold, we send a notification to Slack or Telegram. This blocking prevents accidental size increases from reaching production.

Thresholds and Alerts

Actionable thresholds are set individually. For a typical app, reasonable values:

Threshold depends on app type: for a messenger, +3 MB is critical; for a game with a new level, it's normal. We configure during the assessment.

Version History of Size

We store metrics at each release in a database or JSON. Record structure: {version, build_number, date, ios_compressed_mb, ios_installed_mb, android_aab_mb, breakdown_by_category}. Breakdown by category: Resources (textures, sounds) — 60–70%, Frameworks/Libraries, Executable. On iOS, linkmap shows each library's contribution. In Android Studio, Analyze APK gives byte-level breakdown. Keeping history allows trend analysis and future growth prediction.

What's Included in the Work and Timeline

• Integration of scripts into GitLab CI / GitHub Actions
• Configuration of thresholds and alerts (Slack/Telegram)
• Creation of a dashboard in Grafana or simple JSON log
• Documentation for extension
• Team training (1-hour call)

Estimated timeline: 1–2 working days. Cost is calculated individually based on your stack and infrastructure. Get a consultation — we assess your project within 1 hour.

Our engineers have 5+ years of experience and have optimized over 40 mobile apps. Our proven methodology guarantees size control. Order size monitoring setup now — keep your app lightweight.

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.