---
robots: noindex, nofollow
tags: pitch
---

# Performance examples

## Problem

Measuring performance on an more extensive examples, similar to what our client's app looks like can help us understand more realisticly the performance of our components, and help us earlier cought potentional performance issues, which may not be visible on per component performance tests.

## Appetite

There are many examples that we may add, but we shuold start from the ones we know there are some perf issues at this moment.

## Solution

Provide examples for the following scenarios:
- Calling Roaster
- Calling Screen
- Scrollable Chat

### Risks (Rabbit holes)

There will always be different user's experiences that we may add, but we should just choose some which are more representative and measure for starter the performance on those.

### Out of scope (No-gos)

We will not be fixing any perf issues with this project