DotIPA

https://lnkd.in/gJgscZhr #iOS #iOSDev #Xcode

🚨 New version drop 🚨 dotIPA 1.2.7 is out! We improved the drag and drop experience when inspecting builds, making it faster and smoother to analyze your builds. Give it a try and let us know what you think. https://dotipa.app/ #iOS #iOSDev #macOS #Xcode #Swift #BuildSize

Let's gooooo, another 5-star review just came in for Dotipa ⭐️⭐️⭐️⭐️⭐️ “A convenient and simple application for quick IPA analysis” Get it on the App Store: https://lnkd.in/gJgscZhr #iOSDevelopment #Xcode #AppSize #iOSDev

We just dropped Dotipa to $4.99 (one time purchase). If you build #iOS apps and care about IPA size, now is the best time to try it. Runs 100% locally on your Mac. https://lnkd.in/gYyf7rR4

We’re up on X! Follow us there for occasional #iOS app size analyses and product updates. https://lnkd.in/gjYDSQce

https://lnkd.in/gJgscZhr #ios #buildsize

When you spot duplicate mp4s totaling ~6𝗠𝗕𝘀 of duplication in the 𝘧𝘳𝘦𝘴𝘩 #sora2 iOS app from OpenAI but aren't cool enough for an access code. 📽️ cameo_onboarding_0.mp4/create_ifu_1.mp4 📽️ cameo_onboarding_2.mp4/create_ifu_0.mp4 https://lnkd.in/gcdAZ_kj https://lnkd.in/gJgscZhr

Out of curiosity, we ran the FanDuel iOS app through DotIPA to see how its ~200 MB IPA breaks down. Some interesting bits: ~57 MB of assets in a single catalog ~25 MB bundled assets as zipped packs A couple of neat Core ML models for (presumably) on-device ID verification flow (~1 MB) DotIPA can make these kinds of deep dives quick and repeatable. More build information 👉 https://lnkd.in/g7bBAs4G #appsize #iOS #appleintelligence

We're climbing the App Store charts like your build size when you forgot to compress assets, up to the 47th spot in Developer Tools this week 🥳. Also, version 1.2.1 is out today and it includes a crash fix and minor UI improvements 💥😎. #iOS #xcode

We asked ChatGPT to analyze our build metadata file for the latest #iOS app from Walmart, and here's what it came up with: 📦 Overall Size The app is ~433 MB on disk, which is very large for a consumer retail app. Most of that bulk comes from resource bundles (*.bundle) packed with images, PDFs, and animations. These account for hundreds of MBs, while the binary itself is much smaller. 🖼 Asset Observations Redundant PDFs & Images: In bundles like TippingAndFeedbackResources.bundle and ConverseResources.bundle, I saw the same images (close.pdf, driverIcon.pdf, pickupHeaderImage.pdf, etc.) repeated multiple times in slightly different sizes. Assets are duplicated with different suffixes (@1x, @2x, @3x) even when vectors (PDF/SVG) should scale. Heavy PDFs: Some PDFs in RegistryResources.bundle weigh in at 80–120 KB each (e.g. Step-3.pdf, Step-5.pdf). A dozen of those adds MBs quickly. Large PDFs could be simplified or replaced with vector assets (SF Symbols, Lottie, or optimized SVG). Lottie Animations: The app uses multiple .lottie files (SparkyAssistantLottie, SparkyTypingIndicator, etc.). These are relatively small individually (~6–14 KB), but the number of them adds up. Worth checking if animations can be consolidated or dynamically themed instead of duplicating variations (e.g. Indigo vs Default). 🌍 Localization Footprint Every bundle includes en.lproj, es-US.lproj, and Base.lproj, but many are empty (Zero KB). This bloats the app unnecessarily—consider stripping unused localizations or using Xcode’s --exportLocalizationsto confirm what’s actually needed. 🔒 Code Signature Overhead Each bundle contains a full _CodeSignature directory (~10 KB each). With dozens of bundles, this adds non-trivial size (~1 MB just for signatures). You can’t remove them (needed for iOS integrity checks), but you could consolidate bundles to reduce the number of signatures. 🔑 Key Improvement Areas De-duplicate Assets Ensure that vector assets are reused instead of embedding multiple rasterized/variant versions. Consider asset catalogs (xcassets) with universal vectors instead of separate PDFs. Bundle Consolidation Many bundles are <20 KB of metadata + ~10 KB of signatures. Grouping related features into fewer bundles would reduce overhead. Feature Modularization (Optional) Consider moving less-used features (e.g., Registry, InspirePage, Tipping & Feedback) into App Clips or on-demand resources. That way the core app download is smaller, and secondary features load as needed. ✅ Summary: Walmart’s app size is driven mostly by duplicated and heavy resource files. Biggest wins would come from asset deduplication, vectorization, and pruning unused localizations. If aggressive, modularization via on-demand resources could cut the core app down significantly. View more about this build here 👉 https://lnkd.in/gw7yvAxC