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
On the user flow for delivery volunteers to pick up deliveries, they have to enter their phone number for each request. Since this can be repetitive, it would be nice to save this phone number in the browser and have it autopopulated in the form.
Requirements:
We will also need a way to clear this saved number.
Number should only be stored if it has been successfully submitted once
Do not store number if it is malformed/not valid
Where
View: /delivery-needed?sms_pickup=true
Click on Claim Delivery
Click on "Yes I accept" button
This is the phone field form:
Considerations
Which makes more sense to use, localStorage or sessionStorage?
Should we have some text explaining that this is only stored on their browser?
Proposed design
Doesn't have to be exact to this rough mock, best to use MaterialUI components (maybe a secondary button?)
The text was updated successfully, but these errors were encountered:
@somstrom another contributor has offered to work on this ticket, but we have many other good first issues (
good first issueGood for newcomers
) to pick up when you are ready!
hi @ifearcompilererrors how are things going with this ticket? i think the approach of setting the input type you mentioned on Slack will work great for this!
hi @ifearcompilererrors how are things going with this ticket? i think the approach of setting the input type you mentioned on Slack will work great for this!
hello! thanks for pinging- aiming to get the PR up by wednesday 👍
Summary
On the user flow for delivery volunteers to pick up deliveries, they have to enter their phone number for each request. Since this can be repetitive, it would be nice to save this phone number in the browser and have it autopopulated in the form.
Requirements:
Where
View: /delivery-needed?sms_pickup=true
Claim Delivery
Considerations
Proposed design
Doesn't have to be exact to this rough mock, best to use MaterialUI components (maybe a secondary button?)
The text was updated successfully, but these errors were encountered: