Help me understand Module structure.

[DharitParmar]

So I understand that each module in :core is an individual gradle module. But how about the :core module it self? is it a gradle module or a library?

[SimonMarquis]

@DharitParmar, technically yes, :core is a Gradle project (aka module), but it is an empty one. We use these as namespaces to group modules together.

[DharitParmar]

you mean it's just a directory(a container) and thus it's not buildable by it's own, right?

[SimonMarquis]

Yes. You can test it yourself by running this command: gradlew projects

> Task :projects

------------------------------------------------------------
Root project 'nowinandroid'
------------------------------------------------------------

Root project 'nowinandroid'
+--- Project ':app'
+--- Project ':app-nia-catalog'
+--- Project ':benchmarks'
+--- Project ':core'
|    +--- Project ':core:analytics'
|    +--- Project ':core:common'
|    +--- Project ':core:data'
|    +--- Project ':core:data-test'
|    +--- Project ':core:database'
|    +--- Project ':core:datastore'
|    +--- Project ':core:datastore-proto'
|    +--- Project ':core:datastore-test'
|    +--- Project ':core:designsystem'
|    +--- Project ':core:domain'
|    +--- Project ':core:model'
|    +--- Project ':core:network'
|    +--- Project ':core:notifications'
|    +--- Project ':core:testing'
|    \--- Project ':core:ui'
+--- Project ':feature'
|    +--- Project ':feature:bookmarks'
|    +--- Project ':feature:foryou'
|    +--- Project ':feature:interests'
|    +--- Project ':feature:search'
|    +--- Project ':feature:settings'
|    \--- Project ':feature:topic'
+--- Project ':lint'
+--- Project ':sync'
|    +--- Project ':sync:sync-test'
|    \--- Project ':sync:work'
\--- Project ':ui-test-hilt-manifest'

Included builds
\--- Included build ':build-logic'

[DharitParmar]

gotcha! Make sense! One more thought: When the idea of having core is the reusability then why not to seperate framework layer(all that is depend on SDK and external interfaces. such as dataSources)? That way the core(bisuness and data logic) becomes framework independent - Just a thought out of my limited knowledge :)