Unfortunately, this will break if the parent updates. You can see what I mean if you load it up in a playground with this: https://gist.github.com/dav....

You're right. Each time parent is updated, ImageLoadingView gets recreated, but onAppear will be called only once. ImageLoader will be also recreated and won't contain previously loaded image. Looks like we need to cache image loader instances and trigger image loading in different place, e.g. like here. It feels so ugly though, having this shared state to cache loaders. We can also not cache loaders at all and make image cache an implementation detail of particular ImageLoadable (e.g. UIImage does not need it at all, image loading for URL can be delegated to e.g. Kingfisher)

I'll try to update the article as soon as possible after refining the above approach - making it work with any ImageLoadable etc.