at_widgets
at_widgets copied to clipboard
Offer option to upload key file in onboarding widget
Lead: @sarika01
Describe the solution you'd like
Onboarding should offer these options:
- Upload and existing atKeys file
- Create a free atsign
- Activate an atsign
For 3 it should then offer:
a. Scan a QR code b. Enter the atsign name to be activated.
Describe alternatives you've considered This was discussed in the architecture call, and no alternatives emerged.
Additional context Asking people to enter the name of their atsign before uploading an atKeys file is error prone and inconvenient.
No Progress.
With the existing issues coming up in onboarding flow - https://github.com/atsign-foundation/at_widgets/issues/353, https://github.com/atsign-company/at_handle_registrar_web/issues/271 this was not taken up.
Also, similar ticket: https://github.com/atsign-foundation/at_widgets/issues/352
This task is going to be addressed along with refactoring the entire code (https://github.com/atsign-foundation/at_widgets/issues/145). This will take longer than 5SPs.
Adding it to current sprint with one week's effort. Need to re-evaluate post that.
Work is in progress. Moving to next sprint.
Planned work for first review is done and given for testing.
Work is done. Planning to roll out in phased manner after other changes like chunk based encryption.
I've made screenshots of the onboarding flow in Wavi app. Please check it!
screenshot.zip Please try again with this file. Thank you!
@tinashe404 & @pavithragk please test this issue with two app:
- Wavi on branch:
feature/onboarding-2.0
- Atmosphere Pro on branch:
feature/onboarding-2.0
Both of them use the at_onboarding_flutter in branchfeature/on-boarding-2.0
linked to issues reported on this ticket https://github.com/atsign-foundation/apps/issues/468
Closing as completed