A workshop that will get you started with making animations in React applications.
For Booster Conference 2020.
Welcome! In this workshop you'll get to play with a relatively new framework for making animations in React: Framer Motion! V1 of Framer Motion was released in June last year and is the successor to Pose, for those who are familiar with that. Read this article for a brief intro to Framer Motion.
The official documentation for the Framer Motion API can be found here, where you'll find simple examples of the most basic functions and possibilities that the API provides, among other things.
Tip: Scroll down to the "More" section, located under "Examples" in the documentation, and you'll find links to working code examples in CodeSandbox!
Done reading the introductory article? Then you are ready to move on to the exercises!
You will see some emojis in the exercise descriptions. They mean the following:
🏆Task: This is what you are supposed to do
💡Tip: Some extra info that might be good to know for solving the relevant exercise.
🚨Solution: Click me! 😊
Here is a full proposal of how you may solve the exercise.
-
Clone the repository:
git clone git@github.com:bekk/react-animation-workshop.git -
Navigate to the repository folder and run
npm install -
Run
npm run startand the app will run onlocalhost:1234in your browser.
We've made a simple card game that will be the starting point for everything you'll do in this workshop. The cardgame is called war ("Krig" in Norwegian). Just ask any of us if you don't know or remember the rules, but it doesn't really matter, because we've implemented all the game mechanics for you. What you should focus on is the possible animations that may suit such a game.
💡There is a lot of game logic implemented here and there in the app, and although we have tried to hide as much as we possible, you'll still have to deal with files and components that contain some logic. However, we will try to guide you to the right places in the app where the tasks is supposed to be solved.
💡Sometimes it may be difficult to know where to begin in order to solve an exercise - a quick look at the solution proposal may be wise (and allowed) in this case.
💡You are allowed to continue to play with the API, even after you've done exactly what the exercise asks you to do. In fact, we encourage it! You'll probably learn a lot just trying out different things on your own.
After doing this exercise you should be able to pull a card from one of the card stacks to the area that says Drag the card here.
Let's break it down:
🏆We start with the first step: Make it possible to click on a card and drag it around (without any rules of where it should land).
💡Navigate to components/Card/Card.jsx and change the component such that it returns a <motion.div /> instead of a regular <div>
🚨Solution
<motion.div
...
drag
>
🏆Add some constraints such that the card doesn't just float away. Don't think about getting it to the right position yet, we'll come back to that later.
💡<motion.div> has the relevant props: dragConstraints, dragElastic and onDragEnd.
As mentioned, we've made the game logic so that you may focus on making the animations. Therefore, just add the following:
onDragEnd={(event) => {
if (intersectsPlayArea(event)) {
dispatch({ type: Action.PLAY });
}
}}This will change the state of the game and flip the card when it is dragged and dropped within the shaded area.
🚨Solution
The trick to make this work is to set the constraints to 0 in all directions. Framer's `drag` has an elasticity that can be controlled with the `dragElastic` props, which allows the card to be pulled to the correct position even if it is not allowed to "land" anywhere other than where it started. <motion.div
...
dragElastic={1}
dragConstraints={{
top: 0,
right: 0,
bottom: 0,
left: 0
}}
onDragEnd={(event) => {
if (intersectsPlayArea(event)) {
dispatch({ type: Action.PLAY });
}
}}
>
🏆Dragging should only be allowed if the card is flipped down. Make it so.
💡You can implement conditional drag like this: drag={true}
💡The Card-component has a state: CardState
🚨Solution
<motion.div
...
drag={state === CardState.CLOSED}
...
>
Let's continue animating!
The animate prop takes an object with values that tell the motion component how to animate itself. Whenever any of these values change, the motion component will smoothly animate itself accordingly. Check out the official docs for a complete overview of what animate can do. Examples of fields you can specify in the animate object are rotation and scale. For now you should probably focus on two fields you can use to position the component: x and y.
🏆Make the cards move to the right position when they're dragged to the "drag card here"-area.
💡The Card component has a state variable, position, that updates for certain events in the course of the game. Use this to update the motion component.
🚨Solution
All the game logic has already been implemented, which makes this exercise pretty straightforward. Simply assign the `position` variable to the motion components' `animate` prop. Here we've also assigned a rotation to the `animate` object for added realism, but this is optional. <motion.div
...
animate={{
rotate: rotation,
...position
}}
>
<motion.div className={classNames('Card', isOpen ? 'open' : 'closed', suit)}>
{isOpen && <CardFace value={value} />}
</motion.div>
</motion.div>Every game needs a menu screen, and since this workshop is all about animations our menu is of course going to be an animated menu. We have prepared a simple menu component you can use which you'll find in /components/Menu/Menu.jsx. Before you start you need to add it to the app by rendering it at the top of the App component:
<div className="App">
<div className="MenuContainer">
<Menu />
</div>
<div className="Table">
.
.
.As you can see the menu is quite static at the moment, but we'll fix this in a moment.
🏆Add a simple animation when the user clicks or hovers over the menu button. You should look in Menu.jsx for this exercise.
💡You'll find a list of available props to pass to the motion component here: https://www.framer.com/api/motion/component/. Take a closer look at whileHover and whileTap
🚨Solution
Easy enough: Convert the button elements to motion.button and pass the whileHover and whileTap props.
const MenuButton = ({
onClick,
clicked
}) => {
return (
<motion.button
...
whileHover={{scale: 1.1}}
whileTap={{scale: 1.2}}
>
<div className="bar1"></div>
<div className="bar2"></div>
<div className="bar3"></div>
</motion.button>
)
}🏆Repeat exercise 3a) but for each menu element as well
🚨Solution
<motion.li whileHover={{ scale: 1.5, translateX: 50 }} key={x.id}>
<a href={x.url}>{x.name}</a>
</motion.li>🏆Define visual state with the variants prop to show/hide the menu when the menu icon is clicked.
💡Variants define visual state for an element and its descendants, and is a powerful tool for orchestrating animations in a declarative way. You can read more about variants here.
💡Take a look at the Menu and MenuArea components.
🚨Solution
First we need to change the nav to a motion.nav and assign it a state/variant label of either open or closed depending on whether the menu button has been clicked or not.
Any variants we assign to a child motion component that define animations for these two states will then animate itself based on which state is currently active.
export const Menu = () => {
const [isOpen, setIsOpen] = useState(false);
return (
<motion.nav className="Menu" initial="closed" animate={isOpen ? "open" : "closed"}>
<MenuArea />
<MenuButton onClick={setIsOpen} clicked={isOpen}/>
</motion.nav>
)
}MenuArea is the component we want to be able to show and hide, and we're able to do that if we make it render a motion.div instead of a regular div and at the same time assign it a variants prop which is an object defining animation for the states open and closed.
const MenuArea = () => {
const variants_menuArea = {
open: {
opacity: 1,
x: 0,
},
closed: {
opacity: 0,
x: -200,
}
};
return (
<motion.div className="MenuArea" variants={variants_menuArea}>
<MenuNavigation/>
</motion.div>
)
}In our solution we make the menu fly in from the side, but there's nothing stopping you from experimenting with different styles of transition.
💡Show/hide the menu
We can use the css-property `clip-path` to get a cool effect for our state transitions. Try this out:
const variants_menuArea = {
open: {
clipPath: `circle(500px at 40px 40px)`,
transition: {
type: "spring",
stiffness: 50,
}
},
closed: {
clipPath: "circle(30px at 40px 40px)",
transition: {
type: "spring",
stiffness: 50,
}
}
};We'll animate the menu contents next.
🏆Make the list containing the menu items fly in from the top whenever the menu opens/closes.
💡Variants is a good way to achieve this effect. Add a short delay when the card is closed so that the contents are able to finish their animations before the menu disappears.
💡Look into MenuNavigation
🚨Solution
Create a variants object, variants_menuList, in MenuNavigation:
const variants_navItems = {
open: {
opacity: 1,
y: 0
},
closed: {
opacity: 0,
y: -50
}
}Assign it to the list items:
<motion.li variants={variants_navItems} key={x.id}>
<a href={x.url}>{x.name}</a>
</motion.li>To add a delay add the following to the closed variant:
transition: {
delay: 0.5
}Variants let us animate entire sub-trees by simply changing a few properties of a parent component. staggerChildren is a prop that allows us to stagger or delay the animations of every child component and make them execute in sequence.
This sounds like a great fit for our menu!
🏆Use staggerChildren to make each menu item fly in in sequence.
💡The variants example in the Framer documentation has a menu that coincidentally looks a little bit like our, where they make use of staggerChildren...
🚨Solution
Our open and closed variants each need transition objects that define staggerChildren. The open variant should also define a delayChildren transition so that the menu items don't fly in before the card has appeared fully.
TODO (fra Bendik): Kan også sette staggerChildren rett på variants_menuArea, da fungerer det og man slipper å måtte legge til variants på motion.ul-elementet (siden det propageres nedvover til barnekomponenter). Vurdere å endre lf'et.
const variants_navList = {
open: {
transition: { staggerChildren: 0.1, delayChildren: 0.2 }
},
closed: {
transition: { staggerChildren: 0.05}
}
};And add it to the motion.ul element:
<motion.ul className="MenuNavigation" variants={variants_navList}>In the last exercise you'll need to add some animation to a feature that displays the scores of the players. This will be an open exercise since it can be done in multiple ways, but first: Render the <Score> component in <App> (right after the menu, for instance).
<div className="MenuContainer">
<Menu />
</div>
<div className="ScoreContainer">
<Score playerScore={state.score.player} computerScore={state.score.computer}/>
</div>🏆Use what you've learned so far (or learn and make use of something completely new!) and add an animation to the scores every time they are updated.
💡A couple of relatively simple suggestions:
- Add rotation
- Scale the numbers according to the difference of the score values
Then we have a couple of suggestions for what you can do now:
🏆Make it possible to rearrange the elements in the menu with drag and drop
💡Take a look at an example in the Framer documentation that does the same
🏆Convert the elements in the menu to "Accordions" with some random content
💡Accordion example in the docs
🏆Display a modal when clicking on "Rules" in the menu that contains a long and scrollable text