11–20 of 21 posts
If you use Sketch to draw your interface, you get @2x exporting and slicing is built in. It hurts my head to think about what I would have to do if I was using Photoshop.
This is a very good guide. The only part I found odd was the advice to design at 1x rather than 2x. My strategy, is design in 2x, but everything must have even dimensions. For the iPhone I just downsample the assets and don't even bother to check if they look good. For iPad, I will touchup 1x assets if needed.
I've found that the best reason to design at 1x is because the coordinates match the coordinates for the developer and also because sometimes the 2x size won't split nice and evenly if you don't keep it in mind. For instance 15px for a gutter.
It just seems impossible to take something with texture at 1x, and then scale it up. I often pick subtle textures for 2x, and then just drop or re-zoom the texture in the 1x version. How many people really have non-retina devices these days?
I use fieldtestapp.com to test my prototypes. Super easy to work with.
If you use Sketch to draw your interface, you get @2x exporting and slicing is built in. It hurts my head to think about what I would have to do if I was using Photoshop.
If you use PaintCode, you get CoreGraphics c code output. If you deliver your designs to a developer in CG code, their jaw will drop.
Earlier quoted context omitted.
I've found that the best reason to design at 1x is because the coordinates match the coordinates for the developer and also because sometimes the 2x size won't split nice and evenly if you don't keep it in mind. For instance 15px for a gutter.
That is what I actually meant by even dimensions. I meant divisible by 2, not balanced. It just seems impossible to take something with texture at 1x, and then scale it up. I often pick subtle textures for 2x, and then just drop or re-zoom the texture in the 1x version. How many people really have non-retina devices these days?
This is a distance vs. area mistake, right? I thought that a point is used as a one-dimensional (distance) unit, and is generally one or two physical pixels.
> A point can be represented by many pixels (normally one or four). This is a distance vs. area mistake, right? I thought that a point is used as a one-dimensional (distance) unit, and is generally one or two physical pixels.
If you use Sketch to draw your interface, you get @2x exporting and slicing is built in. It hurts my head to think about what I would have to do if I was using Photoshop.
If you use PaintCode, you get CoreGraphics c code output. If you deliver your designs to a developer in CG code, their jaw will drop.
Earlier quoted context omitted.
If you use PaintCode, you get CoreGraphics c code output. If you deliver your designs to a developer in CG code, their jaw will drop.
what's the point, exactly, to doing this (serious question)
* Scalability - you can resize a button and get the correct look
* Simplicity - you don't need to create 1x and 2x resources
Do you do this as a series of images in any order, or do you use some tool such as Invision, to build interactive prototypes?