Lyre / documentation
Early accessGet Lyre

Your first project on a phone

Set up your computer, pair your phone, and try one small change.

What you need

  • A supported computer with Lyre Studio open.
  • The Lyre mobile app for your phone (iOS or Android, subject to release availability), on the same trusted network for the first test.
  • A project folder, or a coding provider set up to help you create one.

Use the download section and check the release notes for your build. Start on your home or work Wi-Fi, rather than a guest network that isolates devices.

1. Describe one useful thing

Give your assistant a goal and an example. You don’t need to name a framework. Ask for a plan before asking it to change files.

“Help me make a checklist for opening our café. I want to tick off tasks and see what is left. Start with a simple web version and explain your plan before changing anything.”

Read the proposed steps. Ask what a command will do if you are unsure. An assistant can make mistakes; checking the result is part of the workflow.

2. Open and start the project

Select the project folder in Lyre Studio and prepare its dependencies. In Project settings, review and save the preview service. If your app has a separate backend, save that service too: starting the app launches both and waits for their ports before opening the preview.

A dependency is a software package your project uses. A start command starts the local service that displays your app. Follow the numbered existing-app setup guide and choose a recipe for your framework.

3. Pair your phone

Open the host’s Pair Device controls and follow the invitation flow shown by your build. Connect the phone to the intended computer. Grant developer access only to a device you trust to work on approved projects.

Pairing connects devices. It does not publish the app on the internet or put it in an app store.

4. Try it, change it, try it again

Open the approved project from the phone. Tap its buttons, type into a form, and check the small-screen layout. Ask for one improvement, review the edit, and test again.

Keep the computer awake. A frontend edit may refresh automatically; changes to dependencies or the server can require a restart. Save your work before restarting.