Docs
Documentation
Everything about drawing a screen and getting code out of it.
Everything here is about one thing: drawing a screen and getting real code out of it. If you are new, the two pages below are the whole picture in about ten minutes.
Start here
Getting started takes you from an empty canvas to exported code. Read this first.
Why the canvas is the source of truth explains the one idea the product rests on and the layout trade-off it requires. Read this second, especially if you are evaluating whether we fit your project. It is the page most likely to tell you we do not.
What you can build is the full inventory: every shape, control, text setting and export option, with what each one proves about the code you get. Read this when you want to know the ceiling.
Per platform
Each guide covers what that generator produces, what it handles well, and where it stops.
Working with the product
- Controls and inputs, turning a box into a button or a text field, and how auto-growing multiline fields push content down.
- Exporting, getting the code out and what you own.
Two things worth knowing up front
Screens do not stretch to fit. You design a screen at one device size, and it exports at that size rather than rearranging itself for other screens. To cover a phone and a tablet, you draw two screens. This is a direct consequence of how the fidelity works, and the fidelity guide explains why.
The device you pick decides which languages you can export. SwiftUI is not offered for Android devices, and React Native is not offered for desktop. A language only appears where we can fully build for it, so you will never pick one that cannot work.