Skip to main content

Modularizing your Android app, some quick notes (Part 4)


Basically, in part 3 of this series we managed to fully modularize an Android app.  However there are some notes that need to be taken. We didn't cover too much about resources (res folder) in any of our parts therefore we are handling it now.

Here are some things that we should notice about resources in modularization:

1- Strings. No need there for a large file of it. It's easier when each module has access to it's own string values rather than accessing them all from a :core_module. It's easier to read, easier to find strings and if you have a double String resource (like having 2 languages or more) the complexity gets lower. Of course, string resources that are present in more than one module, must remain in the only source of truth.

2- Colors & drawables. It's really important to pay attention to drawables because they significantly affect the APK/Bundle size. The same rule should apply here (not to mention that sometimes we forget to delete drawables that are not used at all).

3- Styles. If you have only one theme applied to the whole app you better not touch this file for side effects. Keep it in the core module of the app.

4- Common layout files and fonts. Kotlin synthetics gave me hard time and runtime exception when I added <include></include> tags in other modules which would be referenced by all modules. (I usually keep loading and error layout in a single part and use <include> tags.) Therefore I still think that the findViewById() is safer than them.

APK/Bundle size:

I noticed that my bundle size was reduced by nearly 30% after modularization. Which means more installs and happier users:




Also builds are significantly faster.

Stavro Xhardha

Popular posts from this blog

What I learned from Kotlin Flow API

I used to check the docs and just read a lot about flows but didn't implement anything until yesterday. However, the API tasted really cool (even though some operations are still in Experimental state).Prerequisites: If you don't know RxJava it's fine. But a RxJava recognizer would read this faster.Cold vs Hot streamsWell, I really struggled with this concept because it is a little bit tricky. The main difference between cold and hot happened to be pretty simple: Hot streams produce when you don't care while in cold streams, if you don't collect() (or RxJava-s equivalent subscribe()) the stream won't be activated at all. So, Flows are what we call cold streams. Removing the subscriber will not produce data at all, making the Flows one of the most sophisticated asynchronous stream API ever (in the JVM world). I tried to make a illustration of hot and cold streams: Since I mentioned the word asynchronous this implies that they do support coroutines also. Flows vs…

Modularizing your Android app, breaking the monolith (Part 1)

Inspired by a Martin Fowlers post about Micro Frontends, I decided to break my monolithic app into a modular app. I tried to read a little more about breaking monolithic apps in Android, and as far as I got, I felt confident to share my experience with you. This will be some series of blog posts where we actually try to break a simple app into a modularized Android app.

Note: You should know that I am no expert in this, so if there are false statements or mistakes please feel free to criticize, for the sake of a better development. 

What do you benefit from this approach:
Well, people are moving pretty fast nowadays and delivery is required faster and faster. So, in order to achieve this, modularising Android apps is really necessary.You can share features across different apps. Independent teams and less problems per each.Conditional features update.Quicker debugging and fixing.A feature delay doesn't delay the whole app. As per writing tests, there is not too much difference about…

From Gson to Moshi, what I learned

There is no doubt that people are getting away from GSON and I agree with those reasons too. The only advantage GSON has over other parsing libraries is that it takes a really short amount of time to set up. Furthermore, the most important thing is that Moshi is embracing Kotlin support.

First let's implement the dependency:
implementation("com.squareup.moshi:moshi:1.8.0") It's not a struggle to migrate to Moshi. It's really Gson look-a-like. The only thing to do is annotate the object with @field:Json instead of @SerializedName (which is Gsons way for JS representation):

data class User( //GSON way @SerializedName("name") val name: String, @SerializedName("user_name") val userName: String, @SerializedName("last_name") val lastName: String, @SerializedName("email") val email: String ) data class User( //Moshi way @field:Json(name = "name") val name: String, @field:Json(name = "user_name…