Your Xcode archive and the IPA you upload can be larger than what users download. Apple delivers device-specific variants, and development artifacts can contain files users never receive. Measure the device variant before deciding which assets to cut.
Read the app thinning report
Archive the app and export a development, ad hoc or enterprise distribution build that produces all compatible device variants. Look in the output for App Thinning Size Report.txt. Apple distinguishes compressed size, the download estimate, from uncompressed size, the installed app estimate. Pick a few variants that match the devices you support and record both figures.
Record the Xcode version, release configuration and commit alongside the numbers. When you compare exports, use the same settings and device descriptors. That gives you a fairer comparison than looking at archive sizes or mixing a debug build with a release build.
Compare like-for-like releases
Imagine a new welcome video bumps one variant from 42 MB to 56 MB compressed but leaves another almost unchanged. Compare assets served to those variants, then make one change such as replacing the video with a smaller equivalent. Export again under the same settings and compare the same variants. Check the actual welcome screen on a device so you know the change kept the intended quality.
If compressed size stays stable but installation size grows, check assets and frameworks in the variant. If installed size looks fine yet the device fills after weeks of use, investigate the app’s documents and caches separately. The export report describes the bundle, while runtime storage changes as people use the app.
Confirm on App Store Connect
After a build becomes available in TestFlight or the App Store, check the size information in App Store Connect. Apple calls these measurements the most accurate for distributed builds. Save a row per device variant and track it alongside releases. This workflow comes from Apple documentation. The numbers above are illustrative.