Table of Contents:

Diving In
1. Getting started -Android is the world’s most popular mobile operating system.
Building interactive apps
2. Apps That Do Something - Most apps need to respond to the user in some way.
Layouts
3. Being a Layout- We’ve only scratched the surface of using layouts.
Constraint layouts
4. Draw Up a Blueprint - You don’t build a house without a blueprint.
The activity lifecycle
5. Being an Activity- Activities form the foundation of every Android app.
Fragments and navigation
6. Finding Your Way- Most apps require more than one screen.
Safe args
7. Passing Information -Sometimes fragments need extra information to work properly.
Navigation ui
8. Going Places -Most apps need to be able to navigate between destinations.
Material views
9. A Material World- Most apps need a slick UI that responds to the user
View binding
10. Bound Together -It’s time to wave farewell to findViewById()
View models
11. Model Behavior- As apps grow more complex, fragments have more to juggle.
Live data
12. Leaping into Action -Your code often needs to react to property value changes.
Data binding
13. Building Smart Layouts- Layouts can do more than control your app’s appearance
Room databases
14. Room with a View - Most apps need data that persists
Recycler views
15. Reduce, Reuse, Recycle- Lists of data are a key part of most apps.
Diffutil and data binding
16. Life in the Fast Lane- Your app needs to run as smoothly and efficiently as possible.
Recycler view navigation
17. Pick a Card -Some apps rely on the user selecting an item from a list.
Jetpack compose
18. Compose yourself- All the UIs you’ve built so far have used views and layout files.
Integrating compose with views
19. Perfect Harmony -You get the best results when things work together.
Leftovers
The Top Ten Things (we didn’t cover) - Even after all that, there’s still a little more.