Compose Layouts: Build UI by Describing It
Describe your UI, and Compose draws it. Use Column and Row to position elements, then augment them with modifiers. The footgun is coding before you've broken the visual design into reusable parts, leading to a tangled mess.
Why it exists
Jetpack Compose was created to simplify UI development on Android. Instead of manually manipulating a view hierarchy, you describe how your UI should look for a given state, and Compose handles the work of drawing it on screen and updating it when the state changes.
The mental model
Think of building a UI like assembling LEGOs. First, analyze the final design and break it down into its smallest reusable pieces. You then implement these small pieces as composable functions and combine them into larger, more complex structures until the entire screen is built.
How it works
You arrange UI elements using standard layout composables. Column stacks children vertically, Row arranges them horizontally, and LazyRow or LazyColumn efficiently displays scrollable lists. You then augment these composables with modifiers to add padding, control size, set alignment, and more. For complete screen structures, you use slot-based layouts like Scaffold, which provides designated areas (slots) for top app bars, bottom navigation, and the main screen content.
When to use it
Use Compose layouts for building any UI in a modern Android application. This approach is fundamental for creating everything from a simple text display to a complex, multi-section app with scrolling lists, grids, and navigation. It is the standard for declarative UI in Kotlin.
When not to use it
Avoid jumping straight into coding a complex screen without a plan. The biggest mistake is failing to analyze the design first. If you don't break the UI down into a hierarchy of smaller, reusable composables, you will end up with a monolithic, hard-to-manage function that is difficult to debug and modify.
One canonical example
A wellness app screen can be broken down this way. The overall screen is a Scaffold containing the main content and a BottomNavigation bar. The main content itself is a Column holding three children: a SearchBar composable, a horizontally scrolling section built with LazyRow for "Align your body" items, and another section for "Favorite collections" displayed in a grid. Each individual item in the row or grid is its own small composable.
Interview question
What is identified as the biggest mistake when building UIs with Compose layouts?
- a.Overusing Column and Row instead of more efficient layout composables.
- b.Failing to analyze the design and break it into reusable components before coding.Correct
- c.Manually manipulating the view hierarchy instead of describing the UI state.
- d.Not using slot-based layouts like Scaffold for full screen structures.
Why? this is the answer
The card explicitly states, "The biggest mistake is failing to analyze the design first. If you don't break the UI down into a hierarchy of smaller, reusable composables, you will end up with a monolithic, hard-to-manage function." Option A, while potentially leading to less efficient code in some cases, is not framed as the primary architectural pitfall.
Just read this? Test yourself on what you have been reading.
Read the original → developer.android.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on android — each one lists the topics its interview covers.
See open roles