You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jetpack Compose is the new popular UI toolkit for Android Apps. https://developer.android.com/jetpack/compose
It has some significant advantages over XML and it seems like XML make be deprecated in future. It can be used along with XML so I suggest someone who is interested in working on this issue can start with a very basic activity and see how difficult is to move from XML to Jetpack Compose.
Please note that working on this issue would first need approval from collaborators and also extensive knowledge of the app codebase.
The text was updated successfully, but these errors were encountered:
Hi @madhurgupta10, @nicolas-raoul , @psh
Seems like I am pretty late into discussion towards this. I am working on #6063, so while migrating the rxjava to retrofit would it be okay if I implement it using hilt.
Can you explain why you need Hilt? It seems to me that the principle of state hoisting puts dependencies in the right place for existing Dagger injection to serve them without adding an extra dependency.
Hilt is a dependency injection built on top of Dagger, it is much easier to understand and implement than Dagger. https://developer.android.com/training/dependency-injection/hilt-android
Flows is a Kotlin extension for coroutines and works best along with Jetpack Compose. https://developer.android.com/kotlin/flow
Jetpack Compose is the new popular UI toolkit for Android Apps. https://developer.android.com/jetpack/compose
It has some significant advantages over XML and it seems like XML make be deprecated in future. It can be used along with XML so I suggest someone who is interested in working on this issue can start with a very basic activity and see how difficult is to move from XML to Jetpack Compose.
Please note that working on this issue would first need approval from collaborators and also extensive knowledge of the app codebase.
The text was updated successfully, but these errors were encountered: