Jetpack compose

[OxygenCobalt]

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.

[realjoni17]

Hi i wanna contribute to it

[OxygenCobalt]

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.

[Koitharu]

I hope this app will not migrate to compose

[OxygenCobalt]

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.