Reports & violations center

My role
Product Designer – Trust & Safety
Collaborators
1 PM, Design Systems Team, Legal Team, and Engineering
Timeline
Duration: ~3 weeks (2023) Status: Shipped (2024)
Platform
iOS, Android
overview

The Reports and Violations Center helps users track reports and submit appeals

With ~70% of Reports and Violations Center (RVC) traffic coming from mobile, the lack of a native experience limited access to a key transparency and support flow, creating compliance risk.

I led design of the native experience to preserve user trust and help prevent revenue loss from fines.


Impact
6% saved in global revenue
the problem

Report outcomes were difficult to access on mobile

On mobile, RVC relied on non-native patterns that disrupted access to report updates. Authentication failures, redirect issues, and inaccessible outcome explanations made it difficult for users to review report details.

This was especially critical given EU transparency requirements requiring users to easily access explanations for reported and removed content.

Left: Blank state caused by auth failures; Middle: Non-responsive reports list view; Right: Content is cut off

the approach

Working within a three-week timeline, I partnered closely with PM, legal, engineering, and the design systems team to design a native solution that balanced resolving urgent risks and backend limitations.


Exploration

Translating a desktop table pattern for mobile

The existing design system included a desktop-optimized table pattern, but no mobile equivalent. I explored how to adapt this pattern for mobile, while updating tab microcopy from 'Your Account' to 'Your Violations' to clarify intent based on early feedback.

Left: Initial stacked layout with light dividers; Right: Increased separation between violations


Refining the hierarchy and consistency

As the pattern evolved, I moved to using a single divider between violations to strengthen groupings of related information and better align with patterns used across other Pinterest surfaces.

Proposed design – 'Your Account' tab


Exploring progressive disclosure and rejecting it

I explored a collapsible interaction pattern to reduce cognitive load and make the groupings clearer at a glance, allowing users to expand details as needed.

However, after reviewing EU transparency requirements with Legal, we needed to keep all violation details immediately visible, so we moved away from this pattern.

Left: 'Your Violations' tab – All rows collapsed; Right: 'Your Violations' tab – Row expanded

Refinement

Contributing to the design system

I partnered with the Design Systems team to validate and refine the mobile table pattern for reuse across similar surfaces.

New table pattern – No action taken; Reviewed; Appeal In Progress; Deactivated (Action Taken)

Adopting native patterns

To better align with native mobile expectations and reduce engineering lift, I replaced components in the 'Submit Appeal' workflow with native iOS patterns.

Rather than directly translating the desktop confirmation pattern into a mobile partial sheet, I used toast notifications to provide clear feedback without interrupting the flow.

Left: Direct translation of desktop confirmation pattern; Right: Proposed design – Native toast pattern


I extended this toast pattern to desktop for a unified cross-platform experience.

Proposed design – Successful appeal submission

shipped Solution

Accessing reports reliably

The final solution delivered a trustworthy, native reporting experience, closing critical gaps while giving Pinners visibility into decisions made on the content they report.

States: Loading; Empty; Violation user's account; Downloaded PDF


Submitting appeals

Users can challenge content moderation decisions and receive clear feedback throughout the appeal process.

States: Violation's on user's account; Appeal submission; Successful submission; Submission error

Outcomes
  • Improved access to report and violation information on mobile
  • Closed key usability gaps in a previously desktop-only experience
  • Introduced a mobile table pattern to support scalability and consistency