DEV Community

Marcus Kim
Marcus Kim

Posted on Originally published at marcusykim.medium.com

Signal Is Blocking Screenshots. Can Your Support Form Work Without One?

Good Luck, Have Fun

On November 20, Signal announced that it would prevent screenshots in its app on iOS 27 and restrict capture on Android when it detects an AI assistant trying to read the screen. That's a change to Signal, not a ban on screenshots in every app. But it exposes a surprisingly ordinary design mistake: a support form that won't accept a report until someone attaches a picture.

Imagine you build a scheduling app. A customer tries to move an appointment. The app shows an error, and your support form asks for a screenshot. Behind that error is a calendar with other people's names. Even if the phone lets the customer take the picture, why should reporting a failed appointment change require sharing someone else's calendar?

I would design the report around the decision the support person needs to make: did the appointment move, and what should the customer do next? Here is how I'd test that before shipping.

Start with the answer the customer actually needs

Suppose the appointment service knows it rejected a change because the selected time was no longer free. The customer can use that fact immediately: "That time was taken. Your original appointment hasn't changed. Pick a different time." A screenshot of a red banner would have told support less than those three sentences tell the customer.

A timeout is different. If the app didn't receive confirmation, it may not know whether the change went through. Don't write the same reassurance for both cases. Say what is unknown, offer a way to refresh the booking, and keep a route to support if it still looks wrong. The goal isn't to collect better pictures of errors. It's to stop asking a person to prove something the app already knows, and to be honest about what it doesn't.

Give support a reference, not a copy of the screen

For the uncertain case, I'd offer a "Report this change" button with a short, random reference the customer can copy. Before sending anything, show the proposed report in plain language. In this example it might contain the operation ("move appointment"), the app version, and the reference. Don't quietly attach the calendar, appointment notes, or a full diagnostic log.

A reference is useful only if an authorized support person can match it to a minimal event record. It shouldn't encode the customer's email, grant access to the booking, or promise indefinite lookup. Decide who can look it up and how long the record will last. Give the customer a text route even when that record is missing. In particular, a failure that happens offline may never produce a server-side reference.

Try the handoff from both sides

Use a test account and a fictional appointment. First, have someone else take the chosen time before you confirm. Then try a separate case where the confirmation never reaches the app. Leave the attachment field empty in both runs. Can you tell, from the screen alone, whether to pick another time or check the booking first?

Now give a teammate only the report the customer agreed to send. Ask which case occurred and what they would tell the customer. If they can't tell, find the smallest missing fact. If they can see the appointment notes, you've sent too much. Also try reading and copying the reference using a screen reader. Signal's earlier Windows announcement described accessibility tradeoffs from blocking screen capture; a support path meant to remove one barrier shouldn't introduce another.

My release criterion would be simple: the customer can ask for help without an attachment, and the person answering can either give a useful next step or say exactly what remains unknown. That's a better result than a support ticket with a mandatory image nobody needed.

This article was prepared with AI assistance. The scheduling app is a hypothetical example.

Top comments (0)