Workflow questions need a dedicated page
A workflow search should not fall back to the homepage or pricing page by default. It needs a page that explains where each next step belongs.
Solution Page · Unity UI Delivery Workflow
For Unity UI delivery, separate status, setup, and the next step before you talk about trial
Use this page to separate Unity workflow status, setup, and the right next step before trial becomes the question.
The safest current Unity path is still a released path such as Lanhu to Unity. Figma to Unity should still be evaluated with Beta expectations.
Source-to-engine paths are not interchangeable
Even inside Unity, the right next step changes depending on whether the current path is released or Beta.
Docs come after status clarity
The integration guide is strongest when the team already knows which path is being evaluated and what delivery boundary it belongs to.
Suggested workflow order
1
Name the exact path first
Do not stay at the vague “Unity automation” layer. Resolve the source-to-engine combination before you evaluate anything else.
2
Use roadmap as the maturity source
Release status, Beta meaning, and later-stage planning should be read from roadmap, not inferred from a landing-page headline.
3
Use docs and prerequisites for setup
Once the path is clear, move into prerequisites and the English integration guide instead of jumping straight into trial.
4
Use community for real project blockers
When the issue becomes team-specific or project-specific, move out of generic guidance and into public support.
Best fit for scenarios like these
- You need one clear English workflow route instead of bouncing between homepage, FAQ, and docs with no clear sequence.
- The team wants to understand how roadmap status, setup work, and trial timing connect in one Unity workflow.
- You want a realistic evaluation path, not a claim that every Unity scenario is equally mature today.
Check these before rollout
- If the project is still mostly comparing manual vs automated delivery, read the comparison page first.
- If the team is already focused on one narrow path, move into that path detail instead of keeping everything at the workflow level.
- Do not treat this as a replacement for setup docs or project-specific support.
Capability Status
Confirm the current delivery boundary before planning rollout
Use the roadmap as the source of truth for what is released, what is in Beta, and what is still planned.
The safest current Unity path is still a released path such as Lanhu to Unity. Figma to Unity should still be evaluated with Beta expectations.
Released
Lanhu → Unity
Beta
Lanhu → Cocos, Figma → Unity, and Figma → Cocos
Planned
Platform expansion beyond Unity plus the planned agent and plugin marketplace
FAQ
Common questions
When should I start here?
Start here when the team is working through workflow and handoff questions such as “Unity UI delivery workflow” or “how to hand design files to Unity development.”
Why do I still need roadmap first?
Because workflow planning without maturity clarity creates the wrong expectations. Status has to come first.
Should I register before reading docs?
No. The safer order is roadmap first, prerequisites second, integration guide third, and only then a contained trial decision.
Next steps
Browse Solution Pages
View related pages in this category and choose the next route that best matches your workflow.
Design-to-Unity handoff guide
Start with the handoff guide if the team is still asking how design files should be handed off before setup begins.
Unity UI automation guide
Start with the automation guide if the current question is how to begin automation, not only what to review next.
Review Figma to Unity path
Move into the Figma to Unity path details if the current evaluation is already centered on that Beta route.
Prerequisites
Review account, API key, and design-source access before trial.
FAQ
Use FAQ for invite-only access, Beta meaning, pricing, and common blockers.
Community
Project-specific blockers and capability requests should continue in community.