Unity_Kit는 Flutter 프로젝트 내에서 Unity 3D 게임 및 애플리케이션을 원활하게 통합할 수 있도록 해주는 Flutter 플러그인입니다. Flutter와 Unity 간의 효율적인 통신을 위한 타입 지정 브리지와 바이너리 프로토콜을 제공하여 고성능을 보장합니다. AR 기능을 지원하며 Android, iOS, Web, Windows, Linux, macOS와 호환됩니다. Flutter의 UI 기능과 Unity의 강력한 3D 렌더링 및 게임 로직을 결합하고자 하는 개발자에게 이상적입니다.
사용 사례
Flutter 앱에 Unity 3D 게임 삽입
Flutter와 Unity로 AR 경험 만들기
크로스 플랫폼 3D 콘텐츠 전달
풍부한 그래픽을 갖춘 하이브리드 앱 개발
기존의 유니티 자산을 플러터 워크플로우에 통합하기
주요 기능
안전한 데이터 교환을 위한 타입 브리지
저지연 통신을 위한 이진 프로토콜
Unity 장면에서의 AR 지원
다중 플랫폼 호환성 (Android, iOS, 웹, 데스크톱)
최소한의 오버헤드로 효율적인 성능
적합한 대상
3D 또는 AR 애플리케이션을 구축하는 Flutter 개발자
Unity를 사용하는 게임 개발자 중 플러터 UI를 원하는 사람
크로스 플랫폼 상호작용 경험을 만드는 팀
고성능 3D 렌더링이 필요한 프로젝트
기존 Unity 프로젝트를 현대적인 Flutter 앱에 통합하는 개발자
고려 사항
Unity 프로젝트 설정 및 구성이 필요합니다
성숙한 플러그인과 비교해 문서가 제한적
Flutter와 Unity 간 상태 관리에서 잠재적인 복잡성
Unity 런타임으로 인해 앱 크기가 증가할 수 있습니다
완전한 배포를 위해 플랫폼별 빌드 단계가 필요합니다
원본 README
연결된 소스 저장소의 README 원문 스냅샷입니다. 최신 내용은 저장소에서 확인하세요.
Unity Kit
A Flutter plugin for Unity 3D integration. Embed Unity content in Flutter apps with typed communication, lifecycle management, asset streaming, and support for Unity 2022.3 LTS through Unity 6.
📚 Documentation
Full hosted documentation — a complete zero-to-running walkthrough, native setup guides, API reference and troubleshooting — lives at codigee.com/open-source/unity-kit.
Flutter handles UI (screens, buttons, navigation). Unity handles 3D (rendering, game logic). They run in the same app but are separate worlds -- they talk by sending JSON messages through a native bridge.
Flutter (Dart) Unity (C#)
UI, screens, JSON messages 3D rendering,
business logic <=========================> game logic
native bridge (iOS/Android)
There are no direct method calls. Everything goes through serialized JSON over the platform bridge. Flutter never calls C# directly, and Unity never calls Dart directly.
Repository Structure
.├──unity_kit/# Flutter plugin package (published to pub.dev)│├──lib/# Dart source code│├──android/# Android native layer (Kotlin)│├──ios/# iOS native layer (Swift)│├──unity/# C# scripts for Unity side│├──example/# Example Flutter app│├──test/# Test suite (35 files, 640+ tests)│└──doc/# API reference & asset streaming guide├──doc/# Detailed guides│├──unity-export.md# Step-by-step Unity export guide│├──unity_integrations.md# Content loading methods (scenes, Addressables, etc.)│├──android-integration.md# Android native architecture & known issues│├──ios-integration.md# iOS native architecture & known issues│└──architecture.md# Overall architecture overview└──.github/workflows/# CI/CD (auto-tag + pub.dev publish)
Key Features
Feature
What it does
Typed Bridge
UnityMessage objects instead of raw strings. Structured, type-safe communication.
Copy unity_kit/unity/Assets/Scripts/UnityKit/ into your Unity project. A FlutterBridge GameObject auto-creates on scene load and handles all communication.
// Receive messages from Flutter
public class MyHandler : FlutterMonoBehaviour
{
protected override void OnFlutterMessage(string method, string data)
{
switch (method)
{
case "StartGame":
// do something
NativeAPI.SendToFlutter("{\"type\":\"game_started\"}");
break;
}
}
}
For downloading 3D content from a server at runtime:
1. Flutter downloads content_manifest.json from CDN
2. User selects a toy/asset in the UI
3. Flutter downloads the .bundle file to local cache (SHA-256 verified)
4. Flutter tells Unity: "cache is at /path" (SetCachePath)
5. Flutter tells Unity: "load asset with key 'alphie'" (LoadToyRemote)
6. UnityAddressables loads from local cache (not from network again)
7. Unity sends "toy_loaded" back to Flutter
Building Addressables
Setup (one-time):Flutter > Setup Addressables
Add asset: place prefab in Addressables group, set address key
See doc/faq.md for the full list. Here are the top issues:
Black screen after Unity loads (Android)
Unity needs an explicit "refocus" after attaching to the view: windowFocusChanged(true) + pause() + resume(). This is handled by unity_kit automatically. If you see a black screen, check that you're using the latest version.
Touch not working (Android)
Unity's New Input System requires InputDevice.SOURCE_TOUCHSCREEN on touch events. The UnityContainerLayout in unity_kit fixes this. If touch doesn't work, make sure you're not overriding the touch handling.
White/blank screen (iOS)
Usually a timing issue: Unity's Metal renderer needs a non-zero view frame before initialization. unity_kit polls with waitForNonZeroFrame(). If it persists, ensure the UnityView widget has a non-zero size in the layout.
Release build works differently than debug (Android)
ProGuard/R8 can strip classes used via reflection or JNI. unity_kit's Build.cs auto-adds ProGuard keep rules during export. If you see silent failures in release, verify proguard-unity.txt contains keep rules for com.unity_kit.** and com.unity3d.player.**.
Messages not reaching Unity / Flutter
Check FlutterBridge GameObject exists in the first scene
Check your handler's target name matches what Flutter sends
Check Unity Console for [UnityKit] No handler registered for target: xxx
On iOS: verify UnityKitNativeBridge.mm is in Assets/Plugins/iOS/
Environment preflight
Before mounting a view, ask what the build actually carries:
final env = awaitUnityKitPlatform.instance.environment();
if (!env.isReadyForUnity) {
// No Unity runtime in this build: a UnityView would come up blank.debugPrint(env.summary);
}
if (env.failsPageSizeRequirement) {
// Google Play rejects updates targeting Android 15+ whose native// libraries are aligned to less than 16 KB.debugPrint('Not 16 KB aligned: ''${env.unalignedLibraries.map((l) => l.name).join(', ')}');
}
env.summary prints a single line for logs, for example:
The Unity 6 class rename.env.runtime says which player class was
found, so a build that silently shipped without the Unity libraries is
obvious instead of showing up as an empty surface.
16 KB page sizes. Since 1 November 2025, Google Play requires every
native library in an app targeting Android 15 (API 35) or newer to be
aligned to 16 KB. Unity satisfies this from 2022.3.56 and from
Unity 6, but an app can still ship an older prebuilt .so. The check
reads the p_align of each PT_LOAD segment out of the shipped files, so
it reports the binary's truth rather than the Unity version's claim.
iOS reports the runtime and page size but no alignment verdict: the 16 KB
rule is an Android packaging requirement.
Unity 6 compatibility
unity_kit uses reflection to detect Unity 6's UnityPlayerForActivityOrService class automatically. No manual configuration needed. If you're using Unity 6 and see issues, check the Android Integration guide for constructor signature details.
Roadmap to 1.0
3D model loading utilities and prefab management helpers
Full step-by-step tutorial covering the complete integration flow
Additional example scenes and sample Unity project