Split app into modules

[mdrlzy]

Modules structure

ARK-Rate
├── app
├── core
│   ├── data
│   ├── db
│   ├── di
│   ├── domain
│   └── presentation
├── feature
│   ├── pairalert
│   ├── portfolio
│   ├── quick
│   ├── quickwidget
│   ├── search
│   └── settings
├── fiaticons
└── cryptoicons

Resources

All resources are located in :core:presentation. Keeping resources in feature modules and ensuring that they are not duplicated will be a mess. We can easily access them via type aliases.

CoreR.kt

typealias CoreRString = R.string
typealias CoreRDrawable = R.drawable

Navigation

Feature modules generate compose-destination classes. We collect them in app module and create a single graph manually.
compose-destinations library works in destinations mode

ksp {
    arg("compose-destinations.mode", "destinations")
}

DI

We have CoreComponent in :core:di that contains common dependencies with Singleton scope. Feature modules create own components that depend on CoreComponent with own scopes. App holds CoreComponent and provides it.

Feature component are stored in separate object called FeatureComponentHolder inside the module. This is the easiest way to reuse component between compose screens in module.

Notes

• :core:di and :core:db needed to not expose :core:data module and implementation so feature modules only know about :core:domain and interfaces
• Build config replaced with BuildConfigFields and BuildConfigFieldsProvider. BuildConfigFieldsProvider created in :core:data module and initialized in app module. So all modules can use the build config of app module.

[hieuwu]

The dependencies graph look good & packaging very clean. 👍

[shubertm]

SVID_20241203_151830_1.mp4

• Trying to change the "from currency" creates new "to currency"