Participants: Participants: Sarah Meadows (SSIT), Ed von Aderkas (SDS), Ryan Qiu, Desmond Atikpui, Matthias Choi

Intro

• ship web app internally by the end of this semester
• ship mobile app next semester
• users disliked past user interface because functional but dated
• recurring meetings? (Matthias will provide more details)
  • drivers might not be able to attend despite scheduling

App Details

• carriage must be implemented, and then re-implemented/integrated by the Cornell IT services into their own tech stack
• will this app be a containerized webapp? (yes, currently in progress)
• separated into three components
  • web (admin view, students and drivers)
  • driver (web and mobile)
  • rider (web and mobile)
• cannot use google analytics due to legal issues

Questions

• CULift as a set range where they can pick up and drop off students. How will Carriage address this and let students/drivers know what is and what is not a valid location?
• can students add their own locations, or do they have to be added manually?
  • as of now, locations can only be entered by admin

Pain Points

• currently, there are no ways to specify specific details about pickup: things like accessible entrances, ramps, loading docks

Misc.

• is this a summation error? how are these values calculated?CULift Area