[Story] Peer Testing #1 Feedback & Fixes

[connordoman]

Description

There are several things we need to work on leading up to Peer Testing #2. We got pretty consistent feedback mostly focused on UX, most of which should be straightforward to fix. Some feedback was more valuable than others. The following is a list of fixes we should implement for our Week 6 milestone.

New features for Week 6 and Week 8 will be in another issue (e.g. appointment video display/delete features, backend restructuring).

Feedback

• [x] More descriptive homepage
  • Sign-in/register should be more prominent (e.g. placed centrally on /)
• [x] #487
  • e.g. create appointment should redirect, buttons should be stateful
• [x] Phone number in Cognito is awkward/unnecessary
• [x] "Sign in with Cognito" feels like you need a Cognito account
• [x] #573
  • e.g. appointment cards feel confusing because time is understated
• [x] #515
• [ ] Info card coloring looks amateurish
• [x] #562
  • [x] ~Staff don't need to access User area (give staff their own hub with quick views)~
• [x] Navigation bar (once logged in) can show quick details $\to$ #524
  • e.g. sign-in/sign-out, staff/user status, upload button
• [x] Progress indicators should be used (i.e. loader spinner, progress bars) $\to$ part of #514
• [x] #571
  • e.g. email button doesn't do anything, we don't have a YouTube page

Quick Links

Patternfly

• Notification drawer
• Navigation demos
• Loading buttons
• Loading spinner
• Label
• Masthead/Navigation bar
• Avatar/Profile picture
• Background image Can't use because of @next/image
• Brand logo
• Flow/Progress stepper
• File upload $\leftarrow$ Wasn't there a reason we couldn't use it?
• Tooltip
• Alert/Toast
• Description list/key-value list

Other React Components

• React Video Recorder

[tthvo]

When displaying information about an object (i.e. user, appointment), you can use: https://www.patternfly.org/components/description-list

[tthvo]

Carry over from last peer testing (See #349):

The original deliverables from the project doc are as follows:

• [x] Professionals can edit appointments for clients
  • [x] #367
  • [x] API route to save to database
• [ ] Clients can view appointment details (videos sent, times, etc.)
  • [ ] #365
  • [ ] #366
• [ ] Clients can cancel appointments
  • [ ] #363
• [x] Clients can view a list of their appointments
  • [x] #362
• [x] Videos are processed into censored versions
  • [x] #360
  • [x] #361
• [x] API routes for upload to video processing server
  • [x] Upload to S3
  • [x] Store resource URI in database/update message history

Additional work that needs to be done:

• [x] Transition (or partial transition) to serverless
  • [x] RDS
  • [x] Lambda
  • [x] S3 input, S3 output
• [x] Reintegrate video upload pipeline
• [x] Improve usability, critical path

[tthvo]

Tracked in #584