Skip to content
Blog

The LG webOS SDK: Flutter Comes to LG Devices

LG announced an upcoming webOS SDK for building Flutter apps that target webOS devices. Here is what the SDK promises — Firebase, gamepads, hot reload — and why big-screen Flutter matters.

Published on • October 2, 2026

AI Assistant

Flutter’s platform list keeps growing. Alongside the 2026 Toyota RAV4 infotainment system, Flutter 3.44 announced another target for the big screen: an upcoming LG webOS SDK that will let developers build Flutter apps for webOS devices.

Source: What’s new in Flutter 3.44, The Flutter Blog, May 20, 2026.

What LG announced

The Flutter team’s language in the 3.44 release notes is carefully hedged — “on the verge of launching” — but the scope is concrete:

LG is on the verge of launching the webOS SDK to help developers easily build Flutter apps that target WebOS devices, empowering Flutter for the big screen and beyond. The webOS SDK will include plugin support for Firebase, video players, gamepads, and more. It’ll even come with support for all of the Flutter features that you know and love, like stateful hot reload and state management with Riverpod.

Three things stand out in that paragraph:

  1. Firebase support as a first-class plugin. Auth, Firestore, and analytics on TV-class devices means real product apps, not just demos.
  2. Gamepad support. TV and set-top interfaces are driven by remotes and controllers, not touch. Input abstraction is the hard part of any new Flutter platform, and it’s being addressed up front.
  3. Stateful hot reload. A sign the SDK targets a genuine Flutter toolchain — not a stripped-down renderer that merely executes Dart.

Why webOS is a meaningful target

webOS runs on LG’s smart TVs and, through licensing, a range of other connected devices. Historically, TV app development meant web technologies wrapped in platform-specific runtimes — a lowest-common-denominator stack where performance and native APIs were afterthoughts.

Bringing Flutter there gives you:

  • A single codebase spanning phone, desktop, web, automotive, and now television.
  • Impeller-rendered performance — relevant on TV hardware where GPU drivers can be quirky and shader compilation hitches are painfully visible on a 4K panel.
  • The existing plugin ecosystem — or at least the Firebase/video/gamepad slice of it, which covers most TV app requirements.

Flutter’s embedded momentum

webOS doesn’t exist in isolation. The 3.44 release frames Flutter as “everywhere, everyday, built by everyone,” citing:

  • The 2026 Toyota RAV4 multimedia system running embedded Flutter.
  • LG webOS devices as the next embedded target.
  • Canonical leading multi-window desktop support.
  • 1.5 million monthly developers and 1.3 billion pub.dev package downloads in 30 days.

The roadmap reinforces this with work on Flutter Engine extensibility for out-of-tree platforms — improving the embedder API so new platform targets can be authored outside the core repo. That’s the structural bet: if adding a platform is a community/OEM effort rather than a Google-scheduled one, platforms like webOS, Fuchsia, and automotive stacks can ship on their own timelines.

What developers should do now

Since the SDK was described as launching “in the coming weeks” as of May 2026:

  1. Follow the Flutter release notes and blog for the official launch post — plugin availability and minimum webOS versions will land there.
  2. Audit your app’s platform channels. Any custom native code (MethodChannels, Pigeon interfaces) needs a webOS implementation before your app can port.
  3. Design for 10-foot UI. Revisit text sizes, focus traversal, and remote-control navigation. Flutter’s desktop input support (keyboard accelerators, focus management, hover) is closer to TV needs than touch conventions are.
  4. Check your plugins. Firebase, video players, and gamepads are promised; long-tail plugins are not. Budget for platform-interface work if you depend on niche packages.

The takeaway

Every new Flutter platform expands what “write once, deploy everywhere” credibly covers. Automotive already proved embedded Flutter works in a demanding, safety-adjacent environment; webOS extends that thesis to the largest screen in the house. For teams already shipping Flutter apps, it’s another deployment target with near-zero marginal UI cost — and for the TV app ecosystem, it’s an upgrade from web-wrapper runtimes to a GPU-composited UI toolkit.