Test log
UXPin test data
Raw results for the UXPin review. The verdict is in the review.
- Tested
- 5 November 2026
- Tester
- Miles Foster
- Account
- Free demo account, signed up by RankDude, nothing paid to the brand
- Tests
- 9
- Screenshots
- 8
- Method
- Published methodology
- Environment
- Google Chrome on desktop
Results
| ID | Test | Key measurement | Score |
|---|---|---|---|
| T01 | Brand Kit & Consistency | – | n/a |
| T02 | Sharing & Collaboration | – | n/a |
| T03 | Brief to First Draft | Landing page: under 1 minute | 5/5 |
| T04 | Brief Adherence | Elements right: 34 of 40 | 3/5 |
| T05 | First Draft Quality | Design faults: 11 | 2/5 |
| T06 | Editing Freedom | Edits that worked: 4 of 12 | 2/5 |
| T07 | Export & Handoff | Export points: 4 of 10 | 2/5 |
| T08 | Rights & Commercial Use | – | 4/5 |
| T09 | Pricing & Value | – | 2/5 |
| Overall (in the review) | 3/5 | ||
Brand Kit & Consistency
n/aNot Tested- Method
- Upload logo, fonts and colours as a brand kit, then generate ten designs and check each.
- Remark
- Not graded; left out of the average.
Raw notes
Upload logo, fonts and colours as a brand kit, then generate ten designs and check each.
Not run: ten generations would not fit in the 14 per cent of trial credits left.
- Needs a paid month.
Sharing & Collaboration
n/aNot Tested- Method
- Eight points tried with a second account.
- Remark
- Not graded; left out of the average.
Raw notes
Eight points tried with a second account.
Not run: no second account was made.
- Needs a second test account.
Brief to First Draft
5/5Tested- Method
- Each brief was typed into UXPin's AI chat.
- Landing page
- under 1 minute
- Booking app
- 5 min 30 s
- Average of two
- about 3 minutes
- Remark
- Scale 5: median under 5 minutes. Two of three briefs were run, so the median of two is their average.
Raw notes
Each brief was typed into UXPin's AI chat. The clock ran from pressing Create Component to the last screen being built, read from screenshots every ten seconds and the screen recording.
The landing page was built in under a minute: the first page content was on the canvas after about 30 seconds and the chat had stopped by 50 seconds.
The booking app took about five and a half minutes from send to the fifth screen. That clock includes the AI's plan (about 105 seconds), a second message in which I attached the studio photo, and the plan for the other four screens, which I confirmed with Build all. The four screens themselves took about one minute. The average of the two briefs is about three minutes.
- The bakery brief was not run. The app time includes my own pauses to read and confirm two plans.
Brief Adherence
3/5Tested- Method
- Twenty required elements per brief were checked in the first draft before any editing: text, colours and fonts read from the page, sizes from the properties panel, the rest by eye at 2x.
- Elements right
- 34 of 40
- Scaled to three briefs
- 51 of 60
- Remark
- Scale 3: 45 to 53 of 60 right. The invented labels, button and photos are listed here and do not count as invented reviews or claims.
Raw notes
Twenty required elements per brief were checked in the first draft before any editing: text, colours and fonts read from the page, sizes from the properties panel, the rest by eye at 2x.
The landing page had 17 of 20 right: 1440 pixels wide, the sections in order, every line of text word for word, Fraunces headlines, Inter body, four of the five colours and the cards on white. Missing: the berry colour was never used, the logo is one the AI drew, not my file, and the hero photo is a stock photo, not my yarn photo.
The booking app had 17 of 20 right: five screens, every title, button, card price, time slot and field exactly as typed, all five colours, Fraunces titles and Inter body. Missing: the Welcome screen is 510 pixels high, not 844; the logo at the top is one the AI drew; the studio photo is not visible as the Welcome background.
Across the two briefs that is 34 of 40, or 51 of 60 scaled to three. UXPin also added text I did not write: a "Step 1 of 5" line on every screen, a "Small-batch yarn shop" label, a "New on the shelves" heading, a "Reserve a seat" button, a booking summary with an invented date, and three stock photos on the product cards.
- Bakery brief not run. The landing run had no photo attached because the start page offered no way to attach one.
First Draft Quality
2/5Tested- Method
- The first drafts were checked for design faults: contrast calculated from the hex values read on the page (WCAG AA: 4.5, large text 3), sizes, overlap, placeholders.
- Design faults
- 11
- Remark
- Scale 2: 11 to 20 faults.
Raw notes
The first drafts were checked for design faults: contrast calculated from the hex values read on the page (WCAG AA: 4.5, large text 3), sizes, overlap, placeholders.
Eleven faults. On the booking app's Welcome screen the title, the subtitle and the brand line are cream on a white background, a contrast of about 1.1 to 1, so they cannot be read, and the gold "Step 1 of 5" line is 2.4 to 1. Screens 2 to 5 have a "Step" label at 4.2 to 1, just under 4.5. The Welcome screen is 510 pixels high, not 844.
On the landing page the hero photo is a stock photo the AI itself calls a placeholder, and the three product cards carry stock photos. Everything else held: no text was cut off, nothing overlapped and the type sizes made a clear order.
- Not checked at 360 and 768 pixels wide: the editor builds one fixed-size canvas. The bakery pieces were not built.
Editing Freedom
2/5Tested- Method
- Twelve fixed edits on the generated landing page.
- Edits that worked
- 4 of 12
- Remark
- Scale 2: 4 to 6.
Raw notes
Twelve fixed edits on the generated landing page. An edit counts when it did what was asked with a normal control and no workaround.
Four worked: a font changed through the theme tokens (Inter to Georgia on the text that follows the base font; the headlines keep their own font), one colour changed everywhere through the theme tokens (the button colour changed on three elements at once), one word typed in place in the properties panel, and a section added by duplicating one.
Four did not: moving an element by hand and resizing a text box, which inside a layout need code typed into the sx field; aligning three elements, where I found no working control; and locking an element, where a Lock icon sits in the layer list but I could not confirm it locked anything. Changing the canvas size to 1024 pixels wide did not keep the layout: the PNG export came out with the hero photo and the third card cut off.
Three more were partial or not run. The image swap worked (I uploaded my yarn photo) but I found no crop control. Undo reverted the section I had added, but not the canvas size or the font change. The written-instruction edit was not run because it spends credits. Counted: four of twelve.
- Edits were made on the generated landing page. The AI instruction edit was left out to protect the credits.
Export & Handoff
2/5Tested- Method
- Ten export points tried on the finished landing page: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma or Sketch, React or HTML code, fonts, full resolution, bulk export, no watermark and the source assets.
- Export points
- 4 of 10
- Remark
- Scale 2: 3 to 5.
Raw notes
Ten export points tried on the finished landing page: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma or Sketch, React or HTML code, fonts, full resolution, bulk export, no watermark and the source assets.
Four of ten passed: a PNG at exactly 1440 pixels wide, React code downloaded as a project of seven files, full resolution with no upscaling and no watermark on any export.
Six did not: there is no SVG and no Figma or Sketch export; the PDF has no bleed box; the PDF names Georgia only, so Fraunces headlines were replaced; there is one page, so I could not show a bulk export; and the code and HTML exports hold the uploaded photo only as a web address, not as a file. The export dialog itself warns that local and Typekit fonts are replaced with Arial in PNG and PDF.
- The React project was downloaded and read but not built. The bakery pieces were not made, so the print checks ran on the landing page.
Rights & Commercial Use
4/5Tested- Method
- I read the Terms of Service and the AI Terms, reached from the site's footer links, on 5 November 2026.
- Remark
- Scale 4: ownership and commercial use clear, no indemnity.
Raw notes
I read the Terms of Service and the AI Terms, reached from the site's footer links, on 5 November 2026.
Ownership is clear: "You retain full ownership of the content you input and the outputs generated through UXPin AI". Training is covered too: "UXPin never uses your content or project data for model training or fine-tuning", so there is no opt-out to find. The Terms of Service call the design content Subscriber Data, owned by the subscriber, and allow design work for your own customers.
There is no indemnity: the AI Terms say UXPin "cannot guarantee that generated content is free from third-party intellectual property claims". The terms do not set a separate rule for commercial use on the free plan.
- Read on the free trial; no paid-plan terms were compared.
Pricing & Value
2/5Tested- Method
- Plans were read in the product's plan chooser and on the public pricing page, in both billing views.
- Remark
- Scale 2: $300 or more a year, or the briefs need paid top-ups.
Raw notes
Plans were read in the product's plan chooser and on the public pricing page, in both billing views.
The cheapest paid plan that adds custom fonts, the nearest thing to a brand kit, is Core: $49 a month, or $29 a month paid yearly. That is over $300 a year. It includes 200 AI credits a month. Growth is $69 a month, or $40 paid yearly, with 500 credits. More credits cost extra: 200 more for $13 a month.
The free plan keeps 2 prototypes and 50 AI credits in total, on a basic model. The trial credits used by my two briefs (86 per cent) say a month of Core would not go far for a team.
- No plan was bought; renewal prices were not seen.
Other features checked
Coverage
Tested
- Two of the three fixed briefs typed into the AI chat, with one supplied photo attached to each run
- Twenty required elements per brief checked in the first draft, with fonts and colours read from the page and contrast calculated
- Twelve fixed edits in the editor and its theme tokens
- Ten export checks: PNG, PDF, HTML and React code downloaded and measured
- Terms of Service, AI Terms, the plan chooser and the public pricing page read
Not tested or limited
- The bakery brief was not run: the two briefs I ran used 86 per cent of the trial credits, so a third would have passed the 85 per cent limit
- The chat shows credits as a percentage, so credits per brief are not reported
- The AI start page offered no way to attach a file, so the landing run had no photo; in the app run I attached the studio photo in a follow-up message. Only one image can be attached at a time, so my logos were never attached
- Brand kit was not graded: it needs ten new generations, which the remaining 14 per cent of credits could not cover
- Collaboration was not graded: every point needs a second account
- The AI-regenerate edit (edit 10) was not run because it spends credits; the editing grade counts four of twelve
- Layouts were not checked at 360 and 768 pixels wide: the editor builds fixed-size canvases
- No plan was bought, so renewal prices and the paid libraries were not tried
Still to test
- The bakery brief on another day, with fresh credits
- Brand kit with ten generations on a paid month
- Collaboration with a second account
- The written-instruction edit and a build of the downloaded React code