Beta is a delivery boundary, not a slogan
This path is usable, but the right expectation is controlled validation rather than broad production rollout by default.
Feature Page · Figma to Unity Beta
Evaluate the current Figma to Unity path before you treat it as production-ready
Start by clarifying the Beta boundary, then review the safest validation order before trial.
Figma to Unity is currently a Beta path. Validate it in a small real project scope before you treat it as a broad rollout candidate.
Start from a representative module
The safest way to evaluate the path is to test one real Unity screen first and only then expand the scope.
Roadmap, docs, and support each solve a different need
Use roadmap for maturity, docs for setup, and community for project-specific blockers.
Suggested setup order
1
Confirm the current Beta boundary
Use roadmap first so the whole team shares the same expectation for maturity, coverage, and delivery risk.
2
Prepare account and design-source access
Check prerequisites, API key binding, and access-token extraction before you spend time debugging engine-side behavior.
3
Validate one real Unity screen
Choose a small but representative screen so you can judge structure, naming, and output quality in context.
4
Route project-specific blockers into community
Once the trial reaches real project constraints, use the community and feedback page instead of forcing every edge case into docs alone.
Best fit for teams like these
- Your team already uses Figma and wants to test whether Unity UI delivery can be automated in a controlled scope.
- You need an English page that speaks to workflow readiness, not only a translated product slogan.
- You are willing to validate Beta in a contained module before expanding into a wider production path.
Check these before moving forward
- Do not assume Beta means the same thing as a fully released production path.
- If the project needs the most stable current path, compare this path against released Unity/Cocos options first.
- Do not start trial until invite-only access, API key binding, and design-source token setup are already clear.
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.
Figma to Unity is currently a Beta path. Validate it in a small real project scope before you treat it as a broad rollout candidate.
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
Does Beta mean the path is unusable?
No. It means the path works, but stability, coverage, or production readiness still need contained validation before a broader rollout.
Why is the first CTA roadmap instead of signup?
Because current status has to be clear before signup. If the team does not understand the boundary, the trial path gets noisier and less reliable.
Where should project-specific blockers go?
Once the issue is no longer a standard setup question, move it into community support and feedback rather than keeping it in docs alone.
Next steps
Browse Feature Pages
View related pages in this category and choose the next route that best matches your workflow.
Figma to Unity guide
Start with the guide if the current question is still “can we validate this Beta path safely?”
Unity UI delivery workflow
Step back into the broader Unity delivery flow before you decide how to evaluate the Beta path.
Integration guide
Use the public integration guide when you are ready to test the first Unity build path.
Pricing
Review access and plan expectations before moving into trial.
Community
Use the public support page for capability gaps, project blockers, and real feedback.