Skip to main content

Open your app.
Keep it in Git.

Lindi reads your project folder and draws its screens on the canvas. Connect GitHub, and every branch opens as a file.

Opening an app in Lindi, as a looping animation: the tavola-app project folder is dragged into Lindi, which reads its Swift and puts its 5 screens on the canvas. The camera closes in on the Menu screen, which turns into the SwiftUI it is read from and back. A designer then recolours its Add button, and beside the screen a pop-up shows the line of Swift that change is, ready to push.

From a folder
to your screens.

  1. Choose the folder

    In Lindi Desktop, create a Code Designed file and choose the folder that holds your app, in your Mac’s own folder dialog.

  2. Lindi reads it

    Lindi Build looks at the folder, says what it is built with and which screens it sees, and offers to draw them.

  3. The design system first

    Colours, type and shared components are drawn first, onto a Design System page of their own.

  4. Then every screen

    Each screen arrives as layers you can edit, built from those components, in one step you can undo.

Open the app
you already have.

Choose your project folder in Lindi Desktop and its screens are on the canvas, read from the code they are written in. This is what it reads today.

  • SwiftUIiOS

    Read from your Swift, with nothing run. Lindi finds the screens and draws them at iPhone size, in your asset-catalog colours.

    Text, colours and fonts publish back into the Swift.

  • React / Next.jsWeb

    Lindi runs your app and captures each page as it renders. Next.js pages are found for you.

    Words and tokens publish back into the source.

  • AngularWeb

    Pages are found from your routes and drawn from the code, with nothing run.

  • Jetpack ComposeAndroid

    Read from your Kotlin, with nothing run. Screens are drawn at phone size, in your Material theme.

    Colour and size tokens publish back into the Kotlin.

  • HTML/CSSWeb

    A plain site, no framework needed. Every .html file in the folder is a page.

  • Other web appsWeb

    A web app on a dev server, such as a Vite app. Lindi runs it, and you add the paths to capture.

NextFlutter, React Native

Your design tokens come with the screens: CSS variables, your Tailwind theme, asset-catalog colours and Compose colour schemes.

What comes
onto the canvas.

  • Screens you can edit.

    Frames with real layers and real sizes. A SwiftUI app’s screens are grouped into flows by feature, with prototype links read from its navigation.

  • Your components, as components.

    Shared components become library components, and the screens use them as instances. Change one and every screen that uses it follows.

  • Your tokens, as variables.

    Colours, sizes and type come in as variables, with light and dark modes where your code has them.

The code moves on.
The canvas keeps up.

Changes from the code wait for you.

When the code changes outside Lindi, the screens it touches are listed under “Incoming from code”. Compare your design with the code, then accept the change or keep your design.

  • Nothing is redrawn until you accept it
  • Side by side, or one over the other
  • Accept one screen, or all of them
  • SwiftUI and Compose are checked when you open the file

Publish writes your design into the code.

Change a screen and publish. Lindi writes what it can straight into your files, and hands the rest to Lindi Build as one prompt with the file and the line.

  • Text, style and tokens written in place
  • A file that changed on disk is refused, never overwritten
  • The rest goes to Lindi Build, which shows you each edit
  • Publishing needs the folder on this computer

Git, the way your
team already uses it.

Lindi reaches GitHub through its own GitHub App. You choose which repositories it may use, and you can disconnect at any time.

  • Connect GitHub.

    In Settings, under Integrations. It is not a way to sign in: Lindi uses it only to reach the repositories you grant.

  • Link a repository.

    Link a repository to a project, and every branch of it can open as a file in that project.

  • Clone onto your Mac.

    Lindi Desktop clones a repository of up to 500 MB into a new folder, ready to open.

  • A branch for each session.

    Start a Lindi Build session on its own branch, in its own folder. Finish by merging it, opening a pull request, or keeping the branch.

  • Pull requests from Lindi.

    Open a pull request for a branch from the top bar. GitHub decides the merge, and your reviewers review it as they review everything.

  • Commit, pull and push.

    Lindi Build’s Git tab stages, commits, fetches, pulls and pushes, with the Git credentials you already have.

What Lindi does
with your code.

  • Only folders you choose.

    Lindi reads and writes only inside folders you picked yourself, in your Mac’s folder dialog. Choosing a folder allows Lindi to make changes in it.

  • What leaves your Mac.

    When Lindi Build works on a project, the files and command output it needs go to Lindi’s servers and to our AI provider.

  • Careful with Git.

    Lindi never force-pushes, never commits files that look like secrets, and creates new repositories as private.

Before you import.

Which apps can Lindi import?

SwiftUI, React / Next.js, Angular, Jetpack Compose, HTML/CSS and other web apps. Flutter and React Native are next.

Do I need the desktop app?

Yes. Importing, running, publishing and cloning happen in Lindi Desktop, on a Mac with macOS 11 or later. On the web you design on the screens, link repositories and open pull requests.

Which plan do I need?

Importing your code, publishing to it, and cloning and pushing start at Professional. During early access nothing is charged.

How many screens can a file hold?

Up to 160 screens for a SwiftUI app and 64 pages for a web app. A file holds one app.

My app is in a monorepo. Which folder do I choose?

The app’s own folder: the one with its package.json or its Xcode project.

Will importing change my code?

Reading and drawing your screens changes nothing. For a web app, Lindi Build adds a small lindi-library folder and a development-only page to your project, so it can draw your components. It shows you each edit before it makes it.

Does Lindi work with GitLab or Bitbucket?

Linking repositories and pull requests work with GitHub only. Lindi Build’s Git tab commits and pushes to whatever remote your repository already has.

Put your app on the canvas.

Lindi is free for its early users. Sign up, open your project, and your screens are on the canvas.

  1. 1Sign up, free
  2. 2Open your project folder in Lindi Desktop
  3. 3Connect the agent you code with
  4. 4Push your first change into your code