Wireframes and software development: They don’t have to make you cry.

posted in: process | 0

Title: From Wireframes to Code, Part I
Context: Can wireframes work harder in the software development process than as merely a UI blueprint? Sure. Why not?
Synopsis: The value of wireframes may actually be a matter of perspective. If they are only looked at as an early stage of design iteration than they probably do not have much long term value. But – and this is a big “but” (not an anatomical analysis) – if they are seen as the starting point for collaboration between the engineering and UX/UI teams then the value proposition changes a bit. They don’t look like a bunch of unstyled boxes but more like the code foundation for the final UI, which can not only speed up production but also cut down on production errors (Agile development anybody?). Whether or not we all become facile in the production of working integrated code wireframe prototypes is not really the question, it is simply a point of view that we should all consider. Also, the pro and con discussion towards the end of the article is alone worth the price of admission.
Best Bit: “The key concept wireframes revolve around is collaboration. Wireframes are essentially a team collaboration tool. They let designers, project leaders, developers, stakeholders, and users all see a project from a common standpoint.”

via uxmatters.com

Leave a Reply

Your email address will not be published. Required fields are marked *