APKs are getting bigger and bigger. And why they shouldn’t be as developers are trying hard to meet with rising demands of users. Indian app development companies are working on fitting all functions in one app which results in a big size app. But do you really think that big size apps with tons of features are a solution to multiple-users problem or it is just an extension to challenging app economy?
Well, being an appaholic, I know how I cringe when I see an app of 50MB+ size. All my intentions or curiosity to play with app goes down to drain the moment I get familiar with big app size. No doubt, why many users change their app download decision after landing to app page and reading each detail.
All in all, I want to tell you to stop loading your app with codes and try to minimize the size, so your users won’t return back without downloading your app. And the answer to your next question – how to minimize the app size? – is given below.
Healthy Coding
When someone is on diet, that means he/she has to stick with healthy food instead of fatty food. Just like that you have to start with healthy coding which means you have to get rid of all unnecessary/unused libraries. Put an up to date code in your app and delete all old codes that having nothing to do with current technology.
Proguard
There is another tool. Sometimes I wonder how I could go for an app-relevant article without a tool. Back to the discussion, Proguard scans your app code to find out unused code to delete it and to make out possibilities of shirking codes. It is popular with the name java shrinker, optimizer, obfuscator, and preventifier. That means it works for Java only.
Lint
What about languages other than Java? There is a tool for that called Lint. Proguard works only with Java codes, not resources while Lint analyzes the code as well as resources to free your app from unnecessary things. For e.g. if Lint find out an image is not in use, it will strip the reference while keeping image on place.
Put the Code for Updated OS
How many OS versions Android and iOS have? Many, right. The important question is how many of them are actually in use? Obviously, the old ones are forgotten or deleted and the new ones are making place rapidly. You don’t need to make an app that supports all the OS versions starting the moment apps came into existence – it just leads to increase the size of app and that is also for no reason. Focus on OS versions in use and make an app with that.
Focus on Resources
Not only codes, but your app is also rich with resources coming from Google Play Services, Facebook SDK, Android Support Library, etc. They all fill your app with necessary and unnecessary resources. You have to analyze them and take them out to make your app breathe.
Reuse Code
Reuse the same code as and when possible. Don’t put a different line of codes in different manners just to show off the graphics in various angles. Users are meant with features of the app not with the looks. So, reusability is safe with app especially when it decrease the size of app up to a good extent.
Final Thoughts
All you have to do is eliminate the unnecessary code and shrink the necessary ones. Not only code, but resources as well. I bet users won’t feel heavy when they see your light-weight app. In fact, they would like to see what magic your app can play with such a little space.
Well, being an appaholic, I know how I cringe when I see an app of 50MB+ size. All my intentions or curiosity to play with app goes down to drain the moment I get familiar with big app size. No doubt, why many users change their app download decision after landing to app page and reading each detail.
All in all, I want to tell you to stop loading your app with codes and try to minimize the size, so your users won’t return back without downloading your app. And the answer to your next question – how to minimize the app size? – is given below.
Healthy Coding
When someone is on diet, that means he/she has to stick with healthy food instead of fatty food. Just like that you have to start with healthy coding which means you have to get rid of all unnecessary/unused libraries. Put an up to date code in your app and delete all old codes that having nothing to do with current technology.
Proguard
There is another tool. Sometimes I wonder how I could go for an app-relevant article without a tool. Back to the discussion, Proguard scans your app code to find out unused code to delete it and to make out possibilities of shirking codes. It is popular with the name java shrinker, optimizer, obfuscator, and preventifier. That means it works for Java only.
Lint
What about languages other than Java? There is a tool for that called Lint. Proguard works only with Java codes, not resources while Lint analyzes the code as well as resources to free your app from unnecessary things. For e.g. if Lint find out an image is not in use, it will strip the reference while keeping image on place.
Put the Code for Updated OS
How many OS versions Android and iOS have? Many, right. The important question is how many of them are actually in use? Obviously, the old ones are forgotten or deleted and the new ones are making place rapidly. You don’t need to make an app that supports all the OS versions starting the moment apps came into existence – it just leads to increase the size of app and that is also for no reason. Focus on OS versions in use and make an app with that.
Focus on Resources
Not only codes, but your app is also rich with resources coming from Google Play Services, Facebook SDK, Android Support Library, etc. They all fill your app with necessary and unnecessary resources. You have to analyze them and take them out to make your app breathe.
Reuse Code
Reuse the same code as and when possible. Don’t put a different line of codes in different manners just to show off the graphics in various angles. Users are meant with features of the app not with the looks. So, reusability is safe with app especially when it decrease the size of app up to a good extent.
Final Thoughts
All you have to do is eliminate the unnecessary code and shrink the necessary ones. Not only code, but resources as well. I bet users won’t feel heavy when they see your light-weight app. In fact, they would like to see what magic your app can play with such a little space.