overview

Designing a reliable mobile reporting experience

The Reports and Violations Center (RVC) enables Pinners to track the status of content they've reported, view outcomes, and submit appeals.

‍But with 70% of Pinners on mobile, the lack of a native experience limited access to an important transparency and support flow, introducing compliance risk.

the problem

Authentication failures and inaccessible content limited access to report outcomes

On mobile, the reporting experience relied on non-native patterns and often broke when users tried to access report outcomes. Authentication flows required re-entering credentials, redirect issues caused blank screens, and downloads of outcome explanations were unreliable.

This was especially critical given EU transparency requirements, which are intended to ensure users can easily access explainations for reported and removed content.

‍
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 with backend limitations.

Focus areas:

• Translating existing system patterns into a mobile context
• Improving hierarchy of report and violation information
• Using native mobile components where appropriate to improve consistency
• Ensuring system feedback remained clear on mobile

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 by vertically stacking each violation and using dividers for easier scannability, while updating tab microcopy from 'Your Account' to 'Your Violations' to clarify intent based on early feedback.

Refining hierarchy, scannability, and consistency

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

‍

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 people to focus on key information first and 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.

‍

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.

Improving interaction patterns with native components

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

‍
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.

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

what shipped

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

impact

• Improved accessibility of report and violation information on mobile
• Closed key usability gaps in a previously desktop-only experience
• Introduced a reusable table pattern for mobile
• Supported compliance requirements for transparency in reporting flows, saving 6% in global revenue loss