How is Android development similar to front-end web development?

Question

Android

1. What instead of HTML, CSS, what is the interface based on?
2. Is there a division into structure, styles and program code?
3. What are the most significant differences from the web in general?

Answer 1

1. Native android development is carried out mainly using java (kotlin), sometimes c ++. Usually the interface is described in the form of xml files, which are vaguely reminiscent of html, it is also possible to separately describe styles / themes also in xml files.
2. Yes. Logic - in java classes, structure and styles - in xml files.
3. As for me, native android development and the web have very little in common.
I'll give you the advice you didn't ask for. If you want to enter the world of mobile development from the web as easily and quickly as possible, don't choose native development. Take a cross-platform framework like Flutter or React Native - whichever is closer to you, there are many options now.
I myself switched to Flutter after native android development, the impressions can be described with the phrase "could it be like that?". Haven't tried React Native and others.
The main advantage of new cross-platform frameworks is a high abstraction from the platform. For me, the biggest pain of native development was in managing the application lifecycle. In Flutter, everything is much simpler. If you ever run out of performance, you can always write something native and pull from a framework like Flutter.
In general, not for the sake of holivar, I did not want to offend anyone, just advice.

Answer 2

1. What instead of HTML, CSS, what is the interface based on?
Markup, graphics, and some (much) documentation
2. Is there a separation between structure, styles, and code?
There are layouts, styles are applied to them, you manage all this economy from the code
3. What are the most significant differences from the web in general?
Speed, smoothness, lack of crutches, and recommendations from the vendor.