Now that the product is getting close to its final stages, it is time to start doing some high-quality testing. Unlike the rapid prototypes, these should be high quality and well thought out. Focus again on a single idea and design for it, sometimes these will make up a large part of the product that needs to be worked on. These prototypes can come in the shape of invision prototypes with a click through of screens. They are good to show the team exactly how a product looks when it’s done and how a user navigates through them. They also allow the target users to really give their feedback.
These prototypes can also include code prototypes. These are usefully for testing functionality and concepts before really fleshing them out into the full product. Use sites like Codepen or JSfiddle to test out ideas or even build them on Codebots and see how they work.
Before you start
- Pixel perfects
- Wireframes
Details
Level of difficulty
Hard
Stage
Realisation
Suggested time
4hrs to 6hrs
Participants
- Squad lead
- Designer
- Web engineer
- Test engineer
Materials
- Invision
- Codebots
- Design software
- Codepen
- JSfiddle
Steps
- Take your designs or concepts into your medium of choice and start to build them out.
- Make sure you include interactions, animations and functionality if you can.
- Get feedback and testing for each idea and start to refine them further.
- Make sure that you did most of your learnings earlier on in the scope so this time is spent fixing aesthetics and experimenting with functionality.
Justification
These prototypes are good to show the team exactly how a product looks when it’s done and how a user navigates through them. They also allow the target users to really give their feedback.
Written by Christine Chien
Marketing Operations and Partnerships
Our very own Christine is a marketer by day, nerd by night. If she isn’t developing our marketing strategy, she is usually found by her 3D printer or at a local plant shop.
