How to learn Android development the right way?

Question

Android

Hello. I must say right away that this is not a question from the category of how to start learning something (I already found answers to it a long time ago :)). This is the question that I had today - how to study something correctly. What I mean? Look, here I bought two books: Head First Kotlin and Big Nerd Ranch Android 4 edition. The last week I stormed Kotlin in order to rebuild from Java (taught at the university) and study everything before the android itself, at least to the initial OOP topics. And for the last 3 days I have already begun specifically to teach Android, but some doubts began to take over me that I was doing something wrong. Here's how to learn a language, it's understandable, for example - I studied arrays -> on conditional code wars I did tasks for them, etc., but what about android? Because, it seems to me that stupidly doing Ctrl + C, Ctrl + V with examples in the book is such a thing. Yes, I came up with a conditional project, but it doesn't look much like the examples in the textbook. So, is it worth continuing to copy-paste from the book purely for a general understanding of the information that is given in this book, but what I need to google separately? Or just take the information I need from the book and forget about those examples? Or, in general, first read the book completely with all the examples and only then proceed to the project and googling, because for example, for the project I already need a second activity at the beginning, and according to the book it is given only after 140 pages? what do I need to google separately? Or just take the information I need from the book and forget about those examples? Or, in general, first read the book completely with all the examples and only then proceed to the project and googling, because for example, for the project I already need a second activity at the beginning, and according to the book it is given only after 140 pages? what do I need to google separately? Or just take the information I need from the book and forget about those examples? Or, in general, first read the book completely with all the examples and only then proceed to the project and googling, because for example, for the project I already need a second activity at the beginning, and according to the book it is given only after 140 pages?

PS off topic, but I also need it - from your personal experience, which book on algorithms would you recommend?

Answer 1

These books are for informational purposes only. Continue as you started, get acquainted with all the possibilities that the book presents, then google each topic separately: what is an activity, what is a fragment, what are their differences, what are their methods, why is it better to use one activity, what is tax, what is backstack, how it works, why they did it.
But if you can’t explain the most basic things of the language, what an array or a hash map is under the hood, how classes that inherit the Set interface are arranged, then it’s too early for you to get into android, there is too much information that cannot be learned in pieces, everything is connected and you have to learn everything at once.

Answer 2

I'll tell you this - you don't need a second Activity. You need fragments. There is nothing complicated there. Go to developers.android.com and read the topics. Make your project, add features. Books in Russian? Forget it, it doesn't roll on android. Kotlin books? Solve koans.

Answer 3

You open Google -> developer.android
There is a guides section, there is all the information you need, there is also a section on the site with Google courses for beginners, you can start with them

Answer 4

What book on algorithms would you recommend?

Yes, what the hell algorithms, there is nothing special to study there. All these data structures and "algorithms" are studied in a couple of days.

stupidly doing Ctrl + C, Ctrl + V with examples in the book is such a thing.

Well, it’s obvious what needs to be done not stupidly, but with an understanding of what you are doing and how to improve what is given

Yes, I came up with a conditional project for myself, but it doesn’t look much like the examples in the textbook.

judging by what you wrote, you still don’t know shit, neither in kotlin, nor in programming, nor in android. First, study from the textbook what exists in principle, and then study in detail what you need to study

because, for example, for a project, I already need a second activity at the beginning

so that you don’t say such crap, you must first familiarize yourself with the textbook and articles.
then when the basics are, then you can already look for only what you need