Is your feature request related to a problem? Please describe.
OpenUI currently focuses on JavaScript/TypeScript runtimes and examples. Teams building Android apps with Kotlin 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 in Kotlin/Compose.
This makes Android integration require a bridge through a web view, a backend-rendered layer, or custom protocol handling in the app. That adds friction for Kotlin-first teams and makes OpenUI harder to adopt in native Android products.
Describe the solution you'd like
Add native Kotlin support for OpenUI, ideally targeting Android and Jetpack Compose.
The integration should make it possible to:
- Define OpenUI component libraries in Kotlin with typed props.
- Generate system prompts from those component definitions.
- Parse OpenUI Lang output, including streamed/incremental output.
- Render parsed OpenUI Lang into Jetpack Compose UI.
- 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 Android sample app showing an end-to-end streaming chat flow.
A good first version could focus on the core runtime and Compose 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 Android.
- Keep OpenUI rendering on the server and send pre-rendered UI to the app.
- Build a custom app-specific Kotlin parser for a limited subset of OpenUI Lang.
- Use React Native for Android instead of native Kotlin.
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 mobile teams that already use Kotlin, Jetpack Compose, and native Android architecture. It would also establish OpenUI Lang as a framework-independent protocol rather than something tied mainly to web runtimes.
Is your feature request related to a problem? Please describe.
OpenUI currently focuses on JavaScript/TypeScript runtimes and examples. Teams building Android apps with Kotlin 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 in Kotlin/Compose.
This makes Android integration require a bridge through a web view, a backend-rendered layer, or custom protocol handling in the app. That adds friction for Kotlin-first teams and makes OpenUI harder to adopt in native Android products.
Describe the solution you'd like
Add native Kotlin support for OpenUI, ideally targeting Android and Jetpack Compose.
The integration should make it possible to:
A good first version could focus on the core runtime and Compose renderer, with parity for the most common OpenUI Lang features before expanding to the full component surface.
Describe alternatives you've considered
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 mobile teams that already use Kotlin, Jetpack Compose, and native Android architecture. It would also establish OpenUI Lang as a framework-independent protocol rather than something tied mainly to web runtimes.