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

Responesive Tip calculator

preact, tailwind-css
Marvellous Obatale•520
@MARVELGARR
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


While making a tip calculator using React, I learned a lot about state management, props drilling, and conditional rendering in React and Tailwind CSS.

One of the most important things I learned was the need for state management in React. Since the tip calculator required dynamic updates based on user input, I had to use React state to manage the data and ensure that the UI was updated in real-time. By using state, I was able to ensure that the calculator remained accurate and that users always had the most up-to-date information.

I also found that props drilling was an important concept to understand. While building the calculator, I had to pass data down from the parent component to its child components. This required me to use props and drill down into the component hierarchy to ensure that each child component had access to the necessary data.

Finally, I found that conditional rendering was an essential aspect of building the calculator's UI. By using conditional rendering, I was able to show or hide certain components based on the user's input. I also used Tailwind CSS to style the calculator and found that the library made it easy to create responsive and visually appealing UI components.

Overall, building the tip calculator in React was a great learning experience. It taught me a lot about state management, props drilling, and conditional rendering in React and showed me how powerful the library can be for building dynamic and responsive UIs.

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 Marvellous Obatale'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.