3 ms·

The arguments expressed in article actually defeat itself (article is self-contradictory)... 1) Getting attached to wireframes (or any other design concept) wo

by watt 16y ago

The arguments expressed in article actually defeat itself (article is self-contradictory)... 1) Getting attached to wireframes (or any other design concept) would be detrimental (OK... let's agree) 2) Wireframes are ugly (Well... that's actually good, so you wouldn't get attached to them?) 3) It would be better to start designing and coding on the target environment right away... Well wait a minute, don't you get that by doing (3), you will get attached to your first iteration design, and will not realize when it's time to throw it away, and reset/pivot with a new approach?

sgdesign 16y ago
Wireframes being ugly is not really a problem. And I happen to think that Balsamiq wireframes are ugly, but wireframes created with other tools (especially sketching) can be quite beautiful. Of course you could get attached to your first photoshop mockup or your first prototype, but my point is that since they are closer to the real deal, it's easier to judge if they'll work or not.