Is it worth making applications for Android without knowing Architecture Components and the like!?

Question

Android

I’ve been studying Android for 3 months, I’m already well versed in the main topics of AndroidSDK, but so far I can’t understand Architecture Components, Jetpack, Room, Dagger and so on, such things that all Android developers talk about? So is it worth it to first figure it all out and then slowly start writing something, or is it not as important as it seems ?!
All jobs almost require you to know all these things!
And sometimes if I try to create some kind of application, I can’t understand where to start and what to use.

Answer 1

Come on, spank the code right away, be like 90% of Android developers.
It may seem that I am joking or joking, but no. I'm serious.

Answer 2

Create some kind of product for yourself, study yourself on a combat project. Pulled? Go to the fighting channel - freelancing.
And what they write in vacancies... I worked for a year as a designer, where the obligatory requirement was to have the Principle skill, which I never launched in my life.
Iii... yes, I completely agree with Ronald McDonald , a huge number of developers put the bolt on some kind of "Architecture Components, Jetpack, Room, Dagger", etc.

Answer 3

Write already.
Learning is 1000 times faster - when you code, not read.
For in practice, you will meet there sooooo much that you won’t read in books.

Answer 4

Are you too lazy to read the documentation, dig into demo projects and write some TODO application for yourself? If you don't write and experiment, you won't learn anything.
And yes, all this diversity has appeared in recent years, previously they managed. The exercise "write something without using libraries" will help you better understand how the platform itself works.