Right, resolution independence doesn't solve the problem of having to design different interfaces for different device classes and form factors. There's no magic bullet for that, and that's why I'm skeptical about Microsoft's Metro (using almost the same interface for 3" phones and 23" PCs).
There are at least three (almost orthogonal) problems here: - resolution independence (better: "awareness") - designing the proper interface for a certain device class - making UI elements scale with text (because we're not using VB6 anymore, and because German words are really long), but not necessarily fixed to the text (bad for the reasons you mentioned)
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: You are both right and wrong.
Date: 2012-07-16 05:35 pm (UTC)There are at least three (almost orthogonal) problems here:
- resolution independence (better: "awareness")
- designing the proper interface for a certain device class
- making UI elements scale with text (because we're not using VB6 anymore, and because German words are really long), but not necessarily fixed to the text (bad for the reasons you mentioned)