Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Some things can’t be wireframed

insideintercom.io

Post reply on HN
Print view View original

11–19 of 19 posts

Re: Some things can’t be wireframed

#11

Post by marcosdumay »

drakaal wrote: post #8
buzzmckinnon wrote: post #7

Earlier quoted context omitted.

The author's point is that for some projects wireframing may not be appropriate. I've had this experience on numerous occasions where let's say a full-color design comp or an interactive prototype would better serve the concept, which may be hard to grasp otherwise. This is especially true when taking a design first approach, or when your project gains nothing by illustrating hierarchies, navigation, or other wirefra…

The author either thinks the readers are either stupid and don't know the difference between a Hammer and a Screwdriver and why you can't drive nails with a screwdriver.... Or the author is stupid and was driving nails with a screwdriver and wrote this post to explain why they changed.

Look, it's great when the person in charge of deciding policies is the same person doing the work, and the same in charge of selling it to whoever must be convinced. But most people work on different environments (yep, even when they own the company), and communicating, even things that appear obvious to one of the parties, is crucial to make right decisions on those other environments.

For example, if you are looking into hiring a designer, if you didn't read the article and makes the obvious decision of asking a wireframe from the biders, you just alienated everybody that could make your site great. That this is obvious for the alienated designers changes absolutely nothing.

Re: Some things can’t be wireframed

#12

Post by drakaal »

destraynor wrote: post #9
drakaal wrote: post #8

Earlier quoted context omitted.

The author either thinks the readers are either stupid and don't know the difference between a Hammer and a Screwdriver and why you can't drive nails with a screwdriver.... Or the author is stupid and was driving nails with a screwdriver and wrote this post to explain why they changed.

Or Drakaal is a gutless troll who wishes he could write articles that people cared or even talked about. That's also a possibility I guess.

I think you will find from my comments on HN, My youtube channel, and my interactions in volunteerism, with political movements, and law enforcement that I may be a Troll. But I'm not gutless.

-Brandon Wirtz

Re: Some things can’t be wireframed

#14

Post by destraynor »

drakaal wrote: post #12
destraynor wrote: post #9

Earlier quoted context omitted.

Or Drakaal is a gutless troll who wishes he could write articles that people cared or even talked about. That's also a possibility I guess.

I think you will find from my comments on HN, My youtube channel, and my interactions in volunteerism, with political movements, and law enforcement that I may be a Troll. But I'm not gutless. -Brandon Wirtz

Respect.

Re: Some things can’t be wireframed

#15

Post by andrewflnr »

destraynor wrote: post #9
drakaal wrote: post #8

Earlier quoted context omitted.

The author either thinks the readers are either stupid and don't know the difference between a Hammer and a Screwdriver and why you can't drive nails with a screwdriver.... Or the author is stupid and was driving nails with a screwdriver and wrote this post to explain why they changed.

Or Drakaal is a gutless troll who wishes he could write articles that people cared or even talked about. That's also a possibility I guess.

This is a very low-class and frankly foolish way to interact with someone criticizing your work. Even if it's true that drakaal is not a popular content-producer, and even considering he could have phrased his points more respectfully, that's no reason to just blow off his reasoning entirely.

Anyway, here we all are caring and talking about something he wrote.

Re: Some things can’t be wireframed

#18

Post by seanmcdirmid »

drakaal wrote: post #6

Wireframes are maps, not models. Author doesn't seem to know what a wire frame is. And doesn't seem to have any concept of how UI/UX should be done. Wireframes are typically used for determining how much of each screen something will take up. After that you move to a Mock up. You don't need to see video play to know that the video is going to be too small if the Logo is 1600x800 on the page. A wire frame should be mo…

> Author doesn't seem to know what a wire frame is. And doesn't seem to have any concept of how UI/UX should be done.

Don't be harsh. We all have different ideas of what wireframes are.

> Wireframes are typically used for determining how much of each screen something will take up. After that you move to a Mock up.

I guess web design is a bit different from the more app design field I'm used to, where wireframe is more of an interaction tool used to describe non-visual user experience and flow while the visual toolkit/guide does what the web wireframe would otherwise (not just layout, but everything else visual also). Mockup is mostly used in the early concept and planning stages before design begins in earnest. You move up from wireframe and visual guides to...prototypes.

Re: Some things can’t be wireframed

#19

Post by laander »

My quick summary: 1) Bad example of a detail-poor wireframe that actually could have been good with actual content text and more precision. 2) Explanation that wireframe leads the design direction and sets its own limits of creativity. They constrain your execution to well-known paradigms and restricts innovation. 3) A vague point about alternative methods of user interaction that can't be wireframed and one must leave the comfort zone of traditional UX.

Ironically, the whole post seems to be a retrospective reflection on how Intercom.io COULD have developed their own product, but chose not to. https://www.intercom.io/ is a direct example of wireframe-driven design that fits into the same boxes that OP wants to break.

Post reply on HN