51% of Indian Daters Are Replacing Ghosting. Apps Aren't Ready.

A survey of 9,347 Indian daters shows the country is systematically replacing ghosting with something more deliberate and arguably more complicated. Fifty-one percent of users aged 23-35 now prefer gradual fade-outs over abrupt disappearances, deploying therapeutic language and intentional slowdowns to end conversations they do not want to continue. The shift is the most significant change in rejection behavior on dating apps since ghosting became normalized around 2013.

This is not a soft story about kindness trending on dating apps. It is a product challenge: the features built around the ghosting era, read receipts, last-seen timestamps, binary match and unmatch mechanics, all assume users want clarity. Half of India's dating app users are now trying to engineer ambiguity instead. If your UX is fighting your users' intentions, you have a design problem, not a user problem.

The High Intent Take

India's dating app market at $323M projected by 2027 is not a niche anymore. It is large enough that behavioral shifts here are worth treating as signals for global product strategy, not regional quirks. QuackQuack CEO Ravi Mittal attributes the trend to heightened emotional awareness and mental health focus among young daters, which may be true. The more actionable interpretation is this: after a decade of dating apps training users to treat matches as disposable, a correction was inevitable. Whether that correction represents emotional progress or simply fatigue from managing too many simultaneous conversations is less important than the product reality it creates.

If half your users are trying to engineer ambiguity, your UX is fighting their intentions. That is a design problem, not a user problem.

The research on the psychological consequences of being rejected on dating apps adds weight to why users are seeking alternatives to the hard stop. The emotional stakes of digital rejection are real. Platform teams that treat rejection mechanics as a minor UX detail are underestimating how much it shapes user trust and retention.

Two Patterns, One Underlying Problem

The survey identifies two distinct rejection styles that have taken hold among Indian daters. "Nice avoidance" appears in 39% of women across Hyderabad, Mumbai, and Kolkata, and 31% of men in Pune, Kochi, and Ahmedabad. These users reach for workplace-adjacent phrasing: "I'm working on myself right now" or "I'm not the right fit currently." The language is professional rather than personal, borrowed from a recruiter's rejection email rather than a dating conversation. It maintains the form of communication while withdrawing the substance.

"Soft ghosting" is the larger pattern. Forty-four percent of users aged 22-28 report maintaining minimal contact, an occasional story like, a periodic emoji response, while fundamentally withdrawing. Young men particularly favor this approach. The behavior creates relationship purgatory: not present, not gone. The person being soft-ghosted often cannot tell whether rejection has occurred or the other person is simply busy.

The naming exposes the contradiction. Soft ghosting is still ghosting. The pace is slower and the signals are more ambiguous, but the endpoint is the same: one person disappears from another's life without explicit acknowledgment. Whether spreading that process over days or weeks genuinely reduces harm is debatable. Traditional ghosting delivers a clear signal quickly. The soft exit redistributes the discomfort across a longer timeline, potentially making it harder to identify when the rejection has actually occurred and move on.

What This Forces Product Teams to Decide

Dating platforms built their communication features for a different user behavior. Match mechanics assume binary interest. Notification systems optimize for engagement, not graceful exit. Read receipts and typing indicators were designed to create urgency and accountability, both of which work against users trying to engineer a deliberate fade.

If you are running product at a dating platform, this data forces an uncomfortable choice. You could build tools for ambiguity: delayed message send, gradual notification reduction, or soft-exit prompts that let users signal diminishing interest without a hard block. That risks enabling the exact passive behavior that makes app dating exhausting for the person on the receiving end. Or you could double down on transparency tools that push users toward directness. That fights against what half your user base now considers the emotionally intelligent approach.

The line between emotional intelligence and passive aggression is uncomfortably thin, and it is genuinely difficult to encode in product design. There is no feature that makes rejection feel good. The question is whether your platform makes the mechanics of rejection clearer or murkier, and which side of that trade-off your users are asking you to be on.

The Economic Dimension Nobody Wants to Say Out Loud

Platforms monetize extended engagement. Users who maintain minimal contact indefinitely, still technically active, still occasionally opening the app to send an emoji, occupy a commercially interesting gray zone. They are not generating enough activity to need premium features, but they have not churned either. They count in your MAU figures. They keep your retention numbers from deteriorating as fast as they otherwise would.

The uncomfortable truth is that soft ghosting may be economically beneficial to platforms even if it is emotionally costly to users. A product team that optimizes against soft ghosting risks accelerating the churn of users who would otherwise have remained nominally active for longer. That is a real trade-off, and the right answer depends on whether your business model prioritizes engagement metrics or actual relationship outcomes.

Rejection remains remarkably common on dating apps, with users rejecting roughly 80% of potential matches on average. That means rejection mechanics are not an edge case. They are a central part of the daily user experience. The platform that figures out how to make the rejection experience less damaging without enabling indefinite stringing-along has solved a real problem that no major operator has cracked yet.

Regional Signal or Global Preview?

India's post-pandemic dating app growth was unusually compressed. The country skipped the slow cultural normalization that Western markets experienced over a decade and adapted to app-based dating in a much shorter period. Whether that acceleration produces permanently different norms around rejection, or whether India is simply arriving earlier at patterns that will eventually appear globally, is genuinely uncertain.

The generational split in the data offers a clue. Adoption of soft ghosting at 44% among 22-to-28-year-olds significantly outpaces older cohorts in the same survey. Gen Z's well-documented preference for asynchronous communication and aversion to direct conflict shows up clearly here. If this is a Gen Z behavior first and a regional behavior second, the trajectory is predictable: as Gen Z forms a larger share of dating app users globally, the behavioral patterns visible in India today will appear across Western platforms in the next three to five years.

For operators targeting international expansion in South and Southeast Asia, this data is current, not predictive. Your product features need to work for users who are actively practicing soft exits right now, not who might adopt them later. That means auditing your read receipt implementation, your notification cadence, and your unmatch flow for whether they support or undermine what your users are actually trying to do.