Separate Dart and Flutter

_↴ Ported from [flutter/genui#600](https://github.com/flutter/genui/issues/600) — originally opened by [polina-c](https://github.com/polina-c) on 2025-12-11._
_Original labels: P2_
_Original assignees: [polina-c](https://github.com/polina-c)_

---

From @jacobsimionato :

Empower the community to build ACX and Jaspr renderers by refactoring the Gen UI package to separate generic Dart logic from Flutter-specific logic “By the end of the quarter, a developer can build a DOM-based web application using the core of the Gen UI SDK”.
We could refactor our genui package to separate the core Dart logic from the Flutter rendering utilities and implementation of the standard catalog. There would be a separate genui_flutter package containing this flutter-specific code. This would allow the community to easily build Jaspr and ACX A2UI renderers which depend on the shared genui package. This would also be a positive architectural change for us.
Catalog items should plug in to the library

---

### 1 comment(s) from the original issue

**[parlough](https://github.com/parlough)** commented on 2025-12-12:

Exciting to see this is a goal! Thanks for the hard work :D

\cc @schultek A possibility to explore in the future :)

The work involves refactoring the genui package to separate core Dart logic from Flutter-specific rendering utilities. Start by examining the current package structure to identify what is generic and what is Flutter-specific. The goal is to create a new genui_flutter package, allowing other renderers like Jaspr and ACX to depend on the shared core.

由索引模型根据 Issue 内容生成。