What Is the Difference Between Wireframe, Mockup and Prototype?
1–10 of 29 posts
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#2It says functionality is represented in a wireframe. Doesn't wireframe simply shows structure? That is, which elements goes where. The functionality is shown in a prototype.
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#3It says functionality is represented in a wireframe. Doesn't wireframe simply shows structure? That is, which elements goes where. The functionality is shown in a prototype.
You could argue that Wireframe shows functionality, whereas Prototype tests functionality.
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#4I really disagree with thinking about the interactions that late into the process. I think that, today, interactions are at the core of an application instead of just being eye-candy.
Putting your wireframes in a prototyping tool allows you to quickly test and figure out if the interactions that will drive your flow are good or not. You really don't want to know this only when you're done choosing your fonts/colors and aligning everything.
With the "wireframe prototype" you get a good idea of the structure and the main interactions. The mockups can give you the look of the app. The final high quality prototype is also not always super useful, and should be used, imho, as a communication tool with the clients if they need it.
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#5Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#6It says functionality is represented in a wireframe. Doesn't wireframe simply shows structure? That is, which elements goes where. The functionality is shown in a prototype.
You could argue that Wireframe shows functionality, whereas Prototype tests functionality.
Exactly. As long as you share a common language in your team, and with your client, it doesn't really matter.
If someone says "I need a wireframe/mockup/prototype" then clarify exactly what they are looking for - functionality? layout? content?
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#7It says functionality is represented in a wireframe. Doesn't wireframe simply shows structure? That is, which elements goes where. The functionality is shown in a prototype.
Mateusz Warcholinski mentioned Balsamiq[1] as an example of his definition for a "wireframe" tool.
Therefore, instead of trying to parse his description of "wireframe", it may be better to just look at Balsamiq's capabilities: https://balsamiq.com/
To me, it looks like his idea of wireframe is something "clickable" ... such that it launches another fake page, but not functional. A Balsamiq/wireframe tool is something non-programmers like designers and business leads could use to communicate a UX/UI.
[1]Mateusz Warcholinski wrote: "My favourite tool to do it: Balsamiq"
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#8I really disagree with thinking about the interactions that late into the process. I think that, today, interactions are at the core of an application instead of just being eye-candy. Putting your wireframes in a prototyping tool allows you to quickly test and figure out if the interactions that will drive your flow are good or not. You really don't want to know this only when you're done choosing your fonts/colors a…
To me, a wireframe specs out the UX and shows all possible user interactions. A mockup is a static representation of a wire frame with design added. A prototype is a working representation of a wire frame with the design added. Though the functionality may be simulated or mocked.
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#9why is this article at the top? this is like web dev 101 stuff
Re: What Is the Difference Between Wireframe, Mockup and Prototype?
#10why is this article at the top? this is like web dev 101 stuff
[deleted]