Uli Bubenheimer

…ntent non-nullable Fixes #493

android-maps-compose 4.3.2 Marker info windows do not preserve visibility across configuration changes. One would expect this functionality to be covered by `MarkerState`, which offers access to info window visibility, and...

fix: make DefaultMapProperties, DefaultMapUiSettings, and NoPadding public

1

Fixes #513

android-maps-compose 4.3.2 The `GoogleMap()` compose function uses certain default expressions on optional parameters that are not public. This prevents overriding the function in app code in a reasonable manner. This...

GoogleMap() subcomposition performs excess recompositions

2

android-maps-compose 4.3.0 The GoogleMap() implementation's subcomposition performs excess recompositions. Specifically, starting with the third composition, the subcomposition always performs an additional composition, i.e. it recomposes twice for every change. I...

Flag non-remembered State object creation

1

android-maps-compose 4.3.0 It appears that accidental misuse of android-maps-compose state objects like `MarkerState` without `remember()` is common. It would be nice to have the UI/Lint flag such usages.

Potentially overly slow initial map composition caused by exhaustively setting *all* possible map configuration options

2

android-maps-compose 4.3.0 I see an avoidable performance hit in the code for the initial `GoogleMap()` subcomposition run: the code essentially configures all possible Map configuration options in an exhaustive manner,...

Map initialization with desired configuration is delayed

1

Setting an initial camera position for the GoogleMap is commonly done by passing an appropriately initialized CameraPositionState parameter to the GoogleMap() Composable. While reviewing the android-maps-compose code (4.3.0) I noticed...

GoogleMap() currently uses `null` for a default `content` parameter. This seems an unusual approach to me, plus less descriptive than using `{}` and keeping the parameter non-nullable. It also slightly...

The GoogleMap() implementation uses a gazillion individual rememberUpdatedState() calls. This is unwieldy and likely contributed to #481. Instead, a single State object encapsulating the individual state properties can be used...