Docs · Getting started
How a run works
Brief, directions, the one you keep, files in your folders — the shape of every job.
A run is a conversation that ends in files
You say what the collection has to do. DuoHand asks what a designer would ask, comes back with directions, and argues about them with you. What you approve it builds, in the software on your own machine, and the files land in your folders.
- 01
You say what it has to do
Who the collection is for, the occasion, the price band, the metal. What you leave vague it asks about rather than guessing.
- 02
It comes back with directions
Several, each with a point of view and a reason. You keep one and say what is wrong with the others.
- 03
It builds the piece
Modelling and layout run on your machine through DuoHand Bench. Every step that writes a file or runs a command asks you first.
- 04
You take the files
The model, the design sheet, the renders and the deck, in the formats your workshop already uses.
Questions
While a run is going
Can I change my mind halfway?
Yes. Say it mid-run and the work bends to it rather than finishing the wrong thing.
Do I have to sit and watch?
No. A long job keeps running on the server; close the tab and it is waiting when you come back.
What if it gets something wrong?
Tell it what is wrong and why. A reason travels to the next piece; a bare rejection teaches it very little.
More in this chapter
- Signing inEmail links, Google, and staying signed in.
- Where everything isThe sidebar, the chat box and Settings, named the way the app names them.
- Your first collectionWhat to bring the first time, and what comes back.
- Changing your mind, and stoppingWords typed while it works steer it; an empty box and the same button stop it.
- What it costs, roughlyThe shape of the bill before you spend anything: cents a question, three finished pages for A$8.50, nothing for a run that fails.