Currently when a user uploads an image only the path to the image and some metadata is being stored in the database. So when the image is being loaded in the feed the dimensions of the image are unknown until the image is downloaded. This is a problem because as the image is being processed the scrollview is not aware of how big the image is so it allocates an arbitrary scale to the image. So when the image is actually loaded the scrollview fragment is resized, the user can see the resizing happening and that's a big no no. I propose to add the dimensions of the image in the metadata, then use that scale to appropriately define how much space the image is going to use, so there's no resizing to be done once the image is done loading.
Currently when a user uploads an image only the path to the image and some metadata is being stored in the database. So when the image is being loaded in the feed the dimensions of the image are unknown until the image is downloaded. This is a problem because as the image is being processed the scrollview is not aware of how big the image is so it allocates an arbitrary scale to the image. So when the image is actually loaded the scrollview fragment is resized, the user can see the resizing happening and that's a big no no. I propose to add the dimensions of the image in the metadata, then use that scale to appropriately define how much space the image is going to use, so there's no resizing to be done once the image is done loading.