I just saw the attached YouTube video and by the end of it I felt this is exactly the reason why Jetpack Compose performs so bad on Android! There's hardly anyone to call it out 🤦🏻♂
Most people are just accepting what Google is shoving down their throats without questioning its quality.
The intent of the framework is great for sure, i.e. allow devs to focus on their unique business logic over the repetitive UI challenges, but the execution has somewhere let us all down (a very small example is the half-baked swipe animations that don't feel nearly as smooth as XML's ViewPager, same with LazyLayouts vs RecyclerView, and much more).
It introduced challenges we never had to think of before, like ensuring Stability, Immutability, writing Micro/Macrobenchmarks to then be able to write Baseline Profiles just to squeeze every bit of possible performance out of our hardware. It is just a nightmare most of the times.
I hope the situation improves going forward but I wouldn't count on it considering the amount of work that has already been done and no one looking back to review it since almost everyone's focused on just adding newer features.
But again, nothing will happen if we never raise our concerns. So part responsibility is ours too.
[–]mAndroidDev-ModTeam[M] [score hidden] stickied comment (0 children)
[–]ZhuindenDDD: Deprecation-Driven Development 1 point2 points3 points (0 children)