Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialLaura Ross
Courses Plus Student 2,449 PointsiOS Android Conversion
I'm not sure I get this. It sounds like, if you're designing for retina, you should actually make sure to keep your artwork at divisibles of 8 so that you can convert to android.
- MDPI (non-retina) - 4px
- XHDPI (retina) - 8px
- HDPI - 6px
- LDPI - 3px
Is that correct?
1 Answer
Mohammad Laif
Courses Plus Student 22,297 PointsFrom my experiences, dealing with screen resolutions in Android is pain, making XHDPI, HDPI, MDPI and LDPI and trying to perfect the app on all densities available in each Android devices are very painful.
Here are a list from Material Design for most standard devices by screen sizes and density.
Best thing to do while designing to Android App UI is to go with the lower screen you want to support, then fitting it to the larger screen devices. Also the original material (artworks) need to be larger in size like XHDPI then minimize it to lower scale. Otherwise it will be nightmare when opening the app on small screen devices.
For example, it was my first mistake, when I designed my app to Nexus 6p (density 3.5 xxxhdpi, in px 1440 x 2560, 411 x 731 in dp, 16:9 ap, 5.7 in screen size.), and then try it on lower device screens it was nightmare in all means.