flutter-platform-integrationlisted

# Flutter Platform Integration Prefer an existing maintained plugin when it meets the requirement. Write platform code when the capability is unavailable, product-specific, or requires a controlled native contract. ## Choose the boundary - Use a package API for established cross-platform capabilities. - Use Pigeon or another typed generated contract when a multi-method channel benefits from compile-time structure. - Use a basic method/event channel for small, stable request/response or event surfaces. - Use FFI for suitable native C-compatible libraries and performance-sensitive calls. - Use platform views only when native view embedding is required and account for composition, gestures, accessibility, and performance. Keep domain models outside the channel contract. Version or evolve messages compatibly, validate all values at the boundary, and map platform failures into actionable Dart errors. ## Load references conditionally - Read [integration strategy](references/integration-strategy.md) when choosing among an existing package, channels or Pigeon, FFI, JS interop, and platform views. - Read [plugin development](references/plugin-development.md) when creating or evolving a reusable plugin package, federated implementation, platform interface, or multi-platform native API. `flutter-package-development` owns reusable public APIs, package shape, compatibility, federation decisions, consumer quality, and publication readiness. Use both skills when package design and na