GlideImage

Start a request by passing model to RequestBuilder.load using the given requestManager and then applying the requestBuilderTransform function to add options or apply mutations if the caller desires.

alignment, contentScale, alpha, colorFilter and contentDescription have the same defaults (if any) and function identically to the parameters in Image.

If you want to restrict the size of this Composable, use the given modifier. If you'd like to force the size of the pixels you load to be different than the display area, use RequestBuilder.override. Often you can get better performance by setting an explicit size so that we do not have to wait for layout to fetch the image. If the size set via the modifier is dependent on the content, Glide will probably end up loading the image using com.bumptech.glide.request.target.Target.SIZE_ORIGINAL. Avoid SIZE_ORIGINAL, implicitly or explicitly if you can. You may end up loading a substantially larger image than you need, which will increase memory usage and may also increase latency.

If you provide your own requestManager rather than using this method's default, consider using remember at a higher level to avoid some amount of overhead of retrieving it each re-composition.

This method will inspect contentScale and apply a matching transformation if one exists. Any automatically applied transformation can be overridden using requestBuilderTransform. Either apply a specific transformation instead, or use RequestBuilder.dontTransform]

Transitions set via RequestBuilder.transition are currently ignored.

Note - this method is likely to change while we work on improving the API. Transitions are one significant unexplored area. It's also possible we'll try and remove the RequestBuilder from the direct API and instead allow all options to be set directly in the method.