Migrate to Compose

[Manish-Bannur]

Is your feature request related to a problem?
XML layouts can become complex and hard to manage, especially with nested views and intricate designs. Maintaining and updating these layouts can be cumbersome and time-consuming. Furthermore, XML-based UIs often require additional boilerplate code in Activity and Fragment classes to manipulate UI components, leading to less readable and maintainable code.

Describe the solution you'd like:
Propose to transition our UI implementation from XML-based layouts to Jetpack Compose. Jetpack Compose offers a modern, declarative approach to building UIs in Android

Describe alternatives you've considered:
Continuing with XML-based layouts: While this maintains the status quo, it doesn't address the issues of complexity and maintainability.
Using a hybrid approach: Gradually introducing Jetpack Compose for new features while maintaining existing XML layouts for older components. This can reduce the initial transition effort but might lead to inconsistencies in the codebase.

[skydoves]

Hey @Manish-Bannur, thank you for raising this issue. I'm considering to support Jetpack Compose on the next release :)