What is the structure of an Android application when working with a database?

Question

Android

Hello!
I'm learning Android quite recently. Studied working with SQLite. I decided to sketch an application like Notes. I am using RecyclerView. I also implement everything through activities with fragments. But the question is global. What is the structure of modern applications (meaning when using new development tools and frameworks)? It means how and by what means should the modules in the program interact? Often there is a statement that it is necessary to implement everything through fragments - is this true? Searched for sample projects to learn from, but to no avail.

Answer 1

What is the structure of modern applications (meaning when using new development tools and frameworks)?

There is no consensus, there is no analogue of Laravel or Django, but the tools you need to know and have an idea about:
Dagger 2
MVVM
MVP
Data Binding
No, fragments should be used where needed. I have projects that only use fragments, and there are projects that don't use them at all. The guys from square decided to abandon them altogether (if it were not square, I would just twist my finger at my temple), but for me their approach seems doubtful, I'm not sure if this is a good idea
As for the database specifically - I personally am old-fashioned in this regard, I like reliability and the convenience of the ContentProvider (convenience of work, in the sense of what I did and forgot, its api is disgusting) but time goes by, I start looking at rx for the same tasks