{"id":28362,"date":"2022-04-14T07:42:54","date_gmt":"2022-04-14T07:42:54","guid":{"rendered":"https:\/\/emizentech.com\/blog\/?p=28362"},"modified":"2023-08-29T11:08:19","modified_gmt":"2023-08-29T11:08:19","slug":"wireframe-mockup-prototype","status":"publish","type":"post","link":"https:\/\/emizentech.com\/blog\/wireframe-mockup-prototype.html","title":{"rendered":"Wireframe vs Mockup vs Prototype: What Is The Difference?"},"content":{"rendered":"\n

Some of the common terms that any product design team uses are Wireframe, Mockup, and Prototype. The design team uses these terms to make an illustration of any concept, to gather feedback, and to gain consensus. With the help of these, the team will be able to create the design. These things also help to build the exact need of the customers. Maybe wireframe, mockup, and prototype seem to sound similar but are unique. All of them are unique and have unique roles at different times while the product is developing. This is also known as the lifecycle of product development.<\/p>\n\n\n\n

The product designing<\/a> team uses these terms interchangeably. For this, there might be any confusion. The confusion regarding which is what and when to use that particular term? How to use that particular term in the cycle? And how do any of these get done? You should also know the exact time of using each of those during any product development process. You need to choose the right process at the very right time. This will help you to get the correct effort level of investment. This will also help you to deliver what exactly a customer wants.<\/p>\n\n\n\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n