Yeah, but it will also have disadvantages of mono-repo. For existing apps, moving to a mono repo would mean combining already huge android and iOS git repositories linked to many dev and release processes built over years, which is a huge effort task in itself without ROI.

When considering a fresh new app to be created, an out-of-box project with a mono repo with few devs(2-3) is ok, but as the team gets bigger(>10) and project size keeps on increasing. As a lead, you would like to split teams into owning different parts of apps each. The first simple split would be based on primary skill set as this makes sense plus exposing only those parts to them to avoid unwanted impacts in other parts leading to Android + KMP (Kotlin) and iOS repository. But as KMP is a new cross-platform tech, there are some rules you need to learn to avoid crashes when the same code is used in iOS, so you will have Android devs who know Kotlin but do not know K/N rules so you might not want them to work on KMP code and align them on pure Android code. So you would like to have Android, KMP, and iOS as part of the project split.

We already have 24 devs and huge individual repo size due to apps being more than 10+ years old, so the last split seemed ideal for us.

I hope this explanation answers your question.