I have some 1.5 GBs of images and videos in my app bundle. Will apple allow such a huge size app?
Can we optimize the app to bring the size down?
Yes, Apple will allow apps of any size on the App Store. As a point of reference, the game Infinity Blade III is 1.92GB.
But keep in mind that apps (or their updates) over 100MB cannot be downloaded over cellular, so if it's possible to structure the app in such a way to accommodate that (i.e., download the videos and images separately etc), then that will definitely help.
Related
From what I have been able to understand from Apple's documentation, there is a 100mb over-the-wire limit on downloadable apps from the app store.
Apple recently introduced 3x assets for iPhone6+, causing ridiculous levels of bloat in our applications. Thus, app-thinning... So the idea is, I add an asset catalog and put all my images in there, and then the app store will know when an iPhone 6+ user downloads the app, it will only give them the 3x and 2x versions (i'm assuming for zoomed / non-zoomed), and when an iPhone 6 user downloads the app, it will give them the 1x and 2x versions (i'm also assuming for zoomed / non-zoomed).
So the 3x users are really only saving space by not downloading the 1x size assets (which are small and insignificant). And the 2x users are saving space by not downloading the 3x size (which is significant)... However, my question is app-thinning is only available for iOS9.. So what does that mean?
An iPhone 6 user on iOS8 will not be able to download the app at all because they don't have app-thinning and therefore they would be downloading the entire collection of assets and it will exceed 100mb?
I am asking this question because I uploaded my cocos2d game build to iTunes Connect and it says its compressed file size is 172mb with a yellow exclamation point, so I am worried about this... In my case, I know the problem really comes from the 3x size art. I'm not currently using asset catalogs because cocos2d (v2.x at least) doesn't support them, and I don't want to bother adding support for that if it's pointless as I am thinking based on what I've described above...
App slicing takes place on the App Store Servers so devices running iOS 8 or earlier are still able to download apps, which have app thinning enabled.
The App Thinning Documentation states
Sliced apps are supported on devices running 9.0 and later; otherwise, the store delivers universal apps to customers.
If the size of the universal app exceeds 100MB, the user has to download it over WiFi. A method to lower the initial download size are on demand resources.
Note:
As the pixel density on the iPhone 6 Plus is higher than on other models, even when non-zoomed, only the 3x images are needed so the 2x images do not need to be downloaded so the iPhone 6 Plus users do save a little bit more.
What are the different video size and resolutions that can be added within the bundle of an iOS app to play for all iPhone and iPad models. Is there any limitations over size and resolutions of videos. What is the proper video/size to play well on all devices
There are many downsides to including large amounts of content (a large total bundle size will force your users to install over WiFi, for example) but as to specific content size/format restrictions, there aren't any.
Just in case... If you're talking about "what is the proper video format/size to play well on all devices", that's a different question and not the one I am answering (effectively, "aggregate bundle content size").
I am working on an App, that includes iphone(4,5 potarit only) and Ipad(Landscape as well Potarit). App includes 120 MB of IMAGES and the folder size of my project is 123 MB.
But I made its ipa, that goes to 185 MB . I am worried about the size of the build. How it happened to become 185 MB.
On what factors it is depending upon?
How Can I reduce the size of my build?
Will there be any problem uploading this app to the app store?
There are total of 15*3=45 NIB files in my project.
part (3) - "Will there be any problem uploading this app to the app store?" :
The maximum size of .ipa in AppStore depends on your internet connection.
For app to be downloaded over 3G, the maximum size should be 100MB. Over Wi-fi connection or iTunes the maximum size is 2GB.
part (2)
To reduce the iPA size you can reduce the size of the images. Generally in an application you do not require high resolution images (not more than what the device supports).
If there are images you can make the application download from some external server, that would be better. That way you can download the images the first time app is launched and save in the sandbox of the app and they can be used later in the app by fetching from the sandbox. This can reduce your iPA size considerably.
part(1)
Generally the binary size is less than the actual folder size. I could not see from where your iPA size is increasing.
As far as I know
1 . ipa file size mostly depends on the Images size.
2 . So try to ask your designers to reduce the image for saving the memory or try to use the .jpg files for images except for splash screens,icons. No need to worry about the xib files .
3 . There is no need to worry about the size while releasing the app . Only issue is takes some time to download from the iTunes.
The size of application mostly not depend on the code but on the resources you have added into your application like images, video and sound files.
Most time number of images to support the different display need to add more images cause large size of IPA but for that I think the best way is use stretchable images that decrease IPA size around upto 40 to 60 percent and very neat and clean. do not include over side video and mp3 just compress them at optimum level so user experience will be great. Size could be around 40 mb is best for general ios application
Another approach is to download necessary assets during the first launch.
Pro: user will only get images that compatible with his device
Con: there must be a stable internet connection to download the images. Wi-Fi is preferred, because 3G is not always free of charge for user.
I want to make an iOS app. This app will have over 200 images, each with different sizes (500x500[maybe smaller] and less). What is the best method to keep them, having a smaller app size?
I think about optimizing their sizes for web in photoshop, but still the app will have a big size if I want to keep and a respectful quality.
Any ideas?
Well, I don't know if you can do this for your app, but you can download them from the internet once the user installed your app. This way you can keep the size of the package as small as possible (I assume you talk about non-critical images, that can be obtain afterwards).
UPDATE
Alternatively you can use SVG instead of bitmaps, of course if applicable:
how to render svg file in iphone and ipad
I'm creating an iOS app with some preloaded data which includes images, it will have between 150 and 200 images. This images are not downloaded from a server, since the app won't connect to the internet.
I'm wondering about if saving the images locally can cause any problem, what is the max size that I can use to store them? Can this affect the app's performance? Anything else that I should be aware of?
Thanks in advance!
Over the air cellular maximum download is now 100MB since the iOS 7 launch.
Your maximum app size is 2GB with a maximum binary size of 60MB. With 200 images I don't think you'll hit the 2GB mark, so long as you use the proper compression techniques.
The only thing that would affect your app's performance is the way the images are presented. If they're really large images, 10+ MB you'll most likely hit memory problems in older devices and if you go larger, memory problems in newer devices. There's plenty of techniques like tiling in a scroll view to get around these problems but it requires you splice up your images and create multiple resolution versions of the image.
If your app is greater than 50MB (at the time of writing) because of the images being included then users will need WiFi to install it.
Other than that, your performance concerns should be around how many of the images you will have loaded into memory at any one time and how you can reduce that number.