Create a small design and keep the source editable
Open Design in a build that includes the feature, then create or open a design project. Start with one screen or flow and a brief describing the audience, task and essential states. Generation may request missing material information before proceeding.
The local LDF document holds page source and design settings. Use the canvas and inspector to refine the result. Select an element when a requested edit concerns that element, then inspect whether the proposal preserved the surrounding layout. Availability depends on the installed build and the configured service.
Review AI proposals and local changes
AI generation uses a hosted service with server-selected models; it is separate from Code's configurable BYOK workflow. Local editing and local storage do not mean that generation runs offline. Selected prompts, design source and requested context may leave the device.
If you change the document during generation, review the saved proposal before applying it. Reopen the project after a significant edit and verify that the intended version was saved. A completed generation is still a proposal to inspect, not evidence that the interface is correct.
References: Licuse data practices
Use preview to inspect behavior
The editing canvas does not execute page JavaScript. A separate sandboxed preview runs page interactions. Preview presets use logical CSS dimensions, with optional frames and safe-area guides. They help inspect layout, while real browser and device checks remain necessary.
Click through the main flow and an error path. Identify any simulated behavior, such as a form that displays confirmation without calling a service. Keep that limitation visible when sharing the prototype.
Export the project with its assets
A folder export includes the LDF document, assets and generated standalone page files. Keep the folder structure intact so relative references resolve. An LDF export is a design export; private conversation history is stored separately and is not a substitute for a portable design handoff.
Review the exported page in a separate location. If you need React components, application routing, authenticated data or a deployed service, plan those as implementation work. The current export does not provide those integrations automatically.
Choose the tool by the deliverable
Licuse can suit someone who wants editable static prototypes beside code and UI design. If your team needs an established shared component library, simultaneous multiplayer design, native app delivery or a specific design-file interchange format, verify those requirements directly before adopting it.
A collaborative design editor, framework-native prototype or your existing component environment may fit better. This guide is published by Licuse and describes the implementation rather than an independently benchmarked comparison.
Use Licuse Design for an inspectable prototype and portable static output. Keep application integration, production behavior and real-device validation as explicit next steps.
Sources & further reading
References checked October 18, 2026. Features, prices and account eligibility can change; check the live documentation. Inclusion here is not a hands-on test or vendor endorsement.