- Next.js + Typescript
- Framer Motion
I'm a big fan of the Framer-motion animation library since I started playing with it a couple of months ago.
It comes in handy when I have to deal with high effect interaction designs.
I decided to dig a little deep more by using it for a simple drag and drop puzzle in a side-project.
I stumbled upon this Dribble design from Dwi Ash, and decided to implement it.
Here is how it looks like:
First, I chose a pixelated and personified version of an apple, as the main puzzle picture.
This choice was made as a visual representation of the company I'm working with called Pommeclic (appleclic in French).
It's more complex than the original dog design, and I had to subdivide it into smaller grid cells.
Then I had to break the character into multiple pieces and add a grid system and pieces IDs to translate the whole thing as React components.
I have done that using Figma.
I decided to go with full css implementation using a data objects to compute both empty slot zones and floating pieces around.
Slots are rows of squared units, each containing utility classes that I defined using Tailwind and based on css variables.
Pieces are grouped squared units, using the same system of utility classes, this is mandatory to be able to render proper bevel effect with light and shadow bevels at the right place.
Then, render the markup is only a matter of looping over these datas into the JSX part.
The index page contains of course lot of additional logic that I can't explain in detail (to keep this article concise), but the whole architecture is based on this showcased CodeSandbox from Matt Perry.
This CodeSandbox is a simple demo of a Framer Motion shared layout used within a drag and drop feature between 2 zones.
My project is much more complex as I have to handle multiple start and end zones (pieces and slots).
Framer Motion has a built-in drag and drop feature that can be easily implemented on any HTML tags (set as motion.div), using specific attributes and methods (drag, onDrag, onDragStart, onDragEnd, dragElastic, dragTransition..).
I think Framer Motion shines when dealing with shared layouts. It means we can use two different components, but keep only one displayed and animate it smoothly between one and another.
This what is done between a dragged piece and a positioned piece : both are defined at their final positions in their own containers.
I used multiple third party packages that I found useful along the way:
- div100vh: as it's a responsive and centered design, this help to deal with real viewport size on mobile
- Lottie React Player: to implement Lottie Json animations (the firework at puzzle completion)
- clsx: my go-to package to help dealing with complex conditional classes
- usehooks-ts: A very convenient collection of utility hooks written in Typescript
Completing the puzzle display a reward message, and a reset button.
I added a helper on the top-left corner of the screen to trigger the completion, that is useful during the development phase.
Here is how the final stage looks like:
I intend to dig more on this lib as I barely scratched the surface of what is achievable.
I personally didn't use Framer so far but maybe should I?
Don't hesitate to tell me if you identify code smells within the prototype, as I started using React since a bit less than a year and Typescript for a couple of months.