I had been discussing with @louwers also re. maplibre/maplibre-native#1151 (comment) how to structure the Android-specific code.

I notice that there is currently some deprecated annotations code in maplibre native, and a non-deprecated (but highly confusingly essentially duplicate) implementation here in the plugins. Most of the maplibre plugins are currently also unmaintained.

It can also be confusing for developers that there's two separate sample apps (one for maplibre-plugins-android and one for maplibre-native android).

For these reasons we think that the current situation is rather messy and should be cleaned up. One possibility would be to move the plugins into maplibre-native.

Possible benefits (if done correctly):

• remove deprecated code and replace it with working one
• less confusing structure
• tighter integration has benefits regarding APIs for users (more sensical structure)