Purpose of JSON assets in prod builds?

[AndresMaca]

Hi folks, I’ve been exploring the network layer and had a question about how we package demo data.

Right now the demo JSON assets (news.json, topics.json) live under core/network/src/main/assets, and DemoNiaNetworkDataSource is only used in the demo flavor (via the flavored FlavoredNetworkModule). My understanding is that this means these assets are included in all variants, including prod, even though they’re only needed by the demo flavor, apologies if I’m missing something here.

Would it make sense to move those assets under core/network/src/demo/assets so they’re only packaged in demo builds? Or is there a specific reason we keep them in src/main (e.g., tooling, tests, or the release process) that I’m not aware of? I’m mostly asking because I know app size can be a concern, especially in larger apps.

Also, I was wondering if it could be useful to add a bit more testing around the content verification itself. For example, given a JSON array, we could assert that the elements are in the expected order and that they produce the right NetworkChangeList entries. Happy to help with this if it seems worthwhile.