You Can Use Framer Whether You Code or Not
I admit, I was one of the skeptics. I pestered everyone I knew using Framer, asking, “But why? Why learn this strange Coffeescript framework when you can use real code?”
Earlier this year I went to a meet up and saw a Framer demonstration by @TheDaveCrow. Ever skeptical, I recognized that forward-thinking design teams were gearing up and using Framer. I quickly saw the utility of trying it for myself. To understand its full potential I bought a license and started making my own little prototypes. Besides, who am I to get behind on design tools? 😉
Normally there's an ad here. 🤔
I run this site by myself, so it would be awesome if you turned off your ad blocker.
But I already know how to code. Why do I need Framer?
This was the question I asked myself everyday as I tried to wrap my head around what Framer offered. I already enjoy coding my own sites, like uxtools.co, so I didn’t comprehend the need for another layer of abstraction between me and my project. I’ll attempt to answer this question by explaining what Framer is and what it isn’t.
Framer is for communication.
This isn’t only true of Framer, it’s true of all prototyping tools. Prototyping inherently lends itself to answering questions, validating ideas, and proving concepts. Instead of describing animations to a developer (or watching over their shoulder), Framer empowers the designer to add interactions and motion to their prototypes, and more accurately communicate the vision of their design.
Every time an idea changes hands, some amount of information is lost. The stakeholders can never get their exact idea into the head of the designer, nor the designer into the head of the developer. Framer allows the designer to take an idea one step further than state-based prototyping tools (like InVision and Marvel) before handing-off to a developer.
Framer is not for production.
And that’s a good thing! Framer isn’t an attempt to accelerate or bypass the development process. Where some designers may write HTML or CSS to facilitate accurate front-end development, Framer can be seen as more of a communication and validation tool. Set yourself free from the concerns of cross-browser, production-ready, accessible, scalable code. Embrace the excitement of a quick and dirty prototype.
Considering that Framer produces very messy code (a slew of divs with inline styles), very little of what is written in FramerJS will actually be used to create the real product. Some motion parameters may still be relevant (delay, easing, and timing) but very few lines of code will still translate to the development process.
Framer is not your only prototyping solution.
I originally began learning Framer thinking Sketch and Framer would be the final form of my workflow. I quickly realized I didn’t need a heavy-weight like Framer for all of my projects.
Don’t get me wrong — it’s a great tool. But choose the right tool for the right job. Just need simple slide-right animations from screen to screen? Use Adobe XD. Making micro-animations? Atomic.io will do the job. Framer becomes relevant with interaction-heavy, logic-based prototypes (For example: easing an animation as a drag event occurs). Choosing the right tool is a game of timing and investment.
Framer is like skipping HTML & CSS.
Framer prevents the need to recreate designs before prototyping. Framer Import skips the redundancy, and maintains the integrity of the design layers to facilitate quick prototyping. All of the artwork is preserved as it is brought into Framer, ready to be animated and manipulated.
Framing the Future
I’ll be the first to say that Framer Studio isn’t perfect. I get sad every time I use the “undo” function, only to watch my work skip back. One. Letter. At. A. Time. There are certain luxuries I’ve simply come to expect from a code editor that Framer doesn’t have, like Sublime’s ability to edit multiple lines simultaneously.
There are some nice features, however, like code folds and auto-code. These speed up the design workflow and help keep the workspace organized.
Many tools are leveraging drag-and-drop interfaces to mimic what would normally take complex code to produce. Framer is simplifying the code to lower the learning curve for creating complex prototypes. Neither approach is wrong, and both have their advantages.
TL;DR: Use Framer when it makes sense.