Paintcode sketch plugin
![paintcode sketch plugin paintcode sketch plugin](https://developerlife.com/assets/airbnb-4.png)
I feel that at this point the real ‘known’ in iOS design handoff is that there’s no ‘right’ way. We’ve reduced the number of graphics used and overall application size, while dramatically smoothing out the workflow between design and development. While far from perfect, at this moment in time I really love working this way, and our developers do too. Swift sample: class PaintCodeButton: UIButton let myButton = PaintCodeButton() ame = CGRect(x: 0, y: 0, width: 100, height: 50) It’s great. Developers can instantiate PaintCode objects as subclasses of standard iOS objects, and then set their frames just like they would for any UIButton, UILabel, etc., depending on the available screen size. PaintCode allows for objects to be instantiated with dynamic sizes, so you can easily scale them to fit all of the screen sizes your apps support. Re-exporting when changes occur is simple. When it comes to handoff, we link the Swift file PaintCode outputs from Dropbox to Xcode. Begin setting up each graphic on its own canvas-More here:.Recolor with proper colors stored in PaintCode.Copy graphics into your master PaintCode file.
![paintcode sketch plugin paintcode sketch plugin](https://i.ytimg.com/vi/DYhPufgcqF4/maxresdefault.jpg)
Strip out any colors that came over or were replaced by PaintCode.
![paintcode sketch plugin paintcode sketch plugin](https://developerlife.com/assets/airbnb-1.png)
Remember that artboard with all of our custom drawn graphics on it? I’ve heard that this can cause performance issues but I’d love to see that better substantiated. Colors in PaintCode can be used in other parts of the app beyond your graphics allowing you to alter every instance at once.Īssets-We use PaintCode for every graphic we create: no bitmaps are used within our interface. This is valuable if you’re creating the product from scratch and experimenting with brand/colors/graphics during build. To change our blue color to red everywhere in the app takes one step when using PaintCode. In the case of FaceParty we use blue very prominently. We keep all of our brand colors in PaintCode and dynamically color all of our elements depending on our interaction rules. This has helped our developers and I quickly create consistent experiences that match our styleguide and UI without wasted time on questions about color, state, etc. What goes into PaintCode and what doesn’t? Application Colors-PaintCode’s best feature is probably the organization / naming of colors in your interaction model. Thanks to the symbol reuse, we reduce the complexity of our design assets dramatically and get the right look every time. to create passive/active states of your buttons, up/down states, dynamic text, animation from variables, and more. With PaintCode you can use expressions, variables, etc. Not familiar with PaintCode? PaintCode uses your SVG paths and color data to generate Swift or ObjC classes. While it has some pitfalls, it’s a powerful tool that saves us a lot of time and communication.