✨ Riders sign up for deliveries via app

[mveytsman]

Problem Statement

This is tracking everything we need to do to go from where we are now to having

• (non-dispatcher) Rider can login via their phone into Bike Brigade
• Given a link (from https://bikebrigade.ca/deliveries) a Rider can sign up for a delivery.

Miro board: https://miro.com/app/board/uXjVO_hw8Go=/

Core Issues

Tasks

Preview Give feedback

1. Riders can login to the dispatch app #135
   +0
   
2. Login screen should be suited to riders logging in #133
   +0
   
3. Create a separate changeset for profile for added security
4. Rider Profile Page #134
   +0
   
5. Rider itinerary page (basic) #136
   +0
   
6. When a delivery detail page expires show the distance and metadata but not the link in itinerary, to hide people's addressese
7. Rider Login via itinerary #137
   +0
8. Campaign creation supports rider sign-up #139
   +0
9. Riders sign up for a specific campaign via app #140
   +0
10. Choose a sample campaign or two and slow launch rider-facing signup (issue TBD) #267
    +0
    
11. Full launch of rider-facing campaign signup (issue TBD)
12. Polish riders profile/stats #241
    +0
    
13. Opt-in into the leaderboard (riders can choose to show their name on the leaderboards) #268
    6 of 7
    +0
    
14. Phase out delivery token to just link people to the itinerary page (maybe with the given delivery highlighted) #261
    +0
    
15. Don't allow riders to unassign themselves within N hours of the delivery #294
    +0
    

Nice to haves / Future work

Tasks

Preview Give feedback

1. Rider itinerary page (redesign) #138
   +0
   
2. Rework the Program/Campaign entity relationship #128
   +0
3. Show all the opportunities inside the app? (possibly linking to existing sheets, or wait till we switch everything over)
4. Milestones and badges

[chadmohr]

Variations in signup requirements

- Rider specifies ONLY how many deliveries that can take (Foodshare)

• Rider chooses day of delivery (PCFB)
• Drop off location not known at opportunity creation (SNAP)
• Rider specifies number of units they can take (MAP, OOTC, ESN, Moss Park CTS)
• Split pickup time (PCFB)
• Rider chooses drop off location (various CFTO programs)
• Grouped deliveries - same building (ALAB, SPAFYCC, FYFB)
• Alternating schedule - bi-weekly (SOH)
• Routes with no address (EYMOW, Dixon, WNH)
• Campaigns that don't use signups (EYMOW, Dixon, WNH)
• Pre-assigned rides, dispatcher assigns regular riders

[chadmohr]

Variations in signup requirements

- Rider specifies ONLY how many deliveries that can take (Foodshare)

• Rider chooses day of delivery (PCFB)
• Drop off location not known at opportunity creation (SNAP)
• Rider specifies number of units they can take (MAP, OOTC, ESN, Moss Park CTS)
• Split pickup time (PCFB)
• Rider chooses drop off location (various CFTO programs)
• Grouped deliveries - same building (ALAB, SPAFYCC, FYFB)
• Alternating schedule - bi-weekly (SOH)
• Routes with no address (EYMOW, Dixon, WNH)
• Campaigns that don't use signups (EYMOW, Dixon, WNH)
• Pre-assigned rides, dispatcher assigns regular riders

@mveytsman, cc @teesloane this is where the signup variuations are. They may not make a lot of sense on their own. A couple screens from https://xd.adobe.com/view/e64dceb0-2df2-400f-8971-405ce662631f-b31e/ show some basic wireframes related