My app has huge size of images, I wanted to reduce the size, I have achieved reducing the size by using webp format images. I followed this.but the sad part is, It is taking so much of time to load images as a result my app performance is vey slow.Could any one help how to fix this issue?
Thanks in advance.
Related
My android build size is 30mb, but my iOS build size (appstore size) is 400mb. After some researches, I found out that it may be because of assets compression. However, I found really old answers on the forum and I don't know what to do exactly.
I have several PNG images of the size 8192x1080 that I can't shrink because of the quality (I know this is big, but suppose there is no way to reduce or split it) :
What should I do ?
Use a plugin ? Which one ?
Create an AssetBundle ? I never used it.
Make my images 8192x8192 ? When I do so, the size increase to 85mb.
Don't use Sprite type but Advanced type?
An other question; when my image is not ARGB but RGB, the second warning message change from PVRTC to ETC1. What is the reason and consequence of it ?
Thanks for the help.
I am using ImageMagick version (6.8.9). On converting the image from one format to another the file size seems to increase. I am not able to find out the exact treason for this. I used quality as well. Still i am not able to find a solution for this problem
Thanks in advance
I have a gallery and detailed view controllers in my application, when a user taps a thumbnail in the gallery I redirect them to the detailed controller and begin to asynchronously download original-sized image, which is 640x640 px and it takes like 5-6 seconds to download. Is there a way to optimize the image download speed?
For example Instagram does this in around 0.2-1.0 second, like incredibly fast. My thinking is that they use some kickass compression on the server side and then unarchive the image they got in the Application. Are there any ways to do something like that?
Thanks in advance.
Solved it, I had to change the image format to .jpeg from .png, the compression rate of 40%, the quality is pretty good and the image size changed to 45kb from 600kb, which increased the speed.
I have a simple question for anyone who knows the answer to this... I am making a social photo sharing app and I want to save a large enough image in the app so that it can be used in a full screen website app moving forward. Think...Facebook.
I've been playing around with JPEG compression in iOS and also testing sizes and quality with Photoshop CS5. I get really different results with these two. In photoshop, even at high compression, the image is quite clear and retains lots of detail. In iOS, once the compression dips below about 0.5 it looks horrible and blocky. It almost seems like there's a point where the image quality just dips after a certain magic compression number.
With photoshop, I use the "Save for Web" option and with iOS I am using UIImageJPEGRepresentation(image, 0.6). Is there a huge difference in these two? Aren't all JPEGs use the same kind of compression?
I am really not that informed in this world of image processing. Can anyone advice me on what is a good way to have images compressed to a level that preserves quality and stay bandwidth friendly? I want my images to stay about 1280px in length.
Any advice on this or smarter ways to move JPEGS over the network is welcomed. Thank you.
If your app is producing images from an iOS device, you should continue to use UIImageJPEGRepresentation. I don't think it's productive comparing the UIKit JPEG compression to Photoshop's.
I would find a JPEG compression level you're happy with using the available UIKit APIs and go with that. When you're serving up 30+million images a second it might be worth looking at optimisations but until then leave it to UIKit.
I have a ScrollView with multiple UIImageViews in it which load .jpg images. It runs pretty influently when loading images.
How can I optimize the images to make iOS load them faster? Use which tool? In which specific format and setting? Thank you.
have them as png and pre load them with the "imageNamed" method. This method WILL cache them which makes loading fast. but it also knows how to handle memory which means it will unload them if you are runing low on memory.
Alternatively, depending on the size you can create the thumbnail version of these images for display. This is how the imagepicker manages to display A TON of images very fluently.
Read this question/answer: How can I load images into the iphone system cache?
use cached images. first time it may take time but after that it will be faster.