Bait and Switch

Concept

A design that announces what a tap will do, then does something else, borrowing the user's habits to collect a decision they never made.

Why it exists

Screens like this were being shipped long before anyone had a name for them. The missing piece was the name. You tapped the small x in the corner of an ad and landed on an app store page. You tapped a button labeled free and got a form asking for a card number. The person who used the product felt tricked, and the team that built it said the button copy had probably been a little confusing.

Without a name, the problem cannot be raised in a design review. Saying "this screen feels off" invites the question "which part," and answering it means inventing an explanation on the spot while the meeting moves on. The screen ships on schedule. If the numbers come back strong, it becomes the reference other screens are built against.

Bait and switch fills that empty slot. It carries exactly one test — the announced outcome differs from the real one — so a reviewer can point at a screen without arguing about anyone's intentions. Once the term is in the room, "that's a bait and switch" is enough to send a screen back to be rebuilt, and the conversation takes a minute rather than a meeting.

How it works

It announces an outcome through a familiar symbol, then runs a different action the moment the user taps that symbol without checking it. The sequence has three parts.

  1. The promise. A close icon, a cancel link, a start free button — a control whose meaning is already settled by convention. Nothing is wrong yet at this stage.
  2. The habit. Nobody rereads these controls. They are shapes a person taps dozens of times a day, so the hand moves before the eyes finish.
  3. The switch. The action actually wired to the control is not the announced one. The window doesn't close, an install begins. The subscription isn't canceled, it's paused for a month.

Step two carries the weight. A bait and switch never persuades anyone. It stands on habits the user already built, the way a road sign keeps its familiar shape while the meaning bolted to it quietly changes. Drivers don't miss it through carelessness; it works precisely because nobody reads a stop sign as if for the first time.

One more condition has to hold for the switch to pay off: the new outcome has to be hard to undo. A wrong screen that a back button closes gains nothing for anyone. So the destination is usually a finished install, an approved charge, or a permission that has already changed hands. The longer the reversal takes, the more people leave it alone — and the numbers the team reads afterward count those people as conversions.

Where it shows up

Four places in a product attract this pattern more than others.

  1. Ads and pop-ups. Close icons that belong to the ad rather than to the frame around it, and banners drawn to look like system alerts. The structure turns the act of dismissing something into a click the ad network gets paid for.
  2. Signup flows. The word free appears early and the card field appears at the last step. Push this one step further and it becomes forced continuity, where a trial rolls into a paid charge on its final day with no notice sent.
  3. Cancellation. The cancel button leads to a pause offer or a discount instead of to cancellation. This one usually shares a screen with roach motel, the structure that makes signing up trivial and leaving slow.
  4. Consent and permissions. The accept all button is labeled Next or Get started. From here the flow runs into privacy zuckering, where settings are arranged confusingly enough that people hand over more data than they meant to.

It separates cleanly from patterns that chase the same goal by other means. Confirmshaming puts copy like "No thanks, I'd rather miss out" on the decline button to make it embarrassing to press. Nagging asks again every time the app opens until someone says yes to make the prompt go away. Both label the options honestly and simply raise the price of choosing; a bait and switch does the reverse, keeping the label friendly while the outcome behind it differs from what the label said.

Some screens sit near the line without crossing it. Making an offer is not itself a bait and switch. Show one discount to a person heading for cancellation and leave the cancel button on that same screen, and the promise still matches the result. The test is not whether an offer appeared but whether the announced action still completes in a single tap.

How it sounds at work

"Isn't this a bait and switch? It looks like a close icon but it opens the pricing page."

A request in design review to rebuild the screen.

"Saying free and asking for a card at the end reads as a bait and switch. Let's put that on the first screen."

Trust is the concern, not the metric, so the disclosure moves earlier.

"Conversion went up, but that's bait-and-switch traffic. Look at refunds first."

A number rose and shouldn't be counted as a result yet.

At Pagedeck the phrase came up over a pop-up that told free-plan users about paid features. Ravi proposed an experiment: send people to the pricing page even when they tap the pop-up's close icon, which he estimated would triple pricing page visits. Noa named it a bait and switch on the spot. Mia didn't block the experiment — she attached a second number to it, asking the team to track not just visits but the share of visitors who actually paid.

Two weeks later visits were up 3.1 times and payments were flat. Every additional visit came from someone trying to dismiss a pop-up, and a few of them left one-star reviews on the app store on the way out. The pop-up went back to what it had been. What Pagedeck kept was a rule of thumb: numbers a bait and switch lifts stop at the click and never reach the payment.

What people get wrong

The most common mistake is assuming that without intent to deceive, it isn't a bait and switch. The people who built the screen know what they meant by it, so the assumption comes naturally. The test, though, is the gap between the promise and the result, not the state of mind behind it. Users don't get to read the meeting notes; they see the screen. Judge by intent and every review ends with "that wasn't the idea" while the screen stays exactly as it was — and once that answer works, it works again on the next screen.

Reading a lift in conversion as proof of a good design is the other one. What rises is clicks, and refunds, cancellations, and falling ratings arrive a few weeks behind. When those numbers live on a different dashboard than the conversion rate, only the first one gets reported.

Where to go next

  • Dark pattern

    the family this belongs to, and the five other types in it

  • Confirmshaming

    bends the same moment of choice, but through the wording rather than the outcome

Last updated 2026-09-16