June 14, 2016 at 4:01 pm #5637
Importing Sketch files is a great way to move entire projects into UXPin, but if you just need a few items, then export artboards or individual bits as SVGs. This has several advantages:
- Fewer layers make for better performance and easier asset management.
- Imported SVGs are vector, and therefore scalable.
- SVGs are great for making quick visual updates in Sketch for your interactive UXPin prototypes.
- When you replace an image by dragging a new file onto it, UXPin preserves its interactions.
- You can easily update graphics in smart elements for site-wide changes.
Having said that, exporting and importing individual SVGs can get tedious with large projects, which is why UXPin lets you import whole Sketch docs in one go. Which is best? Depends on your workflow. When designing in UXPin itself, then consider keeping your work modular with SVG imports.
September 9, 2016 at 4:35 pm #6326
September 12, 2016 at 2:28 pm #6344
November 30, 2016 at 9:49 pm #8544
One workaround (that’s far from ideal) is to create an icon font using something like fontastic.me and then upload it to uxpin as a custom font. This will allow you to easily change colors for the icons. The main drawback is you need to know the mappings between the letters and the icons (I had to print out a cheatsheet) – also, special characters are also pretty difficult to work with in this case.
Having editable SVG’s (like how Sketch does it) would be ideal.
October 5, 2016 at 9:10 pm #6477
Being able to then export out of UXPin with the layers and .svg files in tact I think would go a long way
You must be logged in to reply to this topic. Click here to login or register