wing • Chapter time to focus on R&D and personal growth • We aim in providing the best experience for our users using the latest tech and guidelines. • Task force of 3 engineers to read, learn and create a guide on how the chapter will migrate from XML UI to Compose • Focus on new screens, migrate old screens for training and awareness • Dedicated support channel for engineers • Constant feedback from team helped shape our Compose Guidelines
to make simpler UI structures • Redrawing (Re-composition) the UI is avoided as much as possible causing a smoother experience for the user. • Re-compositions can be easily checked through the layout inspector to find issues with your UI.
can be used in existing Activities/Fragments • Navigation Integration: Compose can be integrated with existing navigation graphs • View Interoperability: Compose can be used in XML and vice-versa (ComposeView, AndroidView) • Data Flow: Compose can work with existing data flow frameworks such as LiveData and Flow.
and error our screens are now comprised of the following: • a Fragment • a ViewModel • a UI state class • a UI transformer • a composable function In the following slides you will see how these work together in one of our screens (Vodafone eShop).
screen, we use multiple small views (UIView) that each has its own data class (UIViewData). The example on the right is of a generic text view we use for many different screens.