You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
We have a "generate link" feature that allows users to generate a link to request coins. They can then send this link to another user. This link will open the Massa Wallet module on the send coins page with the address and amount fields already filled.
Generated links looks as follow: https://station.massa/plugin/massa-labs/massa-wallet/web-app/send-redirect/?to=...&amount=...
When a user opens the link, they will either end up on the send coins page, or an error if Massa Station isn't running or if the user doesn't have Massa Station installed.
To avoid users ending up on an error page, we could redirect users to a web2 website page, for example, station.massa.net. So we would endup with a link like: https://station.massa.net/send-redirect/?to=...&amount=...
This page will check if Massa Station is running:
If so, we redirect to https://station.massa/plugin/massa-labs/massa-wallet/web-app/send-redirect/?to=...&amount=...
If not, we tell the user that we couldn't detect Massa Station running, they can install it (with a link to it), or open it (we can probably automate Massa Station starting, but a first version just telling people to open it is fine IMO). And, we display the Address that requested the amount and the requested amount so if the user doesn't want to install Massa Station, they still have the information to send the requested coins.
I think it could help us to improve user experience, even for people that does not have Massa Station installed, and that would also promote a Massa Station when users start using the generate link feature
User flow Describe the user flow using user stories so the end result is super clear - PM
How to List the step-by-step to get it do if needed - PM
Technical details Give the technical insights so anyone in the team can tackle the tasks - Dev
QA testing Does this task require some QA tests ? If yes, explain how to validate it
The text was updated successfully, but these errors were encountered:
Note that in case of Massa Station not detected as running, we could probably also use the Wallet Provider to allow users to send coins directly from the page using a web browser extension.
Priority-wise:
We will need to discuss a few different solutions regarding your proposal after the ICO quest release. For the ICO quests we will go with the currently implemented functionality and flow.
This is a proposal and still WIP
Context
We have a "generate link" feature that allows users to generate a link to request coins. They can then send this link to another user. This link will open the Massa Wallet module on the send coins page with the address and amount fields already filled.
Generated links looks as follow:
https://station.massa/plugin/massa-labs/massa-wallet/web-app/send-redirect/?to=...&amount=...
When a user opens the link, they will either end up on the send coins page, or an error if Massa Station isn't running or if the user doesn't have Massa Station installed.
To avoid users ending up on an error page, we could redirect users to a web2 website page, for example,
station.massa.net
. So we would endup with a link like:https://station.massa.net/send-redirect/?to=...&amount=...
This page will check if Massa Station is running:
https://station.massa/plugin/massa-labs/massa-wallet/web-app/send-redirect/?to=...&amount=...
I think it could help us to improve user experience, even for people that does not have Massa Station installed, and that would also promote a Massa Station when users start using the generate link feature
User flow
Describe the user flow using user stories so the end result is super clear - PM
How to
List the step-by-step to get it do if needed - PM
Technical details
Give the technical insights so anyone in the team can tackle the tasks - Dev
QA testing
Does this task require some QA tests ?
If yes, explain how to validate it
The text was updated successfully, but these errors were encountered: