Native Flutter integration

オープン
  • 何か問題がありますか？
#394 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@AKASH80047 がすでに取り組んでいます。

2026年9月7日 から。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
dart, flutter
領域
mobile

調査の方向性

Start by reviewing the existing JavaScript/TypeScript runtimes and OpenUI Lang features to identify what a Dart runtime and Flutter renderer would need to support. Use the proposed openui_lang, openui_flutter, and examples/flutter_chat modules as a starting shape. Done means Dart can define component libraries, generate prompts, parse streamed output, render common primitives, expose callbacks, and demonstrate an end-to-end streaming chat flow.

索引モデルが issue の本文から書いたものです。

説明

enhancement help wanted

Is your feature request related to a problem? Please describe.
OpenUI currently focuses on JavaScript/TypeScript runtimes and examples. Teams building Flutter apps do not have a native way to define OpenUI component libraries, generate OpenUI Lang prompts, parse streamed OpenUI Lang output, or render generated UI directly as Flutter widgets.

This means Flutter integrations would likely need to rely on a WebView, a custom bridge to the web runtime, or an app-specific parser/renderer. That adds friction for Flutter teams and makes OpenUI harder to adopt in mobile products that are otherwise fully Dart/Flutter.

Describe the solution you'd like
Add native Flutter/Dart support for OpenUI.

The integration should make it possible to:

  • Define OpenUI component libraries in Dart with typed props.
  • Generate system prompts from those component definitions.
  • Parse OpenUI Lang output, including streamed/incremental output.
  • Render parsed OpenUI Lang into Flutter widgets.
  • Support common OpenUI primitives such as layout, text, forms, buttons, lists, tables, and charts where feasible.
  • Expose action/event callbacks so generated UI can trigger app behavior.
  • Provide a minimal Flutter sample app showing an end-to-end streaming chat flow.

A good first version could focus on the core Dart runtime and Flutter renderer, with parity for the most common OpenUI Lang features before expanding to the full component surface.

Describe alternatives you've considered

  • Use a WebView and render the existing React runtime inside Flutter.
  • Keep OpenUI rendering on the server and send pre-rendered UI to the app.
  • Build a custom app-specific Dart parser for a limited subset of OpenUI Lang.
  • Use React Native instead of Flutter for mobile OpenUI experiences.

These options work around the gap, but they either reduce native integration quality or create duplicated protocol/rendering work.

Additional context
This would make OpenUI more useful for teams building cross-platform mobile apps with Flutter. It would also help position OpenUI Lang as a portable UI generation protocol that can target native mobile frameworks, not only web runtimes.

Potential package/module shape:

  • openui_lang for parsing, validation, prompt generation, and streaming state.
  • openui_flutter for Flutter widget rendering.
  • examples/flutter_chat for an end-to-end demo.
主要言語
TypeScript
スター
10k
フォーク
698
平均マージ
1日 6時間
マージ済み PR（30日）
148

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

thesysdev/openui のほかの issue

thesysdev/openui の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。