Real-Time Communication 

Between Flutter and Game Engines

Real-Time Communication Between Flutter and Game Engines /
Stream data bidirectionally between your Flutter application and embedded game engines.

Feature Hero

Real-Time Data Streaming

Stream events, state, and assets between Flutter and your game engine with bidirectional communication channels and built-in integrity verification.

High-Performance Channels

Game Framework establishes optimized communication channels between Flutter and your game engine. Binary protocols minimize serialization overhead, delivering sub-millisecond message delivery for local communication.Game Framework establishes optimized communication channels between Flutter and your game engine. Binary protocols minimize serialization overhead, delivering sub-millisecond message delivery for local communication.

High-Performance Channels

Bidirectional Flow

Data flows both ways between Flutter and the game engine. Send commands, UI state, and configuration from Flutter to the engine. Receive game events, state updates, and scene information back in real-time.

Bidirectional Flow

Stream Types for Every Use Case

Choose the right stream type for your use case: event streams for discrete interactions, state streams for continuous synchronization, and asset streams for progressive content loading.

Stream Types for Every Use Case

Stream Types

Store, organize, and access all your game assets from a single source of truth.

Event Streams. Discrete events from either side. Touch inputs, game events, UI triggers—delivered reliably and in order.

Event Streams

State Streams. Continuous state synchronization. Game state flows to Flutter for UI updates; Flutter state flows to the engine for game logic.

State Streams.

Asset Streams. Progressive asset loading. Stream large assets in chunks, with progress callbacks and cancellation support.

Asset Streams.

Raw Messages. Send and receive unstructured data directly between Flutter and your game engine through the MethodChannel bridge. Ideal for custom payloads, debug info, or engine-specific data formats that don't fit standard event or state patterns.

Raw Messages
Automatic Reconnection
Automatic Reconnection
Streams automatically retry with exponential backoff when the engine connection is interrupted.
Backpressure Handling
Backpressure Handling
Configurable throttling and batching prevent slow consumers from being overwhelmed by fast producers.
Message Ordering
Message Ordering
Messages maintain FIFO order through indexed chunking and sequential queue flushing.
Delivery Confirmation
Delivery Confirmation
CRC32 checksums and SHA256 hashes verify data integrity on every transfer.

Frequently Asked Questions