Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Calculator App - React, Themes, CSS Flex/Grid Responsive Design

accessibility, react, vite
Lucca Rodrigues•430
@ChromeUniverse
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello again, FEM community! 😄

This is my solution to the Calculator App challenge - and boy, was this a fun one! I wrote about my thought process when tackling this challenge in a blog post too!

The hardest part by far was implementing the actual algorithm that powers the calculator - I really wanted to make this calculator's UX feel as close as possible to a native mobile app, so replicating the iPhone's classic calculator app was the natural benchmark I set for this challenge. It took quite some time to get the algorithm working 100% of the time, but it all worked out in the end! 😄 I went into more detail on how I achieved this on this in a recent blog post I made, so if you're stuck on this challenge and need a hand, I highly encourage you to read my article! 😉

The most tedious part though was implementing the three color themes - I had already learned from my previous attempts at theming and finally used React's Context provider. Once I had that setup, I added some conditional class styling, set up three boilerplate stylesheets for each theme, and copied over the colors from the style guide. A relatively straightforward and painless process, all things considered.

Lastly, I used CSS Grid and Flex quite a bit to achieve the correct layout. Making the layout responsive was as simple as making the keypad's buttons and the display width proportional to the viewport's width.

Any feedback would be greatly appreciated! 😉

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Lucca Rodrigues's solution.

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.