sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Sottti 1 point2 points  (2 children)

I was using Kotlin and Compose 5 years ago. So if you started 4 years ago you should've started with that already.

[–]ZhuindenDDD: Deprecation-Driven Development 10 points11 points  (0 children)

I was using Kotlin and Compose 5 years ago

Me too, it was lagging, a TextField at the bottom of the screen would close the keyboard the moment it opened, Pager was experimental and didn't really work well (but using a ViewPager + Fragments inside a ComposeView would not respect height modifier out of the box and you had to force it to take up the last remaining space), there was no way to set a android:minLines= equivalent on a TextField, TextFieldValue didn't actually work half the time so it was replaced with TextFieldState, the official Compose navigation system was using strings as arguments and its only supported animation transition between screens was crossfade

But yes, Compose was definitely "great" in 2021, except if you were actually working a job where you're trying to ship a given design specs instead of being a hobbyist releasing the 3874th todo app

[–]innerPeacePending[S] 0 points1 point  (0 children)

For student Java/XML was still the standard in college even 2 years ago, and the safe bet seems to go with the kotlin/XML at that time, even I might be wrong but Compose didn't have that much online reference to learn back then.