Good thing:
I like how simple it is to set it up with AWS.
Complain:
The problem we had was that we used GatsbyJS for the front end, and we HAD to use gatsby-source-strapi because of the images (and we didn’t have a great experience with it), which meant we had to stop using graphql only because of the images.
So I guess the complain is not directly linked to de Media Library plugin, but of the Strapi/Gatsby stack handling of images. This is a very popular stack for many good reasons, and we thought you supported it better (the gatsby-source-strapi is an official Strapi Plug-in).
Feature I would like to see:
The number one reason of why we use GatsbyJS for the front-end is because of gastby-images-plugin wich crops the images automatically, and can even give us a SVG format of it wich is great for performance.
So basically I would like to see that with the automatic crop of the images, a SVG version to be generated too.
And (in a more abstract level) try to mimic the functionality of gatsby-images-plugin by maybe giving a React image component that is meant to go with Strapi Media Library so that I don’t have to care about optimizing and displaying the images properly.
Good handling of images is probably the biggest difference between a performant site and a slow one, but is a pain to do it right, maybe Strapi can give us a hand on that.
Outside of that it has worked very well for us