We’re thinking about implementing this feature in the future.
However we would need your feedback so we can see whether we can implement it to properly satisfy your needs. Could you please comment the specific use case for layer comps in your workflow and how exactly are you using them?
Are you using layer comps only for showing and hiding of layers – effectively creating different states of the design?
Or are you also using them for changing styles and effects of specific layers?
Your input will help us figure out the best way to support layer comps if we are able to. If you have any example design which you could send us so we can understand how you use layer comps, please send it to firstname.lastname@example.org
76 votesj.olson commented
Yes. We need improved PNG export in Avocode and uploading bitmap assets would even be better if they could be upscaled (using Sketch vector info in background I assume.)
We cannot use SVG as it is not adequately supported in React Native for instance and has problems ...needs heavy de-linting, alll sorts of unwanted design app transforms get carried through etc. e.g. design looks great in Sketch, some piece of icon is upside down when exported from Avocode because the 180° transform used in Sketch to build said icon is buried in the code. Outputting SVG directly from Sketch yeilds better results.
We design in vector in Sketch @ 1x MDPI, upload to Avocode, design settings are MDPI. But icon exports to PNG are not satisfactory at all. They look really crusty. PNG export for say 4x (1440x2560) screens is not ready for primetime. ....major part of justification for Avocode is not there presently as design team has to side-export assets directly from Sketch to Github etc.
Furthermore to the original point of this thread we would like to build some layouts in Sketch using bitmaps if clean or upscaled export were possible. Simplifies number of layers in Avocode for engineering and the export would be foolproof as they wouldn’t drill inside the icon for instance.