-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jetpack compose #901
Comments
Hi i wanna contribute to it |
Cool @realjoni17, although I don't think the app is in a good state for this yet. Compose is somewhat in flux and has some weird UX differences that I would need to hack around to maintain parity with the existing app, so it would be a very delicate and gradual migration. Additionally, I would also need to do some drastic refactors to the current app architecture just so Compose's idioms actually work, hence #761. Will let you know when the app is good to go for this. |
I hope this app will not migrate to compose |
Hey @Koitharu, do you have anything to share on compose's drawbacks? The most I'm aware of is that it has similar problems to i.e flutter apps, where some components just don't feel quite right. But I think like basic lists and detail views would be able to benefit from compose and they seem pretty native from what I know. |
but compose have great upperhand upon xml . due to its flexibility and easy to maintain. i also wanted to contribute let me know if its possible. |
I'm just...hesistant @navneet851. Lots of things in android "look" simple and ergonomic and then crumple into something worse than the "old manual system" once you apply it to something real-world and complex. I have a really high bar for UI stability and if compose doesn't meet it I'm better off with normal XML. |
once you try it you would never look back , i guarantee it. its that simple and effective. |
you can watch my song streaming app UI on my github all made upon jetpack compose. |
Give up and move literally everything but the nightmarish bottom sheet scaffold to Jetpack Compose.
I'm just tired of the state management issues in the current UI. Working with React during my summer internship and on other projects has been actually enjoyable, compared to the current View model. It would also allow me to do nice little animations easier and actually keep up with Android Studio's rapid deprecation of XML.
I'll try to do it within reason, maintaining the same exact user flow fundamentally and trying to avoid making the app feel "weird". Would guess this co-incides with #761.
The text was updated successfully, but these errors were encountered: