This is actually surprisingly common, much more so these days with cookie cutter repositories.
There are large communities of developers who feel better with a large toolkit of functionality in a build environment, where a typical project may only benefit from a fraction of the included libraries
My limited experience of iOS dev suggests this is less of a problem Here, but I’m sure still is a factor
In my experience, these tend to be the same type of developers who tend to copy-paste code extensively and not really understand what they're doing. They may be really good at finding these "cookie cutter" solutions and following instructions, but when asked to actually explain, they're unable to. This is particularly problematic for debugging, when you ask one of these developers about the reason for the way something is written and he doesn't know beyond the fact that he saw and copied it from somewhere.
If you take a closer look and think about it you often easily spot some no brainers like simply applying compression or reduce the quality of media assets to something that actually makes sense.
Also see if there are any tools for your environment specifically made to find issues, unused assets and so on. This allowed me to easily remove 200+ unused images yesterday. All in all I removed and compressed 18mb of unused images and files and counting.
If anyone is wondering, since it is related to iOS as well, I used Slender. Highly recommended but use with care, since it has false positives and false negatives. I double checked almost all files it found.
1. Wrote to disk the entire payload actually required/retrieved for the user to be both authenticated and invoke meaningful business logic.
2. Compress each component in a manner representative of the transfer medium. Save them in a separate directory tree as the uncompressed data.
2a. If you aren't using any compression in your payload, apologize to your users and start using it. Return to Step 1.
3. From here you can use standard filesystem tools to view payload composition by media type, compressibility, etc.
4. Identify the largest consumers of space in the payload and research how to reduce their size.
5. Implement reductions identified in research.
These steps should really be all you need in most scenarios.