This is a read-only archive of the Framer Community on Facebook.

What is Framer? Join the Community
Return to index
Jules Cheung
Posted Jul 20 - Read on Facebook

Hi everyone, Framer noob here. Care to chime in on why you prefer Framer over other prototyping tools? Pros / Cons? Thanks!


George Kedenburg III

My advice: try as many tools as you can and stick with the one you like the most. No tool will magically make you a better designer! The only thing that matters is that you're able to convey your ideas quickly and easily.

Kevin Kwa

I like Framer for mobile prototyping. Especially so for concepts/animations which are more complex in nature. It's probably the most flexible tool out there since you can do (almost) anything in Javascript/Coffeescript.

Jordan Robert Dobson

I have had zero reasons to try other tools. Before this I used HTML / CSS / JS to build prototypes and Framer was much quicker and felt more flexible and easier to throw away.

It could explore ideas quicker. So find what does that for you.

Aditya Jain

Because Sketch+Framer 💯

Michael Lee

I tried almost all of them, for me I stuck with Framer because other tools I ran into the issue of it not being possible to create a specific interaction or animation I had in mind, but I never ran into that problem with Framer

Misha Scholte

I use Framer because other tools, like Principle and Flinto, make me feel handicapped. The learning curve is pretty steep though

Isa Bison

1. Can import assets from Photoshop and Sketch.
2. Provides a display hierarchy where elements can be changed independently of one another, and an API for creating, nesting, and modifying them without much hassle.
3. Elements dispatch events.
4. Provides a basic animation API. (Commands for making things animate in basic ways).
5. Allows you to ignore the procedural layout rules of a normal web document.
6. Uses a scripting language so I can make it do what I need it to.

Peter Gr

Gabe Pompilius

German Bauer

Other tools like Principle run out of steam more quickly when the interactions you need are not covered by the built-in things they can do, but the initial learning curve and time effort for simpler interactions might get you running faster on those. It really depends on what you need.
And the only way to get a feel for what you need is to try them out on a real world case of something you want to build as George pointed out. I personally use both because for small simple micro interactions there is no time/need to re-invent or go more custom.

Dave Crow

I just did an hour presentation on this a few weeks ago. Hopefully the video goes up soon. 😀

Javier Eduardo Treviño

make use of any tool you like, don't go with the mentality of sticking to just one, try instead to use the right tool for the job. I use Framer for native app protoypes but HTML/CSS/JS for web apps, sometimes for native apps I even design screens on Sketch and just import them to Marvel App to create the user flows, it takes me 10 min to do it and that does the job of conveying the idea.

Dezideriu Raita-Beeckman

Frame is Prototype

Dezideriu Raita-Beeckman

Is so far The Best on Market because what you code it's prototyping visual while you are busy coding

Read the entire post on Facebook