Wallet Review Call #1 - Phoenix

[pavlenex]

Date: 2021-10-08
Time: 3:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-10-08 15:00 UTC

Agenda

This Friday Oct 8th, we will host a Phoenix wallet review. The goal is to evaluate and take notes on our own experience and possibly suggest improvements to the Phoenix wallet.

Anyone willing to explore Lightning Network and wanting to get involved with the community is invited to participate ❤️ Don’t be shy! This is great opportunity to get involved as a newcomer.

1. Download Phoenix wallet
2. On your google doc/figma take notes on possible improvements, problems, ideas. Feel free to note things that you liked as well.
3. On a jitsi call on Friday, you can share your screen and showcase what you’ve discovered.
4. We will then discuss how we may solve those and pass feedback to the Phoenix team.
5. For Figma addicts, here’s is all screens teardown

If there’s community interest afterwards, we will schedule another call, take deep dive into the wallet technicalities, why certain features work that way, etc. (checklist for in-depth dive). Any questions, ideas feel free to comment in the thread. ❤️

Check your timezone

https://everytimezone.com/s/cc15595c

Join the call

https://meet.jit.si/bitcoindesign

[pavlenex]

This was a very productive call with a few of us attending.
The goal was to take a look a the Phoenix from a first-user perspective.
There are many things that Phoenix does well that can be used as a model for the guide (fee transparency, simplicity, etc)

On our next call, we will have a deep dive into Phoenix and take a look at their design decisions.

As far as this call is concerned, we identified 4 key things that will be packed in the issues and posted on Phoenix GitHub.

1. Copyrighting changes to the onboarding

We pointed out that this screen would probably be better with an improved copy (what are payment channels is one of the questions which came up)

2. Progressive backup error message

Phoenix informs users to backup their wallet even when there are no fees. We came up to a conclusion that a "scary" backup message can appear only after user receives funds to their wallet, when they have actual financial incentive to perform a backup. Furthermore, we suggested that backup message contains a link or instructions on how to back a wallet up.

3. Receive page

User cannot receive less than 10 000 sats with Phoenix on their first payment (fees associated with channel creation). However their Receive screen generates a zero-amount invoice which may lead towards errors. There's currently a WIP effort on restructuring this flow to either hardcoding 10 000 SATS or implementing it within the onboarding screen. Link to Figma.
We talked about CTA restructure as well.

4. Settings page re-structure.

The settings page has some options which can be unified:

• Automatic Backup and Recovery seed backup can be unified under Backup tab and then there may be automatic vs manual backup option according to our guideline.
• Electrum and Tor seem like advanced options
  

[moneyball]

Where can one find the links to the 4 issues cited?

[pavlenex]

@moneyball Best way it to keep an eye on a global tracking issue of the Wallet Improvement Project.

Phoenix today opened a "global issue" here for tracking or recommendations, so before opening the 4 issues mentioened above:

1. I'd like to get buy-in from Phoenix if we should opening issues or comment on that one discussion they have.
2. I'd like for us to come up with concrete suggestions for issues 2 and 3.