Lessons on the architecture of android applications and the use of popular third-party libraries?

Question

Android

The basic principles of android development and the SDK in general are quite easy to learn from official documentation, this is no secret to anyone. But between basic things and real applications, I have some kind of barrier that is very difficult to overcome by reading tons of articles and documentation of third-party libraries. Maybe there are lessons (sensible articles, chapters from books), where the architecture of real applications for android would be laid out on the shelves? + talked about all sorts of Gson, Oauth, Retrofit, robospice, Spring for Android, GCM, Firebase, OrmLite, GreenDAO, ActiveAndroid, Picasso, Dagger, RxJava, Volley, how it should work in a complex, etc. etc.
For example, the most typical task: authorization / authentication through social networks + RESTful services + local cache + push notifications. How are such applications built, how to cope with the whole zoo of ready-made solutions and technologies?
It so happens to me that often at the stage of task decomposition, you first dig into reading about technologies A, B and C, then you read about established patterns X, Y, Z, for each of which, in turn, there are several ready-made libraries. And in the end it is not clear what exactly to do.

Answer 1

Programmers have recently created such a thing as Github . There you can now find projects of any complexity. What's stopping you from learning from them? You can start with iosched 2014 , u2020

Answer 2

Here you can see all the popular applications that have open source codes and study them in a different way.