Label draws a line. You do not have a label without a string; if you did this, what would he draw?
The last thing I checked, UILabel uses UIWebView internally, so you can really make a more efficient version. One way is to use Core Text; another will use CATextLayer .
As for UIImage, technically yes; UIImage wraps CGImage, so cutting UIImage will save memory. However, 99% of the memory used by the image is for the image itself, its pixels; they are contained in CGImage, and the UIImage is tiny compared to it. You have the best you can spend on reducing time.
Instead of guessing and / or relying on general considerations for your optimizations, use the "Tools" to find out exactly what your application uses. Once you know with confidence where all your memory is located, you will know where you can look for savings.
Wrappers usually do not increase memory usage; the objects are small, so you will only pay them a lot if you create them. Look instead at shortening their life; don't hold on to objects (in caches, collection objects, or directly in instance variables / properties) longer than you need.
source share