21–29 of 29 posts
why is this article at the top? this is like web dev 101 stuff
A lot of developers still don't do this often, don't do it properly, or don't know what to call what they're doing. To you it may be 101 stuff, and it is to me, but if you were educated in front of, say, a form designer, that's a hard habit to break.
those terms are arbitrary to some extend. You can have any degree of interactivity with any of those states.
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…
Some categories exist in such abundance that one way to stand out is the create superior interaction.
But it's not always necessary to be successful.
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…
sketch -> wireframe -> prototype -> stylish paint job
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.
Demo is where you combine look and feel with core functionality. It can still be very hacky under the hood and use pre-rendered output etc.
Granted, this assume complex functionality. If your reusing a common pattern like website with checkout then it's a non issue.
With regards to "when should one introduce interactions / logic / UI" decisions, I think it depends on the sort of application you're building, who is the user, and what are the risk factors that need addressing.
If the goal is to build a simple blog-like site for a mom-and-pop shop, then you might want to start with paint & chrome, because while many platforms could suffice, the importance of front-end gloss might drive implementation choices.
If the goal is to build a geodetic-measurement app for plate-tectonic specialists, perhaps you want to start with the engine, without which the entire effort is pointless.
To me it's all about
- Achieving a shared vision early then refining
- Surfacing risk areas early then addressing
Past that, how many iterations you need and what you call them is mostly semantic, once you understand what you're trying to achieve.
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…