near-wallet
near-wallet copied to clipboard
near
Move Migration Landing Page to New Project
Implements new post migration landing page for NEAR Wallet. https://near-wallet-pr-2783.onrender.com/
Your Render PR Server URL is https://near-wallet-pr-2783.onrender.com.
Follow its progress at https://dashboard.render.com/static/srv-catcfjh0gd05b6sj2ppg.
![render[bot] avatar](https://avatars.githubusercontent.com/in/14658?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy Preview for glittering-pavlova-0e9247 ready!
| Name | Link |
|---|---|
| Latest commit | 08f80a19b3fb9be2bac3e93753f2364db759fbf3 |
| Latest deploy log | https://app.netlify.com/sites/glittering-pavlova-0e9247/deploys/630386e264931e00082cf3e4 |
| Deploy Preview | https://deploy-preview-2783--glittering-pavlova-0e9247.netlify.app/report |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Export accounts flow will need to be updated to reflect updates in #2780.
cc: @loosefer @esaminu
@gutsyphilip could you copy over the code in this PR? Also MNW logo needs to be updated in both PRs
@gutsyphilip could you copy over the code in this PR? Also MNW logo needs to be updated in both PRs
I don't think I'll be able to do that. Hence my tagging you both. I have been assigned other tasks. I'll push an update for the logo however.
Your Render PR Server URL is https://my-near-wallet-pr-2783.onrender.com.
Follow its progress at https://dashboard.render.com/static/srv-cb1c4b4gqg45rlgblpc0.
Hi guys,
Just looking at this PR today- is this the UI that is currently planned for the migration page for Near Wallet ?
I was under the impression that the migration was going to be completely neutral as far as helping the user move their accounts to a new wallet goes. This UI as shown in this PR does not appear neutral to me at all- first of all "We've moved" is already telling users that MyNearWallet is the "new" official wallet, only that's its moved- this is not the case, right? MyNearWallet is a wholly new commercial entity? (that just borrows the code of the current Near Wallet implementation) I thought that was the point of creating MyNearWallet- to open to ecosystem up and move away for "centralization" of Near tooling. I mean it literally says "Near Wallet is now MyNearWallet"- we were under the impression this is not the case, its a new separation that simply borrows the old code.
Secondly, the buttons layout seems to imply that the main blue "action" button is going to use MyNearWallet for the migration, and the other "white-out" secondary button is for using other wallets. This is also another clear bias and seems to go against the information we've been told.
We'd appreciate some clarification on this.
Hi Paul, thanks for your feedback. We’ve updated this transfer solution drastically to be fully neutral and help users learn what wallets are available.
On Sep 8, 2022 at 4:57:23 AM, Paul Myburgh @.***> wrote:
[image: image] https://user-images.githubusercontent.com/1508863/189078496-ca6f125a-6b54-439f-8394-4b151d05c15a.png
Hi guys,
Just looking at this PR today- is this the UI that is currently planned for the migration page for Near Wallet ?
I was under the impression that the migration was going to be completely neutral as far as helping the user move their accounts to a new wallet goes. This UI as shown in this PR does not appear neutral to me at all- first of all "We've moved" is already telling users that MyNearWallet is the "new" official wallet, only that's its moved- this is not the case, right? MyNearWallet is a wholly new commercial entity? (that just borrows the code of the current Near Wallet implementation) I thought that was the point of creating MyNearWallet- to open to ecosystem up and move away for "centralization" of Near tooling.
Secondly, the buttons layout seems to imply that the main blue "action" button is going to use MyNearWallet for the migration, and the other "white-out" secondary button is for using other wallets. This is also another clear bias and seems to go against the information we've been told.
We'd appreciate some clarification on this.
— Reply to this email directly, view it on GitHub https://github.com/near/near-wallet/pull/2783#issuecomment-1240428922, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYS4ZA2LJ5FXIRLRTNT4Z6TV5GS7HANCNFSM52BOCD7A . You are receiving this because you were mentioned.Message ID: @.***>
I believe we are not going to go with this approach anymore. Feel free to reopen if I'm wrong @gutsyphilip
We will be needing this for the new landing page project deployed on *.near.org after migration it seems.
Your Render PR Server URL is https://near-wallet-pr-2783.onrender.com.
Follow its progress at https://dashboard.render.com/static/srv-ccmqsgqrrk01p2d4e71g.
Your Render PR Server URL is https://my-near-wallet-pr-2783.onrender.com.
Follow its progress at https://dashboard.render.com/static/srv-ccmqsiarrk01p2d4e7ng.