3 ms·
I see a ridiculous amount of fixed-width webpages, which would imply that using even fairly simple, standard components in a fluid way is far more difficult tha
by Groxx 16y ago
I see a ridiculous amount of fixed-width webpages, which would imply that using even fairly simple, standard components in a fluid way is far more difficult than many developers are interested in doing. Many, not all by any means.
Ask an average phone user if they think of the UI as a webpage. Given that nearly all are menu / button based, not links-in-content based, I'd imagine nearly all will say "no". The expectations differ, so their perceptions of the same app differ.
Ultimately, which do you want: ubiquitous Android, or geek-only Android? And guess which the average users (and thus hardware makers) want. The push will be to make it ubiquitous, thus successful apps must compete with the iPhone directly in usability and "feel", or people will always feel they've got a second-rate device / application, which is degrading to the whole ecosystem.
(for clarification: different devices on the hardware don't bother me for programming - use them or don't, it's your app. The many screen sizes however imply fluid layouts, or huge amounts of fixed + minor fluidity... and clearly nobody wants to make those if they've got careful design (see: webpages). In time with a good library or ten, this could definitely change, as would more focus on design for Android apps. But until that happens, it's fairly damaging to highly-polished apps, which tend to make money more effectively.)
- chaosmachine 16y agoWidescreen monitors killed the fluid layout. It's extremely difficult for a website to look good at both 800px wide (typical netbook) and 2560px wide (27" imac).
- Groxx 16y agoVery true, though not restricting me to 800px wide would be nice sometimes. Say, cap it between 800 and 1024 or a bit higher. Too wide is too hard to read anyway. Given the amount of reading I tend to do, and the infinite-scrollability of webpages, I'm often a portrait-mode fan. It just sucks when you need a bunch of applications open for comparison / parallel development. edit: hm. widescreen / horizontal Android devices exist (ODROID). So we're back to the same issue...
- theBobMcCormick 16y agomartythemaniak said Android UI development is similar to doing HTML + CSS, he didn't say it's the same. The Android UI layouts are significantly less broken than CSS, even before you include the clusterfuck that is varying browsers support for CSS. If you've ever tried doing a UI Layout for Android, you'll find it's actually pretty damn easy to support multiple resolutions. If you're actually interested, here's the canonical resource on supporting different screen in Android: http://developer.android.com/guide/practices/screens_support.html#range http://developer.android.com/guide/practices/screens_support... BTW dealing with multiple resolutions is a problem that's rapidly heading to the Apple ecosystem. The iPad is 1024 × 768, the current iPhone is 320×480, the next iphone is rumored to be some multiple of the current iPhone resolution, etc.
- Groxx 16y agoThanks for the link, hadn't seen anything for Android yet. But it does nothing to alleviate the problem. Re-post of my other comment: 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. The issue here isn't for all applications, it's for highly styled applications, which are kicking ass lately and are important for perceived value of a device. Resolution independence and fluid-ish layouts do indeed make basic UI extremely easy. But basic UI evidently can't compete equally with a more stylized UI, as the iPhone shows pretty clearly.
- enjo 16y agoBut basic UI evidently can't compete equally with a more stylized UI, as the iPhone shows pretty clearly Support that. I can name several apps on my iPhone that are hardly high-style, yet useful and well received (Quickoffice, iFitness, Yelp!... just to name 3 on my home screen). Larger than this. This is something that vector graphics solves extremely well. You want really nice images at multiple resolutions? Illustrator is your friend.
- theBobMcCormick 16y ago
- martythemaniak 16y ago1. 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 ago1) 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 ago1) 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 agore: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 ;) ]