Summary
On Android, scrolling a plain Flutter ListView that sits on top of an ArcGISMapView (for example in a bottom sheet) runs at a much lower frame rate (visible jank) than the identical screen with the map removed. The map is idle while the list scrolls. In a minimal project the Flutter frame rate during the scroll falls from about 83 fps to about 22 fps on a Galaxy M14, from about 105 fps to about 67 fps on a Galaxy Tab S11, and from about 111 fps to about 78 fps on a Galaxy S25 Ultra.
ArcGISMapView uses Flutter's Hybrid Composition on Android (PlatformViewsService.initExpensiveAndroidView in lib/src/geo_view.dart). We would like a supported way to choose a cheaper mode (Texture Layer, initSurfaceAndroidView).
Environment
arcgis_maps 300.0.0+4935 (300.1.0+5042 still calls initExpensiveAndroidView). Flutter 3.44.9 stable, Impeller, profile builds, minSdk 30.
Devices: Galaxy M14 (Exynos 1330, 90 Hz, Android 15), Galaxy S25 Ultra (120 Hz, Android 17), Galaxy Tab S11 (120 Hz, Android 16).
Minimal reproduction (no API key needed): the full project (pubspec, Android config) is on GitHub as getorobo/arcgis-list-jank-repro, and I can share it another way on request. A condensed version of the screen is below: the Stack in the Scaffold body, where controller is an ArcGISMapViewController and onReady sets an ArcGISMap whose basemap is a tiled layer for the public World_Imagery service.
One screen: ArcGISMapView (public World_Imagery tiles) full screen, with a DraggableScrollableSheet holding a ListView of 100 simple cards. Build with MAP=true and with MAP=false (the map is replaced by a ColoredBox), then swipe the list repeatedly. Build commands:
flutter build apk --profile --dart-define=MAP=true --dart-define=SHEET_PCT=60 --dart-define=SHEET_MAX=60
flutter build apk --profile --dart-define=MAP=false --dart-define=SHEET_PCT=60 --dart-define=SHEET_MAX=60
// condensed repro screen (lib/main.dart)
Stack(children: [
Positioned.fill(
child: kMap
? ArcGISMapView(controllerProvider: () => controller, onMapViewReady: onReady)
: const ColoredBox(color: Colors.blueGrey),
),
DraggableScrollableSheet(
initialChildSize: 0.6, minChildSize: 0.2, maxChildSize: 0.6,
builder: (context, sc) => Material(
child: ListView.builder(
controller: sc,
itemCount: 100,
itemBuilder: (context, i) => Card(
child: ListTile(
leading: const CircleAvatar(),
title: Text('Layer $i'),
subtitle: const Chip(label: Text('Feature Layer')),
trailing: IconButton.filled(onPressed: () {}, icon: const Icon(Icons.add)),
),
),
),
),
),
])
Measurements
Frame rate is counted from Flutter's own timeline (launching with the trace-systrace extra, Perfetto, GPURasterizer::Draw slices per second over six consecutive one-second swipes), three runs per row.
Device | Map visible | Map removed | Drop (mean of runs) |
|---|
Galaxy M14 | 19.9-24.9 fps (Draw 28-34 ms) | 83.4-83.7 fps (about 3 ms) | about 73% |
Galaxy Tab S11 (landscape) | 66.3-67.0 fps (Draw 4.0-4.1 ms) | 104.1-110.4 fps (1.8 ms) | about 37% |
Galaxy S25 Ultra | 76.7-79.1 fps (Draw 8.9-9.1 ms) | 107.1-115.1 fps (1.4-1.5 ms) | about 30% |
High-end hardware hides most of the cost (about 30-35% here) but does not remove it. In our production app (a heavier Flutter UI) the same list over the same map runs at about 17-18 fps on the M14.
What the traces show
On all three devices every Flutter frame is presented twice (QueuePresentKHR, alternating ImageReader surfaces below and above the platform view). Flutter's raster work runs on the Android main thread and waits for the GPU each frame, then the system composites the result again. In the production app on the S25, SurfaceFrame::Encode is about 3 ms per surface versus 0.49 ms in the minimal project, so a more complex Flutter scene is paid for twice per frame in this mode.
What we tried
Texture Layer: patching initSurfaceAndroidView into geo_view.dart. On the M14, in our app, the interval between screen changes went from about 53 ms to about 21 ms (measured 2026-11-02 with screen recording, not re-measured). Map render, pan, pinch, tap and resume still worked in a quick check; we did not verify identify, editing, offline maps, drawing, 3D or iOS.
ARCGIS_MAPS_USE_TEXTURE=true as a dart-define (undocumented switch in the plugin): similar improvement, but idle CPU was about 111-117% of a core versus about 42-44% because of the per-frame pulse.
Flutter's io.flutter.embedding.android.EnableHcpp=true in AndroidManifest.xml (Android 14+ with Vulkan; older devices fall back): in the production app on the M14 the frame rate rose from 16.7-18.5 fps to 37.1-38.9 fps (three runs each). Costs: about +80 MB resident memory (S25), idle CPU unchanged, no crash on an Android 11 emulator. Flutter documents it as experimental, and it does nothing on Android 11 to 13, which is where the weakest devices are.
Questions
(1) Is there a supported way to choose the Android platform-view composition mode (for example a parameter on ArcGISMapView)?
(2) Is ARCGIS_MAPS_USE_TEXTURE an intended, supported option? If so, could the per-frame pulse be avoided when the map is idle?
(3) Could Texture Layer become the default on Android, and is that on the roadmap? Or is there a known reason Hybrid Composition is required (touch, keyboard, accessibility, rendering fidelity)?
(4) Any known issue with EnableHcpp and ArcGISMapView?
Perfetto traces for the rows above are available on request.