Skip to main content

How I Reduced the Size of My React Native App by 85%

How and Why You Should Do It
I borrowed 25$ from my friend to start a Play Store Developer account to put up my first app. I had already created the app, created the assets and published it in the store.
Nobody wants to download a todo list app that costs 25mb of bandwidth and another 25 MB of storage space.
So today I am going to share with you how I reduced the size of Tet from 25 MB to around 3.5 MB.

Size Matters

Like any beginner, I wrote my app using Expo, the awesome React Native platform that makes creating native apps a breeze. There is no native setup, you write javascript and Expo builds the binaries for you.
I love everything about Expo except the size of the binaries. Each binary weighs around 25 MB regardless of your app.
So the first thing I did was to migrate my existing Expo app to React Native.
  • react-native init a new project with the same name
  • Copy the source files over from Expo project
  • Install all dependencies of the Expo project except Expo specific libraries.
  • Make neccesary adjustments to app.json file
  • Copy over your .git folder into the new project.
  • Download the signing key of your Android app from Expo using exp fetch:android:keystore and set it up
  • Build and test your app
This reduces the size to around 7.5 MB, thin but we can go thinner.
This is what you have been waiting for, I know.
  • Open up android/app/build.gradle
  • Set def enableProguardInReleaseBuilds = true this would enable Progaurd to compress the Java Bytecode. This reduces the app size by a tad bit
  • Set def enableSeparateBuildPerCPUArchitecture = true . Android devices support two major device artitectures armebi and x86. By default RN builds the native librariers for both these artitectures into the same .apk.
Setting the last function creates two distinct .apk in the build folder. You have to upload both of this .apk to Play Store and Google would take care of distributing the app to the correct architectures.
Using this split generates version numbers for both .apks in the order of 104856 and such. This is auto-generated by the build to avoid version conflicts, so don’t freak out (I did).
This split reduced the .apk size from around 7MB to 3.5MB for arm and 5MB for x86 respectively.

Yeah

So that’s how you lose weight. Reducing the size of your app has many added benefits, the best being more users will be willing to download your app.

Comments

Post a Comment

Thank You.

Popular Posts

React Native - Text Input

In this chapter, we will show you how to work with  TextInput  elements in React Native. The Home component will import and render inputs. App.js import React from 'react' ; import Inputs from './inputs.js' const App = () => { return ( < Inputs /> ) } export default App Inputs We will define the initial state. After defining the initial state, we will create the  handleEmail  and the  handlePassword  functions. These functions are used for updating state. The  login()  function will just alert the current value of the state. We will also add some other properties to text inputs to disable auto capitalisation, remove the bottom border on Android devices and set a placeholder. inputs.js import React , { Component } from 'react' import { View , Text , TouchableOpacity , TextInput , StyleSheet } from 'react-native' class Inputs extends Component { state = { ...
Post a Comment
Read more

How to recover data of your Android KeyStore?

These methods can save you by recovering Key Alias and Key Password and KeyStore Password. This dialog becomes trouble to you? You should always keep the keystore file safe as you will not be able to update your previously uploaded APKs on PlayStore. It always need same keystore file for every version releases. But it’s even worse when you have KeyStore file and you forget any credentials shown in above box. But Good thing is you can recover them with certain tricks [Yes, there are always ways]. So let’s get straight to those ways. 1. Check your log files → For  windows  users, Go to windows file explorer C://Users/your PC name/.AndroidStudio1.4 ( your android studio version )\system\log\idea.log.1 ( or any old log number ) Open your log file in Notepad++ or Any text editor, and search for: android.injected.signing and if you are lucky enough then you will start seeing these. Pandroid.injected.signing.store.file = This is  file path where t...
Post a Comment
Read more