What's your opinion on Picasso? That seems to be t...

# android

[amanda.hinchman-dominguez]

What's your opinion on Picasso? That seems to be the recommended library to use to easily grab urls and (for my case) project resource drawable images

[gildor]

Very popular image downloading library for Android. What kind opinion are you looking for?
There is also Glide and Fresco, all of them are popular and supported

[gildor]

Why do you need image downloading library to load project resource? Why not just set resource id?

[amanda.hinchman-dominguez]

I guess I'm just wondering why there's a need to create an external library just to use a resource id

[amanda.hinchman-dominguez]

obviously, it's optimal for urls, but I've always found it slightly aggravating that using a local in an image feels like a workaround

[gildor]

But those libraries not for resource id, those libraries created to easily download and cache images from network

[amanda.hinchman-dominguez]

right. Like I said, they're optimal for urls but they're also compatible for local resources

[Alex Stulnikau]

Depends on resource, it could be a heavy task to load

[kingsley]

Hey.
One advantage I’ve discovered for using either of those libraries (I use picasso) to load resources is that, they can help downscale the resource depending on the dimensions of the image view.

This way, you can avoid OOM exceptions in cases where the image is abundantly larger than is needed by the view

[gildor]

Does it really common case to downscale local resources?

[kingsley]

Probably not. Just one more case in favor of the libraries 🙂
Of course. If all you do is slap a resource unto an image view. Then you’re better off doing that without introducing any extra dependency.

But with lots of dynamic loading, animations and all that. It would be an added advantage

[gildor]

I agree, we use it too for a couple cases, just want to say that usually better to avoid this