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

Age calculator app

SudodoSu•210
@SudodoSu
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Features Implemented

  • Accurate Age Calculation: The app provides precise age calculations in years, months, weeks, and days.
  • Age Difference Calculation: Users can also calculate the age difference between two dates.
  • Responsive Design: The app is built with a responsive layout, ensuring optimal user experience across devices.
  • Error Handling: Proper validation is in place to handle invalid inputs and provide meaningful error messages.
  • Clean and Intuitive UI: The user interface is designed to be clean, intuitive, and easy to navigate.

Technologies Used

  • HTML
  • CSS
  • JavaScript

Learning Experience

This challenge has been a great learning experience for me. It allowed me to further develop my frontend skills and practice working with form inputs, user interactions, and data calculations. I also gained experience in handling errors and providing clear feedback to users.

I thoroughly enjoyed working on this project, and I am proud of the end result. It was a valuable opportunity to apply my knowledge and improve my coding abilities.

Takeaways

  • Strengthened HTML, CSS, and JavaScript skills
  • Improved form handling and validation techniques
  • Enhanced understanding of responsive design principles
  • Developed error handling and feedback implementation

Feedback and suggestions for improvement are always welcome.

Thank you for taking the time to review my submission!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Duncan Ngugi•220
    @ngugimuchangi
    Posted about 2 years ago

    @SudodoSu Great solution. The age calculation is quite precise. You can improve on date validation when the year of birth is the same as the current year but the month or day is beyond the current date, i.e., the date is in the future. For instance:

    • 01 July 2023 should return an error, or
    • 05 June 2023 should also return an error.

    I hope this helps. Happy coding.

    Marked as helpful

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.

Oops! 😬

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

Log in with GitHub