There is a job posting I see every few weeks.
Looking for a Framer.js designer.
I know what they mean about a third of the time. The rest of the time the applicants and the company are describing completely different work to each other, and nobody notices until week two.
The phrase is broken because the product changed names three times and the internet never caught up.
Why the confusion exists
Framer started as Framer.js — an open-source JavaScript library for building interactive prototypes. You wrote code. It produced motion. Designers who could handle a bit of JavaScript loved it, and for a while it was the most respected prototyping tool in the industry.
Then it became Framer Classic, then Framer X, which moved to React components. Each version asked for less code than people assumed and more code than most designers wanted.
Around 2021 the company pivoted hard. Today Framer is a website builder. Visual canvas, CMS, hosting, publishing. You can drop in custom React code when you need it, but the majority of a Framer site today is built without writing any.
Meanwhile the animation library that came out of that history — Framer Motion — became the default way to animate React applications. It is a separate product with a separate purpose, and it is now widely known simply as Motion.
So "Framer JS" points at three different eras and at least three different skill sets. When you search for it, you inherit all of them.
The three jobs hiding in that phrase
1. You need a website
This is most people. You want a marketing site, a launch page, a product site with a blog behind it. Fast to ship, easy for your team to edit, good on mobile, decent on Google.
What you want is a Framer expert — someone fluent in the current builder. Layout systems, CMS structure, breakpoints, SEO basics, and enough code literacy to write a custom component when the canvas runs out of road.
What you do not want is a JavaScript engineer with no visual judgment. They will build it, and it will be structurally fine and commercially flat.
2. You need animation inside a React app
Your product is already built. It works. It feels stiff.
What you want is a React developer who is strong with Motion — someone who understands layout animations, shared element transitions, gesture handling, and how to keep all of it from dropping frames on a mid-range phone.
That is engineering work with a design sensibility attached. It has nothing to do with the Framer website builder, and hiring a Framer site specialist for it will waste both your time.
3. You need high-fidelity prototypes
You want to test an interaction before committing engineering to it. Realistic motion, real states, something a user can actually hold.
This is the closest thing to the original Framer.js job. In practice today it gets done in Framer, in code, or in whatever gets there fastest. What you are hiring for is prototyping judgment — knowing what fidelity is enough to answer the question — not a specific tool.
How to tell which one you need
Ask one question: what breaks if you do nothing?
If people land on your site and do not understand the product, that is job one. A website problem.
If people use your product and it feels cheap or unresponsive, that is job two. A Motion problem.
If your team keeps arguing about how a flow should work and cannot resolve it, that is job three. A prototyping problem.
They are rarely the same person, and the middle one is the most commonly misdiagnosed. Plenty of teams hire a website specialist hoping to fix a product that feels wrong. The site gets nicer. The product still feels wrong.
Write the brief in outcomes, not tools
The tool name is the least useful part of your posting. It is also the part most people lead with.
Name the outcome and the right people apply. Name the tool and you get whoever recognized the keyword.
Instead of "looking for a Framer.js designer", try:
"We need a five-page marketing site with a CMS for case studies, live in six weeks, that our marketer can edit without help."
Instead of "need Framer JS animation", try:
"Our React dashboard feels sluggish and static. We want transitions between views and better loading states, without hurting performance."
Both of those get you a shortlist of people who can actually do the thing. The first version gets you a shortlist of people who recognized a keyword.
What to screen for either way
Whichever job it turns out to be, the same three things separate a good hire from an expensive one.
Can they say no to a tool? Someone who tells you Framer handles every case has not pushed it far enough. The useful answer sounds like: this in Framer, this in a code component, this somewhere else entirely, and here is why.
Do they think about the reader or the user? Ask why the first screen is shaped the way it is in their best project. If the answer is about composition and trend, you are buying decoration. If it is about what someone needs to understand in the first ten seconds, keep talking.
Does their work survive real content? Beautiful layouts collapse the moment a headline runs long or a case study has nine bullet points instead of three. Ask to see something two years old that a client has been editing since.
The short version
Framer JS is a name from a product that no longer exists in that form. The three things people mean by it are a website, an animated React app, and a prototype.
Decide which one you need before you post the job. The right hire becomes obvious about ten minutes later.
FAQ
Is Framer.js still a thing?
Not as a product you would start a project with today. Its lineage runs into Framer the website builder and into Framer Motion, now called Motion, for React animation.
Is Framer Motion the same as Framer?
No. Motion is an animation library for React applications. Framer is a visual website builder. They share history and a name, nothing else operationally.
Can one person do both?
Some can, and I am one of them, but do not assume it. The overlap is smaller than the shared brand name suggests, and a specialist in the wrong half will be slower than an honest generalist.
Do I need a developer at all for a Framer site?
Often no. That is the point of the tool. You need one when the site starts behaving like a product — custom logic, unusual integrations, data that has to come from somewhere real.
If you are not sure which of the three you need, describe the problem and I'll tell you straight. If it turns out to be a website, read How to Hire a Framer Expert Without Paying for Pretty Screenshots and what it actually costs.
