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

Responsive Calculator App

FabFalch•130
@FabFalch
A solution to the Calculator app 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?

I'm proud to have finally completed this project! I encountered quite a few challenges along the way, and although it took longer than expected, I’m really happy with the result.

If I were to build this again, I would have liked access to the Figma file to ensure precise measurements and alignments.

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

I faced quite a few challenges throughout this project! One of the biggest was figuring out how to handle the theme switching. It took some planning, but I decided to create three separate CSS files for each theme. In JavaScript, I set up an object with the themes as keys and added an event listener to the toggle slider, allowing it to loop through them smoothly.

The JavaScript for the calculator itself was also a challenge. I spent time researching how others approached similar projects, which really helped me understand the logic behind it. As a beginner coder, this was a great learning experience, and I can confidently say that I could build it again from scratch if needed.

What specific areas of your project would you like help with?

Honestly, the HTML and CSS were pretty straightforward for me (though getting the buttons to flex properly did require a few pauses along the way!).

The biggest challenge was definitely the JavaScript—I would have loved more guidance on that. After planning my approach, actually bringing it to life took longer than expected. I often found myself stuck on syntax and the correct placement of code, which slowed me down. But in the end, working through those challenges helped me improve and understand JavaScript better.

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 FabFalch'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

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.