Hi, great video, thanks for pro tips. Could you explain how did you solve the problem with nods in layout inspector? I'm struggling with it very often..
Good stuff bruther. So I'm assuming my class could still be marked Immutable if it doesn't get its properties directly updated anywhere, but those underlying properties might be updated from the database? Like my list is a list of items that can be edited/updated in another screen, but the properties aren't directly updated anywhere in the list screen. If that makes sense.
My LazyList with Cards (Checkbox + Labels) got recomposed whenever a new Card got added, despite that the Array is immutable and never changes. The initial buildup of the screen really took some time but with your steps it solved the issues. Ty!
In the third example would the solution also be to make the collection as immutable list? Then the data class wouldn't contain any mutable properties and shouldn't be marked as unstable right?
if images count changed from repository but uuids are generated in subsequent sessions, the uuids will changed for same data all the time. Is there some problem for lazy column animation?
Super video. However, if I have understood you correctly, @Immutable and @Stable cannot be applied to constantly changing lists. For example, if you load the data with a pager, can you only show a loading animation or is there also a way to improve performance and only recompose the newly loaded data and not the existing data in a lazy column?
Just make sure all the items in data class have val so when you are updating data you have to use copy function and you will be good to go and will be able to use Immutable and Stable without worries
@@ggstbthat’s my way to go but if I have an list inside of an data class, I‘m running into an recompose and this is also an problem if I'm using the Paging 3.0 Library.
When I debug the app using an emulator the app runs perfect, but if I debug it on my cell phone the app has a lot of lag. When I searched the internet, I found that changing the Build Variant from debug to release fixes it and it really works. Do you know why this could happen?
Thanks for the video! Another option for making the MyImage class stable is to replace the List type with a Kotlin immutable collection type, such as ImmutableList.
Have you ever run into the issue that the Run button in Android Studio loads an old version of the app onto the emulator? Sometimes after I change code, and click Run app, it loads a version with old code, before I made the changes, or EVEN earlier, before a lot more changes were made. Any way to fix this?
I encountered something similar to what you have described. Whenever I cleared the app's cache then the app was reset to the oldest version. Still remember being confused in front of the client as the feature that was working suddenly didn't. I turned out it was what I have mentioned.
I just wanted to thank you for all the help and support yo you've done for me by sharing your experiences ❤
Fantastic… i never heard about this annotation for data class. Thanks to share that .
The last tip is awesome, thanks!!!
I'll apply this after holidays, thanks a lot 👌
Was Waiting for this ❤️
Hi, great video, thanks for pro tips. Could you explain how did you solve the problem with nods in layout inspector? I'm struggling with it very often..
Good stuff bruther.
So I'm assuming my class could still be marked Immutable if it doesn't get its properties directly updated anywhere, but those underlying properties might be updated from the database? Like my list is a list of items that can be edited/updated in another screen, but the properties aren't directly updated anywhere in the list screen. If that makes sense.
My LazyList with Cards (Checkbox + Labels) got recomposed whenever a new Card got added, despite that the Array is immutable and never changes. The initial buildup of the screen really took some time but with your steps it solved the issues. Ty!
This is what i needed
@Philipp can you suggest me what is best way to use multiple state in composable screen.
In the third example would the solution also be to make the collection as immutable list? Then the data class wouldn't contain any mutable properties and shouldn't be marked as unstable right?
if images count changed from repository but uuids are generated in subsequent sessions, the uuids will changed for same data all the time. Is there some problem for lazy column animation?
thank you man your the best
Informative video, thanks. Can you please do a tutorial on video compression.
Great video, thanks, Philipp. Is it also reasonable to add baseline profile for lazy column scrolling? I usually encounter lags on first few scrolls
Yes, absolutely
great man, great man ❤
Thanks. Really appreciate your videos
I love this guy, since he is saying "those images are from the real camera" 😅
Can you make video on zoom custom ui, does it have any resources?
Just a query:
How about ImmutableList instead of @immutable ?
what is the alternative of actionMode and menuInflater in jetpack compose?
For backend which lang do you use .And when are going to teach us from scratch ?
Thanks
Isn't there a way to declare the tags as an Immutable List of Strings in the MyImage data class? If possible, then that seems much more intuitive.
I use the official kotlix.collections.immutable library
Super video. However, if I have understood you correctly, @Immutable and @Stable cannot be applied to constantly changing lists. For example, if you load the data with a pager, can you only show a loading animation or is there also a way to improve performance and only recompose the newly loaded data and not the existing data in a lazy column?
Just make sure all the items in data class have val so when you are updating data you have to use copy function and you will be good to go and will be able to use Immutable and Stable without worries
@@ggstbthat’s my way to go but if I have an list inside of an data class, I‘m running into an recompose and this is also an problem if I'm using the Paging 3.0 Library.
When I debug the app using an emulator the app runs perfect, but if I debug it on my cell phone the app has a lot of lag. When I searched the internet, I found that changing the Build Variant from debug to release fixes it and it really works. Do you know why this could happen?
My buddy is life saviour
Thanks for the video! Another option for making the MyImage class stable is to replace the List type with a Kotlin immutable collection type, such as ImmutableList.
Have you ever run into the issue that the Run button in Android Studio loads an old version of the app onto the emulator? Sometimes after I change code, and click Run app, it loads a version with old code, before I made the changes, or EVEN earlier, before a lot more changes were made. Any way to fix this?
Edit configuration of the run config, clean build
I encountered something similar to what you have described. Whenever I cleared the app's cache then the app was reset to the oldest version. Still remember being confused in front of the client as the feature that was working suddenly didn't. I turned out it was what I have mentioned.
I think it has happened to me a couple of times. I simply rerun it and it loads the new code
@@szymonkurpas1172omg yes. And then I went to issuetracker to find the same issue and didn't find any ticket mentions about it
Never got this 🤔
What about adding a rememberLazyListState to the state field of the LazyColumn?
I didn't see you do that
it`s not needed here ( in terms of optimiztion) , it will be needed on customizng the scroll behaivor or get info about your scrolling behavior
❤
isn't data class by default meant to be immutable?
only when all the objects in it is stable. Since regular List is not stable, it is not marked as stable
@@raheemadamboev thank you! Probably I don't use that many data classes with lists.
Why you don't use all the `MyImage` data class as a key?
That is because keys need tobe parcelable.
@@iZakirSheikhhashCode() is pretty parcelable 😊
단순히 텍스트만 있어도 레이지 컬럼은 성능이 좋지 않음.
still am facing lazy column lag...
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
ContactTheme {
Surface(
modifier = Modifier.fillMaxSize(),
color = MaterialTheme.colorScheme.inverseSurface
) {
LazyItem()
}
}
}
}
}
@Immutable
data class User(
val name: String,
val id: String = UUID.randomUUID().toString()
)
@Composable
fun LazyItem() {
val item = (1..100).map {
User(name = "Random name $it")
}
LazyColumn(
verticalArrangement = Arrangement.spacedBy(4.dp),
contentPadding = PaddingValues(6.dp)
) {
items(item,
key = {
it.id
}) {
com.example.contact.ui.presentance.screen.CardContact(name = it.name)
}
}
}
I am learning English but, do you have videos in Spanish? XD
The documentation tells us to strive to keep our class stable without using these annotations.
Please slow down Philipp you speak so fast😅
Android studio is so slow!! ...