Plans, designs and builds

Synonode decides how much ceremony a request needs. A question is simply answered and a small change is simply made. An app or a bigger piece of work goes through the steps below, and nothing is built until you say so.

#1. Questions

If something important is unclear, Synonode asks first: the question appears in the chat with its choices, marked Needs your input. Tap a choice and Submit, pick Other to answer in your own words, or Skip to let Synonode choose. You can also just type your answer in the message box. Once answered, the question stays in the chat with your answer under it. It only asks what changes the result.

#2. The plan

Then it writes a plan you can read: what the app does, its screens, and what it'll use. Two buttons sit under it:

• Build it starts the work.
• Change something lets you say what to change; the plan is written again.

#3. Two designs

For anything with a look, Synonode makes two designs of the main screen: one in the direction you gave, and one of its own, a different direction it recommends. They show side by side in the preview, each taking half of it, and the chat asks which one to build, with the same two as options.

• Click one to choose it, in the preview or in the chat. Add a note if you like (make the header darker), then press Build. The app is built to match it.
• Open a design to see it full size, and select, comment or draw on it to say what to change.
• Regenerate one, or Regenerate all, to get new versions.
• Something else: write what you want in the message box, and Synonode reworks them.

If you have a brand, give Synonode your design system (colours, fonts, logo) and the designs follow it.

#4. The build

Synonode writes the app, starts it, and shows it in the preview while it works. You see each file change as it happens. Web apps use React, TypeScript, Vite and Tailwind by default, and can have a Supabase backend for data and logins. Python, Node scripts and other languages work too.

Big jobs may be split up: Synonode can start agents to search the code or do parts of the work in parallel.

#5. The checks

Before it says it's done, Synonode uses what it built: it goes through the pages, presses the buttons, fills and saves the forms, and reloads to see the data stayed. Then it holds the result against everything you asked for. See How it checks its work.

#6. The answer

The final message tells you what you can do now, how it was checked, and anything it noticed on the way. It doesn't list files and line numbers. If you want those, open the change summary under the message, or the git panel.

#Changing it afterwards

Just say what to change, or point at it: select part of the page, type over its text, pin a comment or draw on it in the preview. Every answer leaves a restore point, so you can always go back.