3 ms·

1. You rather missed my point. I brought up web development from a developer's perspective, not a user's perspective. 2. Take the typical case right now - acco

1. You rather missed my point. I brought up web development from a developer's perspective, not a user's perspective. 2. Take the typical case right now - accommodating the Nexus One and a typical large-screen HVGA device - the difference would be about 0.5-0.8cm in extra vertical space. Coming up with a design to work on both screens isn't going to ruin your application, neither is it so exceptionally hard as to not be worth it. As you've demonstrated, its a very popular piece of Android FUD right now.

Groxx 16y ago
1) which is why I pointed out the relative lack of fluid layouts on the web. Developers not doing what's best for users, because it's a pain. Granted, I spent more time in user-land. 2) so if you've got a background image which you want a button to appear over, you either need bottom buffer space on one, and is weighted off the bottom, or it gets cut off on the other. Or you need two images and two layouts. Same issue, and this is for highly styled apps, not for basic stuff (which is legitimately easy). As to the resolution independence, you still need to make a ton of resolution-specific images if you want the sharpest possible image, which - again - matters for perceived value. And you're royally screwed if you do pixel-art instead of something easily resized.
- martythemaniak 16y ago
  1) It's far more of a pain on the web, which unlike Android wasn't designed to easily deal with this issue from the get-go. 2) Having different resolution renderings of 3D images or tile/patterned images is not a problem. Think of Bejeweled on the iPhone (it is a stylish app that uses a bg image as per your example) - minor cutoffs (ie showing more sky) and different resolutions would not be a big issue. Given the new iPhone 4G (2x the resolution) and the iPad (different resolution and different screen size) these are issues iPlatform developers face too, and they'll get around them the same way.
- brehaut 16y ago
  re:1 - No. If the page is primarily content based rather than app based then a fixed width design may well be the best thing for the user; the readability of a design is heavily effected by the interrelationship between factors such as type size, line length, line height etc. Changing the line length without effecting any other aspect of the design can easily have an adverse effect on readability. If your user's primary task is reading, you have just done your users a disservice. While some fixed width designs are because the designer went nuts with the rasters and making it scale is hard, many designers are doing it for good reason. [citation needed ;) ]

Groxx 16y ago

1) which is why I pointed out the relative lack of fluid layouts on the web. Developers not doing what's best for users, because it's a pain. Granted, I spent more time in user-land. 2) so if you've got a background image which you want a button to appear over, you either need bottom buffer space on one, and is weighted off the bottom, or it gets cut off on the other. Or you need two images and two layouts. Same issue, and this is for highly styled apps, not for basic stuff (which is legitimately easy). As to the resolution independence, you still need to make a ton of resolution-specific images if you want the sharpest possible image, which - again - matters for perceived value. And you're royally screwed if you do pixel-art instead of something easily resized.

martythemaniak 16y ago
1) It's far more of a pain on the web, which unlike Android wasn't designed to easily deal with this issue from the get-go. 2) Having different resolution renderings of 3D images or tile/patterned images is not a problem. Think of Bejeweled on the iPhone (it is a stylish app that uses a bg image as per your example) - minor cutoffs (ie showing more sky) and different resolutions would not be a big issue. Given the new iPhone 4G (2x the resolution) and the iPad (different resolution and different screen size) these are issues iPlatform developers face too, and they'll get around them the same way.
brehaut 16y ago
re:1 - No. If the page is primarily content based rather than app based then a fixed width design may well be the best thing for the user; the readability of a design is heavily effected by the interrelationship between factors such as type size, line length, line height etc. Changing the line length without effecting any other aspect of the design can easily have an adverse effect on readability. If your user's primary task is reading, you have just done your users a disservice. While some fixed width designs are because the designer went nuts with the rasters and making it scale is hard, many designers are doing it for good reason. [citation needed ;) ]