I'm interested especially in the case in which you absolutely have to support older android versions. What is especially annoying is the fact that they constantly change their implementation and this creates files which are A) Bloated and huge and B) use duplicated layers for assets just to be able to support an older os version. Ex: Lolipop now has color overlay which is not present in Kitkat, but most apps have to support kitkat as well, so having an app that uses 100% the potential of Lolipop would need to make use of the app-compat library that does not know how to render color overlay on images/icons. And so you have to create 4 images per button just because of it.

Any pointers or ideas ? It's friggin annoying to have to bloat a huge file with more layers just because of backwards compatibility and it also destroys any hope of a nice workflow I had created for myself.

  • That's backwards compatibility in a nutshell. I find it hard to answer you question as to describe an entire workflow is outside the scope of one question. Maybe we can dial it down to your button example? Why do you need 4 images? – KMSTR Apr 29 '15 at 12:05
  • Because that's what Android needs. 1 image per state. 1 for normal, one for selected, one for pressed and one for disabled. Post-lolipop they were encouraging use of image/state. In lolipop they have built-in effects (ripple) that is drawn over graphics. In order to simulate that effect, the library forces a color paint over the regular image. But only for 1 state. So to have a "fake" look, you need all 4 images. Of course, you don't have the animation, but that's the limitation of the appcompat library. – lorddarq Apr 29 '15 at 12:10
  • So only for simulating that effect, really. That's a self set requirement though. – KMSTR Apr 29 '15 at 12:19
  • I can only suggest making assets with extra layers with the overlays, that way you can just batch export via visibility. – KMSTR Apr 29 '15 at 12:20
  • That's what I did. And I guess that's pretty much the only way I see how you could do it (by duplicating asset layers). And this is regardless of what software you're using btw: Sketch and Photoshop are following the same platform-imposed workflow. Would be nice if SVG was more reliable on both iOS and android. That would make sure for way less work for mobile ui designers. – lorddarq Apr 29 '15 at 12:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.