↵

Ask DN: What's your workflow when handing off PSDs to an iOS Developer?

10 years ago from Alyssa Pelletier, Designer at Camp 4 Creative

  • Marc EdwardsMarc Edwards, 10 years ago (edited 10 years ago )

    I’m really against giving a PSDs to devs. I want to know how they want the images cut up, and I’ll work with them to implement whatever they need, with the file naming convention we agree on. To be honest, there really isn’t that many ways to do things, and it’s usually easy to predict the most efficient method.

    I realise that things could be different if you’re in a situation where client has requested PSDs. I usually provide annotation/specs for text as text files. I also assume that I’ll be the one doing QA on the implementation, so I’ll be able to let the dev know which elements need to be nudged and sized differently.

    Again, not everyone will have the ability to work like that.

    Here’s why I give devs PNGs, rather than PSDs:

    1. Being more involved with the dev process means less back and forth on way things are bolted together, saving time and giving better results. This is especially true with UI animation.

    2. I can ensure images are exported without colour profile issues. I never, ever want images exported from someone else’s computer that hasn’t been set up correctly. Having images exported from many computers is asking for colours to not match. More info on how I set things up: http://bjango.com/articles/photoshop/

    3. I want to ensure exporting is set up in a way that’s completely automated and reproducible. Software evolves over time, even before the first version is released, and you should be prepared for that. I use slice sheets and think they’re the best way to automate exporting.

    4. I want control over things like stretchable images, because as the designer, it’s more likely that I’ll know what’s important (like needing the repeating section to be 20px wide because there’s dithering or noise, vs it being 1px wide and looking ugly when stretched).

    5. And finally, it seems a little lazy to hand over a half finished job. (Again, clients may request PSDs, so you may not have a choice!)

    1 point
    • Alyssa Pelletier, 10 years ago

      Hey, thanks for this well thought out & detailed answer! I really appreciate it. I wasn't really talking about anything that needs to be sliced / exported – I will definitely be doing all of that, and luckily it's pretty "flat" so there isn't much to slice. (Guess I wasn't clear on that in my original post.)

      You mentioned that you make a text file for the text information... do you also do an annotation that shows spacing for everything?

      0 points
      • Marc EdwardsMarc Edwards, 10 years ago

        Hey, thanks for this well thought out & detailed answer! I really appreciate it.

        No probs. :)

        I wasn't really talking about anything that needs to be sliced / exported.

        Ah, ok!

        You mentioned that you make a text file for the text information... do you also do an annotation that shows spacing for everything?

        Typically not, only because it seems like a lot of work for not much benefit. I prefer talking to the dev as they’re building. If they have a question, I can measure the parts we’re talking about and tell them. I think it’s easier that way, because the implementation may mean that the measurements are taken from a place that isn’t initially obvious.

        Quite often we just slap the UI in roughly, then I’ll measure everything and provide a document with changes. They look like this: http://i.imgur.com/qlvA9.png

        That means the developer can worry about the code without getting hung up on the UI being pixel perfect.

        I do provide specs for text though (usually made before the dev starts work on that section of the app).

        1 point
    • Jonathan YapJonathan Yap, 10 years ago

      I second the approach of communicating with your devs, especially when there are situations when you are developing for iOS and Android at the same time. Catching up in sprints are more helpful than a 1 off hand off because there are cases where you would overlook some technical feasibility during implementation.

      There are situation when you need to provide documentation, but I would still keep an open communication and provide them actual PNG assets + design mockups. There are too many accounts of Dev cocking up the designs with hand off.

      One more advantage of PNG is you can work on Sketch too :)

      1 point