We test designs before develpment, qualitative test with 5-10 users. Post development, we test with 20-50 users on beta, to reduce/remove functionality issues. On production app, we monitor each screen's sucess rate and drop rate. This monitoring gives us more of quantitative data, of our designs, showing whether its working for masses or not.
@@uxtrim I meant design testing as in , when you get your designs on staging , how do you test the ui issues . Do you do mannualy comparing it with your figma file or do you use any tool ?
Okay. Lets, take an example of pre-checkout screen while booking a movie ticket. An User selects his/her movie, selects number of seats, then seats in perticular rows and aisle, and then.. user reaches preview page, where app asks for confimation. Here on this preview page, you will decide and put which section will be editable, other states of section depending of previous selections, state when user want to re do some selection, sections which may or may not appear depending on theare selected such as addons or food etc. Here you put notes along side this screen and its other states that when other states will be visible and why they exist for developers to understand user flow as well. You can write about interaction for deleting selection or some other action. if you have time, you can create this animation in after effects or figma. I'll be covering this topic in near future. ☘️
Nicee!
✌
How do you test your design after your design is developed?
We test designs before develpment, qualitative test with 5-10 users. Post development, we test with 20-50 users on beta, to reduce/remove functionality issues.
On production app, we monitor each screen's sucess rate and drop rate. This monitoring gives us more of quantitative data, of our designs, showing whether its working for masses or not.
@@uxtrim I meant design testing as in , when you get your designs on staging , how do you test the ui issues . Do you do mannualy comparing it with your figma file or do you use any tool ?
Oh, that... Okay.. so post development, it goes through review by Dev team, Design team, and QA team. We do it manually.
Could you please elaborate on design handover file, maybe with hypothetical examples
Okay. Lets, take an example of pre-checkout screen while booking a movie ticket.
An User selects his/her movie, selects number of seats, then seats in perticular rows and aisle, and then..
user reaches preview page, where app asks for confimation. Here on this preview page, you will decide and put which section will be editable, other states of section depending of previous selections, state when user want to re do some selection, sections which may or may not appear depending on theare selected such as addons or food etc.
Here you put notes along side this screen and its other states that when other states will be visible and why they exist for developers to understand user flow as well. You can write about interaction for deleting selection or some other action. if you have time, you can create this animation in after effects or figma.
I'll be covering this topic in near future. ☘️