Should Android apps adopt Jetpack Compose as the default UI toolkit for new projects?

16 Eyl 19:45

With Jetpack Compose maturing and receiving regular updates, many teams consider switching from XML‑based layouts to a declarative UI approach. What are the practical implications for code maintainability, performance, and team onboarding when making Compose the default for all new Android projects? Have you encountered any hidden challenges during early adoption, and how do you weigh those against the long‑term benefits? Looking for experiences and thoughts on making this strategic decision.