Perplexity's Pushy Notifications Are Angering Users: Where Should AI Products Draw the Line?

A one-line Reddit complaint reveals how Perplexity's pushy feature notifications are crossing from guidance into annoyance.
A Reddit post titled "Please stop begging us to use Perplexity Computer" — with no body text — cut straight to a widespread AI product problem: in pursuit of feature adoption and user retention, teams are pushing new features so aggressively through pop-ups and banners that they damage the core experience, erode user trust, and trigger psychological backlash. The article uses this as a lens to examine Perplexity's growth pressures, analyzes the three costs of over-notification, and outlines practical strategies — context-aware recommendations, easy mute options, and "subtraction" design — concluding that earning users means making them *want* to engage, not pushing them to.
A Brief Piece of Feedback That Hit a Nerve
A Reddit post recently appeared that was strikingly short yet deeply relatable. The title said it all: "Feedback: Please stop begging us to use Perplexity Computer" — and the body of the post contained exactly one line: "Title says it all."

Despite its minimal content, this post captured a widespread frustration with AI products today: high-frequency feature push notifications from product teams are crossing the line from "helpful guidance" to "outright annoyance." The word "begging" — slightly tongue-in-cheek yet genuinely exasperated — perfectly encapsulates the fatigue users feel toward repeated pop-ups and new feature prompts.
Perplexity's Growth Anxiety and Its Push Notification Strategy
As a rising star in AI-powered search, Perplexity has been rapidly expanding its product portfolio in recent years — from its core AI search Q&A, to the Comet browser, to various new features (including the "Perplexity Computer" capabilities mentioned in the post). The company is clearly in a phase of aggressive iteration and user growth.
Why "Push Anxiety" Happens
In the intensely competitive AI landscape, product teams have strong incentives to promote new features:
- Driving feature adoption: New capabilities that go unused can't demonstrate product value or generate the feedback needed for optimization.
- Boosting user stickiness: Getting users to engage with more features theoretically improves retention and paid conversion rates.
- Keeping up with competitors: ChatGPT, Gemini, Claude, and others are all stacking features at a rapid pace, so Perplexity needs users to know it has comparable capabilities.
However, when these business motivations are channeled directly to users through frequent pop-ups, banners, and onboarding prompts, they tend to backfire. Users open a product with a specific task in mind — not to explore new features.
Where Should the Line Be Drawn?
The real value of this piece of feedback is what it reveals about a universal challenge in AI product design: how to strike the right balance between promoting new features and respecting the user experience.
The Three Costs of Over-Notification
First, it damages the core experience. The competitive edge of AI tools lies in efficiency. When users have to dismiss a feature recommendation pop-up every time they open the app, that efficiency advantage starts to erode.
Second, it undermines trust. Repeatedly pushing the same feature makes users feel like the product "cares more about its own KPIs than their actual needs." The fact that users described it as "begging" signals that these notifications have been downgraded from "useful tips" to "annoying marketing."
Third, it creates feature blindness. Ironically, over-pushing can trigger a psychological backlash — users may start actively ignoring or dismissing feature prompts, ultimately harming the very adoption the product team was trying to drive.
Design Lessons for AI Product Teams
This brief, real-world piece of user feedback carries lessons for the entire AI industry. In an era of rapid feature iteration, product teams need to critically reassess their notification strategies.
Approaches Worth Considering
- Context-aware recommendations: Only surface feature suggestions when users are genuinely likely to need them — not through blanket, high-frequency pushes.
- Easy dismiss and mute options: Let users silence a certain type of notification with a single tap, and make sure the system remembers that preference.
- Embrace "subtraction" design: More features don't automatically mean a better experience. Restrained, well-timed guidance earns more user trust than aggressive in-app marketing.
- Close the feedback loop: User voices like the Reddit post above deserve serious attention from product teams — not to be buried under growth metrics.
Closing Thoughts
"Please stop begging us to use" might sound like a minor user gripe, but it's actually a pointed reminder about AI product design philosophy. In today's fiercely competitive AI tool market, the products that truly respect users' attention and autonomy are the ones more likely to build lasting relationships.
For Perplexity, rapid growth matters — but "making users want to use a feature" will always be more valuable than "nagging users into using it." A feature's worth must ultimately be proven through experience, not sold through repeated prompts. That may be the deepest lesson this deceptively simple post has to offer every AI product team.
Related articles

Catalyst: A Vision for an Enzyme-Like Testing Framework for AI Agents
A developer shared Catalyst on Reddit, an Enzyme-inspired framework for AI Agents, exploring why agents need observable, testable dev tools and the design philosophy behind them.

The Real Capability of AI Coding Agents: Best Models Complete Only 35% of Feature Development Tasks
The 'Agents on Rails' benchmark finds top AI models complete only 35% of feature development tasks. What this means for coding agents and developer teams.

How to Prevent Duplicate Refunds After an AI Agent Crashes: CellaFlow's Durable Execution Approach
How can AI agents avoid duplicate refunds after a crash without deadlocking workflows? CellaFlow uses durable execution, shared work identity, leases, and fencing to solve safety and liveness in multi-agent systems.