Transaction decoding v2: design decisions

Links
1 - Owners don’t know what they’re signing 📆

Mobile
Data decoding v2 - Special handling for multisends #350 🐱
Data decoding v3 - More info in Multisends #351 🐱
Data decoding v2 and v3 - Special handling for multisends 📆
Show decoded function & params on tx details v1 #329 🐱
Multisend Miro board 📌

Web
Decoding Transaction Information in Tx List #882 🐱
Decode multiSend tx details #1106 🐱

Platform: web, mobile.

App version: Android 2.3.0, iOS 2.5.0, web 2.9.0.

Which problem do we solve?
Owners don’t know what they’re signing (see 1 - Owners don’t know what they’re signing 📆). Transaction data is cryptic.

How does the feature fit into the product and larger product decisions?
This feature adds special handling for multisend transactions. Mobile and web are not quite aligned on this. Web already decodes multisend since v2.9.0.

What are the metrics and KPIs we will be measuring for this feature?
See Data decoding v2 - Special handling for multisends #350 🐱

Is there user research or quantitative data informing decisions made here?
Data from discovery interviews Q1 2020 💡
Insights from discovery interviews Q1 2020 💡
Roadmap Q3/Q4 2020 📆