Not network, but local database cache.

​@@StevdzaSan But if my app doesn't want to maintain local copy. No need to save or fetch from db . Can pass data from previous screen unless there is a chance to modify from other place while visiting the detail screen.

@vengateshm2122 Yes, that's correct, but you gotta be careful, though. Each situation is different, and you need to evaluate it accordingly.

@et_matrix, I agree. I think it depends on how expensive or time-consuming the API call is vs the size of the data to transfer, vs the problem of stale data. Situations are different.

@@StevdzaSan do you have any tips or sources on caching?

Thanks! 🙌🚀

Yep, that's also another way 👌

Totally, I would too if I were to use Java

I sometimes feel the same way, to be honest, primarily because of Google's policies. It seems that they are gradually making it impossible for indie developers to even exist on the Play Store. It appears that their focus is solely on catering to big, multi-billion dollar corporations on their platform.

@@starry_shivam What policies exactly?

@@StevdzaSanFor example, consider the requirement for 20 testers, which is next to impossible for solo devs to manage. I could list more of these, but you can simply glance at the comments on Google's PolicyBytes videos on YT to understand the situation.

@@StevdzaSan Let's take the requirement for 20 testers for example, which is almost impossible to manage for solo developers who are building apps as hobby or side projects, and it doesn't even makes much sense practically either, I could provide more of them, but you can simply glance at the comments on Google's PolicyBytes videos to understand the situation.