Coding by writing — Vibe Coding
You don't need to know how to code. Just write what you want in the chat, and Lyen builds the app and shows it on screen. Don't like it? Write how to fix it.
Here's what you can make
Tap one below and Lyen starts making it right away.
What is Vibe Coding?
It’s a way of where you describe the feel and behavior you want in writing, then see the result right away with and keep improving it together.
When do you use it?
Great for quickly testing an idea, making a small or game, or having fun learning , , and .
How does it work?
① Write what to make → ② Lyen writes the code → ③ Check the preview → ④ Write again to fix it. Repeat as needed.
How to ask Lyen well
Lyen builds what your words describe. The clearer the picture in your request, the closer the first is to what you imagined, and the fewer rounds of fixing you need.
-
Say what it is
Start with the kind of thing: a game, a quiz, a timer or a homepage. Add who it is for, such as 'for my 8-year-old brother'.
-
Describe how it looks
Colors, sizes and positions: 'a dark blue background', 'big round buttons', 'the score in the top corner'. The words you would use with a friend are enough.
-
Say what happens
What happens when you click, press a key or run out of time? 'When I press the space bar, the cat jumps.' Rules turn a picture into an app.
-
Change one thing at a time
After the first version, ask for one change per message: 'make the cat bigger', then 'add a sound'. If something breaks, you know exactly which request caused it.
Same idea, two ways to ask
Make a game.
Make a game where a cat moves with the arrow keys and collects falling stars. Show the score at the top and end the game after 30 seconds.
The vague request is not wrong. Lyen will still build something, but it has to guess the rest, so the result is a surprise. The clear request answers those guesses in advance.
When it doesn’t work
Even a clear request sometimes gives an app that does not work the way you wanted. That is normal — every programmer fixes things again and again. There are three ways out.
-
Let Lyen fix the error
If the preview shows an , Lyen gets the error text and tries to fix it once on its own. If the error is still there, you can press the button to hand it over again. After three tries in all it stops and asks you, because repeating the same fix rarely helps.
-
Say what you see
Describe the difference between what you expected and what happened: ‘When I press the space bar, nothing happens. The cat should jump.’ Lyen cannot see your screen, so a picture in words is the fastest fix. The next to the preview lists the errors; copy one into the chat.
-
Go back to a version that worked
Every save — yours or Lyen’s — becomes a new version, and each project keeps its latest 50. If a change made things worse, open the version list and restore the one that worked. Restoring is saved as a new version too, so nothing is lost.
Sharing safely
Sharing is off when you create a project. Turn it on and anyone with the address can open and run your app; turn it off and the addresses stop working. Turn it on again and the app's run address works again, while the share-page address is new. A shared app runs in a separate, locked box, so it cannot reach anyone’s SONUB account. Still, never put passwords or personal information into an app you share — and do not type them into other people’s apps either.
Want to know what Lyen wrote?
The app Lyen makes is one HTML file with CSS and JavaScript inside. You do not need to read it to start. When you want to fix one line yourself or understand why something broke, these pages help.
Want to know how it works underneath? Learn
Lyen already answered with code for this project, but it was never saved to the app. You can bring it back.
This project is empty. Write what you want to build in the chat.
Tap one below and Lyen starts making it right away.
Nothing here yet.