Designed to Be Reposted

The name was the brief. Ripost means repost. If we were going to call ourselves that, the product could not treat sharing as a row of buttons bolted under the headline.

I worked on user experience, and most of what I did came down to one question asked in different places: what happens to this page after it leaves us.

Content leaves in worse condition than you think

A well-designed article page is a fiction. Almost nobody experiences it.

People experience a screenshot of two paragraphs. A link preview in a chat. A video ripped and re-uploaded to a page with more followers than us. A quote pasted with no source. That is what “reposting” actually looks like in the wild, and it is not polite.

Two options. Fight it, which is what publishers were doing and still lose. Or design for it.

What designing for it meant

• Every unit had to survive being taken out of context. A short news item made sense alone. A list item made sense alone. If a piece only worked in the surrounding page, the piece was wrong.
• The mark had to travel with the content. Not a watermark that ruins the image. A visual identity strong enough that people recognized the thing three shares later.
• Link previews were a design surface. The image, the title and the description that appear in a Facebook post or a chat window get seen far more than the page itself. We treated them as the primary layout, not as metadata.
• Screenshot-friendly typography. Short line lengths and real contrast, because half of our distribution was somebody’s thumb and a screen capture.
• Copying text stayed easy. No interception, no “read more at” tail appended to the clipboard, no selection blocking. We were inviting people to copy. Booby-trapping the copy would have been a lie.

The vertical video problem, in 2016

Phones were the whole audience, and the video coming out of the shows was still being cut for a horizontal frame because that is how video had always been cut.

That argument took longer than it should have. Editing habits are stubborn, and the person cutting the video is looking at a large horizontal monitor while the person watching it is holding a phone at a bus stop. The interface cannot fix a format decision made upstream, so a lot of UX work at Ripost was actually production work in disguise.

What I took from it

Most media UX is defensive. Keep people on the page, block the exits, hide the share, wall off the text. It is a strategy built on the belief that attention is something you trap.

Ripost assumed the opposite, out of ideology first and practicality second. If your content is going to be taken anyway, the useful question is not how to stop it. It is whether it still works when it arrives somewhere else, with your name on it, in a form you did not choose.

Design for that and you stop fearing the repost. It becomes distribution you did not pay for.