Build a landing page with a chat prompt

Most small projects need a simple page: a landing page for a new product, a portfolio, a waitlist, a menu. The page itself is not hard, but getting from a blank file to something you can share often takes longer than the idea deserves.

The Create App Builder is made for this. You describe the page in plain words, Create builds it as a single page, and you change it by chatting. When you like it, you publish it to a link.

What the App Builder makes

The App Builder makes a website or small app as one page. Think of a coffee shop landing page, a portfolio, a habit tracker or a waitlist page. You get a live preview you can click around in, and you can view it at desktop, tablet or phone width. If you want to read the code, it is there too.

It is worth being clear about what version 1 does not do, so you can plan around it:

• It builds one page, in a single file of up to 300 KB.
• It has no database and no backend. A published page keeps nothing between visits, and a form on it cannot send data anywhere. An email box can only show a message.
• There is no custom domain. Published pages live at a create.vin link, and they are not listed by search engines.

If you can live with those limits, it is a fast way to get a real page in front of people.

What it costs

The first build costs 12 credits, and each change you ask for costs another 12 credits. Restoring an earlier version costs no credits. A failed build is given back. The App Builder is part of every paid plan, from Basic upward, and the credits come from your plan.

How to build a landing page, step by step

Here is a simple path from idea to live link.

1. Open Apps. Go to the App Builder and press New app.
2. Describe the page. Pick a starter idea or write your own request, up to 4,000 characters. Be concrete. Say who the page is for, what it offers, and the sections you want. For example: "A landing page for a small bakery in Brisbane. A hero with the bakery name and a short line, three featured breads, opening hours, and a contact block. Warm colors, bold headings, friendly tone."
3. Check the live preview. Click through the page. Switch between desktop, tablet and phone width and see how it behaves on each.
4. Chat to change it. Ask for changes in plain words: "Make the hero text bigger", "Add a section with three customer questions and answers", "Use a darker background for the footer". Each change is applied to the same page.
5. Use versions when you are unsure. Every change is saved as a version, and up to 100 versions are kept for each app. If a change makes things worse, look at an earlier version and restore it. Restoring adds it back as the newest one.
6. Publish. Publishing gives you a public link in the form create.vin/s/ followed by eight letters and numbers. You can update the live page to a newer version later, or unpublish it.
7. Or download the file. If you would rather host the page yourself on your own domain, download the single file and upload it to any web host.

Tips for better pages

Write the content you care about in your first message. Names, prices, opening hours and the exact wording of your main button are easier to get right at the start than to fix later.

Change one thing per message. If you ask for five changes at once, it is harder to see which one helped. Smaller steps also make versions more useful, because you can go back to the exact point where the page looked right.

Use the phone preview early. Many visitors will open your link on a phone, so check that view before you share it.

Keep placeholders honest. The page cannot take sign-ups or payments, so a button that says "Join the list" will only show a message. If you need real sign-ups, publish the page as a preview of the idea and use a form service on your own host after you download the file.

Limits to know

You can publish up to 5 apps at once and keep up to 50 apps per account. You can unpublish one to make room for another. Because the page is a single file, it works best with simple layouts, text, drawn graphics and small bits of interaction.

Try it