Feature Description

With jnigen and the generated JNI classes it's possible to replace pigeon with direct interop. This has a performance boost (sometimes even 10x!) and supports synchronous calls. Some calls to the MapLibre Android SDK need to be on the UI thread. This thread is called the platform thread inside dart and can get called via runOnPlatformThread. Methods that require the platform thread can stay async while the other methods can become sync.

Checklist

• Replace pigeon with JNI inside MapLibreMapStateJni. Reference implementation for something that needs to run on the platform thread:

  flutter-maplibre/lib/src/native/widget_state_jni.dart

  Lines 424 to 441 in 4d0c6db

  	Future<LngLatBounds> getVisibleRegion() async {
  	final projection = _jniProjection; // necessary to use it in platform thread
  	final jniBounds = await runOnPlatformThread<jni.LatLngBounds>(() {
  	final region = projection.getVisibleRegion();
  	final bounds = region.latLngBounds;
  	region.latLngBounds.release();
  	region.release();
  	return bounds;
  	});
  	final bounds = LngLatBounds(
  	longitudeWest: jniBounds.longitudeWest,
  	longitudeEast: jniBounds.longitudeEast,
  	latitudeSouth: jniBounds.latitudeSouth,
  	latitudeNorth: jniBounds.latitudeNorth,
  	);
  	jniBounds.release();
  	return bounds;
  	}

• Make MapController methods that don't require the platform thread synchronous.