👋 Any multiplatform async image loading library that supports local files? (

android.net.Uri

and file://

NSUrl

) I know Kamel but it doesn't support local files.

https://github.com/Kamel-Media/Kamel Not entirely sure if supports local files but think so.

It doesn’t support local files, no 😞 . At least not out of the box.

It has resource fetcher for desktop and Android/jvm. Would be possible iOS plugin hybride I guess.

This is easier, I think. It’s just that the images can be selected locally. Imagine a social network, you are in the edit profile screen, the avatar image is either a remote URI (the API sent you) or a local URI (you selected a file and didn’t submit yet).

Yeah I would do a custom compasable compatible with all variants, Kamel, Coil, Url, File etc and delegate per platform. I do this always to also support Lottie :) Then able to support all frameworks with one image composable you control ;)

🤔 You mean to check if NSUrl is a local file and delegate to Kamel if it is remote and print it with a native solution otherwise?

Yeah :)

That could work 👍 I’ll give it a try!

Also my suggestion work for things like Lottie, video, animated gifs, vectors etc. If can use local or remote but also for remote selecting rendering option per platform. Would also decouple it to like CustomImageSource and different implementation for iOS and Android as of example. Not sure which targets you have. Then having almost everything in commonMain will be possible :)

That’s a good advice, thank you! 👍

@Nacho Ruiz Martin kamel does support local files

Hey, Luca. Sorry I wasn’t super clear! It indeed does support local files with the File API. What I meant is that it doesn’t support local URIs. Meaning

file://

NSURLs on iOS or

content://

android.net.Uri

on Android. I saw 62 and I will study the possibility to contribute to the library by adding support for them. I don’t have spare time now but as soon as I find some I’ll make a proposal 👍 .

@Nacho Ruiz Martin so yeah, it looks like

NSURL

will only resolve remote urls based on how I implemented it. Can you get a path from the

NSURL

? if so you can just use

File("/path/to/image.png")

as I was saying.

That sounds like a really elegant solution. Would you want me to test and contribute that to the library?

https://github.com/Kamel-Media/Kamel/blob/c83ef4ae6ad05bd58a00a51352bda7068057cd02[…]l-core/src/commonMain/kotlin/io/kamel/core/utils/ConfigUtils.kt would need to be modified as well to support multiple mappers per input type

Maybe having something to check if it's applicable just as you have for fetchers?

that or just have a mapper return null if it can’t do it and try the next one if available

Please, create the issue and I’ll try to schedule it 🙂.

Yes, sounds easy. I’ll try to go for it asap. Do you prefer the

//Mapper.kt
...
public fun map(input: I): O?

nullable approach or the

public val I.isSupported: Boolean

new property approach (that would require to update all mappers)?

hmm maybe isSupported would be better. just to be consistent

Ok 👍, let’s go for that.