LoginSign Up
← Back to all sparks
U

UXPin

DESIGN
Velocity5.0
www.uxpin.com ↗

A prototyping tool rebuilt around AI, now shipping working React apps instead of mockups.

ai-ui-generationprototype-to-codedesign-toolingreact-exportusage-based-creditsproduct-consolidation
◆Current state
UXPin has spent 2026 rebuilding around two AI surfaces. Forge, introduced in February, replaced the editor's previous AI workflow and became the primary way users generate and edit UI. Wire, introduced in June, takes those designs and turns them into working flows with logic, navigation, and form behavior, shareable as a hosted link or exported as a React app. The releases since are mostly Wire scaffolding — collections, previews, dashboard management — alongside AI credit purchasing and additional models.
◆Where it's heading
The direction is away from prototyping-as-artifact and toward prototyping-as-working-software. Each Forge release widened what a single prompt could produce — one screen, then a complete flow, then UI recreated from a live URL — and Wire closes the loop by making that output something a developer can start from. The monthly digests show the two surfaces converging rather than competing, with the June release connecting Forge results directly into Wire. Monetization is tracking the same curve: AI credits are now sold from inside the editor.
◆Prediction
Expect the next releases to keep filling in Wire as a delivery surface — export fidelity, hosting and sharing controls, and a tighter path from Forge output into a Wire build. The mid-editor credit purchase flow points at usage-based pricing pressure, so metering and plan changes are the most likely non-feature move.

◆Recent moves

  1. 4d ago

    Organize, preview, and create Wire projects from Dashboard

    Wire gets the management layer a new product surface needs once people actually use it: collections to group builds, previews from the dashboard, and project creation without entering the editor. A static landing page option for HTML-based builds widens what a Wire project can be published as. This is scaffolding around the June launch rather than an extension of what Wire does.

    View source ↗
  2. 10d ago

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

    A monthly digest whose most telling item is commercial rather than technical: AI credits can now be bought from Forge Settings without leaving the editor, which is what a vendor does when generation volume, not seat count, is the thing being consumed. Wire picks up image support and API key control, and longer-output models arrive. The generic title hides both the pricing change and the Wire work.

    View source ↗
  3. 1mo ago

    Forge gains design system presets and pipes output into Wire

    The clearest sign of the two surfaces converging: Forge results now connect directly to Wire, turning what were separate launches into one path from prompt to working flow. Design system presets constrain generation to a chosen style, and code streams as it is produced rather than appearing at the end. Filed under a month-stamp title that gives none of this away.

    View source ↗
  4. 1mo ago

    Introducing UXPin Wire

    ⚡ SPARK

    The second of the year's two structural launches, and the one that changes what a UXPin project is for. Where Forge changed how designs get made, Wire changes what leaves the tool — connected screens with logic and navigation, delivered as a hosted link or a React export. Read against the Forge releases before it, this is the destination the whole arc was heading toward.

    View source ↗
  5. 1mo ago

    Forge fetches live page content from a pasted URL

    Forge can pull facts and content from any URL inside the editor and keep the results in conversation context. It extends the same instinct as the earlier URL-to-UI feature — treat the live web as an input to generation rather than something the designer transcribes by hand. Published under a month-stamp title on the same day as the Wire launch, which buries it.

    View source ↗
  6. 3mo ago

    Generate complete flows from a single prompt with Forge

    Forge moves from generating a screen at a time to generating a whole flow — a checkout, an onboarding sequence — from one prompt, with a live task list showing progress. It is a real widening of what a single instruction produces, though it extends Forge's existing generation model rather than changing direction. The multi-screen output is also the raw material Wire would need when it arrived seven weeks later.

    View source ↗