20 MB of Panels iOS is bloat from binary symbols in the app ⚖️
There's also another couple MB of savings from optimizing images, videos, and removing duplicate files
In the android app, two videos make up ~1/4 of the app size. The largest video is splash_screen.mp4 (2.6 MB)
These type of videos are a great example of where dynamic features can be used. Once a user makes an account, they'll never see it again so the video could be offloaded
We did see the use of Kotlin in the iOS app 👀
Specifically we see Panels using Skie from @TouchlabHQ for ActionWalls 🤖
Finally, some libraries Panels is using
Firebase, @RevenueCat, Lottie, Kingfisher
Pic is all the dynamically linked Firebase frameworks
Thanks to all who tagged us about this ☺️
We'll continue to monitor the Panels app and can report on any big changes 🫡
Let us know what you think and if you have any questions! Full analysis links 👇
Let's take a look at why the @SantanderUK iOS app is at a whopping 613.3 MB and how 35% of it does nothing for the user 🧐
Right off the bat, it looks like most of the app (587.6 MB) is dynamic frameworks
Dylibs let you share code between targets, but are larger than static frameworks b/c static let's the compiler strip dead code. It's likely that Santander doesn't need ALL of those to be dynamically linked
Also, note the "String Tables" in the dynamic frameworks— these are unnecessary binary symbols that can be stripped out and save 215.5 MB (35% of install size) for Santander UK 🤓
Another day, another "How is this app so big tweet" 🤓
This time its the @DJIGlobal iOS app, which comes in at 1 GB
A lot of the comments speculated that the app was large due to assets & while there are 155 MB of .mp4 video files, the bulk of the size is coming from ML models
There's 264 MB of .mlmodelc files - these are compile Core ML Models which are designed to run on Apple devices. Some of the biggest models 👇
Here's a top level view of the latest version of LinkedIn
300 MB for just dynamically linked frameworks & Plugins is...a lot. In fact, just the Dylibs & Plugins today are bigger than the entire app was back in November 2022 🫠
And the Plugins and Frameworks seems to be where the greatest inefficiencies lie. Here is a more detailed look at the LinkedIn Plugins + the dynamically linked VoyagerLibs.framework
Finding accessibility issues in an app is an incredibly manual task that can take hours depending on the size. Which seems like a perfect place for ✨AI ✨
🧵Surfacing accessibility issues in the @Drizly app w/ AI 🧠
A quick background - our Snapshots product turns Previews into snapshots. A recent feature gives the ability to use AccessibilitySnapshot w/ one line
You don't need to write test code to get snapshot tests or to snapshot VoiceOver elements
We can take snapshots for any app leaking Previews into production, which @Drizly (and many other apps) are. We were able to generate 86 snapshots for Drizly
We then fed these images into an AI we're working on to detect accessibility errors. Here's what we found