From 343f11173ec1b38c85e81856b6f0c3f8d96f8d0a Mon Sep 17 00:00:00 2001
From: manuroe <manu@matrix.org>
Date: Wed, 3 Dec 2025 11:18:15 +0100
Subject: [PATCH 01/10] Migration from the draft our design doc

---
 docs/ex_perfomance_metrics.md | 36 +++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 docs/ex_perfomance_metrics.md

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
new file mode 100644
index 0000000..106ca08
--- /dev/null
+++ b/docs/ex_perfomance_metrics.md
@@ -0,0 +1,36 @@
+# EX Performance metrics
+
+| Status | Last updated |
+|--|--|
+| In progress | December 3, 2025 |
+
+<hr />
+
+## Objective
+Crashes are already tracked on Sentry. Performance metrics are also useful health metrics to check. This can be tracked by Sentry too.
+
+This document specifies what metrics we track and how we measure them. It has a focus on EX but it could be extended (and renamed) to track any matrix client app performance.
+
+## UX metrics
+
+
+| Title | Android name / Description | What it is measuring | Initial and final conditions | Tech metrics | Notes |
+| :---- | :---- | :---- | :---- | :---- | :---- |
+| Cold start time | Cold start until cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background User taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (TBD) </li></ul> | It does not consider Sentry init time and the check that the user has consented from disk. |
+| Catch-up | Room list says it is resumed and running | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service turns into `Running` No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to get it |
+| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active The user taps on a notification</li></ul> To:<ul><li>The message is visible in the timeline The timeline around this message is fully loaded |  |  |
+| Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Get and display first timeline items</li></ul> |  |
+| Send a message | ? | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | Needs to be tested for validation |
+
+
+## Additional data
+
+We need to add some data to the metrics so that we can better characterise them:
+
+| Data | Why it is useful | Notes |
+| :---- | :---- | :---- |
+| Device information | <ul><li>It helps to detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry. No additional work |
+| Homeserver URL hash | <ul><li>To compare matrix.org and element.io homeservers speeds</li><li>Measure the impact of a slow server</li></ul> | We use SHA-512 for the hash |
+| DBs file size | <ul><li>Check the impact of growing DB on speed performance</li><li>Check disk space used by the app</li></ul> | We have 4 DBs: state, event, media, crypto |
+| Account size | <ul><li>Check the impact on speed performance</li><li>Check the impact on \`/sync\` response size</li></ul> | It should be part of a new stats FFI API |
+| First /sync response size | <ul><li>Check it stays as small as possible</li></ul> | It should be part of a new stats FFI API |
\ No newline at end of file

From 1b40d5ea9fd2831c036e5da4e2c66ce6880a7000 Mon Sep 17 00:00:00 2001
From: manuroe <manu@matrix.org>
Date: Wed, 3 Dec 2025 14:22:28 +0100
Subject: [PATCH 02/10] First self review

---
 docs/ex_perfomance_metrics.md | 28 +++++++++++++---------------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index 106ca08..425a9eb 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -7,30 +7,28 @@
 <hr />
 
 ## Objective
-Crashes are already tracked on Sentry. Performance metrics are also useful health metrics to check. This can be tracked by Sentry too.
+Crashes are already tracked on Sentry. Performance metrics are also useful health metrics to check. They can be tracked by Sentry too.
 
-This document specifies what metrics we track and how we measure them. It has a focus on EX but it could be extended (and renamed) to track any matrix client app performance.
+This document specifies what metrics we track and how we measure them. It focuses on EX but it could be extended (and renamed) to track any matrix client app performance.
 
 ## UX metrics
 
-
-| Title | Android name / Description | What it is measuring | Initial and final conditions | Tech metrics | Notes |
+| Title | Android name / Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
 | :---- | :---- | :---- | :---- | :---- | :---- |
-| Cold start time | Cold start until cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background User taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (TBD) </li></ul> | It does not consider Sentry init time and the check that the user has consented from disk. |
-| Catch-up | Room list says it is resumed and running | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service turns into `Running` No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to get it |
-| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active The user taps on a notification</li></ul> To:<ul><li>The message is visible in the timeline The timeline around this message is fully loaded |  |  |
+| Cold start | Cold start until the cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
+| Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric  |
+| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded |  |  |
 | Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Get and display first timeline items</li></ul> |  |
-| Send a message | ? | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | Needs to be tested for validation |
-
+| Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | **TODO**: We need to experiment the feasibility of this metric |
 
 ## Additional data
 
 We need to add some data to the metrics so that we can better characterise them:
 
-| Data | Why it is useful | Notes |
+| Data | Why is it useful? | Notes |
 | :---- | :---- | :---- |
-| Device information | <ul><li>It helps to detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry. No additional work |
-| Homeserver URL hash | <ul><li>To compare matrix.org and element.io homeservers speeds</li><li>Measure the impact of a slow server</li></ul> | We use SHA-512 for the hash |
-| DBs file size | <ul><li>Check the impact of growing DB on speed performance</li><li>Check disk space used by the app</li></ul> | We have 4 DBs: state, event, media, crypto |
-| Account size | <ul><li>Check the impact on speed performance</li><li>Check the impact on \`/sync\` response size</li></ul> | It should be part of a new stats FFI API |
-| First /sync response size | <ul><li>Check it stays as small as possible</li></ul> | It should be part of a new stats FFI API |
\ No newline at end of file
+| Device information | <ul><li>To detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry |
+| Homeserver URL hash | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | We use SHA-512 to compute the hash. </br>**TBD:** Define the input string (`https://matrix.org`, `matrix.org`() or `https://matrix-client.matrix.org` (`base_url`) or something else) |
+| DBs file size | <ul><li>To check the impact of growing DB on speed performance</li><li>To check disk space used by the app</li></ul> | We have 4 DBs: state, event, media, crypto.</br>**TODO**: Add here names from the new Rust SDK API |
+| Account size | <ul><li>To check the impact on speed performance</li><li>To check the impact on \`/sync\` response size</li></ul> | It is the number of rooms joined by the user.</br>**TODO**: Add the Rust SDK API for reference |
+| First /sync response size | <ul><li>To check network usage stays as low as possible</li></ul> | **TODO**: Add the Rust SDK API for reference |

From da2e5b8b23188ba99ee312babb97697b117b91d1 Mon Sep 17 00:00:00 2001
From: manuroe <manu@matrix.org>
Date: Wed, 3 Dec 2025 17:47:01 +0100
Subject: [PATCH 03/10] Integrate Sentry naming convention

to define a better mapping between the spec and implementation.
---
 docs/ex_perfomance_metrics.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index 425a9eb..f18ce9d 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -11,9 +11,15 @@ Crashes are already tracked on Sentry. Performance metrics are also useful healt
 
 This document specifies what metrics we track and how we measure them. It focuses on EX but it could be extended (and renamed) to track any matrix client app performance.
 
+## Sentry semantics
+As we use Sentry, we need to adopt its naming conventions for `Transaction(name: String, operation: String)` and `Span(operation: String, description: String)`. 
+More information can be found in the Sentry documentation about [Transaction Name](https://docs.sentry.io/platforms/native/enriching-events/transaction-name/) and [Span Operations](https://develop.sentry.dev/sdk/performance/span-operations/).
+
 ## UX metrics
 
-| Title | Android name / Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
+There are tracked using Sentry transactions. `Transaction.operation` is `ux` to reflect high-level, user journey metrics.
+
+| Metric (Sentry Transaction Name) | Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
 | :---- | :---- | :---- | :---- | :---- | :---- |
 | Cold start | Cold start until the cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
 | Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric  |

From 092f7faf3d118d5fec87eaf673fec09580ed6b88 Mon Sep 17 00:00:00 2001
From: manuroe <manu@matrix.org>
Date: Thu, 4 Dec 2025 17:48:12 +0100
Subject: [PATCH 04/10] Performance metrics: Refined existing UX metrics and
 data. Start Tech metrics

---
 docs/ex_perfomance_metrics.md | 49 ++++++++++++++++++++++++++++++-----
 1 file changed, 42 insertions(+), 7 deletions(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index f18ce9d..fbdb439 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -22,9 +22,9 @@ There are tracked using Sentry transactions. `Transaction.operation` is `ux` to
 | Metric (Sentry Transaction Name) | Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
 | :---- | :---- | :---- | :---- | :---- | :---- |
 | Cold start | Cold start until the cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
-| Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric  |
-| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded |  |  |
-| Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Get and display first timeline items</li></ul> |  |
+| Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric.  |
+| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
+| Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Timeline load</li></ul> |  |
 | Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | **TODO**: We need to experiment the feasibility of this metric |
 
 ## Additional data
@@ -34,7 +34,42 @@ We need to add some data to the metrics so that we can better characterise them:
 | Data | Why is it useful? | Notes |
 | :---- | :---- | :---- |
 | Device information | <ul><li>To detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry |
-| Homeserver URL hash | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | We use SHA-512 to compute the hash. </br>**TBD:** Define the input string (`https://matrix.org`, `matrix.org`() or `https://matrix-client.matrix.org` (`base_url`) or something else) |
-| DBs file size | <ul><li>To check the impact of growing DB on speed performance</li><li>To check disk space used by the app</li></ul> | We have 4 DBs: state, event, media, crypto.</br>**TODO**: Add here names from the new Rust SDK API |
-| Account size | <ul><li>To check the impact on speed performance</li><li>To check the impact on \`/sync\` response size</li></ul> | It is the number of rooms joined by the user.</br>**TODO**: Add the Rust SDK API for reference |
-| First /sync response size | <ul><li>To check network usage stays as low as possible</li></ul> | **TODO**: Add the Rust SDK API for reference |
+| Homeserver | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | **We use SHA-512 to compute the hash of the homeserve domain**, ie matrix.org or element.io.  |
+| DB files size:<ul><li>Crypto store</li><li>State store</li><li>Event cache store</li><li>Media store</li></ul> | <ul><li>To check the impact of growing DB on speed performance</li><li>To check disk space used by the app</li></ul> | Expressed in MB. |
+| Account size | <ul><li>To check the impact on speed performance</li><li>To check the impact on \`/sync\` response size</li></ul> | Expressed in number of joined rooms.</br>**TODO**: Add the Rust SDK API for reference<br/>**TODO**: We need to experiment the feasibility of this metric |
+| Catch-up /sync size | <ul><li>To check network usage stays as low as possible</li></ul> | The response size in kB of the first `/sync` request made during catch-up.</br>**TODO**: Add the Rust SDK API for reference</br>**TODO**: We need to experiment the feasibility of this metric |
+
+## Tech metrics
+
+They are tracked as Senty spans. `Span.operation` follows the [Span Operations](https://develop.sentry.dev/sdk/performance/span-operations/) convention like `http.client`. `Span.description` is the metric name.
+
+| Metric (Sentry Span Description) | Category (Sentry Span Operation) | Description  | Notes |
+| :---- | :---- | :---- | :---- |
+| Timeline load | `function` | `sdkRoom.timelineWithConfiguration ()` | |
+
+**TODO: Add more**
+
+
+## Future considerations
+Later, we could add the following UX metrics.
+
+### UX starting from outside of the app
+* Call answer to call
+* Permalink to message
+* Notification to threaded message
+* Notification to invite (room or space)
+
+And maybe all the variants:
+* Permalink to room
+* Permalink to space
+* Permalink to threaded message
+* Permalink to profile
+* Permalink to Element Call
+
+### UX inside the app
+* Make a call
+* QR code login
+* Open member list
+* Open a permalink (of all sorts)
+* Open a thread
+

From 6df5b246f171054ecf37334fc0839a9506d7fd75 Mon Sep 17 00:00:00 2001
From: Jorge Martin Espinosa <jorgem@element.io>
Date: Mon, 22 Dec 2025 11:03:22 +0100
Subject: [PATCH 05/10] Add a separate table for metrics we want but can't add
 now

---
 docs/ex_perfomance_metrics.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index fbdb439..9e292b1 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -36,6 +36,11 @@ We need to add some data to the metrics so that we can better characterise them:
 | Device information | <ul><li>To detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry |
 | Homeserver | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | **We use SHA-512 to compute the hash of the homeserve domain**, ie matrix.org or element.io.  |
 | DB files size:<ul><li>Crypto store</li><li>State store</li><li>Event cache store</li><li>Media store</li></ul> | <ul><li>To check the impact of growing DB on speed performance</li><li>To check disk space used by the app</li></ul> | Expressed in MB. |
+
+We'd want to add this data too, but it's not possible at the moment given the info we have in the SDK:
+
+| Data | Why is it useful? | Notes |
+| :---- | :---- | :---- |
 | Account size | <ul><li>To check the impact on speed performance</li><li>To check the impact on \`/sync\` response size</li></ul> | Expressed in number of joined rooms.</br>**TODO**: Add the Rust SDK API for reference<br/>**TODO**: We need to experiment the feasibility of this metric |
 | Catch-up /sync size | <ul><li>To check network usage stays as low as possible</li></ul> | The response size in kB of the first `/sync` request made during catch-up.</br>**TODO**: Add the Rust SDK API for reference</br>**TODO**: We need to experiment the feasibility of this metric |
 

From 20ac5ce56132bf840e0e9297994fd35a78a0f67c Mon Sep 17 00:00:00 2001
From: Jorge Martin Espinosa <jorgem@element.io>
Date: Mon, 22 Dec 2025 11:03:43 +0100
Subject: [PATCH 06/10] Update last updated date in performance metrics

---
 docs/ex_perfomance_metrics.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index 9e292b1..e98651b 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -2,7 +2,7 @@
 
 | Status | Last updated |
 |--|--|
-| In progress | December 3, 2025 |
+| In progress | December 22, 2025 |
 
 <hr />
 

From 660f4e2a888ade43ba13fcb6a4ccf7bb95cef550 Mon Sep 17 00:00:00 2001
From: Jorge Martin Espinosa <jorgem@element.io>
Date: Mon, 22 Dec 2025 13:16:10 +0100
Subject: [PATCH 07/10] Add a suggested way to test 'Send a message'

---
 docs/ex_perfomance_metrics.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index e98651b..02372ac 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -25,7 +25,7 @@ There are tracked using Sentry transactions. `Transaction.operation` is `ux` to
 | Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric.  |
 | Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
 | Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Timeline load</li></ul> |  |
-| Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | **TODO**: We need to experiment the feasibility of this metric |
+| Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | The `RoomSendQueueUpdate` enum in the SDK can be used for this: `NewLocalEvent` being returned means the event is in the send queue, `SentEvent` means we received it in the sync. We don't really know when it lands on the timeline, but the delay should be minimal. |
 
 ## Additional data
 
@@ -50,7 +50,7 @@ They are tracked as Senty spans. `Span.operation` follows the [Span Operations](
 
 | Metric (Sentry Span Description) | Category (Sentry Span Operation) | Description  | Notes |
 | :---- | :---- | :---- | :---- |
-| Timeline load | `function` | `sdkRoom.timelineWithConfiguration ()` | |
+| Timeline load | `function` | `Room.timelineWithConfiguration` | |
 
 **TODO: Add more**
 

From fffd87293dfe73415bd1f5239edc3fd3b4988b7e Mon Sep 17 00:00:00 2001
From: manuroe <manuroe@users.noreply.github.com>
Date: Mon, 22 Dec 2025 13:55:38 +0100
Subject: [PATCH 08/10] Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 docs/ex_perfomance_metrics.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_perfomance_metrics.md
index 02372ac..573865b 100644
--- a/docs/ex_perfomance_metrics.md
+++ b/docs/ex_perfomance_metrics.md
@@ -17,13 +17,13 @@ More information can be found in the Sentry documentation about [Transaction Nam
 
 ## UX metrics
 
-There are tracked using Sentry transactions. `Transaction.operation` is `ux` to reflect high-level, user journey metrics.
+They are tracked using Sentry transactions. `Transaction.operation` is `ux` to reflect high-level, user journey metrics.
 
 | Metric (Sentry Transaction Name) | Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
 | :---- | :---- | :---- | :---- | :---- | :---- |
 | Cold start | Cold start until the cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
 | Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric.  |
-| Notification to message | A notification was tapped and it opened a timeline | How long it takes from taping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
+| Notification to message | A notification was tapped and it opened a timeline | How long it takes from tapping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
 | Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Timeline load</li></ul> |  |
 | Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | The `RoomSendQueueUpdate` enum in the SDK can be used for this: `NewLocalEvent` being returned means the event is in the send queue, `SentEvent` means we received it in the sync. We don't really know when it lands on the timeline, but the delay should be minimal. |
 
@@ -34,7 +34,7 @@ We need to add some data to the metrics so that we can better characterise them:
 | Data | Why is it useful? | Notes |
 | :---- | :---- | :---- |
 | Device information | <ul><li>To detect specific device problem, especially on the fragmented Android ecosystem</li></ul> | It is provided by Sentry |
-| Homeserver | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | **We use SHA-512 to compute the hash of the homeserve domain**, ie matrix.org or element.io.  |
+| Homeserver | <ul><li>To compare matrix.org and element.io homeservers speed</li><li>To measure the impact of a slow homeserver</li></ul> | **We use SHA-512 to compute the hash of the homeserver domain**, ie matrix.org or element.io.  |
 | DB files size:<ul><li>Crypto store</li><li>State store</li><li>Event cache store</li><li>Media store</li></ul> | <ul><li>To check the impact of growing DB on speed performance</li><li>To check disk space used by the app</li></ul> | Expressed in MB. |
 
 We'd want to add this data too, but it's not possible at the moment given the info we have in the SDK:
@@ -46,7 +46,7 @@ We'd want to add this data too, but it's not possible at the moment given the in
 
 ## Tech metrics
 
-They are tracked as Senty spans. `Span.operation` follows the [Span Operations](https://develop.sentry.dev/sdk/performance/span-operations/) convention like `http.client`. `Span.description` is the metric name.
+They are tracked as Sentry spans. `Span.operation` follows the [Span Operations](https://develop.sentry.dev/sdk/performance/span-operations/) convention like `http.client`. `Span.description` is the metric name.
 
 | Metric (Sentry Span Description) | Category (Sentry Span Operation) | Description  | Notes |
 | :---- | :---- | :---- | :---- |

From b36f2746086c7d67bd4b17f3de71cb9544fc20d5 Mon Sep 17 00:00:00 2001
From: manuroe <manuroe@users.noreply.github.com>
Date: Mon, 22 Dec 2025 13:56:17 +0100
Subject: [PATCH 09/10] Rename ex_perfomance_metrics.md to
 ex_performance_metrics.md

---
 docs/{ex_perfomance_metrics.md => ex_performance_metrics.md} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename docs/{ex_perfomance_metrics.md => ex_performance_metrics.md} (100%)

diff --git a/docs/ex_perfomance_metrics.md b/docs/ex_performance_metrics.md
similarity index 100%
rename from docs/ex_perfomance_metrics.md
rename to docs/ex_performance_metrics.md

From f4e556f1e4c71118bc63de227ff0ad2d54e7c028 Mon Sep 17 00:00:00 2001
From: manuroe <manuroe@users.noreply.github.com>
Date: Mon, 12 Jan 2026 14:51:40 +0100
Subject: [PATCH 10/10] UX metrics table review

We made a review with @mxandreas:
- `Cold start` --> `Cached Room list`
- `Catch-up` --> `Up-to-date room list`
- Remove the `What is it measuring?` column that has duplicated info.
---
 docs/ex_performance_metrics.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/ex_performance_metrics.md b/docs/ex_performance_metrics.md
index 573865b..d72626b 100644
--- a/docs/ex_performance_metrics.md
+++ b/docs/ex_performance_metrics.md
@@ -19,13 +19,13 @@ More information can be found in the Sentry documentation about [Transaction Nam
 
 They are tracked using Sentry transactions. `Transaction.operation` is `ux` to reflect high-level, user journey metrics.
 
-| Metric (Sentry Transaction Name) | Description | What is it measuring? | Initial and final conditions | Tech metrics | Notes |
-| :---- | :---- | :---- | :---- | :---- | :---- |
-| Cold start | Cold start until the cached room list is displayed | How long it takes from launching the app to displaying cached data on the screen | From:<ul><li>The user is already connected</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cached and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
-| Catch-up | The app syncs and the room list becomes up-to-date | How long until the room list is up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric.  |
-| Notification to message | A notification was tapped and it opened a timeline | How long it takes from tapping the notification to the message becoming visible in the app | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
-| Open a room | Open a room and see loaded items in the timeline | How long it takes from tapping a room in the room list to displaying a full page of messages | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Timeline load</li></ul> |  |
-| Send a message | Send to sent state in timeline  | How long it takes from tapping send to the message appearing in the timeline as sent | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | The `RoomSendQueueUpdate` enum in the SDK can be used for this: `NewLocalEvent` being returned means the event is in the send queue, `SentEvent` means we received it in the sync. We don't really know when it lands on the timeline, but the delay should be minimal. |
+| Metric (Sentry Transaction Name) | Description | Initial and final conditions | Tech metrics | Notes |
+| :---- | :---- | :---- | :---- | :---- |
+| Cached room list | Cold start until the cached room list is displayed | From:<ul><li>The user is already logged in</li><li>The app is not running in background</li><li> The user taps on the app icon</li></ul> To:<ul><li>The room list is fully loaded from the permanent cache and displayed to the end user | <ul><li>First rooms displayed after login or restoration (**TBD**) </li></ul> | The clock starts after the Sentry is initialised. |
+| Up-to-date room list | The app syncs and the room list becomes up-to-date | From:<ul><li>The app was inactive in background and get debackgrounded</li><li>Or the app just finished its cold start</li></ul> To:<ul><li>The room list service state becomes [`Running`](https://github.com/matrix-org/matrix-rust-sdk/blob/matrix-sdk-ui-0.14.0/bindings/matrix-sdk-ffi/src/sync_service.rs#L36)</li><li>No more Syncing spinner |  | The expected final conditions should be:<ul><li>The room list is updated</li><li>Properly sorted</li><li>Last messages are up-to-date</li></ul> But we need more work to compute this metric.  |
+| Notification to message | A notification was tapped and it opened a timeline | From:<ul><li>The app is in background or active</li><li>The notification is for a message in the main timeline</li><li>The user taps on the notification</li></ul> To:<ul><li>The message is visible in the timeline</li><li>The timeline around this message is fully loaded | <ul><li>Timeline load</li></ul> |  |
+| Open a room | Open a room and see loaded items in the timeline | From:<ul><li>User taps a room from the room list</li></ul> To:<ul><li>The timeline is fully loaded with first items loaded  | <ul><li>Timeline load</li></ul> |  |
+| Send a message | Send to sent state in timeline  | From:<ul><li>User hits the send button</li></ul> To:<ul><li>The timeline shows it as sent |  | The `RoomSendQueueUpdate` enum in the SDK can be used for this: `NewLocalEvent` being returned means the event is in the send queue, `SentEvent` means we received it in the sync. We don't really know when it lands on the timeline, but the delay should be minimal. |
 
 ## Additional data