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

Calculator app

AlexCristea2007•840
@AlexCristea2007
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 am most proud of the dedication and effort I put into this project. The final result reflects my attention to detail, creativity, and problem-solving skills. Successfully implementing features like the three-theme toggle, ensuring responsive design, and maintaining clean and organized code are accomplishments I value greatly. I also take pride in overcoming challenges, such as managing complex CSS and JavaScript interactions. However, if I were to approach this project again, I would do a few things differently. I would spend more time in the planning and design phase to streamline the development process and ensure everything is well-structured from the start. Additionally, I would focus on optimizing performance by reducing dependencies and improving accessibility with better keyboard navigation, ARIA roles, and screen reader compatibility. Enhancing testing practices, such as automated testing across browsers and devices, would also be a priority. Finally, I would aim to provide clearer and more comprehensive documentation to facilitate future collaboration and updates.

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

Throughout this project, I encountered several challenges that required creative problem-solving and persistence. One of the primary challenges was managing the complex interactions between the various front-end technologies, particularly the CSS and JavaScript components. Ensuring that the three-theme toggle worked seamlessly across all pages and that the design remained responsive on different screen sizes was initially difficult. I overcame this by thoroughly testing the design on multiple devices and tweaking the media queries and JavaScript functions until they worked harmoniously.

Another challenge was optimizing the code for performance. With various libraries and assets being used, the page load time was slower than I anticipated. To address this, I researched techniques like lazy loading images, minifying CSS and JavaScript files, and using efficient algorithms to streamline the overall performance.

Lastly, I faced some difficulties with accessibility, especially with implementing keyboard navigation and screen reader compatibility. I spent extra time learning about ARIA roles and testing the interface with screen readers to ensure that it was accessible to users with disabilities. This challenge not only improved the project but also expanded my understanding of web accessibility.

By remaining patient, researching solutions, and seeking feedback, I was able to tackle these obstacles and complete the project successfully.

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

Performance Optimization: While I've made improvements, I'm still not fully satisfied with the loading speed of the website, especially when dealing with images and large assets. I'm interested in further optimizing the site, particularly using techniques like code splitting, further reducing file sizes, and improving lazy loading for media content.

Cross-Browser Compatibility: Although I’ve done extensive testing on major browsers, I sometimes notice small discrepancies in how the design is rendered on less common browsers or versions. I would appreciate guidance on ensuring the design works uniformly across all platforms, especially older browsers.

Accessibility Improvements: While I've made strides in adding ARIA roles and improving keyboard navigation, I feel there's still room for improvement in terms of making the site fully accessible to users with disabilities. I would love to get some tips on best practices for achieving a higher level of web accessibility.

User Authentication System: I’ve been trying to implement a secure and efficient user authentication system, but I’ve encountered some hurdles in integrating OAuth 2.0 with my current stack. I would appreciate guidance on setting this up securely and efficiently.

These are the key areas where I feel some expert advice or additional help could make a significant difference in the quality and performance of my project.

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 AlexCristea2007'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.