I think where I get hung up is on pixels vs. inches. Pixels are fine for desiging how the page will look, but it is not for how it will be touched. On screen, the 320x356 size image looks like there is more room to touch because it is larger than the physical size of the iPhone screen (2" x 3"). But if you go on pixels alone, you could create buttons that look large enough on screen but are too small to touch when seen on the iPhone. It feels like we need to accomodate both the visual size of the design (pixels) as well as the touchability of areas when we design (inches).
Also, I had someone else tell me the dpi also increases the clarity of items on screen. So, a designer could opt to use a small font (5pt) that she would never use for a 72 dpi monitor because it will appear clearer and therefore more legiable. Sorry if I am sounding ignorant on dpi and resolution (I am an IA after all and not a designer), but it seems like this touchable browser screen is the first time where we need to be concerned about both pixles and inches. *My visual input device (eye) is measured in pixles, but my pysical input device (finder) is measured in inches.* On Jul 20, 1:41 am, Randy Walker <[EMAIL PROTECTED]> wrote: > I agree. > > Also when working on the graphics on your computer, make sure to view the > file at 100% zoom, ie.in Photoshop. That way every pixel will get it's own > pixel on the screen and there won't be any blurriness or jaggies etc. I > have seen people load a large graphic into Photoshop and then shrink down > the image window so it looks about the size they want it to look. Or zoom > out to like 50% or 66.6%. Or upload a larger dimensioned image to the > server and have the browser rescale it down, thinking it will look 'better' > somehow because of the 'higher resolution.' Do not do any of those things. > > The graphics will naturally appear larger on your computer screen than on an > actual iPhone if the screen is less than 160dpi, which most monitors/lcd's > are. So, on your computer, a 300pixel wide image done at 72dpi will look > identical (will be identical) to a 300pixel wide image done at 160dpi and > they would both take up the same amount of real estate on your screen(s) > because both are 300 pixels wide. > > Dpi really comes into play when dealing with graphics for scanning/print. > Ie.scanning a 4" wide picture at 600dpi would print out an almost identical > 4" replica. Scanning the same 4" wide image at 72dpi would look horrid when > reprinted at the same size. > > You can simply create a 320x356 (for portrait with the top toolbar in place) > image at whatever dpi you like, and as long as it's viewed at 100% scaling > on your computer monitor, you can get a gist of how big percentage-wise each > individual graphic element should be for your design. > > There are countless articles/tutorials online that go into much more depth. > > -=Randy > > On 7/19/07 8:26 AM, "Michael Geary" <[EMAIL PROTECTED]> wrote: > > > > > > >> From: Matt Rehkopf > > >> I have been wondering about what actual resolution size to do > >> design comps in. Are your pixel measurements based on 72 dpi > >> or the iPhone's 160 dpi? > > > Pixels are pixels. DPI doesn't even enter into the equation. > > > A 320x480 bitmap at 72 DPI is the exact same image as a 320x480 bitmap at > > 160 DPI, or 300 DPI, or any DPI. > > > If you create two bitmap images with the same pixel dimensions and content, > > but two different DPI settings, save those to .bmp or .png format, and then > > do a binary compare of the two files, you'll find that the files are > > identical except for a number in the header. > > > That's all "DPI" is, a number in the file header that image processing > > programs may use for things like determining print size. But it doesn't > > change the image content at all. > > > You could create your comps with any DPI setting and it wouldn't make any > > difference, as long as the number of pixels is correct. (I'm not saying to > > use 320x480 - obviously you need to use the smaller sizes posted earlier > > that take toolbars into account.) > > > -Mike- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
