Describe the feature you'd like
Currently, the project uses XML-based layouts and relies on Fragments, which are no longer considered best practice in modern Android development. The recommended approach now is to use Jetpack Compose for building UI components. Migrating to Jetpack Compose would ensure that the project remains maintainable, modern, and easier to work with in the long term—especially as future Android libraries and tools continue to prioritize Compose over XML.
Additional context
Transitioning earlier will help avoid technical debt and make onboarding new contributors easier. Compose also offers better performance, more concise UI code, and native support for themes, previews, and animations.
Screenshots
N/A at this stage—migration would be a structural change.
Would you like to work on the issue?
Yes, I’d be happy to work on this! I’m also open to discussing the broader state of the project and contributing to other issues to help bring more activity to the project.
Describe the feature you'd like
Currently, the project uses XML-based layouts and relies on Fragments, which are no longer considered best practice in modern Android development. The recommended approach now is to use Jetpack Compose for building UI components. Migrating to Jetpack Compose would ensure that the project remains maintainable, modern, and easier to work with in the long term—especially as future Android libraries and tools continue to prioritize Compose over XML.
Additional context
Transitioning earlier will help avoid technical debt and make onboarding new contributors easier. Compose also offers better performance, more concise UI code, and native support for themes, previews, and animations.
Screenshots
N/A at this stage—migration would be a structural change.
Would you like to work on the issue?
Yes, I’d be happy to work on this! I’m also open to discussing the broader state of the project and contributing to other issues to help bring more activity to the project.