LoginSign Up
← Back to all sparks
U

UXPin

DESIGN
Velocity5.0
www.uxpin.com ↗

Forge and Wire stop growing outward and start getting cheaper to steer.

ai-generationprototypingdesign-to-codecredit-economicsdesign-systems
◆Current state
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.
◆Where it's heading
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.
◆Prediction
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.

◆Recent moves

  1. 19d ago

    More control over how AI edits your UI, MUI 9 and more

    Forge's AI edits get a Best/Eco model toggle in both the Editor and Wire, with Eco running a tuned lower-cost model at 5-7x fewer credits. This is the cost-control half of the arc: the same generation surface, now with a cheaper setting for routine single-task edits and the expensive model reserved for planning and complex rewrites. The feed truncates before the MUI 9 details, so the component-library side of this release can't be read here.

    View source ↗
  2. 1mo ago

    Organize, preview, and create Wire projects from Dashboard

    Wire projects gain Collections for grouping, dashboard previews, and a static landing-page option for HTML builds. Two months after launch, Wire is being given the organizational furniture an editor accumulates once people keep more than a few projects in it — a sign it is being treated as a durable surface rather than a demo.

    View source ↗
  3. 1mo ago

    AI credits sold in-editor; Wire adds images and API key control

    AI credits become purchasable directly from Forge Settings without leaving the editor, and Wire picks up image support and API key control. Buying capacity at the moment you run out, rather than through a separate billing trip, is the first clear move toward treating credits as a consumable the user actively manages.

    View source ↗
  4. 2mo ago

    Forge gains design system presets and pipes output into Wire

    Forge gains design system presets that hold generations to a chosen style, streams code as it generates, and routes its output into Wire. The presets are the constraint side of AI generation — narrowing what comes back — and the Wire connection is the first release where the two surfaces stop being separate products.

    View source ↗
  5. 2mo ago

    Introducing UXPin Wire

    ⚡ SPARK

    Wire's launch is the pivot the following three months elaborate on: UXPin's output stops being a picture of an interface and becomes a running React app. Everything since — presets, dashboard organization, model tiers — is scaffolding around this move.

    View source ↗
  6. 2mo ago

    Forge fetches live page content from a pasted URL

    Forge can pull live content from a pasted URL and keep it in context for the rest of the conversation. It extends an earlier feature that generated UI from a website URL, moving from copying a page's layout to using its actual content as generation input.

    View source ↗