Address book usability on mobile needs improvement

[sche]

Part 1: Define the problem

What problem are you trying to solve?

The address book lacks basic functionality that worsens the overall app UX.

Safes and keys names are not stored in the address book It prevents using safes and keys addresses seamlessly when creating new safes and sending funds.

Not easy to add addresses to the address book Now users need to navigate to the address book to add a new address there. We can make additions of new addresses to the address book more accessible.

What is your hypothesis?

Adding new addresses to the Address book easier will lead to better discoverability of the Address book feature on mobile. Aligning the address book between Web and Mobile will lead to better user experience and consistency. Improving the UX of the address book will positively impact the ratio of created Safes and transactions on mobile.

What value does this bring to our customers and/or our mission? What is the goal?

Address book helps keep funds secure since human-readable names reduce the risk of sending funds to the wrong address.

How do we measure it?

• Users using the address book

Links:

Requirements

Part 2: Shaping the problem

Solution

To improve the user experience with Addressbook on mobile, allow the selection of "trusted" recipients during "Send Assets" and make the process of safe creation ( add owner) or owners management more attractive and easier for the user on mobile the following changes should be made:

1. [iOS] Transfer the "safe name" and "owner name" to use address book.

:heavy_plus_sign: One table for keeping created/added on mobile safes, owners keys, imported from the web or added manually addresses instead of 3 separate sources for easier accessibility and visibility. :heavy_plus_sign: The same name for the owners and safes all over the app. Now we have confusing cases when the same safe or owner is located in the address book and on the safe details or owner list with different names at the same time.

:question: What network the generated, imported, connected ledger Nanon X key should be put in the address book under? It will be defined during the preparation of the detailed requirements

2. [iOS] Tapping on an address should suggest adding it to the address book

:heavy_plus_sign: Easy and safe way to add a known address with a human-readable name in the mobile address book directly from the mobile app

3. As a user, I'd like to select an address with a human-readable name from the Addressbook during Send Assets, Safe creation, and Safe owners management.

:heavy_plus_sign: A simple, straightforward and safe way to select often used recipients/owners without a need to open something else except the mobile app as in case of scan QR code or copying to the clipboard the address before the send assets/owner management flow is started.

Rough Scoping & Timeline

The rough estimation is one sprint.

Risk(s), Key Trade Offs & Decisions

The main risk that may influence the implementation time is a data migration No activities on the back-end or web client sides are required

Open Questions

[tschubotz]

What value does this bring to our customers and/or our mission? What is the goal?

Address book helps keep funds safe.

I would add "why?" here to make sure we are all on the same page. E.g. Address book helps keep funds secure since human readable names reduce the risk of sending funds to the wrong address.

[tschubotz]

How do we measure it?

• Users using the address book

Do we have numbers on the current usage? (Also compared to web ideally)

[sche]

@tschubotz We have some numbers. But I would not rely on them. With current implementation on iOS address book is very limited in what a user can do with it. One of the prominent pains: a new user creates a safe, it is needed to add a key with funds to proceed, but when the key is added it is not possible to add it as an owner, as owners can be selected from the address book, but keys and safes are not there, so you need to close safe creation flow to copy the key address, and then to start it again. Another example: you can’t use an address book when making funds transfer. Currently, around 17% of our users visit the Address Book list page hidden in App Settings.

[rmeissner]

Should we add tracking to see how many entries users have (global property) and also tracking for adding (and removing) address book entries?

[sche]

@MouazAlzahabi will assist on tech estimates