Q:

iOS code drawings vs png

I've found a program for converting SVG images directly into code. Sounds like an epic solution for iOS application size problems but here occurs some obstacles. 
Drawing complex images result into 4k+ lines of hardcore code. Its about 100 kB pure file size that almost equals to initial png image size. 
So the question - is there any point(total app size gain) of drawing such kind of images from code or better include em in project as normal pngs? Whats the ration between code size and binary size? Or how could I calculate it? 

A:

After times of research, I've found that UIBezierPath solves my problem pretty nice.
Yes, UIBezierPath is just a wrap for CoreGraphics that is based on CPU but as Apple recommends - use highest level of abstraction for your purposes and let system do it job.
Performance for drawing vector images using UIBezierPath is high enough for any 2D interface element. 
As I've tested - speed factor for retina display even for hardest images was about 45-50 fps that is more than enough for primitive UI animations.
So the verdict is - drawing your interface using code saves memory and nerves. 

