Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributeirondash_engine_context

Provides Dart access to Flutter engine components for native/FFI code.

pub.devRemove
jni

Provides Dart/Flutter bindings to call native Java code via JNI.

pub.devRemove
ScoresHealth5690 (best)
Maintenance2999 (best)
Quality7697 (best)
Popularity5487 (best)
Community4680 (best)
Compatibility93 (best)79
UsageDownloads (30 days)184k11M (best)
Likes964 (best)
Pub points140 / 160160 / 160 (best)
GitHub stars69281 (best)
MaintenanceLatest release0.5.5, a year ago1.2.1, yesterday (best)
Major versions in 12 months0 (best)1
Contributors2100+ (best)
Publisherirondash.devdart.dev
FitPlatformsAndroid, iOS, Windows, macOS, LinuxAndroid, Windows, Linux
WASM-readyYesNo
KindPlugin (native code)Plugin (native code)
Code generationNoNo
Direct dependencies1 (best)8
LicenseMITBSD-3-CLAUSE
Setup effortMediumMedium
JudgementStrengths
  • Simple API to retrieve engine handles and registrars.
  • Supports Android, iOS, Windows, macOS, and Linux.
  • Designed for Rust/FFI integration.
  • Low‑level access to Java without writing platform channel code
  • Works on Android, Windows, and Linux
  • Integrates with JNIgen for automated binding generation
Weaknesses
  • Limited to engine context; no other utilities provided.
  • Requires native code knowledge to use effectively.
  • Requires native build setup and familiarity with JNI
  • Limited to platforms that support JVM (no iOS/web)
  • Potential for memory‑management bugs if misused
Warnings
  • Native setup
  • Native setup
irondash_engine_context vs jni: which Flutter package should you use? | pubscout