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

Tip calculator

arunbabunt•270
@arunbungalowil
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?

I am most proud of how the tip calculator app provides a clean and user-friendly interface, making it easy for users to calculate tips quickly. The responsiveness of the design ensures that it looks good on various devices, from mobile phones to large desktop screens. Additionally, the implementation of custom tip functionality and the ability to handle errors like zero or invalid input for the number of people is something I am particularly satisfied with.

Next time, I would focus on improving the user experience by adding more interactive feedback. For instance, highlighting the selected tip percentage button and animating the calculation results could make the app more engaging. I would also consider refactoring the JavaScript code to be more modular and adding unit tests to ensure reliability.

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

One of the main challenges I encountered was ensuring that the error handling for the number of people input was intuitive and visually clear. Initially, the error message visibility and border color change were not triggering correctly. I overcame this by meticulously debugging the event listeners and ensuring that the validation function was called at the right times during input changes and button clicks.

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

I would like help with optimizing the JavaScript code, particularly in making it more modular and readable. Ensuring that the functions are well-organized and possibly separating the logic into different files or components could enhance maintainability.

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 arunbabunt'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

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.