When does polished UX start feeling a little too pushy?

I keep running into products that look smoother than ever, but somehow feel less honest. The first-time experience is nicer, sure, but sometimes I miss the awkward little cues that told me what was happening under the hood.

Has anyone else noticed that super polished UX can make people trust the product less, not more?

Do you have examples of apps/sites that did this recently?

Figma’s newer AI bits did it for me — super clean UI, but that “Try AI” chip keeps popping up.

That “Try AI” chip is a good example because it’s not just polished, it’s persistent. It stops feeling like a tool and starts feeling like a little salesperson living in the corner of your canvas.

I don’t know if Figma is measuring “engagement” or whatever, but the repetition is what makes it pushy for me. Clean UI is quiet; this isn’t quiet.

That “little salesperson” line is where my trust alarms go off too, because it’s not just aesthetics — it’s the product trying to steer you.

Persistent nags train people to click past prompts without reading, and that’s how you end up with “consent” that isn’t really consent. Clean UI is quiet; this is conditioning.

Most folks seem to agree it’s not “polished” that breaks trust, it’s polish paired with steering. A clean, modern UI can actually feel more honest when it stays quiet and lets you work, but once the experience includes persistent prompts like Figma’s “Try AI” chip, it starts reading less like guidance and more like a salesperson camping in the interface. The repetition is what flips it from helpful to manipulative, and it trains people to dismiss UI messages on autopilot.

The unresolved caveat is that teams are usually optimizing for adoption metrics and feature discovery, so some nudging is inevitable and sometimes genuinely useful, but the line is thin and subjective. Practical takeaway: if you’re designing this stuff, treat persistence as a trust tax—make prompts easy to dismiss permanently, explain what will happen before you click, and bias toward user-initiated discovery instead of repeated interruptions.

“Progress bars that reflected actual work” is the bit I’d underline too. Fake-smooth is where I start side-eyeing a product. When apps swap real state for vague spinners and cute micro-animations, you lose the sense of what the tool is actually doing. Then every “one-click” action starts feeling like it might be doing three other things off-screen. One pattern I’ve seen work is a small “details” affordance on expensive or destructive actions. Keep the default view calm, but let people expand into “Syncing 214 files…” or “Applying changes to: X, Y, Z. ” Naming tip: I’d literally call it “What’s happening? ” instead of “Advanced. ” People click that when they’re nervous.