11–20 of 29 posts
why is this article at the top? this is like web dev 101 stuff
It 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 somethi…
why is this article at the top? this is like web dev 101 stuff
That's not to say it's a great article. But I can see why some people might find it intellectually interesting or useful because it cleared up confusion.
Hacker News is not uniquely immune to Endless September [0]. The expectation regarding dealing with it, using civility, is not unique either. But it is uncommon.
I wrote this, because I couldn't find anything good enough describing this topic. We often got aks by our our customers or first-time-founders - What is the difference? And why and how they can do it?
Earlier quoted context omitted.
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 somethi…
Tad snarky.
After studying Balsamiq, work backwards from that to get an idea of what he meant by "wireframe" and whether or not it has "functionality".
I 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.
It 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.
I would agree they aren't tightly coupled but there is definitely an association there that can't be completely separated.
Not about the op but I've always hated the name "mockup". Maybe it because it seems less technical than other terms used in the design process such as wireframe and prototype. I also dislike the way the word sounds. I often use alternatives like sketch or draft since they describe an output that is usually fairly short in the time frame of construction and open to future change. I hate the name mockup so much I think…