Tali Neiman
Tali Neiman
Tali Neiman
product designer

Tali Neiman (she/her) [1991]
Product designer with 5+ years across SaaS, developer tools, and creative projects. At Front, I owned design for the Developer Platform — API flows, integrations, and AI-powered features. Before that, I've designed MVPs from scratch, redesigned university platforms, and built visual identities for cultural projects in Berlin.

product designer

Tali Neiman (she/her) [1991]
Product designer with 5+ years across SaaS, developer tools, and creative projects. At Front, I owned design for the Developer Platform — API flows, integrations, and AI-powered features. Before that, I've designed MVPs from scratch, redesigned university platforms, and built visual identities for cultural projects in Berlin.

API rate limit visibility
A new dashboard for technical users

ROLE
PRODUCT DESIGNER
AT FRONT.COM

TEAM
DEVELOPER PLATFORM

As the sole Product Designer on Front’s Developer Platform squad, I led the design of API rate-limit visibility, a core infrastructure feature used by technical customers.

Front is a customer communication platform that brings channels into one shared workspace for support teams. 

My role and key responsibilities

→ Led end-to-end design of API rate-limit visibility for enterprise technical users

→ Defined dashboard architecture and data modeling approach

→ Introduced a new stacked bar visualization pattern to the design system

→ Drove cross-functional alignment across product and engineering

→ Ensured scalability and clarity within a complex, infrastructure-heavy surface

Tali Neiman

Considering this is a technical, API-focused feature used primarily by developers, engagement levels indicate strong relevance among power users managing integrations.

PROBLEM

Customers were hitting API rate limits without any visibility into:

→ When limits were being reached
→ Why workflows were failing
→ Which integrations were responsible

This lack of transparency created frustration among technical teams and support escalations.

Tali Neiman

THE SOLUTION: a new dashboard for customers to monitor their API usage

To address the visibility gap and restore trust, we defined strategic goals like enabling self-diagnosis, giving customers access to historical usage data. The second goal was to surface usage patterns for customers to anticipate limits and make informed upgrade decisions.

Tali Neiman
Tali Neiman
Tali Neiman

FINAL DESIGN

The final design was a stacked bar chart because it made volume and distribution easy to compare at a glance. I then formalized it as a reusable component in the design system to support similar use cases across the product.

Exploring different visualization approaches to balance spike detection, rate-limit clarity, and upgrade context.

The interface surfaces total volume alongside a clear distribution between successful, failed, and rate-limited calls, making anomalies instantly visible.

IMPACT

Within weeks of launch, the dashboard was generating 500–1,000 weekly visits across ~150 companies and ~200 technical users. For a developer-focused infrastructure feature, this level of engagement indicates strong adoption among the teams most impacted by rate limits.

API rate limit visibility
A new dashboard for technical users

ROLE
PRODUCT DESIGNER
AT FRONT.COM

TEAM
DEVELOPER PLATFORM

As the sole Product Designer on Front’s Developer Platform squad, I led the design of API rate-limit visibility, a core infrastructure feature used by technical customers.

Front is a customer communication platform that brings channels into one shared workspace for support teams. 

My role and key responsibilities

→ Led end-to-end design of API rate-limit visibility for enterprise technical users

→ Defined dashboard architecture and data modeling approach

→ Introduced a new stacked bar visualization pattern to the design system

→ Drove cross-functional alignment across product and engineering

→ Ensured scalability and clarity within a complex, infrastructure-heavy surface

Tali Neiman

Considering this is a technical, API-focused feature used primarily by developers, engagement levels indicate strong relevance among power users managing integrations.

PROBLEM

Customers were hitting API rate limits without any visibility into:

→ When limits were being reached
→ Why workflows were failing
→ Which integrations were responsible

This lack of transparency created frustration among technical teams and support escalations.

THE SOLUTION: a new dashboard for customers to monitor their API usage

To address the visibility gap and restore trust, we defined strategic goals like enabling self-diagnosis, giving customers access to historical usage data. The second goal was to surface usage patterns for customers to anticipate limits and make informed upgrade decisions.

FINAL DESIGN

The final design was a stacked bar chart because it made volume and distribution easy to compare at a glance. I then formalized it as a reusable component in the design system to support similar use cases across the product.

Exploring different visualization approaches to balance spike detection, rate-limit clarity, and upgrade context.

The interface surfaces total volume alongside a clear distribution between successful, failed, and rate-limited calls, making anomalies instantly visible.

IMPACT

Within weeks of launch, the dashboard was generating 500–1,000 weekly visits across ~150 companies and ~200 technical users. For a developer-focused infrastructure feature, this level of engagement indicates strong adoption among the teams most impacted by rate limits.

NEXT PROJECT →