This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/flutter/customize.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Customize Flutter Nutrient SDK with native APIs

Access native Android, iOS, and Web APIs in Flutter

Markdown version of this page, suitable for AI agents and automation

Nutrient Flutter SDK builds on the Nutrient iOS, Android, and Web SDKs. It exposes a subset of their APIs through a cross-platform Flutter API. When you need a native capability that isn’t available on the cross-platform API, use platform adapters.

Platform adapters replace manual native bridging

In earlier versions, accessing a native API required you to bridge it yourself. You had to fork the plugin and write Pigeon(opens in a new tab) channels for iOS and Android, or use dart:js on the web.

As of Nutrient Flutter SDK 6, the SDK uses generated native bindings: Java Native Interface (JNI) on Android, Foreign Function Interface (FFI) on iOS, and JavaScript (JS) interop on the web. Refer to the platform adapters guide to use that same mechanism as a supported extension point.

Platform adapters are the recommended way to access native SDK functionality because they:

  • Require no plugin fork and no Pigeon code generation.
  • Provide direct, typed access to native iOS, Android, and Web SDK objects.
  • Use the same bindings architecture that the SDK uses internally for document, annotation, form, and event operations.

Next steps

Use these guides to continue: