Ref - https://github.com/raamcosta/compose-destinations

Study

Any topics that are not subscribed by the user will be displayed in explore section.

Imagine a scenario where the user log's out
and therefore all the topics that are subscribed
will be pushed into explore section.

The user then log's in,
goes to the Explore section and tries to fetch his explore topics (unsubscribed topics),

our API call will do the work and get the unsubscribed topics
but remember that all topics were moved into Explore section when the user previously signed out, so we will have to filter the actual Explore topics of API from the cache explore topics and move the rest to the subscription section. (as topics that aren't subscribed are in explore section and vice versa)

1. Move all common reusable .gradle files into gradle/ folder, thereby cleaning root dir.
2. rename worker modules to more explicit names such as daily-read-worker
3. remove unnecessary plugins

As suggested by @ianhanniballake.

• I would suggest avoid using the name of project on classes.

• Singleton CoroutineScope is a wrong pattern because every async operation needs to have a scope to define when they will be canceled. Check here

• As we chatted, the interfaces in the data module should moved out to a new module, let's name it data-api, so other modules that needs it could inject the interfaces. Also as I noticed the interfaces of implementation in data module actually are on wrong modules! For instance, the implementation of ArticleDao interface will be generated in the data module so this interface must be beside other Dao interfaces in the so called data-api module.

• It's hard to understand why you have core module and also common-ui and features/authentication/common-ui modules!

Hope it helps.

Implement Firebase Dynamic Links to share articles

albeit the project build/scan is successful due to file validation inside build.gradle
Reported by: @nirmaljeffrey

https://github.com/JakeWharton/SdkSearch/blob/master/gradle/projectDependencyGraph.gradle - this script written by jake wharton will be helpful in generating modularization graph diagram. This script will use different colors codes for kotlin/java module, android module and multiplatform modules.

Using 'WindowSizeClass'

Reference: https://medium.com/ifood-engineering/modularization-tip-optimize-the-root-module-b0a904a8d5f5

So that users can unsubscribe if they wish.