Export and generation

Yuntu separates editable documents, standard JSON handoff, and generated application code. Choose the output that matches the next step in your workflow.

Export standard JSON

1. Finish relevant edits and check the intended project in the project list.
2. Open that project's menu and choose Export.
3. Select the standard JSON tab and check the output directory.
4. If your downstream tool requires a specific format, inspect the available version options rather than assuming the newest version is compatible.
5. Start the export and wait for its completed result. Read any diagnostics before consuming the output.

The package contains versioned UI information, mappings, and the resources and schemas required by that export. Keep the package together. Do not combine an old UI file with mappings from another export or edit hash-checked files in place.

Standard JSON is Yuntu's versioned exchange format. It works without installing a code generator, and it is not a substitute for the original editable project.

Enable a generation program

The export workflow can register compatible programs for one project or for reuse from a chosen global location. Inspect the program's identity, version, supported input formats, target, and runtime requirements before enabling it.

Registration and execution are separate steps. Importing a program does not mean that it has generated or built your app. Target tabs appear for enabled programs; a missing target is not an invitation to substitute another platform silently.

Project-scoped programs move with the relevant project setup. A globally registered program may need separate installation on another machine. Use a program you trust: generation programs run code in your development environment.

Generate and validate

Choose the target tab, check its selected program and options, and explicitly run generation. The optional official Web exporter produces React and TypeScript for its supported subset. Your own program can adapt the handoff to a different framework or component system.

Keep generated output separate from authoring source. Integrate application behavior, data, and services in your development project, then build and run the result. Check layout, assets, fonts, and interactions at the intended sizes.

Handle unsupported content

Support varies by format version, document type, and generator. Complete official Android and iOS generation is outside the current first-release scope. Not every effect, media workflow, component, or independent document is supported by every target.

When export reports an unsupported object or dependency, use the diagnostic to locate it. Update the chosen workflow, simplify that content deliberately, or use a compatible generator. Do not treat missing output as a successful complete export.

Exporting does not publish your application or upload your source project. Deployment belongs to your target application's own workflow.