Kick-off Stage 3 Design Review
Status of Design
- It seems that the design will be completed at the end of November. Currently, the design efforts are at around 85%.
Design Validation Process
- Flow internal team for the design validation process. Source
- The test passes
- The test fails
- The test passes, but there are some out-of-scope issues
- The process is going to vary based on the acceptance/testing branching strategy
- We can also do dark releases outside of the mentioned flow.
- Browser Support:
- Desktop: Chrome/Firefox/Safari/Edge
- Mobile: Chrome/Safari
- Tablets: Not being tested
- It sounds like testing is done mostly manually. I wonder if we can suggest the use of Browserstack and run some automated tests instead.
- Loom is their favorite tool to add more insightful screenshots and video recordings as feedback.
Design Review Overview
- From Figma nothing is out of the ordinary.
- Is there a style guide available for design components, fonts, colors, and brand icons?
- No mobile-friendly at all right now
Navigation
- Major change expected with the introduction of Menu. Some feats are not available on the mobile experience
!Screenshot 2023-10-30 at 1.07.10 pm.png
- Some features are disabled on mobile
!Screenshot 2023-10-30 at 1.12.06 pm.png
Ads Viewer
- Different states: Pretty standard update of jobs adds. It seems that it is going to be difficult to test different states. Highly suggested to mock states with Storybook at the initial stage.
- Listing preview: Publishers can have a preview of the desktop/mobile version of the ad
- Applications:
- Docs: Cover letters and other documents that can be downloaded
- Emails: Emails sent and received. Also, users can send emails through the platform
- Notes: Notes of other reviewers
Long Names
- They would like to wrap and consider long names from the beginning
Notes Aside for Retro
- Meetings go on for too long as per booking. I'm pretty sure we can try to do the same in under an hour.
- We would benefit from having more general ballpark reviews. Also, do we really need the whole team for every step? I kind of agree that now that they already delivered the first iteration of design and requirements, they are basically tied to that version, but this can be done with a smaller subset of the team.
- Kick-offs sprints/tickets: We are still awaiting some designs, so we will need to initiate kick-offs or potentially adjust estimations later on.
- I'm eager to see a Figma style guide from their end. In my experience, creating components and placing them together and, consequently, using them to assemble pages can significantly improve the development process. Otherwise, I highly suggest that we approach to stories in that way first and then tackle more complex components and pages.