Hi. It depends on your use case. It can be a list of data-classes created from the web API, if you don’t have a cache. If you have it, then you can store data in database - see Room or SqlDelight. It would be better choise to store something in persistance storage. Structure of your data classes can be different at all. But I recommend create different models for all app layers (domain, network, storage), otherwise you will get unsupported code in the near feature (see clean architecture).