UX Review every developer should do before writing the code
One of the ask in the interview is “Person should be a team player can work cross-team”.
Have you ever thought about what it means? Which all trait company is looking in the candidate? Is it just working within the development team or non-tech team too?
You will be surprised that how many times a developer gets rejected because the developer was not able to explain the role he/she plays in cross-team. It is important to learn and understand that development cannot be done in the isolation. It is important to understand the UX, review UX, and work with the UX team.
In my career experience, I have seen a lot of developers lack these skills. There is no ‘course’ for this but one can learn this and with experience improve. You don’t need to be a UX expert but all you need to be is to think like a developer when reviewing the UX — performance, DRY, consistency, etc.
Why?
A successful web project is not because of one person but because of the team. A team, where everyone works together to ship the quality product.
It is important to review the UX before even writing your first line of code to avoid:
- Rewriting the code. If after development there are some issues tester flags in the UX.
2. Making sure that consistency is there across the designs.
3. Making sure that UX is ‘doable’ and won’t be impacting performance.
4. Making sure that cross-browser and cross-OS the UX is possible.
5. Making sure that accessibility has been considered
Read the whole blog at dev.to
