In the KMM project structure, the "android" module acts nearly the same as a normal Android app module in the native Android project, (i.e., from android-templates). There are many same configs, structures, and dependencies that could be shared and reused from the android-templates's app for the KMM's "android" module.
To leverage and reuse the "android" app module from android-templates, we should consider resolving these issues:
use git sub-module to fetch the app module from the template-compose of the android-templates.
android-templates's app uses Hilt (Dagger) while KMM's android uses Koin.
android-templates's app interacts with its data and domain modules, while KMM's android interacts with its data and domain from the "shared" module.
Why
In the KMM project structure, the "android" module acts nearly the same as a normal Android app module in the native Android project, (i.e., from android-templates). There are many same configs, structures, and dependencies that could be shared and reused from the android-templates's app for the KMM's "android" module.
To leverage and reuse the "android" app module from android-templates, we should consider resolving these issues:
git sub-moduleto fetch the app module from the template-compose of the android-templates.Who Benefits?
Developers