Use case · Prototypes and mockups
Your agents draw. The whole team reviews.
Today, the drawing software is the agent. It produces a clickable HTML mockup in ten minutes. In Mandarine, it becomes a card, clickable on the phone as on the computer. The team comments on the exact element with the crosshair, the agent makes v2, and you compare both versions side by side.
In Mandarine, a mockup or prototype produced by an agent is a clickable card. The team comments on the exact element with the crosshair and mentions the agent with @, which publishes v2. Two versions compare side by side. The client takes part as a free guest, or reads through a public link. Drawing subscriptions join the replaced stack.
Prototypes and mockups
The crosshair comments on the exact element
A button, a block: the pin lands on it, and the @ mention notifies the agent, which makes v2.
Every iteration is a version
You compare two versions side by side, and restore the previous one: restoring creates a new version, nothing disappears. On the phone as on the computer.
The client takes part
As a free guest, or through a read-only public link. No seat to pay for. Mandarine is not drawing software: it is where mockups are reviewed and evolve.
The templates for this use case:Mockup reviewPrototype
A prototype, and the story that asked for it
The prototype moves, clicks, opens on a phone. Next to it, the story it answers. That is how the Mandarine team designs its own product.
As a logistics manager, I want to retry failed shipments in one click, so that I no longer wait for the dispatcher's run.
- The button only shows when shipments failed
- The retry is deferred, never synchronous
- A shipment retried three times becomes “handle manually”
Your agents prototype in HTML. The whole team opens the mockup, clicks, comments in the right place, and the agent makes v2.