Aseprite vs UXPin

UXPin now runs two AI surfaces: Forge, which generates and edits UI inside the editor, and Wire, which turns designs into working product flows shipped as a hosted link or a React export. Wire arrived in June and has absorbed most of the release attention since. The last three months of updates are about control and cost of those surfaces rather than new ones — model tiers, credit purchasing, API key handling, and design-system presets that constrain what the AI produces.

The pattern is a shift from capability to economics. Once Forge could generate whole flows and Wire could emit a React app, the open questions became what the generation costs and how tightly a team can bound its output, and the releases now answer those: an Eco model at a fraction of the credits, credits purchasable without leaving the editor, presets that hold generations to a house style. Wire is also being folded into the surrounding product rather than kept separate, with dashboard organization and Forge output routed into it.

Expect the credit economy to keep hardening — clearer per-model pricing, and controls that let an admin cap or route spend rather than leaving model choice to each designer. The entries do not indicate whether Wire's React export is heading toward round-tripping or staying a one-way handoff.