> It becomes an issue if you're not a sloppy kind of designer/programmer, who just lets the widget flow to occupy more available space. What? In most cases, th

> It becomes an issue if you're not a sloppy kind of designer/programmer, who just lets the widget flow to occupy more available space. What? In most cases, that is exactly the right thing to do. Your content should be the center of the app in the first place. > It's not like design only use things like a text entry boxes or a web-views (widgets that just letting them get more space is usually fine and natural). Why don't you name some actual, concrete examples instead of making vague statements like this? Where do you think that this is an issue? > Second, it becomes an issue for every app where you want to have a custom interface -- so the built-in Android widget and layout are of no use to you. This holds for most games, customly designed apps, etc. What does a "customly designed app" even mean? There are countless examples of Android applications designed beyond the norm (http://androidniceties.tumblr.com/ http://androidniceties.tumblr.com/) and they don't seem to have any problem doing so - and guess what: they're using the Android frameworks just like everybody else. And just like application developers, game developers have been working with a myriad of different screen resolutions for ages now. The only people having a problem with this are those exclusively developing for a certain fruit device that has shot itself in the foot by not designing for varying resolutions in the first place. It's not rocket surgery.