# Getting started > Your first app, from the description you type to the first version your team signs in to. This page follows one app from its first line to its first live version. Each step names the part of the portal you use. Before any price, we show you a working first version of your app on made up sample data: see [How a quote works](/en/pricing/#quote). The portal itself is described in [Using the portal](https://golocomotive.fr/docs/using.md). ## 1. Open your portal We send you a link. It opens your portal in your browser and keeps you signed in on that browser. The portal shows your apps on the left, the review cards in the middle, and your app itself on the right. ## 2. Describe the app Click **+ new** in the apps column. Give the app two things: - **A name**: lowercase letters, digits and single dashes, starting with a letter, 40 characters at most. For example `field-service` or `stock`. The name is also the first part of the app's address once it is live. You can change the address later. - **A description**: what the app is for, who uses it, and what they do in it. Write it as you explain it to a new colleague. > **Tip.** Name the things your team handles (orders, clients, tickets, machines), the people who use the app (a manager, a driver, a client), and what each one must and must not see. That one paragraph saves several rounds. When you click create, the portal makes the app at once. It is a small working app with a sign in page, and it shows in the preview on the right. An agent then starts to build what you described. ## 3. Watch the first build The build is a card in the review column with a live status: the agent's last action, how long it ran, and what it spent. You do not need to stay on the page. The agent works on its own, and the card waits for you. If the agent needs an answer from you, it does not wait in a chat. It turns the card into a question and stops. You answer on the card, and the same agent continues from where it stopped. ## 4. Judge the result When a part is ready, the agent sends a card: a short title, a few lines on what changed, and a picture of the screen before and after. Compare the two, try the change in the live preview next to it, then answer: - **Approve** when it is right. - **Approve with a fix** when it is right but for a small detail. Draw a rectangle on the detail and say what to change. - **Reject** when it is wrong. Say why, and draw on the picture where it helps. A fix or a rejection goes back to the same agent, with your words and your rectangles. The next card replaces the old one. More in [Review a change](https://golocomotive.fr/docs/using/review.md). ## 5. Add your users Open the **Users** tab. Create an account for each person: an email, a role, and a password you type or let the portal generate. The portal shows the password once, with a text you can copy and send to the person. More in [Users and access](https://golocomotive.fr/docs/using/users.md). ## 6. Release and go live Open the **Releases** tab. The changes your agents made wait under "Unreleased", each one as a line your users can read. Click **Release v1** to freeze them into version 1, then **Deploy v1 to prod**. The portal shows each step as it runs, then the address of your live app. Your live app is open to anyone who has an account in it: its own sign in page is the gate. If you prefer, you can also limit it to a list of internet addresses (your office, for example). See [App settings](https://golocomotive.fr/docs/using/settings.md). ## 7. Keep asking From now on, every change follows the same loop: you ask, an agent builds, you look, you decide. When the next version is ready, release it and deploy it the same way. Your users see a short "what's new" note at their next sign in. ## Next - [How it works](https://golocomotive.fr/docs/start/how-it-works.md): who does what, and why it is safe. - [Your first week](https://golocomotive.fr/docs/start/first-week.md): requests that work well. - [Connect your AI](https://golocomotive.fr/docs/connect.md): work in your app from Claude or another MCP assistant.