How to prepare (what all sizes and resolutions) mockups and UI graphics for an Android app in PS
I've seen similar questions asked here but they did not answer my question 100%. So please bear with me.
Now I am starting an app design project for iOS and Android. I've been designing for iOS for some time now but Android is totally a new thing for me. Android has so many devices at so many different resolutions and sizes that it is actually quite confusing to me at this point as to where to begin.
Is it possible to create your elements for the highest resolution and then use some method to scale them down for other smaller sizes? Or do we HAVE to do it manually and create them for each of the different sizes? What are the best practises and ideal flow for any such multi-platform requirement. Is there a way to easily reuse the iOS graphic assets? TIA :)
I've been designing for iOS for some time now but Android is totally a new thing for me. Android has so many devices at so many different resolutions and sizes that it is actually quite confusing to me at this point as to where to begin.
If you have a good workflow for iOS, youâ€™ll be in good shape.
iOS has three main pixel density targets:
- 1Ã— (non-Retina).
- 2Ã— (Retina).
- 3Ã— (Retina HD, which is iPhone 6 Plus only right now).
Android is really similar:
- 1Ã— (not really used any more).
- 1.5Ã— (not really used any more).
- 2Ã— (xhdpi).
- 3Ã— (xxhdpi).
- 4Ã— (xxxhdpi, still reasonably rare, but on some high end devices).
So it's typically 1Ã—, 2Ã— and 3Ã— for iOS, and 2Ã—, 3Ã— and 4Ã— for Android. Very similar.
If you want to construct your documents in a way they'll scale up and down easily, you'll need to predominately use vector shapes and layer styles if you're using Photoshop. If you're using Illustratorâ€¦ well, you probably shouldn't use Illustrator. It's great for creating print design and SVGs for web, but has some issues that mean it can be less than ideal if you're expecting to get PNGs as production assets.
Is it possible to create your elements for the highest resolution and then use some method to scale them down for other smaller sizes?
You should avoid bitmap scaling at all costs. It looks horrible â€” please do not create xxxhdpi assets as PNGs, then bitmap scale them down. You should scale the document while everything is still separate layers and constructed using vector shapes and generated effects (like layer styles).
I really like working mostly at the 1Ã— scale. This means you have a lower resolution document, but everything scales up to 2Ã—, 3Ã— and 4Ã— perfectly. Or, you could work at 2Ã— and try to ensure everything lands on an even pixel grid etc. There's a few different approaches with pros and cons. If you've constructed your document well, you should actually be able to resize the document and jump between the display densities as needed.
Or do we HAVE to do it manually and create them for each of the different sizes?
You definitely need to have multiple sets of assets for the different display densities, but there are quite a few strategies to automate the process a lot.
Generator is one way to do it: https://blogs.adobe.com/photoshopdotcom/2013/09/introducing-adobe-generator-for-photoshop-cc.html
I use slices, and build documents with all the assets laid out in a grid, so I can batch export, scale the document and re-export. It's a bit harder, but it means I get finer control over the process.
What are the best practises and ideal flow for any such multi-platform requirement. Is there a way to easily reuse the iOS graphic assets?
You can definitely reuse certain assets, but you should probably assume you'll have to remake most of the app in a way that's native to the platform. If nothing else, to take advantage of platform features, like Android's 9-patch images:
Physical size and aspect ratio
iOS uses Auto Layout to help cater for different sized devices. This means you can build a mockup for the iPhone 6, but with a bit of work, you should be able to get the same design to work for all iPhone sizes using Auto Layout in Interface Builder.
Android has a similar(ish!) system in the form of XML declared layout.
This may not be something you'll actually build, but you should be aware that you'll need to cater for portions of the app to expand, contract, hide or be shown, based on the device size.