Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

Tip calculator app using React & Tailwind

tailwind-css, vite, react
Specro•270
@Specro
A solution to the Tip 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?

Read a bit about useMemo and was able to overcome all NaN cases (I think) :)

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

At first I thought I could hold the tip percent state in the tip input component but the reset button made me lift it up. Also I kind of hate how the input with an icon in front requires that much HTML but it seems like all other solutions are pretty hacky.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Serhii Orlenko•415
    @grifano
    Posted 5 months ago

    Hi Specro,

    Congratulations on completing the Tip Calculator challenge! 🎉 I really like your approach to handling the “value not zero” validation—it’s super clean and efficient. I don’t know why I didn’t think of using a utility function for that myself!

    I also had to dig into useMemo recently, especially when I ran into warnings while using useEffect. After exploring it further, I realized it’s a great best practice to avoid unnecessary re-renders—so it’s awesome to see you using it here.

    Overall, you did a fantastic job! 👏 The only thing I noticed is that the Custom field seems to be missing characters in its placeholder. Fixing that would make it look more polished. I’d also suggest adding a red outline to the field when the error message (“Can’t be a zero”) appears. If you want to take it a step further, you could include a notification or toast for a better user experience.

    Great work! Keep up the amazing effort, and happy coding as you take on new challenges! 🚀

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub