Linked by Thom Holwerda on Wed 16th May 2012 21:17 UTC
Thread beginning with comment 518449
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Haven't we been making applications that can withstand arbitrary viewport sizes (window resizing) for the better part of a decade now?
Overall: I don't think so / not really / depends what we mean by "withstand" - many (most?) applications had and have UIs which can't exactly be described as ideal in the first place.
I think the issue with the fixed width web applications is just that the web is broken as a concept for applications. The web is for documents.
Any native application with proper use of layout managers won't have any big issues with resizing. The only problem is that a minimal size is required, of course.
But it is difficult for designer for make flexible UI (Fixed width Web page are a testament of it).
Plus Porting the fixed graphical mockup to a flexible size screen is not straightforward (cost more money)
Plus Porting the fixed graphical mockup to a flexible size screen is not straightforward (cost more money)
Yes, the money thing is real, but seriously, its not technically hard to do. It is creatively and emotionally hard for designers to allow for their creation to not be rendered at a fixed width screen size. I don't really care if there is a tad more blank space between elements or the relative position between elements changes on different screen size. HTML was created with the idea that it would be rendered differently on different screens. Its the professional designers that have mostly screwed that promise up.
Personally, I'm surprised at the whole screen resolution being such a bother to developers. Haven't we been making applications that can withstand arbitrary viewport sizes (window resizing) for the better part of a decade now?
It looks like this. Fast answer is yes, but reality is different:
First of all most mobile developers are not used with this any more AND
For desktop:
1) The DPI didn't increase so fast
2) Apps were not made to work full screen only
3) Touchscreen (mouse adapts easier to changes in DPI)
4) Screen size was not an issue
How does this influence:
1: - Don't need to take care about font size, icon size..., you can assume it will be readable
3: - Don't have to be sure the buttons are big enough to press them easy while small enough to use less screen size.
2: - you don't have to make each app resizable, most dialogs could have fix size.
4: - didn't have to think the interface so well to display all info needed, while taking care that on small screens it should be visible, on big ones uses all space and still look good.
Over all the biggest problem is that you have to create a GUI that looks good and is usable on a 2.5 inch X10 mini, and a 5.3 Galaxy Note.
Most GUIs that worked ok on a 15 inch 800*400px display, also worked ok on a full HD 22inch screen
The upside of mobiles is:
Each OEM knows the size and DPI of the display, so the OS can display the UI right (size of buttons...), with little help from developers: font size resolution independent, use a dynamic layout, be smart about how you place elements - try to use vertical layout as much as possible
Most important thing is to use standard GUI elements, or derive from them, do not create your own GUI framework just because you like it.





Member since:
2009-07-16
I wonder if Apple is so determined to stick to set resolutions because it's easier to do skeuomorphism at set resolutions. That does make me wonder why WP7 is so constrained by comparison. Perhaps it's just not as mature?
Personally, I'm surprised at the whole screen resolution being such a bother to developers. Haven't we been making applications that can withstand arbitrary viewport sizes (window resizing) for the better part of a decade now?