.png)
The Reports and Violations Center (RVC) enables Pinners to track the status of content they've reported, submit appeals, and view outcomes, supporting platform safety and giving users more transparency into how their reports are handled.
After its desktop launch, native mobile access became critical to meet the needs of the 70% of Pinners who primarily use Pinterest on mobile.
.png)
On mobile, the reporting experience was unpredictable and unusable. Relying on non-native patterns and broken redirects meant the experience didn't meet EU expectations for transparent, easy-to-access notices on reported content.
Working within a two-week timeline for design exploration and delivery, I partnered closely with PM, legal, engineering, and the design systems team to design a native solution that balanced resolving urgent risks with backend limitations. This work spanned both iOS and Android, however I am showing iOS screens in this case study for brevity.
.png)
While engineering addressed authentication failures and PDF download issues at the infrastructure level, my design efforts focused on:
Working within a tight timeline, I focused on exploring how report and violation information could be presented clearly on mobile while meeting compliance requirements. I used a vertically stacked table pattern and refined divider hierarchy to improve scannability, while updating tab microcopy from 'Your Account' to 'Your Violations' to clarify intent based on early feedback.
.png)
As the pattern evolved, I refined the layout to reduce visual noise and better support scanning. This resulted in a single divider between violations, while removing the lighter dividers within each violation detail, so related information could read as a cohesive unit aligned with patterns used across other Pinterest surfaces.
.png)
To reduce cognitive load and make the groupings clearer at a glance, I explored a progressive disclosure pattern using collapsible rows, allowing people to focus on key information first and expand details as needed.
In partnership with Legal, we validated this approach against EU transparency requirements. Because all violation details need to remain visible, collapsing content would obscure required information, so we moved away from this pattern.
.png)
I partnered with the Design Systems team during weekly office hours to propose the new mobile table pattern formally, ensuring long-term scalability.
.png)
To meet user expectations and reduce engineering lift, I replaced custom components in the 'Submit Appeal' workflow with native iOS patterns.
.png)
Previously, an unnecessary partial sheet confirmed appeal submission, interrupting the flow. I replaced the partial sheet with a toast notification, providing clear feedback with minimal friction.
.png)
I later extended this toast pattern to desktop for a unified cross-platform experience.
.png)
The final solution delivered a trustworthy, native reporting experience, closing critical gaps while giving Pinners visibility into decisions made on the content they report.
.png)