Midpoint Review - Design Feedback - Digital Health Platform, MVP

[seanasewell]

VFS acceptance criteria

• [x] Let Platform know when the Must feedback has been incorporated
• [ ] Leave any comments for feedback you decide not to take
• [ ] VFS team closes the ticket

Thoughts/questions

• Great work!

Feedback

• Must = the feedback must be applied
• Should = the feedback is best practice
• Consider = suggestions/enhancements

Must:

• Make sure the cards are using the proper header
• The "Connect" links should be an Action Link or at the very least an Active link and that's in the Card pattern

Should:

• Update the language on the "Go back" button to be more intuitive. "Cancel" makes more sense in the context of closing a modal and abandoning an action.
• We understand the limitations of working with Fitbit as the team is describing, however, you could show a type of device in the Card (Activity monitor (fitbit), Glucose monitor (Freestyle Libre), etc.). Folks may need a bit of a reminder of which device is which and a type could help with that goal.

Consider:

Platform directions

• Update "Issue Title"
• Link to collab cycle Request epic
• Add your feedback
• Add assignees based on collab cycle touchpoint
  • Design Intent: VFS designer, VFS PM (optional), yourself (optional)
  • Midpoint Review: VFS PM, yourself (optional)
  • Staging Review QA Only: VFS PM, yourself (optional)

[zanniemill49]

Because we're releasing an MVP and doing a small pilot with only one device we're going to postpone the addition of device categories and category descriptions. We'll be adding more devices post MVP and will include categorization work there.

[robbie1226]

Thanks for the feedback. Writing to let you know that we applied the "Must" updates to our staging environment.

[allison0034]

@robbie1226 thank you!