100% guessing here, but native apps sometimes use recycling virtualized lists. That means as you scroll the list will reuse the container that renders the post title and image. Often the image is still being fetched but you already know the title. So as you scroll, it reuses a post you previously saw, instantly swaps in the new title, but the new image is still loading, so an image from a previously post in the list is displayed.
the result is you many only need to render and reuse 10 posts in the list, even if the list contains hundreds of posts.
Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.
Yeah, that’s why key props are important. And sanity checks too. But too many programmers these days just turn off eslint rules without understanding why they exist
Happens here too
100% guessing here, but native apps sometimes use recycling virtualized lists. That means as you scroll the list will reuse the container that renders the post title and image. Often the image is still being fetched but you already know the title. So as you scroll, it reuses a post you previously saw, instantly swaps in the new title, but the new image is still loading, so an image from a previously post in the list is displayed.
the result is you many only need to render and reuse 10 posts in the list, even if the list contains hundreds of posts.
Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.
Yeah, that’s why key props are important. And sanity checks too. But too many programmers these days just turn off eslint rules without understanding why they exist