Mockup maker
Pictures of a screen to agree on before anything is built. You describe the screen, or bring the PRD or user story it comes from, and Piko draws three designs in three looks. Each is checked against what you asked for, word by word, before you see it. Pick one, ask for changes, and share it for a yes.
- Asks for
- A sentence or two about the screen: who uses it and what for
- Optionally, a PRD, user story or one-pager from your files
- Optionally, screenshots of your product, for its look
- Gives back
- Three high-fidelity designs of the screen, in three palettes and styles
- A brief with every word on the screen, for whoever builds it
- Changes made by asking, each kept as a version
- A showcase render on a device, and a link a reviewer can approve
- Plan
- Free
- Use next
- Design, Design system, PRD, User story
What it gives you
Rebook after a cancellation · e-commerce storefront · desktop 1 Top bar ........ “Tablo” · “Explore” · “My bookings” 2 What happened .. “Your table at Osteria Lupa on Sat 14 Nov, 19:30 was cancelled by the restaurant.” 3 Heading ........ “Rebook your table” Designs: Clay & Ocean (yours) · Luxury Editorial · Orbit Blue Checked: 31 of 31 words, nothing missing
How it works
An image model asked for “a booking screen” draws something plausible and wrong: invented text, garbled words, colours nobody chose. So Piko writes a brief first — who the screen is for, the one job they came to do, and every word that appears on it — and the picture is drawn from that brief, not from a loose prompt.
Each design is then read back against the brief. A word that came out wrong is caught, and the design is drawn again before you see it. Dates are checked in code, so a Friday on the screen really is a Friday.
In Advanced you choose the look yourself: one of ten kinds of screen, one of thirty curated palettes or your own colours, a style and a theme, with a live preview that repaints as you choose. The three designs are then your palette and two Piko picked to suit the product.
Who it is for
A PM who needs a screen agreed with their team, a stakeholder or a client before design and engineering time is spent on it.
Where it stops
The designs are pictures, not code: nothing in them can be clicked, and very small text can still blur. The brief keeps the exact words for whoever builds it. Each run draws one screen; a flow of several screens is drawn one screen at a time.
Questions people ask
Why pictures and not a prototype?
Because the point is to agree on the look before anyone spends time building it. A picture takes a minute, costs little, and a stakeholder can say yes or no to it from a link without an account. Once it is approved, the brief beside it gives whoever builds it every word and colour.
Can I use my own colours?
Yes. In Advanced you pick one of thirty curated palettes, with two, three or four brand colours, or set your own. A live preview repaints a real screen as you choose, so you see the look before a picture is drawn.
What happens when the picture gets a word wrong?
Every design is read back against the brief before you see it. A design with a wrong word is drawn again; if it is still wrong, it is shown with the word marked and you are not charged for it.
Run it on your own work
Mockup maker needs an account, because it writes against what you give it and remembers what you have told it before. It runs on the Free plan. Or see what the plans cost first.