Reports & Violations Center

My role
Established native mobile interaction patterns for Pinterest's reporting experience, improving usability and trust across key safety workflows.
Collaborators
Product Manager, Design Systems Team, Legal, Engineering Lead
Timeline
10 weeks (2023) Shipped 2024
Platform
iOS, Android
overview

Introducing the Reports and Violations Center (RVC)

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.

Previous desktop and mWeb experience – Not responsive across devices

the problem

Authentication failures & inaccessible content put user trust at risk

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.

Mobile pain points:

  • Pain point #1: Auto-authentication often failed, interrupting users as they attempted to view updates.
  • Pain point #2: Redirection issues sometimes resulted in flashing blank screens, causing confusion and drop-offs.
  • Pain point #3: Users couldn't access required PDFs because the download action didn't work reliably on mobile.

the approach

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.


Design goals

While engineering addressed authentication failures and PDF download issues at the infrastructure level, my design efforts focused on:

  • Goal #1: Leveraging native components to streamline implementation and improve reliability.
  • Goal #2: Laying the groundwork for longevity, by filling the gaps in our mobile design system.
  • Goal #3: Improving clarity of areas that previously caused confusion on the desktop experience.

Exploration

Early designs: Refining a mobile-first table pattern

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.

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


Refined design: Scaling for clarity and consistency

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.

Left: Empty state - No account violations; Middle: Existing account violation; Right: Reports submitted by the user

Explored alternative: Progressive disclosure 

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.

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

Design Decisions

Contributing to the mobile design system

I partnered with the Design Systems team during weekly office hours to propose the new mobile table pattern formally, ensuring long-term scalability.

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


Leveraging native components for platform consistency

To meet user expectations and reduce engineering lift, I replaced custom components in the 'Submit Appeal' workflow with native iOS patterns.

Before: More actions dropdown; After: More actions iOS partial sheet


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.

Before: Appeal submitted confirmation; After: Updated appeal confirmations - iOS toast component


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

Before: Confirmation modal; After: Success toast

what was shipped

Giving Pinners a reliable reporting experience

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


conclusion

Key results

  • Improved user trust by delivering a native reporting flow launch to millions of Pinners on iOS and Android
  • Closed a major EU transparency gap, preventing up to 6% in potential global revenue loss
  • Introduced a reusable mobile table pattern that can be adopted across additional surfaces