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

Replace wallet loading animation with CoinJoin related content #11173

Open
molnard opened this issue Aug 1, 2023 · 5 comments
Open

Replace wallet loading animation with CoinJoin related content #11173

molnard opened this issue Aug 1, 2023 · 5 comments

Comments

@molnard
Copy link
Contributor

molnard commented Aug 1, 2023

General Description

I am looking at this screen a lot. Even with Turbosync, this screen is one which gets the most attention - it is displayed right after the user pressed the button.

What we see now is interesting but it is not "selling" anything. We should grab the opportunity and advertise/educate users on how CoinJoin works and why it is good. The first step is to figure out the concept of the animation but the purpose of this issue is not that but to propose the change.

image

@turbolay
Copy link
Contributor

turbolay commented Aug 1, 2023

More or less Duplicate of #9751

@wieslawsoltes
Copy link
Contributor

@molnard molnard changed the title Replace wallet loading animation Replace wallet loading animation with CoinJoin related content Aug 1, 2023
@molnard
Copy link
Contributor Author

molnard commented Aug 1, 2023

Changed the title to be more precise about what is the point here.

@yahiheb
Copy link
Collaborator

yahiheb commented Aug 2, 2023

This issue and all of these #9076 #9751 #10959 are related to the wallet loading screen. I guess we should have only one issue for all of these.

@molnard
Copy link
Contributor Author

molnard commented Aug 7, 2023

This issue and all of these #9076 #9751 #10959 are related to the wallet loading screen. I guess we should have only one issue for all of these.

I would not close either of them, because they are all different. Whenever we will get to a point to work on this, one will create an epic issue that will gather all of these and converge them (or close with wont fix) into one solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants