No plugins: The main plugin we’re missing is related to accessibility (Stark) but there are browser tools that accomplish the same thing. Plus Figma’s Zeplin integration should be enough for devs resistant to change. fig files but the iterative nature of product design does mean ‘final’ files are less important. No Sketch files: Clients like owning files. It does have a downloadable app that is essentially just a wrapper but might ease the transition. Useful client collaboration.įigma is in-browser: this takes some getting used to, but it’s just as fast, if not faster than Sketch once a file is loaded. I’m not talking design-over-your-shoulder feedback here, that’s horrible-it’s more about fostering useful conversation in the early stages of a project. The feedback loop is so much smaller, and it provides the client with a greater sense of ownership. you don’t need additional tools to prototypeĭuring ideation phases, we’ve had one team member making small changes while another team member presents to the client… live.there is no back and forth with commits etc, versioning just works in the background.there is no exporting, you just hop on a call and share a view-only link, the client’s cursor follows where you are on screen as you discuss and present.Prototyping (basic but powerful), commenting (basic but useful) and versioning is built-in. Present to the client using InVision Freehand or screen-share over Skype or appear.in.Create hotspots within Invision (or using Craft).Open untracked Abstract master Sketch file and sync using Craft.So you’ve completed a bit of design work and you need to present internally or to the client. Presenting design work: From Abstract to InVision
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |