Android data access design patterns: Content provider vs repository

Question

I wonder what folks use as a common data access pattern on Android? Content providers? Repositories? DAOs?

Thanks a lot!

Answer 1

I utilize Content Providers for all data access to SQLite resources, but build DAOs on top of them to handle all domain object conversions.