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

Age Calculator App with React

react, vite
Veli Can Aydın•110
@VeliCanAydin
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Links

  • Solution URL: Frontend Mentor
  • Live Site URL: Netlify

My process

With this project, I had a beginner level knowledge of how to handle forms in React applications. I especially tried not to use a library (like formik or react-hook-form) because libraries slow down your learning curve and squeeze you into a narrow space. The new FormData(); structure I came across while trying to create this project is quite useful. Although I didn't use it in this project, it looks like I can use it in my future projects.

Built with

  • Semantic HTML5 markup
  • CSS custom properties
  • Flexbox
  • Mobile-first workflow
  • React - JS library
  • Vite - Frontend Tooling

What I learned

I learnt React's useEffect() hook to create the counter animation that appears on the screen after the age calculation. I also learnt in this project that all the properties of an object in an array like {...input} can be passed to a component as a prop.

Continued development

Even though I think I have successfully designed and coded this small application, I still don't know how to handle forms with React. I have already left the form validation features unfinished in the project and I will come back to it in the future when I learn more. I need to learn how to handle and validate forms with React better in the future and this is a really complex problem with no single answer.

Useful resources

  • Lama Dev React Forms Tutorial - It is a nice and clean explanation of how you can handle forms with React without using a library, but it is insufficient in complex scenarios. Still, it gave me a good perspective.
  • ChatGPT - I used an AI for the first time in this project and it's really incredible. It's like pair programming with a senior. I ask him questions at every point I have in mind and I can have him explain the parts I don't understand over and over again, and he handles simple tasks for me. AI is definitely something that increases productivity and we can't escape from it, mate.

Author

  • Frontend Mentor - @VeliCanAydin
  • LinkedIn - @Veli Can Aydın
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 Veli Can Aydın'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
Frontend Mentor logo

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.