docs: add Sage's native Flutter integration to ADOPTERS.md

Open
  • Is something wrong?
#1,412 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
flutter
Domain
documentation

Research direction

The change is a single entry in ADOPTERS.md, under the Framework ecosystem section, with the Community integration status. Read the existing entries first to match their format and check whether the project accepts such listings. Do not open a PR until a maintainer approves the proposal, as the author requests. Done means the entry is added in the existing style, with working links, and nothing else in the repository changes.

Written by the indexing model from the issue text.

Description

Following the issue-first contribution guidelines, would you accept a small ADOPTERS.md entry for Sage under Framework ecosystem, marked Community integration?

I maintain Sage. Its 2.1.0 release uses @openuidev/lang-core for parsing streamed OpenUI Lang and maps the resulting tree into a native Flutter renderer. This is a supported component subset, not the upstream Web renderer or OpenUI Cloud Reports API.

Proposed entry:

  • Sage — Uses the official OpenUI Lang parser with a native Flutter renderer for streaming interactive interfaces in Sage Desktop.

The intended change is limited to this adopter entry. I’ll wait for maintainer approval before opening a PR. No endorsement or commercial relationship is implied.

Disclosure: this proposal was prepared with AI assistance and checked against the published source and release documentation. I have not independently run an interactive desktop or live-model compatibility test for this proposal.

Dominant language
TypeScript
Stars
10k
Forks
698
Avg merge
1d 6h
Merged PRs (30d)
148

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thesysdev/openui

All issues in thesysdev/openui

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.