How to design a client-server Android application?
The application must:
-work offline and save the data , after the advent of the Internet, synchronize changes with the server.
-as is clear from the above requirement - local database, backup server.
How to design and what faworki to use?
3 answers
MVP - architecture.
Dagger 2 - DI.
Retrofit 2 for network.
SQLite, Realm under the base.
ORMLite, GreenDAO - ORM if you want. You can still see on the Storio.
If you have the opportunity to connect directly to the database server, not via API (HTTP), then the local database is better to take the same as on the server, for example, locally to raise MySQL (via JDBC), and not to use SQLite - classic-embedded (local) database for Android which is query syntax, etc.
Yesterday I stumbled on Spring for Android framwork. A little googling ran "between the lines" of thought is what I need.
How do you think it will be difficult to ride this framework for a couple of days to grow up with the experience of 4 months?
Find more questions by tags Android
What a strange comment. Well, you wanted a regular telepath learned, what you know? So he's on vacation. I advise that he probably would have been using if there are no additional restrictions, even with the ability to choose. - Art_Christians commented on July 9th 19 at 12:55