Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wallet Improvements Project - Issue Tracker #493

Closed
14 of 30 tasks
pavlenex opened this issue Sep 24, 2021 · 8 comments
Closed
14 of 30 tasks

Wallet Improvements Project - Issue Tracker #493

pavlenex opened this issue Sep 24, 2021 · 8 comments
Labels
Copy Task is about improving text. Design Task is about designing something.

Comments

@pavlenex
Copy link
Contributor

pavlenex commented Sep 24, 2021

This issue will serve as a ticket tracker of all the issues we, as Bitcoin Design Community identify on our design review calls and beyond. The goal is to allow us central place to keep track of all improvements proposals and their implementation.

Maintainers feel free to edit this comment to add new issues to the list, and anyone else feel free to post a links to the issues you've identified.

The screens of wallets we're reviewing can be found in this Google Sheet.

Blixt Wallet

Bluewallet

Breez Wallet

Phoenix Wallet

Bitcoin Design Guide improvements

Bellow are improvements that we've added to the Bitcoin Design Guide based on the reviews we've performed.

@pavlenex pavlenex added Bug Something isn't working and removed Bug Something isn't working labels Sep 24, 2021
@pavlenex pavlenex pinned this issue Sep 24, 2021
@moneyball
Copy link
Contributor

moneyball commented Sep 24, 2021 via email

@pavlenex
Copy link
Contributor Author

I assume what Steve mentioned, refers to the Bluewallet and I agree, I guess the small nits can in the UI can still be ironed out as I don't think implementation would affect them, but we should hold off any major structural feedback and focus on other wallets until Bluewallet is released with LDK.

@GBKS
Copy link
Contributor

GBKS commented Sep 24, 2021

Agreed. I mainly wanted to put together some examples for this initiative and hope that others join in. Roughly, I think we can discuss 4 levels of feedback:

  1. Use case & audience (what user problems are being solved, who are the users, product-market fit...)
  2. Spec (what features and tech is supported, are they appropriate for the use case...)
  3. Interaction (is it easy to understand, navigate, use...)
  4. Execution (layout, icons, colors...)

My examples were intentionally focused on the 4th type, as it's really easy to capture, discuss, and fix. Hopefully we get a few people to do these, I am curious what everyone thinks can be improved.

@Bosch-0
Copy link
Collaborator

Bosch-0 commented Nov 24, 2021

Who's keen for another, I recommend Zap. They're remote node only on mobile but the desktop has a neutrino light client mode. Feedback is also relevant to Zeus redesign

@pavlenex
Copy link
Contributor Author

@Bosch-0 Let's set up one this Thursday. I must admit I've been slacking for the past few weeks on this one.

@Bosch-0
Copy link
Collaborator

Bosch-0 commented Nov 25, 2021

Lock it :)

@GBKS
Copy link
Contributor

GBKS commented Feb 10, 2022

@pavlenex just went through the unchecked links in the issue, all of them are still open.

The issue has gone a bit stale, but I think we can keep using it for any future issues we file with projects via the wallet design improvement project.

There are two additional issues I created with BlueWallet that were not part of the wallet improvement project. Should I add these here, too?

@Bosch-0
Copy link
Collaborator

Bosch-0 commented Feb 12, 2022

Created issues where they did not exist for the zero amount invoice issue Steve brought up

@pavlenex pavlenex unpinned this issue Apr 4, 2022
@Bosch-0 Bosch-0 added Copy Task is about improving text. Design Task is about designing something. Case Studies labels Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Copy Task is about improving text. Design Task is about designing something.
Projects
None yet
Development

No branches or pull requests

4 participants