Q&A сессия про Compose. Обсуждают распространенные вопросы п | StartAndroid

Q&A сессия про Compose.

Обсуждают распространенные вопросы про производительность Lazy списков, судьбу XML, ConstraintLayout, миграцию и т.п.

Полный список вопросов:
- Is it the right time to migrate existing XML code into Compose?
- I’m new to Android development. Should I use Compose or XML?
- When should I use Column vs LazyColumn?
- Is there a schedule for M2 & M3 parity?
- Will there be scroll support out-of-the-box for LazyColumn?
- In what scenarios should I create a custom layout vs use Row/Column/Box?
- So there will be no XML layouts?
- When should I use Modifier.alignByBaseline()?
- How to migrate an app built in Java to Compose?
- Can I pass multiple modifiers in a Composable?
- When will scrollbars be supported?
- Why is RecyclerView faster than Lazy Lists?
- Will there be any impact on performance if we use more columns?
- Lots of Compose features are experimental. How concerned should we be using these features in production?
- What are some tips to debug custom Compose layouts?
- Why should we use composed { } when creating custom modifiers?
- Do I still need to use ConstraintLayout?
- When should I use SubcomposeLayout?
- Which architecture is most suitable for a Compose app?
- What is the fastest way to switch from XML to Compose and migrate ongoing projects?

#android #compose