Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Advanced Animated Numbers with Light & Dark Mode Age Calculator

motion, react, tailwind-css, vite, animation
Abdul Rahman•60
@Abdul-Rahman-E
A solution to the Age 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?

What I'm Most Proud Of

I'm most proud of the advanced animated numbers feature and light & dark mode, which adds an engaging and dynamic aspect to the age calculator. It enhances the user experience and makes the tool more visually appealing.

What I Would Do Differently Next Time

Next time, I would focus on improving the accessibility of the age calculator. Making it fully accessible to people with disabilities would ensure usability for a wider audience.

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

Challenges and Solutions

Challenge: Implementing Animated Numbers

Implementing animated numbers required a thorough understanding of the animation process and synchronizing the animation with the age calculation.

Solution:

Overcame this challenge by integrating the setInterval function to create a simple animation. By synchronizing the animated numbers with the age calculation, I managed to achieve a seamless and visually captivating effect.

Challenge: Implementing a Seamless Switch between Light and Dark Modes

Implementing a seamless switch between light and dark modes without affecting the functionality of the age calculator.

Solution:

Overcame this challenge by using CSS variables and JavaScript to dynamically update the color scheme based on user preference. Ensured that the switch between modes was smooth and visually appealing, enhancing the overall user experience.

Challenge: Optimizing the Performance of the Age Calculator

Optimizing the performance of the age calculator, especially regarding the animation of numbers.

Solution:

Overcame this challenge by fine-tuning the animation sequences and minimizing unnecessary DOM manipulation. Additionally, implemented CSS hardware acceleration techniques to enhance the performance of the animated numbers. With the setInterval function, I ensured smoother and more efficient animations.

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

Next time, I would focus on improving the accessibility of the age calculator. Making it fully accessible to people with disabilities would ensure usability for a wider audience.

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 Abdul Rahman'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.