Reverse a competitor's app into a UI spec

Capture their screens, read the patterns they settled on, and get a spec you can argue with before you build yours.

A mature product has already paid for the layout decisions you are about to guess at. Reading their screens as a set tells you which decisions they made on purpose and which they inherited.

Why this will not look generic: It reads a shipped product that survived real users, so the patterns it surfaces were kept because they worked rather than because they looked good in a concept.

What you walk away with

  • A prompt per screen of their product
  • The interaction and layout patterns they converged on
  • A spec for your own version, with the decisions made explicit

Typical run: 10 to 30 screens. Depth beats breadth here: the whole of one flow tells you more than one screen from ten flows.

What the reverse actually gives you

Point it at: A competitor's product, captured one flow at a time.

What comes back (representative example): Across the onboarding flow the pattern is consistent and deliberate. Every step is a single column at a constrained width with one decision per screen, never two. Progress is shown as a thin bar rather than numbered steps, so the length of the flow is never stated. The primary action is always bottom-right and always filled; the skip is always a text link, never a button, and sits far enough away to be hard to hit accidentally. Illustration appears on only the first and last screens, which makes them read as bookends. The form fields carry no placeholder text, only floating labels.

Things you would never have thought to type:

  • one decision per screen, never two
  • a progress bar rather than numbered steps, hiding the length
  • skip as a text link, placed away from the primary action
  • illustration only on the first and last screens, as bookends

What you change: Your content and your flow. Which of their patterns to adopt is now a decision you can make deliberately rather than an aesthetic you absorb.

How it works

  1. Capture a whole flow (In Chrome) - One complete flow beats scattered screens. Their screenshots are already on the web, so right-clicking them is cheaper than pasting files.
  2. File the flow in order - Tag them by step. Order is part of what you are analysing.
  3. Read it as a spec (In Claude) - Ask what is deliberate versus inherited; a mature product contains both.

Cost and time

This workflow runs at 2 reverses + about 1 minute. Your result carries automatically from each step into the next, so there is no re-uploading between tools. Reverses are billed from your reverse meter and generation steps from your AI Credits, both bundled in every pay-as-you-go credit pack.

Browse all guided workflows or all individual tools. Pay as you go, no subscription, AI Credits never expire.

Prompt Reverse

Solutions

  • Competitor ads
  • Product listings
  • Video & thumbnails
  • Websites & apps
  • Brand consistency
  • Property listings
  • Image SEO

Product

  • Image to Prompt
  • Video to Prompt
  • AI Image Generator
  • AI Video Generator
  • All tools
  • Workflows
  • AI models
  • Integrations
  • Pricing

Company

  • About
  • Guides
  • Learn
  • Trends
  • Contact
  • Feedback

Legal

  • Privacy Policy
  • Terms & Conditions
  • Billing & Credits
  • Sitemap

Follow

  • Instagram
  • X (Twitter)
  • YouTube
  • TikTok
  • Facebook