Native Flutter integration
Los mantenedores suelen responder en 1 día
@AKASH80047 ya está trabajando en esto.
Desde el 7/9/2026.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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_langfor parsing, validation, prompt generation, and streaming state.openui_flutterfor Flutter widget rendering.examples/flutter_chatfor an end-to-end demo.
- Lenguaje dominante
- TypeScript
- Estrellas
- 10k
- Forks
- 698
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 138
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de thesysdev/openui
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
thesysdev/openui#1445 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Add dataInvention flag to PromptOptions to disable the 'generate realistic/plausible data' ruleAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
thesysdev/openui#959 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 18/100
Los mantenedores suelen responder en 1 día
Todos los issues de thesysdev/openui
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
paperclipai/paperclip#19120 ·
Los mantenedores suelen responder en 1 día
-
Gradle liquibaseDiffChangelog drops jhi_date_time_wrapperPosiblemente ocupada @mraible la tomó hoy. Abiertoarea: triage theme: undefined
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
jhipster/generator-jhipster#35998 ·
Los mantenedores suelen responder en 1 día
-
ai:assign:coding feature p3 ui-ux windows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
CherryHQ/cherry-studio#23569 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
lingdojo/kana-dojo#33602 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
GoogleCloudPlatform/BigQuery-Agent-Analytics-Plugins#16 ·
Los mantenedores suelen responder en 1 día