<story><title>Launch HN: Emerge (YC W21) – Monitor and reduce iOS app size</title><text>Hi everyone!&lt;p&gt;We’re Noah and Josh from Emerge (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&lt;/a&gt;). Our company is building a monitoring and analysis tool to help iOS developers reduce their app’s size.&lt;p&gt;You might have heard about app size challenges faced by large iOS apps, particularly those with Swift codebases. I was an iOS engineer at Airbnb for 4.5 years and personally worked on their size reduction efforts.&lt;p&gt;App size is tricky to quantify. The size users most commonly see (what’s on the App Store page) is the install size thinned for their device. This is the size measured after stripping out assets like images and other media not needed for your screen size, or code that doesn’t run on your device’s architecture. However, this isn’t the only size metric out there, there’s also download and universal size (read more about this in our docs [1]).&lt;p&gt;Our tool makes app size easy to understand by visualizing the size contribution of every file in your app, from localized strings to machine learning models. To better our understanding, we even reverse engineered compiled asset catalogs and Mach-O binaries to show size contributions of original images, source files and Swift modules. With this perspective we often see files that don’t belong or are suspiciously large.&lt;p&gt;While testing our tool we analyzed and learned from over 150 iOS applications and found that keeping app size in check is really hard— even for industry leaders. Here are some of our more interesting findings.&lt;p&gt;Dropbox (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;dropbox&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;dropbox&lt;/a&gt;)
From the visualization, you can clearly see why Dropbox’s iOS app is 270 MB— it’s 35% localization files. These files are duplicated from the main app into 7 different app extensions and they all include comments that provide translators with context for the strings. Just removing these comments from the production app could save 46 MB.&lt;p&gt;eBay (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;ebay&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;ebay&lt;/a&gt;)
This is an interesting architecture because although the main app’s executable is only ~150 KB, 86% of the app’s size comes from executables, the biggest one (32 MB) being EbayApp.framework. When building a Swift framework, the binary contains symbols which are not needed in the build uploaded to the App Store. These symbols can be stripped using the method described in our docs [2]. Stripping binary symbols would reduce Ebay’s app size by over 40%. Emerge can generate a script to add to your Xcode build phase to strip symbols for you.&lt;p&gt;Spark (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;spark&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;spark&lt;/a&gt;)
About 1&amp;#x2F;10th of Spark’s ~230 MB app is font files. 10 MB of those font files are duplicates found in an app extension. After a closer look, the fonts duplicated are all SF-Pro-Text, look familiar? These have been system fonts since iOS 11 (the minimum version for Spark). If the system font was used directly, 10% of the whole app could be deleted!&lt;p&gt;If you want to dive in a bit deeper you can check out our Medium post which goes into detail on some other popular apps [3].&lt;p&gt;Our analysis consistently shows that without guardrails in place, app size can get out of hand very quickly. Emerge wants to help developers reduce their size and keep it that way. Our continuous monitoring and binary size profiling prevents regressions by alerting developers of size changes in their pull requests, helping teams build better, smaller apps.&lt;p&gt;We offer a free Growth plan designed for independent developers and small startups. Our paid plans start at $499&amp;#x2F;month, you can view more details here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;pricing&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;pricing&lt;/a&gt;.&lt;p&gt;If app size has come up in your development process, we’d love to hear about how you handled it. We’re always looking to improve and grow our product and we’re especially excited to hear feedback from the HN community!&lt;p&gt;Thanks, Noah + Josh&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;what-is-app-size&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;what-is-app-size&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;strip-binary-symbols&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;strip-binary-symbols&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;swlh&amp;#x2F;how-7-ios-apps-could-save-you-500mb-of-storage-a828782c973e&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;swlh&amp;#x2F;how-7-ios-apps-could-save-you-500mb-...&lt;/a&gt;</text></story><parent_chain><item><author>bberenberg</author><text>Definitely cool from a tech standpoint, but what is the value proposition here? I get that smaller = better, but why should I invest my engineers time in optimizing size using the results you output vs delivering new features or bug fixes to customers?</text></item></parent_chain><comment><author>aripickar</author><text>There are limits based on the size of the binary that apple will allow on the app store. In addition, here&amp;#x27;s a really interesting story about how uber had to fight to downsize the app cause they realized that staying under the cellular data limit made people able to download the app when they were on the go: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;StanTwinB&amp;#x2F;status&amp;#x2F;1336890442768547845&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;StanTwinB&amp;#x2F;status&amp;#x2F;1336890442768547845&lt;/a&gt;</text></comment>
<story><title>Launch HN: Emerge (YC W21) – Monitor and reduce iOS app size</title><text>Hi everyone!&lt;p&gt;We’re Noah and Josh from Emerge (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&lt;/a&gt;). Our company is building a monitoring and analysis tool to help iOS developers reduce their app’s size.&lt;p&gt;You might have heard about app size challenges faced by large iOS apps, particularly those with Swift codebases. I was an iOS engineer at Airbnb for 4.5 years and personally worked on their size reduction efforts.&lt;p&gt;App size is tricky to quantify. The size users most commonly see (what’s on the App Store page) is the install size thinned for their device. This is the size measured after stripping out assets like images and other media not needed for your screen size, or code that doesn’t run on your device’s architecture. However, this isn’t the only size metric out there, there’s also download and universal size (read more about this in our docs [1]).&lt;p&gt;Our tool makes app size easy to understand by visualizing the size contribution of every file in your app, from localized strings to machine learning models. To better our understanding, we even reverse engineered compiled asset catalogs and Mach-O binaries to show size contributions of original images, source files and Swift modules. With this perspective we often see files that don’t belong or are suspiciously large.&lt;p&gt;While testing our tool we analyzed and learned from over 150 iOS applications and found that keeping app size in check is really hard— even for industry leaders. Here are some of our more interesting findings.&lt;p&gt;Dropbox (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;dropbox&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;dropbox&lt;/a&gt;)
From the visualization, you can clearly see why Dropbox’s iOS app is 270 MB— it’s 35% localization files. These files are duplicated from the main app into 7 different app extensions and they all include comments that provide translators with context for the strings. Just removing these comments from the production app could save 46 MB.&lt;p&gt;eBay (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;ebay&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;ebay&lt;/a&gt;)
This is an interesting architecture because although the main app’s executable is only ~150 KB, 86% of the app’s size comes from executables, the biggest one (32 MB) being EbayApp.framework. When building a Swift framework, the binary contains symbols which are not needed in the build uploaded to the App Store. These symbols can be stripped using the method described in our docs [2]. Stripping binary symbols would reduce Ebay’s app size by over 40%. Emerge can generate a script to add to your Xcode build phase to strip symbols for you.&lt;p&gt;Spark (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;spark&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;apps&amp;#x2F;spark&lt;/a&gt;)
About 1&amp;#x2F;10th of Spark’s ~230 MB app is font files. 10 MB of those font files are duplicates found in an app extension. After a closer look, the fonts duplicated are all SF-Pro-Text, look familiar? These have been system fonts since iOS 11 (the minimum version for Spark). If the system font was used directly, 10% of the whole app could be deleted!&lt;p&gt;If you want to dive in a bit deeper you can check out our Medium post which goes into detail on some other popular apps [3].&lt;p&gt;Our analysis consistently shows that without guardrails in place, app size can get out of hand very quickly. Emerge wants to help developers reduce their size and keep it that way. Our continuous monitoring and binary size profiling prevents regressions by alerting developers of size changes in their pull requests, helping teams build better, smaller apps.&lt;p&gt;We offer a free Growth plan designed for independent developers and small startups. Our paid plans start at $499&amp;#x2F;month, you can view more details here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;pricing&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.emergetools.com&amp;#x2F;pricing&lt;/a&gt;.&lt;p&gt;If app size has come up in your development process, we’d love to hear about how you handled it. We’re always looking to improve and grow our product and we’re especially excited to hear feedback from the HN community!&lt;p&gt;Thanks, Noah + Josh&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;what-is-app-size&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;what-is-app-size&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;strip-binary-symbols&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.emergetools.com&amp;#x2F;docs&amp;#x2F;strip-binary-symbols&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;swlh&amp;#x2F;how-7-ios-apps-could-save-you-500mb-of-storage-a828782c973e&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;swlh&amp;#x2F;how-7-ios-apps-could-save-you-500mb-...&lt;/a&gt;</text></story><parent_chain><item><author>bberenberg</author><text>Definitely cool from a tech standpoint, but what is the value proposition here? I get that smaller = better, but why should I invest my engineers time in optimizing size using the results you output vs delivering new features or bug fixes to customers?</text></item></parent_chain><comment><author>nicoburns</author><text>People with small capacity phones (a lot of people) won&amp;#x27;t install your app, and may actually uninstall it if it&amp;#x27;s too big. That may not be priority #1, but it certainly deserves some consideration.</text></comment>