UI:What Ix:How UX:Why :: Think Product Design

Team lead asked me to write what InVision products do I use, how I use them, what are pros and cons. I wrote it today, and really think it will be helpful to share my thoughts with wider audience. So, below is the adaptation of what I provided to the engineering management in one fintech company.  I use InVision to share my hi-fi designs and specs, which I create in Sketch desktop application. This is my primary and every day usage of InVision, and about 90% of all usecases of all InVision products combined.  I sync designs via the plugin in Sketch made by Invision, called Craft .  When they are in InVision, we call those designs prototypes .  It works, but I often experience slowness. Sometimes sync process is failing, and I have to try it again. In Sketch I select one or more artboards, then initiate sync, which sends the artboard to InVision cloud. I have to be logged in Craft plugin with my InVision credentials. Almost every day, especially when I design intens...

Well, five. Because Sketch is not a prototyping tool. Prototyping solution will be Sketch + InVision. On the other hand InVision without Sketch doesn't hold much value, yet. It may be changed with the latest addition - InVision Studio . But let's stick for now with four tools: Sketch, Figma, Principle, and FramerX. The goal of this research is to identify strengths and weaknesses of the tools, and their suitability for the UX team. The main use is to create wireframes and later convert them into interactive prototype. I have chosen these tools because I used them before. The exception is FramerX, which is simply a brand new tool which I wanted to give a chance. No discrimination - there are bunch of other great tools on the market, they are just out of scope of this article. Criteria: Simple click through prototype.  Compatibility with Sketch.  Micro-interactions and animations.  Ease of use.  Collaboration – ability to share, to annotate on UI eleme...