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

Age Calculator App

SatishB15•160
@SatishB15
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?

Proud of:

  1. User Interface Design: I'm particularly proud of the clean and intuitive user interface that makes the Age Calculator easy to use for people of all ages.

  2. Accuracy and Performance: Ensuring that the calculations are precise and the application performs efficiently was a key achievement. The app handles various date formats and edge cases accurately.

  3. Code Quality: Maintaining high code quality with clear documentation and well-structured code has been a significant accomplishment.

Do Differently Next Time:

  1. Enhanced Features: Next time, I would implement additional features such as calculating age in different time units (e.g., weeks, days, hours) and adding a feature to save and compare multiple dates.

  2. User Feedback Integration: I would set up a more structured process for gathering and integrating user feedback earlier in the development cycle to better align the project with user needs.

  3. Automated Testing: Incorporating automated testing from the beginning would help in catching bugs early and ensuring the reliability of the application.

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

Challenges:

  1. Date Handling: One of the main challenges was handling various date formats and ensuring the application could accurately compute ages regardless of the input format.

  2. Cross-Browser Compatibility: Ensuring the application worked seamlessly across different web browsers required significant testing and adjustments.

Overcoming Challenges:

  1. Date Handling: To overcome this, I researched and implemented robust date-parsing libraries that could handle multiple formats and edge cases effectively.

  2. Cross-Browser Compatibility: I utilized extensive testing on multiple browsers and used polyfills to ensure compatibility with older browser versions, ensuring a consistent user experience.

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

Areas for Help:

  1. User Experience (UX) Design: I would appreciate feedback and suggestions from UX designers to improve the overall user experience, making the interface even more user-friendly and accessible.

  2. Localization: Assistance with localizing the application for different languages and regions would be valuable to make the Age Calculator accessible to a global audience.

  3. Advanced Features: Help with implementing advanced features like saving date comparisons, integrating with calendar APIs, or adding more complex calculations (e.g., accounting for leap years more elegantly) would be beneficial.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhammad Gad•280
    @GADMuhammad
    Posted about 1 year ago
    1. The age does not appear when clicking the button or pressing Enter.

    2. There is no need to change the cursor to a pointer when hovering over the input field; keep the default cursor.

    3. Limit the input values based on their type. For example, in the input for days, do not allow the user to enter a number larger than 31, as no month has more than 31 days, and so on.

    4. Prioritize accessibility. It is crucial, and most of the time, users find it more comfortable to use the keyboard instead of the mouse.

    I have already completed this project. You can review it if needed. I believe it will be very useful for providing you with some programming logic.

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