🏢 Company: Meta / WhatsApp

🎯 My Role: UX Copy — Android & iOS

🤝 Collaborators: Product · Design · Engineering · Security

📐 Skills: Security UX · Friction States · Platform-Specific Copy · Cross-platform Consistency · Global Scale

📌 Overview

WhatsApp introduced a feature that blocks users from screenshotting or screen-recording profile photos, a small product change with significant scam-prevention impact across the platform's 3+ billion users.

Bad actors often use profile photos to impersonate real users or building fake accounts to scam friends and family. By blocking the capture entirely, the feature eliminated a key step in this attack pattern.

This case study covers the UX copy that surfaced when a block was triggered across both Android and iOS, with their differing UI conventions and user expectations. The writing problem was specific: communicate protection in a moment of friction, without making users feel punished or alarmed.

🤔 The Challenge

Security features present a specific writing problem: you need to communicate protection without creating fear.

When a user attempts to screenshot or screen-record a profile photo, they're stopped instantly without warning. In that micro-moment, the copy is the only thing standing between "this app is protecting me" and "this app is accusing me." Get the framing wrong, and the user loses trust in the moment they need to feel safest.

The copy had to accomplish three things within a brief, high-friction touchpoint:

1. Explain what happened without being confusing, alarming, or accusatory
2. Frame the block as protection, communicating intent without sounding defensive
3. Use one consistent set of copy for both screenshots and screen recordings, two technically distinct triggers with one user intent

All of this had to land cleanly across Android and iOS, each with different UI conventions, system-message patterns, and user expectations.