---
title: "Evolve your app with AI"
description: "Ask for changes in plain language and let an Evolution Thread plan, build, and verify them for you."
url: https://evonx.ai/docs/get-started/evolve-your-app
locale: en
updated: 2026-09-04
---

# Evolve your app with AI

Ask for changes in plain language and let an Evolution Thread plan, build, and verify them for you.

The first version is never the final one. In this step you'll request your first
real change to Garage Usta and watch an Evolution Thread carry it from idea to a
pull request — with checkpoints where you decide.

> **Note**
> This page continues the journey from
> [Preview your app](/docs/get-started/preview-your-app).

## Ask for a change

1. Open your business chat and describe the change while looking at the preview.
   For Garage Usta:

   > When my staff open a repair job, they should be able to attach photos of the
   > vehicle. Photos should show in the job detail as a small gallery.

2. Send it. For a change like this — touching screens, data model, and API —
   Evonx opens an **Evolution Thread** and shows you its plan: the steps it
   intends to take and which repository each one touches.

3. Review the plan. If the direction is off, say so in the thread before any code
   is written — steering early is cheap.

> **Tip**
> One change at a time beats a wish list. "Add photos to repair jobs" builds better
> than "add photos, invoicing, and SMS reminders" in one message. See
> [Effective prompting on Evonx](/docs/evolve/effective-prompting).

## What happens while it builds

For visual work the thread proposes [mockups](/docs/evolve/design-and-mockups)
before code — approve the one you want. Then the AI executes in an isolated
workspace, splitting the change into steps and
[verifying each one](/docs/evolve/automated-testing) before moving on. You can
watch the run's progress live in the thread.

When the work is done, check it in the preview: the thread's changes are visible
there before they touch your repositories.

## Approve the result

Finished changes arrive as a **pull request** on your repository. You review the
summary (and the code, if you like), then merge — or reject with feedback and let
the thread revise. Nothing lands without your approval. Details:
[Publishing changes](/docs/evolve/publishing-changes).

## Check your work

You've completed the core Evonx loop: describe → plan → build → verify in preview →
merge. Every future change, small or large, follows this same shape.

## Next step

Time to go live:
[Publish your app](/docs/get-started/publish-your-app). To go deeper on the agent
first, read [Evolution Threads explained](/docs/evolve/evolution-threads).