Good question !
It seems that you are trying to achieve the Famous Google I/O design pattern? Google IO Rest design pattern, Finished ContentProvider and stuck now https://www.youtube.com/watch?v=xHXn3Kg2IQE
I did it in the past (maybe as not as well as it should have been done ;-) ). And my advice is be sure of this two points :
- Your tables are not too complex
- Your updates are not always occuring.
If it's not the case, you 'll probably face performance issues due to database accesses. But it's a really good pattern.
Another advice is to use an Event bus instead of boiler-plate, frustrating interfaces for updating the UI . (I usaully use this one https://github.com/greenrobot/EventBus no performance problems, Otto is good and simple too but does not integrate well with android-annotations).
Hope it'll help.