Design Intent - Design Feedback - IIR Team, Veteran Status Card, New Home & User Experience

[allison0034]

Next Steps for the VFS team

• [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• Listen to the recording for any feedback from Ryan Thurlwell or other designers on the call.

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• [ ] Must: Per our guidance, don’t use italics. It doesn’t show up well on a screen, and sometimes it can be harder to read than normal text.
• [ ] Must: Our default body size is 17px, I would change the font size on the card to 17px.

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [x] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone

[rtwell]

ok gang here is a bunch of feedback the mobile app team put together.

There is a lot here and I am happy to put time on the calendar and walk through it. Some of this was said in the meeting and I'm repeating here so it's clear.

Must:

1. Retain the Home Screen design regarding the Branch of Service and the Proof of VS link.
2. Retain the panel interaction (do not move to a full page). You can see all of our page types in our documentation).
3. Dark mode for everything
4. Exclude printing on the app
5. Do not limit to a literal card

6. We need to plan for the card’s capabilities & associated interactions once in the wallet:

   • What are the actions that are in the standard overflow menu (typically this is delete the card from wallet, share, etc)? 

   • The Pass Details screen - aka the “fine print/back of card” (what’s being included here?) 

   • What’s the reason for the difference in capabilities and data between the iOS and Android cards?
     • RFID icon on the iOS card:
       • Can you talk about the card’s RFID capabilities? 

       • Why is it iOS only? 

     • Barcode on the Android card:
       • How is the barcode used? 

       • Why is there a barcode on the card on Android but not iOS? 

     • Disability rating on iOS but not Android? 


Consider:

Veterans from the BVA have been asking for additional things on the PVS panel/in the app:

• Indicator on PVS panel demonstrating that someone is blind 

• Including a high-level disability indicator in the app (ideally on 
PVS panel) 

• Adding the VHIC card to the app (they also felt like the VS 
panel would be a good place to access it) 

• Ability to share the VS "card" (so that they 
could share it with their caregiver, family member, and/or spouse).
• What’s the reason for the difference in design/brand between iOS and Android cards?