android contentprovider - Using content providers/loaders on API Calls with no database changes -

i creating application not store data (other basic user name, password, etc). uses api calls data , displays them when loaded through volley.

i know typically best practice use content providers , loaders when store things in sqlite. question is: should still using content providers , loaders given app not utilize database. have best practices/tutorials on how volley?

thanks!

it depends on use cases. here, no there no need. there other callback mechanisms can use broadcasts, async tasks, handlers or content observers. there nice official tutorial of how communicate uithread aka. visible stuff background logic.

also if want can use loaders without content provider. see so post more informations.