I learned that I have no idea what I'm doing.

Feel free to ask any questions about the article.

I love the attention to detail, Marc. Thanks for sharing.

I'm of course terribly biased, but reading your article and comments really makes me think that PNG Express would be a perfect addition to your workflow. I understand you're not likely to adjust your workflow now, but for others reading your article and liking the ideas but thinking exporting sounds cumbersome, I'd just like to add that a tool like PNG Express could help.

Here's a few examples of how I think PNG Express would improve the process:

• Exports from both a "slice sheet" or from design mockups with full repeatability.
• No need to manually set up slices.. unless you want to.
• Auto slices also have visible export boundaries which you can easily edit.
• Flexible! It's no problem to move assets around or resize slices. Much easier than native slices.
• Multiple states of an asset can be exported from the same slice ensuring consistent dimensions. It also makes design changes super fast because you have fewer layers to edit.
• Assets can be exported to different sub folders and @2x can be added directly.

That is a very detailed and powerful process, thanks so much for sharing.

Fantastic article as always, Marc. Really great tips, especially the suggestion to use gradients for edge effects.

I always love seeing your process, though I second the comment about Slicy, which does a bunch of the 1x/2x work automatically. I would love to find a shortcut way to scale layer effects from 1px to 2px and vice versa. That's usually the most annoying of the scaling changes.

I'm curious - why do you prefer groups to layer comps? I find the actions for quickly exporting layer comps to files for previewing flows extremely helpful.

This is an incredible article but I'm surprised at the amount of effort put into exporting and scaling when Slicy is around. It does most of this automatically with it's handy Group naming scheme and has sort-of Photoshop integration. It does have it's pitfalls but for the most part works extremely well.

I'd love to see how you structure your assets and code in you Xcode project too. Thanks for the great article Marc.

Great article and cool to read that we have almost the same workflow. :-)

This was definitely inspiring for me. I've been very stuck on doing @2x first and then creating slice sheets with both 1 and 2x assets. It takes way too long. Thank you for these great tips. I'm trying them out on my next project.

I'm curious how you handle those pieces that were not intended to be used more than twice in the app but did. Do you have a "GUI" slice sheet?

I use slice sheets too but I have separate PSDs for each control or set of controls. I work at 2x/XDPI for mobile and sometimes 2x for web pages but I find my 2 year old Air struggling. Skala's great I have to say. Makes testing the look and feel and checking sizes so much easier.

I have a friend who constructs slice sheets with smart objects which is then used in the mockups. I find it useless for things like stretchable assets which is like half of the assets usually.