Flutter.
Now on Apple TV.

Same create , run , build , devices commands you know. Same hot reload. Same DevTools. Targets tvOS. flutter-tvos use <version> switches release lines, each pinning a Flutter SDK and the engine built for it.

Siri Remote swipes and clicks flow through Flutter's standard Focus / Shortcuts / Actions . MFi game controllers and BT keyboards work too.

Scaffolds a dedicated tvos/ project — its own Info.plist, AppDelegate and SceneDelegate on the UIScene lifecycle, a Swift package graph and a Podfile beside it. Federated *_tvos plugin model.

Debug, hot reload and DevTools work on a physical Apple TV over the wireless tunnel — not just the Simulator. Release and profile ship AOT, Metal-only throughout. An Apple TV attaches over the network rather than over USB, so the attach is slower than a cabled iOS device and the Simulator stays the fast-iteration path.

Built with the tvOS 27 SDK, an app that does not use the UIScene lifecycle will not launch on tvOS 27 at all. New projects get scenes, and an unmodified existing runner is migrated on its next build — AppDelegate , scene manifest and storyboard.

Apple rejects an app whose embedded engine is not signed by the developer (ITMS-91065). flutter-tvos signs the engine on your machine with your own distribution certificate on every device build, and forwards an App Store Connect API key to xcodebuild on machines with no Xcode account signed in. Verified through TestFlight.

Run flutter-tvos plugin port on any iOS or macOS Flutter plugin from pub.dev, a local path, or git. The transformer widens platform guards ( #if os(iOS) → tvOS), strips tvOS-incompatible APIs, and emits a buildable *_tvos package ready to publish.

Published under the fluttertv.dev verified publisher: shared_preferences_tvos , video_player_tvos , path_provider_tvos , sqflite_tvos , audioplayers_tvos , url_launcher_tvos , and 19 more, including the Firebase family. flutter pub add and ship. 7 of them ship a Swift package; the rest are resolved through CocoaPods, which coexists with it in the same project.

Every Flutter stable is picked up automatically: the pipeline decides whether the tvOS engine has to be rebuilt, ports the patch set, builds all six engine variants, publishes artifacts carrying their licence notices, bumps the CLI and gates the release on an end-to-end run: a real app on a tvOS simulator, and device builds compiled and checked. It runs on Codemagic , on Apple silicon, and the engine for a new Flutter release is usually published within days of it.