Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Remix and Framer Motion

motion, remix, typescript, zustand, react
P
eestaniel•630
@eestaniel
A solution to the Product list with cart challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Navigating Framer Motion for the first time was quite an experience. It was challenging but definitely rewarding to see the animations take shape. There’s still much to learn about customizing animations to enhance the app's functionality

What challenges did you encounter, and how did you overcome them?

Next time, I'd delve deeper into making the images and flexbox layouts more responsive. This project showed me there's room for improvement in handling fluid transitions and layout changes. I did the best I could with the current knowledge, but there's definitely a need for a more structured approach to responsiveness right from the start.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted 12 months ago

    Hey, nice code I'm a react guy but im experimenting with Vue for the time being. One thing I realized about your solution is that it might not be too accessible, what I mean is that from a keyboard POV only the confirm order button is focusable by tabbing other than that, nothing else. I had the same issue on my end and I realized I had a bad habbit of making every functional element a div instead of a button, when I used buttons all of my clickable/functional elements are now focusable through my keyboard. So i guess that could be a thing you could look at if you wanna.

    Also I think it would be nice/cool if we could compare our codes and our component compositions along with our state management solutions, but let me know what you think.

    Marked as helpful
  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted 12 months ago

    Also it would be great if you could check out my multi-step form solution, I used framer motion there, but not alot, just for like sliding between steps of the form.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub