12 size variants of one image. Multiply that with 8. Is there a better and optimized way to scaling images?
By the way, this is a snippet of the tree structure of the JSON response.
I have seen similar things before in websites that are either built by site builder, magazines, and luxury product sites. I can understand the need for resolution but is this the industry standard?
To be honest, I am just curious about the process and how did they come to this decision. I am trying to learn by reverse engineering websites.
Like what’s going through the mind of the back end developers mind? 12 variants for the same image. Does the web designer show the design and the front end guy says “yeah I need twelve different size variants of the same image” something like that?
And the backend developers solution is to store 12 variants of each image in the database? How unusually large the storage must be for a single website. So, what will be the other solution then is to create or resize a mother image to the desired scale based on the API call? So more computation cost.
The reasoning behind this is the question.