Add Portal rating

[prayagd]

As a user i should be able to rate the portal

Acceptance criteria

• After successfully completing any of these actions on portal, show the rating pop-up
  • Issue request
  • Redeem request
  • Staking
  • Unstaking
  • Unlock unstaked tokens
  • Claim rewards
• The pop-up should close after rating is received.
• Once the rating is received from the user, they should not be prompted for rating for 15 days.
• If the user closes the pop-up without providing rating, show it after 15 days
• Following info to be captured in a excel file/database
  • Rating
  • What action the rating was received on? for ex. /pendulum/staking

Wireframe

https://www.figma.com/proto/5up5sghcttBogehUq4255i/App?node-id=2849-5156&t=t26OmPb2nSn7Axcj-0&scaling=scale-down&page-id=136%3A114&starting-point-node-id=2849%3A5156

[prayagd]

@ebma @Sharqiewicz anything unclear about the above? is it possible to capture the data on excel sheet?

Marked it as high priority as it is one, once estimated i would request to work on this asap.

[prayagd]

Hey team! Please add your planning poker estimate with Zenhub @ebma @Sharqiewicz

[ebma]

If the user closes the pop-up without providing rating, show the pop-up for next successful action.

Isn't this a bit too pushy? I would be annoyed if the app was asking me for feedback all the time, even if I manually close the dialog. I think if a user closes the dialog and actively decides not to provide feedback, we should also not prompt again for at least a week, or maybe treat it like the default case of 15 days.

Following info to be captured in a excel file/database

A database is definitely overkill for this so let's rather try to store it differently. While I've never tried it myself, I guess we can send that data to a Google Form.

[prayagd]

@Sharqiewicz please add you estimates

[prayagd]

Isn't this a bit too pushy? I would be annoyed if the app was asking me for feedback all the time, even if I manually close the dialog. I think if a user closes the dialog and actively decides not to provide feedback, we should also not prompt again for at least a week, or maybe treat it like the default case of 15 days.

Fair point, made changes in the ticket

[prayagd]

Please add your planning poker estimate with Zenhub @TorstenStueber

[TorstenStueber]

We would need some backend for this, I think we should not directly push to the Google Form from the frontend, otherwise we expose the credentials.

[Sharqiewicz]

I think we can use Netlify Functions along with Google Sheets. It won't expose credentials. WDYT? @TorstenStueber @ebma

[ebma]

Since Netlify functions use AWS lambda internally, we can also just create a lambda function for this right away. We can then store the credentials in AWS secret manager for example. Creating an extra server that runs 24/7 just for this might be overkill.

[TorstenStueber]

Yes, Lambda or Netlify functions sounds good. This can be setup and managed by DevOps.

[Sharqiewicz]

The code can be copied from Vortex

[ebma]

Yes, let's re-use the great component you already created in pendulum-chain/vortex#182.
Since we don't have a custom backend deployed for the portal, we need to implement a similar logic as part of a Netlify function though.