22 ms·

Launch images (png) for every supported screen size? Sound/media files? Libraries? I’m sure it starts to add up.

by stock_toaster 4y ago

csande17 4y ago
Haven't launch screens used resizable Storyboard layouts for several years now?
- drEv0 4y ago
  They have. I believe Xcode even warns if a project is not using the resizable option.
outcoldman 4y ago
I used to have an app built for some AWS services (mac, ios). First decision to use some AWS libraries added size to the binary, it grew from 1MB to 70MB, I wrote simple AWS library myself just for my needs and that resulted in the binary of 2-3MB. Most of those apps use a lot of common libraries that add a lot of size to the binaries.
- version_five 4y ago
  I'm working on a machine learning project where we're trying to package something up, and bringing in all the packages that get installed by default with the framework we're using adds gigabytes to the size of the application, almost all of which is probably not necessary. The challenge is it's bloat on top of bloat, without an obvious way to pare it down, so it becomes a separate engineering effort to try and make something small and efficient. Under a certain size and for many applications, it's more cost effective just not to worry about it and keep the bloat
  - kelseyfrog 4y ago
    I found myself in the same situation a few years ago. We hacked together a dubious version of treeshaking using 'python -v' and got the thing small enough to run on an aws lambda which saved a bunch of money. Fun times.
causi 4y ago
Launch images (png) I'm flatly amazed that sort of thing isn't some kind of bitmap/vector hybrid format. Like a high resolution central logo and then rules for defining the background, like "blue fading to white at the edges".
- interpol_p 4y ago
  iOS has not required launch images for every size for some time now (since iOS 8 in 2014). It requires instead a piece of UI called a launch storyboard [1], which scales using the standard UI layout system to the different sizes However custom images can still be set for every possible size, if you really want [1] https://developer.apple.com/documentation/xcode/specifying-your-apps-launch-screen https://developer.apple.com/documentation/xcode/specifying-y...
- Lukas_Skywalker 4y ago
  Android has an interesting solution to this called 9-patch-files [1]. They basically add a 1px-margin around the image. By coloring the margin in different colors, you tell the OS what areas to stretch and what should be kept as-is based on the screen size. [1] https://developer.android.com/studio/write/draw9patch https://developer.android.com/studio/write/draw9patch
hulitu 4y ago
> Launch images (png) PNG files (if not generated from a jpg) are quiet small.
- dagmx 4y ago
  They're not. You're likely thinking of indexed color PNGs, but full color depth PNGs are quite large. A JPG/HEIC/AVIF image will be significantly smaller. The source of the PNG doesn't matter.

Launch images (png) for every supported screen size? Sound/media files? Libraries? I’m sure it starts to add up.

csande17 4y ago

Haven't launch screens used resizable Storyboard layouts for several years now?

drEv0 4y ago
They have. I believe Xcode even warns if a project is not using the resizable option.

outcoldman 4y ago

I used to have an app built for some AWS services (mac, ios). First decision to use some AWS libraries added size to the binary, it grew from 1MB to 70MB, I wrote simple AWS library myself just for my needs and that resulted in the binary of 2-3MB. Most of those apps use a lot of common libraries that add a lot of size to the binaries.

version_five 4y ago
I'm working on a machine learning project where we're trying to package something up, and bringing in all the packages that get installed by default with the framework we're using adds gigabytes to the size of the application, almost all of which is probably not necessary. The challenge is it's bloat on top of bloat, without an obvious way to pare it down, so it becomes a separate engineering effort to try and make something small and efficient. Under a certain size and for many applications, it's more cost effective just not to worry about it and keep the bloat
- kelseyfrog 4y ago
  I found myself in the same situation a few years ago. We hacked together a dubious version of treeshaking using 'python -v' and got the thing small enough to run on an aws lambda which saved a bunch of money. Fun times.

causi 4y ago

Launch images (png) I'm flatly amazed that sort of thing isn't some kind of bitmap/vector hybrid format. Like a high resolution central logo and then rules for defining the background, like "blue fading to white at the edges".

interpol_p 4y ago
iOS has not required launch images for every size for some time now (since iOS 8 in 2014). It requires instead a piece of UI called a launch storyboard [1], which scales using the standard UI layout system to the different sizes However custom images can still be set for every possible size, if you really want [1] https://developer.apple.com/documentation/xcode/specifying-your-apps-launch-screen https://developer.apple.com/documentation/xcode/specifying-y...
Lukas_Skywalker 4y ago
Android has an interesting solution to this called 9-patch-files [1]. They basically add a 1px-margin around the image. By coloring the margin in different colors, you tell the OS what areas to stretch and what should be kept as-is based on the screen size. [1] https://developer.android.com/studio/write/draw9patch https://developer.android.com/studio/write/draw9patch

hulitu 4y ago

> Launch images (png) PNG files (if not generated from a jpg) are quiet small.

dagmx 4y ago
They're not. You're likely thinking of indexed color PNGs, but full color depth PNGs are quite large. A JPG/HEIC/AVIF image will be significantly smaller. The source of the PNG doesn't matter.