How do layouts and views work in Android? · IT Interview Practice

How do layouts and views work in Android?

Android UIs are built from Views (UI widgets like buttons, text) arranged by ViewGroups/layouts (containers like LinearLayout, ConstraintLayout). Traditionally defined in XML layouts, modern Android increasingly uses Jetpack Compose (declarative). Understanding the view system is foundational for building UIs.

Views and ViewGroups

text

VIEW → a single UI element (TextView, Button, ImageView, EditText, etc.)
VIEWGROUP → a container that holds/arranges child views (LinearLayout, ConstraintLayout,
  FrameLayout, RecyclerView, etc.) — layouts ARE ViewGroups
→ UIs are a TREE of views inside view groups (composition).

text

LinearLayout → arrange children in a row OR column
ConstraintLayout → flexible, flat layouts via constraints between views (modern, efficient,
  the recommended layout for complex UIs)
FrameLayout → stack/overlay children
RecyclerView → efficient scrolling lists (recycles views for performance — key for lists)

xml

<!-- define the UI declaratively in an XML layout file -->
<LinearLayout android:orientation="vertical" ...>
  <TextView android:text="Hello" .../>
  <Button android:id="@+id/myButton" android:text="Click" .../>
</LinearLayout>

text

JETPACK COMPOSE → modern DECLARATIVE UI toolkit (Kotlin code, no XML):
  → describe UI as composable functions; reactive (UI updates with state)
  → Google's recommended modern approach (similar idea to Flutter/React)
→ New apps increasingly use Compose; XML layouts still common in existing apps.

How do layouts and views work in Android?

Views and ViewGroups

Common layouts (ViewGroups)

XML layouts (traditional)

Modern: Jetpack Compose

Why it matters