I have a query while reading through the article. Please help me understand:

1. “Picasso loads the full-size image into the memory and relies on GPU to resize that image to fit into the size of the ImageView. While Glide loads an image that is already resized as per the ImageView, that requires significantly less memory than loading the full image like Picasso. This helps to prevent your app from throwing popular OutOfMemoryError.” — But then Glide has to store several such images if we have Imageviews of different sizes. The memory consumption then would be much more than that of Picasso. Isn’t it?
2. “This will reduce the time your user has to see image loading spinners without sacrificing quality.”

— Loading the thumbnails of say, 1/10th of the required size sacrifices the quality. Isn’t it? Till the original image replaces the thumbnail, the user will have to look at the thumbnail which is of 1/10th the quality of the original Image. Please clarify…