I Bet You DON'T Know These 3 Performance Optimizations for your Jetpack Compose UI

preview_player
Показать описание
When your Jetpack Compose UI isn't running as smoothly as you'd like, you need to optimize something. In this video I'll show you 3 ways to do this you might not think about at first.

⭐ Get certificates for your future job
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

💻 Let me be your mentor and become an industry-ready Android developer in 10 weeks:

🎓 Become an industry-ready developer in the Mobile Dev Campus:

🎁 Get my FREE 4.5h course "The Best Practice Guide to Android Architecture":

Read our weekly Android blog:

Join this channel to get access to perks:

Get the source code for this video here:

Join my Discord server:

You like my free content? Here you can buy me a coffee:
Рекомендации по теме
Комментарии
Автор

You're amazing Philipp! I'm at the last 4 chapters of the book I'm reading. About Jetpack and clean architecture using MVVM. What you're teaching is the same to what I'm reading! Just amazing!

vilmarcabanero
Автор

Amazing content! Did not get it before but now that I got a performance problem where I work, it helped me to understand the issue. I'm doing MVI and I have a function that executes actions on the view model with lambdas and was generating recomposition :) Thanks Philipp

radbaver
Автор

All the things that were used to be ignored in View framework using Kotlin are now starting to become integral part of EVERY steps in compose world, even the simplest thing like inlining function will save you tons of headaches in compose which arent that significant in the View Framework before

maximooze
Автор

allright, the problem react faced, the jetpack compose are also need to face~~

yexia
Автор

Key function is very helpful, thanks for this advanced video

abada-s
Автор

This was amazing, please make more videos like this!!!!

rahul_spawar
Автор

Immutable classes are not stable, what all about them is that we cannot change its properties, so when we want to have a mutable stable version of them we wrap them with State Object which is a Stable class that have one property called value

abada-s
Автор

Thanks for this very useful information. I have a problem with first on performance issue! 👍👍👍

anvarzaripboyev
Автор

9:28 you can put the remember inside the parameter directly instead, it will work

agungwatanabe
Автор

this video was awesome
well done Philipp

capitalwww
Автор

Great video. Wish there was an Android Studio plugin that could detect these code smells

Rafael-hkpg
Автор

at 6:38 button recomposed 18 times, does anyone knows why?

HimanshuKhanna-fz
Автор

Just finished your Jetpack Compose playlist. Very well explained and thanks for sharing.

LightBueno
Автор

Hello Phillipp, how do you see the market for Jetpack Compose?. I'm thinking of starting to learn it.

renanzumas
Автор

Awesome, hope in black friday to buy some course of you

giovanni_siciliano_ivano
Автор

Can I use Android library on desktop compose??

BashPSK
Автор

I have a screen where is loaded (using an AsyncImage) a background image. The image is a local image loaded from the resources. Why does everytime recomposed the Image even if it is always the same image?

federicocreti
Автор

Wow Philipp, amazing video.. i have to open a refactoring ticket now :D

makzimalist
Автор

We only need to create mapper classes if we're doing cross-module communication right? Also any way of detecting that as well?

rahul_spawar
Автор

What's the reason for method reference to be stable even if the class it belongs to is unstable?

ilaletopisnyj