Comments on: Pixel Dimension Indicators http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/ Because every IA has something funky up their sleeve Wed, 28 Jul 2010 06:45:14 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Paul http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-10713 Paul Mon, 01 Feb 2010 04:32:39 +0000 http://wireframes.linowski.ca/?p=1213#comment-10713 And the vast majority of all the websites in the world look like total sh*t. And the vast majority of all the websites in the world look like total sh*t.

]]> By: Michael Story http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-4119 Michael Story Sat, 19 Sep 2009 02:23:35 +0000 http://wireframes.linowski.ca/?p=1213#comment-4119 Guys, this example is by far the way to go and the web dev trend of the last five years. It helps the designer design to spec (which should be included in the requirements doc/phase) and guides the developer in coding to the design. It couldn't get any more process logical than this. Although the image example is a little lacking in detail but good. The big leagues of web design/dev are completely using this approach to IA, Wireframes and Design as an integrated approach to process management. Web Designers are designing complete sites in Photoshop and putting the wireframes on layers above the design of each page template. That then get reviewed, approved and handed off to the developer to code against. This is efficient because the designer has complete control over dimension of the site with an in-depth understanding of usability goals of the site. Ben Mitchell and other seasoned web builders like him simply need to be brought up to speed on this approach and adopt it. Blackberry.com, HP.com, Apple.com, Quiksilver.com were all done via the process I'm speaking of. Under time, under budget and ahead of the game. Michael International Web Gurus <a href="http://getMikeStory.com" target="_blank" rel="nofollow">http://getMikeStory.com</a> Guys, this example is by far the way to go and the web dev trend of the last five years. It helps the designer design to spec (which should be included in the requirements doc/phase) and guides the developer in coding to the design. It couldn't get any more process logical than this. Although the image example is a little lacking in detail but good.

The big leagues of web design/dev are completely using this approach to IA, Wireframes and Design as an integrated approach to process management. Web Designers are designing complete sites in Photoshop and putting the wireframes on layers above the design of each page template.

That then get reviewed, approved and handed off to the developer to code against. This is efficient because the designer has complete control over dimension of the site with an in-depth understanding of usability goals of the site.

Ben Mitchell and other seasoned web builders like him simply need to be brought up to speed on this approach and adopt it.

Blackberry.com, HP.com, Apple.com, Quiksilver.com were all done via the process I'm speaking of. Under time, under budget and ahead of the game.

Michael
International Web Gurus
http://getMikeStory.com

]]> By: charlene http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-3377 charlene Wed, 26 Aug 2009 18:03:55 +0000 http://wireframes.linowski.ca/?p=1213#comment-3377 Depending on the audience, this info can help or hinder. I generally prefer to let this info live in the style guide prepared by the visual designers. Ironically, I recently had a developer ask for these specs in the wireframes which was a first. Depending on the audience, this info can help or hinder. I generally prefer to let this info live in the style guide prepared by the visual designers. Ironically, I recently had a developer ask for these specs in the wireframes which was a first.

]]> By: Jakub Linowski http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-2948 Jakub Linowski Mon, 03 Aug 2009 17:17:02 +0000 http://wireframes.linowski.ca/?p=1213#comment-2948 Hi Ben, I'd argue that such dimensional information still provides some sort of feel for scale which is often lost in wireframes (especially after printing). Yes, this is detailing that perhaps might be detrimental in the early explorative phases of design. Such information might also most likely be irrelevant when sharing these ideas with end users or business people. However, when talking to more technical audience perhaps such data still has some value that aids in the development process. I'd be really curious to see a "Redlines" sample. Could you submit? :) Cheers, Jakub Hi Ben,

I'd argue that such dimensional information still provides some sort of feel for scale which is often lost in wireframes (especially after printing). Yes, this is detailing that perhaps might be detrimental in the early explorative phases of design. Such information might also most likely be irrelevant when sharing these ideas with end users or business people. However, when talking to more technical audience perhaps such data still has some value that aids in the development process.

I'd be really curious to see a "Redlines" sample. Could you submit? :)

Cheers,
Jakub

]]> By: Jakub Linowski http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-2947 Jakub Linowski Mon, 03 Aug 2009 17:16:17 +0000 http://wireframes.linowski.ca/?p=1213#comment-2947 Hi Ben, I'd argue that such dimensional information still provides some sort of feel for scale which is often lost in wireframes (especially after printing). Yes, this is detailing that perhaps might be detrimental in the early explorative phases of design. Such information might also most likely be irrelevant when sharing these ideas with end users or business people. However, when talking to more technical audience perhaps such data still has some value that aids in the development process. Hi Ben,

I'd argue that such dimensional information still provides some sort of feel for scale which is often lost in wireframes (especially after printing). Yes, this is detailing that perhaps might be detrimental in the early explorative phases of design. Such information might also most likely be irrelevant when sharing these ideas with end users or business people. However, when talking to more technical audience perhaps such data still has some value that aids in the development process.

]]> By: Ben Mitchell http://wireframes.linowski.ca/2009/07/pixel-dimension-indicators/comment-page-1/#comment-2896 Ben Mitchell Fri, 31 Jul 2009 16:48:39 +0000 http://wireframes.linowski.ca/?p=1213#comment-2896 I don't agree that this process is necessary or event slightly correct. It really dismisses the wireframing process at its core and layers the document with unnecessary and distracting items. I would be interested in hearing the reasoning behind setting specific pixel dimensions at this point and why explicit numbering aids the process? Layering what my studio calls "Redlines" on top of a final visual design is the best way to provide necessary dimensions that speak explicitly to developers. These red, pixel width indicators are a lot more specific then the example above shows and speaks to the only real people that need this information: developers. Obviously in a world where interaction designers and visual designers are a. different people and b. are remote locations then a discussion definitely needs to exist between the two parties, but not with a deliverable like this. I don't agree that this process is necessary or event slightly correct. It really dismisses the wireframing process at its core and layers the document with unnecessary and distracting items. I would be interested in hearing the reasoning behind setting specific pixel dimensions at this point and why explicit numbering aids the process?

Layering what my studio calls "Redlines" on top of a final visual design is the best way to provide necessary dimensions that speak explicitly to developers. These red, pixel width indicators are a lot more specific then the example above shows and speaks to the only real people that need this information: developers. Obviously in a world where interaction designers and visual designers are a. different people and b. are remote locations then a discussion definitely needs to exist between the two parties, but not with a deliverable like this.

]]>