Unified tx list: design decisions

Links
Uniform transaction list view #353 🐱
Uniform transaction list view (Transaction List v2) #820 🐱
Problem and proposal + kickoff meeting 🐱
Hypothetical press release 📆
2020-11-11 Refinement 📆
2020-12-01 Refinement 📆
Voting on Slack 📣

Platform: web, mobile

App version: iOS 2.8.0, Android 2.8.0, web: tbd.

Which problem do we solve?
See 4 Same view on all platforms (e.g. Transactions) 📆.

How does the feature fit into the product and larger product decisions?
See Uniform transaction list view #353 🐱

What are the metrics and KPIs we will be measuring for this feature?
tbd

Is there user research or quantitative data informing decisions made here?
#24 Safe Apps & Layout Redesign user tests insights 💡
#26 Safe Multisig Transactions user tests insights 💡
[#29 Quick Transaction List tests insights](https://docs.google.com/document/d/1t4_pumT-XO-cva6hBwjm4Am1RjryyVWjflzpuyh_Oh0/edit#29 Quick Transaction List insights) 💡
#30 Rejections & Advanced Parameters user tests insights 💡

Screens

1. Queue

2. History

3. Only one next transaction

4. Nothing in queue

Main design decisions

1. Structure with two lists

...

2. ...

...

3. ...

...

4. ...

...

User tests – insights, changes after user tests

#27 Signing On Mobile Insights 💡
Recommendations:
...

Changes after release, metrics

tbd