he was using butterknife to bind controls? I need to know will removing butterknife result in a reduced size to the apk
as i need to shrink the apk.
Also if possible please mention the pro and cons of using it .
he was using butterknife to bind controls? I need to know will removing butterknife result in a reduced size to the apk
as i need to shrink the apk.
Also if possible please mention the pro and cons of using it .
ButterKnife has an official web page here http://jakewharton.github.io/butterknife/. It has a very small size, so you don't shrink the apk size much by removing this dependency.
ButterKnife uses code generation to bind annotated views - it means no hurt to app perfomance from reflection of similar. Also annotations provide very clear and pretty looked code. So I strongly recommend to use this tool.
I have noticed only one disadvantage in this lib - there is no annotations for some view listeners, so you are being forced to mix ButterKnife style with usual Android one.
You can determine approximate dependecy size by number of methods it contains. You can use this online tool http://inloop.github.io/apk-method-count/.
ButterKnife let's you not write boilerplate code, but as this code is still needed in your app, ButterKnife will generate it for you. Sure, the library will add some bytes to the resulting APK but I'd not bother really as the overhead will be quite small. If you want to measure more precisely, just write the sample app with and without it and compare. But I'd not waste my time for that really ad stick to the ButterKnife to keep my sources cleaner.