OpenWeatherMap.Cache VS FFImageLoading - Fast & Furious Image Loading

For example I use it in another library I made at https://github.com/MarkCiliaVincenti/OpenWeatherMap.Cache. Here I ensure that if there's an API request to get the weather of a particular location, whilst it's doing so it will not launch another API request to get the weather of the same location concurrently but instead wait for the result of the ongoing call and use the same response.

It doesn't need to be related to finance or databases. Could be related to physical file access, doing operations on UDP packets received, limiting API requests (eg trying to get weather for a location concurrently doesn't make sense, so wait for the result of the ongoing one and provide the result to the second one, that's what I'm using in https://github.com/MarkCiliaVincenti/OpenWeatherMap.Cache). I'm sure you can be creative and think of plenty of other use cases.

I'm fairly sure that you could achieve this using https://github.com/luberda-molinet/FFImageLoading

Look into http caching. For MAUI / Xamarin Forms I recommend using FFImageLoading for displaying images from an URI. It handles caching automatically and I have used it in my projects.

I use FFImageLoading and it works well. Just make sure to manually add the latest SkiaSharp NuGet package to your Android project because otherwise SVGs won't render in Android 10+.

For image caching you might find https://github.com/luberda-molinet/FFImageLoading helpful in your endeavours. For FB login check https://devblogs.microsoft.com/xamarin/authentication-xamarin-essentials-aspnet/

2nd for https://github.com/luberda-molinet/FFImageLoading for image loading & caching needs. Supports SVGs which might be useful for map caching.