KAPOW! Writing prototypes with Framer
I’ve finally used Framer on a client project and couldn’t be happier with the result. I normally use InVision and highly recommend it, but Framer is the obvious choice when we need the experience to feel significantly more real.
Every tool has its pros and cons, however, so it won’t always be the best choice for you.
The one other con is that their documentation is made more for developers than designers. So if you’re not used to digging into developer docs you will likely be overwhelmed and unsure what you’re looking for. Looking elsewhere won’t help you either, there doesn’t seem to be much community around this (yet).
Someone with less coding experience will find Framer difficult and more intimidating than it has to be. I’d recommend dealing with the learning curve by practicing on a few side projects before you put anything important on the line (not that side projects aren’t important).
Framer supports clicks and taps just the same, supports many animation options, is highly configurable, and runs very, very smoothly on all (of my) devices. I’ve tested it on iPhone, iPad, and a Mac. Because of this control and variability of use, your prototypes will feel much more real to the user in a testing scenario. This is especially good when your interactions help communicate state and position.
If you’ve used Framer before, let me know how you like it. There’s only so much time in the world to play with prototyping tools, but my next experiment will be with Origami.
While doing user testing sessions, you may want the testee to work on the actual device. To do so you can use Anvil to create a local web address using Pow. This will give you an address (something like
http://yourappname.youripaddress.xip.io/) that you may access on your device.