3 ms·
The screen size diagram misses an important extra complication: the same pixel counts and screen sizes do not always match up. In this room right now there are
by dspillett 13y ago
The screen size diagram misses an important extra complication: the same pixel counts and screen sizes do not always match up. In this room right now there are ~7" devices with resolutions of 800x<whatever> (where "what-ever" varies depending on aspect ratio), 1024x? and 1280x?. When the G2 Nexus 7 turns up there will be at least one at 1920x? too. Similarly resolutions of 1280x? can be found on devices with physical screen sizes from 4.3" to 10.2".
Of course for many apps, if written properly, this simply doesn't matter - but if you try cram too much on-screen assuming 1280x800 means a 7" device your app may be difficult to use on 4" one.
Most of the people you see complaining about Android fragmentation are people that are avoiding Android because they are scared of it (rather than having tried to deal with it) or people who would prefer you to buy an iOS device that their app is already available for instead of an Android one that drops you out of their target market until such time as they port to Android.
- sjmulder 13y agoLike you say, for a well built app the pixel density does not matter because you design in dp. > if you try cram too much on-screen assuming 1280x800 means a 7" device your app may be difficult to use on 4" one. For the reason above, this just doesn’t follow. A 7" device would be about 600dp wide (in portrait), while a 4" phone would be about 320dp, regardless of pixel density. That’s not too different from iOS – the original iPad and the iPhone 5 have a similar number of pixels.